Bluesky Team,
We need to make plans to take this project to graduation. To graduate, the project must have code to release and have a sustainable community. Right now, we don't have code, we don't have a community and we don't have a plan for acquiring either.

What remains to be done to release working code? What are the blocking issues preventing us from releasing working code? What is the plan to work through each blocking issue? Have the GPL/LGPL and other license compatibility problems been resolved and if not, what is the outlook to resolving these problems? If you can submit a step by step plan for how we will get to working code, I will work with the mentors on getting team members commit access to the project. Clearly, we need to grant commit access to some new team members. Please provide a list of proposed new committers, their role in the project and how long we expect those people to be around. I am expecting a relatively small list here, so please do not include people who are unlikely to spend time learning how to work on ASF projects or make significant contributions. Once I see and review the list, I'll provide instructions for what to do next.

My plan is to revoke the ids of the inactive members (people who have graduated and moved on). Will post those id's to this list and give the team time to review before asking the infrastructure team to revoke the ids.

Thanks
Bill

Reply via email to