Re: Retiring the project

Do we have any statistics we can use for data on guiding this discussion? like download stats, etc? On Wed, Jun 8, 2022 at 8:35 AM Harbs wrote: > That document is for podlings — not for TLPs. > > There’s nothing wrong with a project being in maintenance mode as long as > there’s enough of a PMC

RE: Board report for June 2022 has been submitted

> ## Community Health: During the last quarter, there was no mailing list activity at dev and nearly no activity at users. I would add that questions about Flex have been posted to Royale mailing lists. From: Olaf Krüger Sent: Wednesday, June 8, 2022 8:16 AM To: dev@fl

RE: Retiring the project

For what it’s worth, I am aware of several Flex projects that are still in production. They are all considering transitioning, but have not yet made the decision, or have not finished the transition. I am not aware of new Flex projects being created. From: Csomák Gábor

RE: Board report for June 2022 has been submitted

>I would add that questions about Flex have been posted to Royale mailing lists. Ah thanks, I wasn't aware of this because I do not follow the Royale list. On 2022/06/09 05:35:58 Yishay Weiss wrote: > > > ## Community Health: > During the last quarter, there was no mailing list activity at dev a

Re: Retiring the project

Hi, > That document is for podlings — not for TLPs. Thanks for the hint, maybe this is the right resource, not sure: https://attic.apache.org/ I found this from the Apache PMC overview, see [1]: "In summary, the only reason for a project to move to the Attic is lack of oversight due to an ins

Re: Retiring the project

Hi Olaf, My daily development is about 50% Flex. I have large corporate client for whom I'm taking care of maintenance of his Flex/Air application and new features. There is open source Moonshine which is actively developed daily by me and growing Team. I personally would not want to pass to any o