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 insufficient number of active PMC members. Note that going to the Attic is not necessarily a bad thing: it's merely a reflection that there isn't currently an active community to manage the project. It's also a clear way to set the right expectations for users of the project's code." However, it looks like the project is still more relevant than it seems and as Harbs said, if we are still enough PMCs, we could leave everything as it is. So, can we really guarantee to have at least 3 active PMC members? Please reply if you're still commited to be an active Flex PMC member! I didn't write any Flex/AS3 code for more than 2 or 3 years so please do not rely on me for another couple of years ;-) As long as we're still enough PMCs I think everything is fine. We should add a note to the board report that the project is silent but enough PMCs take care of if. Thanks, Olaf [1] https://www.apache.org/dev/pmc.html#move-to-attic On 2022/06/08 06:35:10 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 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, Olaf Krüger <okrue...@apache.org> wrote: > > > > Hi guys, > > > > we should thinking about retiring the project. > > This seems to be the guideline to retire a project at Apache [1] > > > > It looks like we need a community vote and some volunteers who helps with > > the process of retiring a project. > > > > What do you think? > > > > Thanks, > > Olaf > > > > [1] https://incubator.apache.org/guides/retirement.html > > > >
