Let this serve as a strong preemptive -1 to any boilerplate board report. Yes, I completely agree with you that there isn't much to report on at this point (which is completely fine!). Getting too generic/cookie-cutter is an important concern for projects at any stage in their lifetime.
I would give the following as a reminder: * The board reports are read by other humans * Those humans are technical and want to know how the project is doing (really) * If there are successes, great, let the board know things are great! * If something sucks, let the board know, maybe they can help! A template for reports can be helpful, but please remember that it is not a substitute for real effort in report generation. Please don't take this as accusatorial, but instead encouragement to write reports which elicit regular positive feedback from the board. On May 26, 2016 5:59 AM, "Edward Capriolo" <[email protected]> wrote: > In the projects I have been in making the reports gets redundant. I believe > there is a script that can be used to generate a report. For now since we > just got rolling we can look at how many people are mailing lists members, > and mention that we are just getting underway. If you have a template > maybe share it as a google doc and we can hack at it. > > On Wed, May 25, 2016 at 10:54 PM, P. Taylor Goetz <[email protected]> > wrote: > > > Anyone want to take a crack at this? > > > > I'm happy to help. > > > > -Taylor > > > > > On May 25, 2016, at 10:34 PM, [email protected] wrote: > > > > > > Dear podling, > > > > > > This email was sent by an automated system on behalf of the Apache > > > Incubator PMC. It is an initial reminder to give you plenty of time to > > > prepare your quarterly board report. > > > > > > The board meeting is scheduled for Wed, 15 June 2016, 10:30 am PDT. > > > The report for your podling will form a part of the Incubator PMC > > > report. The Incubator PMC requires your report to be submitted 2 weeks > > > before the board meeting, to allow sufficient time for review and > > > submission (Wed, June 1st). > > > > > > Please submit your report with sufficient time to allow the Incubator > > > PMC, and subsequently board members to review and digest. Again, the > > > very latest you should submit your report is 2 weeks prior to the board > > > meeting. > > > > > > Thanks, > > > > > > The Apache Incubator PMC > > > > > > Submitting your Report > > > > > > ---------------------- > > > > > > Your report should contain the following: > > > > > > * Your project name > > > * A brief description of your project, which assumes no knowledge of > > > the project or necessarily of its field > > > * A list of the three most important issues to address in the move > > > towards graduation. > > > * Any issues that the Incubator PMC or ASF Board might wish/need to > be > > > aware of > > > * How has the community developed since the last report > > > * How has the project developed since the last report. > > > > > > This should be appended to the Incubator Wiki page at: > > > > > > http://wiki.apache.org/incubator/May2016 > > > > > > Note: This is manually populated. You may need to wait a little before > > > this page is created from a template. > > > > > > Mentors > > > ------- > > > > > > Mentors should review reports for their project(s) and sign them off on > > > the Incubator wiki page. Signing off reports shows that you are > > > following the project - projects that are not signed may raise alarms > > > for the Incubator PMC. > > > > > > Incubator PMC > > >
