The key take away from the reports discussions is to ensure you address community development issues and demonstrate a plan for moving towards graduation.
Jena reports have been doing this since day one. The only improvement I cab see (other than those suggested by Ian) is to indicate how much code had not been released, why and when it will be. I know this is partly covered already, but it might be good to be clearer since your mentors are pushing for graduation. Ross Sent from my mobile device, please forgive errors and brevity. On Jan 21, 2012 8:24 PM, "Ian Dickinson" <[email protected]> wrote: > On 21/01/12 17:47, Andy wrote: > >[...] > Looks good. > > The project has successive produced a release. >> > s/successive/successfully/ > > Also, do we want to be more precise about which components have been > released, since one of the plan items is to release further subsystems. > > We could also mention that most support traffic is now via > jena-users@apache, with very little flowing through Yahoo groups. > > There has been a lot of discussion about better podling reports on the > Incubator general list. I must admit I haven't bothered to trawl through > all of it. Mentors, are there any takeaways from that discussion that might > bear on this month's report? > > Ian >
