Google charts for flutter backing

[Kevin Chadwick]

Hopefully I am not just wasting peoples time but thought that an attempt to bring some attention to this, might be useful?

"https://github.com/google/charts/pull/598#issuecomment-792395763"

"While I am personally passionate about data visualizations on many platforms,"

"I hope to get the project revitalized in the future, even hoping to find a team to take the torch, but that'll take some internal backing that I've yet to see so far."

[Suzuki Tomohiro]

(Thanks. I didn't know the library)

You may want to clarify call-to-action by getting people's attention. Do you want people to stay away from the library? Do you want people to appreciate the volunteers' contribution? (Or something else?)

--
You received this message because you are subscribed to the Google Groups "Flutter Development (flutter-dev)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to flutter-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/flutter-dev/CANNfpqc17Rx6nA6bsYvu4yV1%3Dh8ugt8LFpTH7Y82XaiYF_-KLA%40mail.gmail.com.

[Kevin Chadwick]

>> Hopefully I am not just wasting peoples time but thought that an attempt
>> to bring some attention to this, might be useful?
>>
>> "https://github.com/google/charts/pull/598#issuecomment-792395763"
>>
>> "While I am personally passionate about data visualizations on many
>> platforms,"
>>
>> "I hope to get the project revitalized in the future, even hoping to find
>> a team to take the torch, but that'll take some internal backing that I've
>> yet to see so far."

>> (Thanks. I didn't know the library)
>> You may want to clarify call-to-action by getting people's attention. Do
>> you want people to stay away from the library? Do you want people to
>> appreciate the volunteers' contribution? (Or something else?)
>>

Alternative libraries generally lack features like touch and desktop support.

There hasn't been much community contribution, so far. There is a commercial
fork under a broad expensive software license by sync fusion with a different API.

As stated in that link. This is a google internal project where syncs are
occasionally imported. The community could have easily avoided it breaking
(without pubspec,yam pins) upon the Flutter 2 release.

Ideally, I would like to see @cbbraun find the support for the project that he
desires from Google.

Otherwise it would be a case of maintenance forks and hoping the community
handles things like null safety migration well. Or to move on. I don't wish to
push for it to be dropped but that *may* be better than limbo, if said limbo
ends with it being dropped in any case. Perhaps a support decision issue that
states that it is still unlikely to get support for the next 6 months, every 6
months, would help the community?