incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Roman Shaposhnik <...@apache.org>
Subject Re: Report Manager for December
Date Wed, 18 Dec 2013 19:20:14 GMT
Marvin,

if you're still looking for a volunteer for this, I'd love to
give it a try.

Thanks,
Roman.

On Tue, Nov 26, 2013 at 11:58 AM, Marvin Humphrey
<marvin@rectangular.com> wrote:
> Greets,
>
> I'm looking for a volunteer to be the Incubator's "Report Manager" for our
> December Board report.
>
> Many aspects of the report process are now automated.  Below my sig is the
> output of `report_runbook.py`, which is akin to a release script.  It serves
> as a task list, but with custom commands printed out for the Report Manager to
> copy-and-paste in order to reduce effort and error.
>
> I would be happy with either a volunteer who wants to take on only the
> mechanical steps and leave editorial and summary preparation to me, a
> volunteer who wants to prepare the entire report, or anywhere in between.
> The IPMC Chair is ultimately responsible for ensuring that a proper report
> gets delivered to the Board, but does not necessarily have to write it or even
> coordinate it.  It would be good for the Incubator for more people to gain
> increased familiarity with our tools and tasks -- for the same reasons that it
> is beneficial for a project to have many individuals serve as Release Manager.
>
> Hopefully we can get a volunteer to perform the first sequence of steps to
> prep the wiki template soon, since podling report reminders are scheduled to
> be sent out tomorrow.
>
> Marvin Humphrey
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> $ python3 report_runbook.py --apache-id=gmhopper --month=12
>
> ##################################################################
> # Prepare the wiki report template.
> ##################################################################
>
> # Edit podlings.xml: remove the "monthly" attribute for podlings
> # where it has expired.  Commit any changes.
> [... edit podlings.xml with your editor of choice ...]
> svn ci -m "Remove expired 'monthly' attributes."
>
> # Run clutch, regenerate the website, commit and publish
> python3 clutch.py
> ant
> svn ci -m "Run clutch and update Incubator website."
> ssh -t gmhopper@people.apache.org publish.pl incubator gmhopper
>
> # Assign shepherds.
> python3 assign_shepherds.py --month=12
> svn ci -m "Assign sheperds."
>
> # Generate report template and publish on the wiki.
> python3 clutch2report.py --month=12 --upload
>
> ##################################################################
> # Send an email to general@incubator announcing the report
> # timeline, using the following content.
> ##################################################################
>
> December 2013 Incubator report timeline:
>
>     http://wiki.apache.org/incubator/December2013
>
>     Wed December 04 -- Podling reports due by end of day
>     Sun December 08 -- Shepherd reviews due by end of day
>     Sun December 08 -- Summary due by end of day
>     Tue December 10 -- Mentor signoff due by end of day
>     Wed December 11 -- Report submitted to Board
>     Wed December 18 -- Board meeting
>
>
> ##################################################################
> # After the podling reporting deadline has passed, group
> # podlings into the following categories (additional categories
> # may be added if appropriate):
> #
> # * Still getting started at the Incubator
> # * Not yet ready to graduate
> #   * No release
> #   * Community growth
> # * Ready to graduate
> # * Did not report, expected next month
> ##################################################################
>
> # For any podlings that did not report, add a "monthly" attribute
> # in podlings.xml.  See http://s.apache.org/At0 for a sample commit.
> [... edit podlings.xml with your editor of choice ...]
> svn ci -m "Assign podlings which did not report to 'monthly'."
>
> ##################################################################
> # Normalize the formatting of the podling reports and shepherd
> # reviews.  Remove any blank entries.
> #
> # TODO: style guide.
> ##################################################################
>
> ##################################################################
> # The day after the shepherding deadline has passed, extract
> # the shepherd reviews from the wiki and send them in a
> # compendium email to general@incubator.
> #
> # It is important to send this email in a timely manner so that
> # podlings have an adequate window to respond shepherd reviews.
> #
> # Suggested subject:
> #
> #    Shepherding December 2013
> #
> # TODO: Automate shepherd review extraction.
> ##################################################################
>
> ##################################################################
> # On the day that the report is due to be submitted to the Board,
> # no action by the Report Manager is required.
> #
> # The IPMC Chair will perform a final review for completeness and
> # consistency, mark the wiki page as final, then file the report.
> ##################################################################
>
> $
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Mime
View raw message