> Sent: Thursday, June 9, 2022 02:19
> To: dev@flex.apache.org
> Subject: [URL Verdict: Neutral][Non-DoD Source] 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:
>
: Thursday, June 9, 2022 02:19
To: dev@flex.apache.org
Subject: [URL Verdict: Neutral][Non-DoD Source] 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
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
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
com>
Sent: Wednesday, June 8, 2022 1:44 PM
To: dev@flex.apache.org<mailto:dev@flex.apache.org>
Subject: 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
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
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 active.
I think we still have enough of a PMC to maintain the project and I think
people are still using Flex.
Harbs
> On Jun 8, 2022, at 8:26 AM, Ol
