How about this: 1. Discuss the project's graduation on the general list. 2. Fill blanks left on the status page. 3. Reaching a bigger community that will contribute code to the project, though it remains to be seen if it's required before graduation.
Friday, July 1, 2016, 8:51:15 AM, Sergio Fernández wrote: > Hi, > > On Fri, Jul 1, 2016 at 8:45 AM, Daniel Dekany <[email protected]> wrote: > >> How do you mean this to be combined with "Discuss the project's >> graduation on the general list"? >> > > Yes, besides simply say "Discuss the project's graduation on the general > list", be more concrete about the concrete potential issue. Maybe "Find > more active contributors, discuss how to proceed without that" was too > direct, but it's better to be direct than have the risk the board does not > understand the real issue we're discussing here. > > Anyway, whatever working you use is fine for me. > > Thanks. > > > > Thursday, June 30, 2016, 10:02:34 AM, Sergio Fernández wrote: >> >> > Although I agree the wording could be a bit more positive, I think it's >> > important to keep the first point from Daniel >> > >> > What about something like "Reach a bigger community that will contribute >> to >> > the project"? >> > >> > On Thu, Jun 30, 2016 at 8:03 AM, Jacopo Cappellato < >> > [email protected]> wrote: >> > >> >> Hi Daniel, >> >> >> >> the report looks good to me, thank you. >> >> Maybe we could rephrase the following section: >> >> >> >> ============================= >> >> Most important issues to address in the move towards graduation: >> >> >> >> 1. Find more active contributors, discuss how to proceed without that >> >> 2. Fill blanks left on the status page >> >> ============================= >> >> >> >> into this one: >> >> >> >> ============================= >> >> Most important issues to address in the move towards graduation: >> >> >> >> 1. Make sure that the project's status page is updated >> >> 2. Discuss the project's graduation on the general list >> >> >> >> ============================= >> >> >> >> Jacopo >> >> >> >> On Wed, Jun 29, 2016 at 11:28 PM, Daniel Dekany <[email protected]> >> >> wrote: >> >> >> >> > Here's what I intend to submit. Because we want to mention the >> >> > graduation discussion, I thought it's better if you look at it first: >> >> > >> >> > >> >> > FreeMarker >> >> > >> >> > FreeMarker is a template engine, i.e. a generic tool to generate text >> >> > output >> >> > based on templates. FreeMarker is implemented in Java as a class >> library >> >> > for >> >> > programmers. >> >> > >> >> > FreeMarker has been incubating since 2015-07-01. The FreeMarker >> project >> >> > exists and produces releases since around 2001. >> >> > >> >> > Most important issues to address in the move towards graduation: >> >> > >> >> > 1. Find more active contributors, discuss how to proceed without >> that >> >> > 2. Fill blanks left on the status page >> >> > >> >> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be >> >> > aware of? >> >> > >> >> > None >> >> > >> >> > How has the community developed since the last report? >> >> > >> >> > There were no changes >> >> > >> >> > How has the project developed since the last report? >> >> > >> >> > The project has made a new public release, which come with new >> >> features, >> >> > bug fixes, >> >> > and documentation improvements. Discussion was started about the >> >> > possibility of >> >> > graduation. Some missing information on the status page was filled, >> and >> >> > a formal >> >> > "podling name search" was started. >> >> > >> >> > Date of last release: >> >> > >> >> > 2016-06-26 >> >> > >> >> > When were the last committers or PMC members elected? >> >> > >> >> > 2015-10-21 Nan Lei, committer (non-PMC) >> >> > >> >> > -- >> >> > Thanks, >> >> > Daniel Dekany >> >> > >> >> > >> >> >> > >> > >> > >> >> -- >> Thanks, >> Daniel Dekany >> >> > > -- Thanks, Daniel Dekany
