Welcome. if you look at https://attic.apache.org/ you will see when a project should go to the attic.
"Projects whose PMC are unable to muster 3 votes for a release, who have no active committers or are unable to fulfill their reporting duties to the board are all good candidates for the Attic." The board is likely to intervine with these project should they not suggest moving to the attic. The board will see if revival is possible (clearly preferred) A project that does not/cannot make relevant security patches is also a likely candidate. Once a project is in the attic it is "readonly" and cannot be changed, however it can anytime be forked into a new project (theoretically it can leave the attic, should a renewed interest appear, however I do not think this have ever happened). I hope it answers your questions otherwise please ask. Language is not a barrier many of us are not native english speakers (I am danish but live in spain) rgds jan i Sent from my iPad > On 12 Sep 2017, at 07:16, Tong,Jianru <[email protected]> wrote: > > Dear, > Hi, I m from china, and I recently want to find the deatail reasons > about retired projects. > > But after I searched via google and apache portal, I still didn't get > more detail. > > For now, I just know one reason, ie lack of activity. What I want to > know is how to understand "inactivity", lack of document? Lack of > communication? Or lack of code contribution? > > would you pls help me to implement this task if you wanna, or any detail > material about retired project reason > > my English is poor, I ll appreciate much if you can offer me some help. > > many thx.
