Also, I'd be more than happy to handhold. Marvin
did a great job showing me the ropes so I'm
more than happy to return the favor ;-)

Thanks,
Roman.

On Wed, Jan 22, 2014 at 10:23 PM, Marvin Humphrey
<mar...@rectangular.com> wrote:
> On Wed, Jan 22, 2014 at 9:14 PM, Henry Saputra <henry.sapu...@gmail.com> 
> wrote:
>> Hi Marvin, is there any wiki page describing the TODO for Report Manager?
>
> Instead of a wiki page, the instructions are kept in a script:
> `report_runbook.py`.  The script has the advantage of being able to generate
> commands which can be copied and pasted.
>
> Output below.
>
> Note that Roman has already generated the wiki template for February and
> assigned shepherds.
>
>     http://wiki.apache.org/incubator/February2014
>
> The way things are organized right now, the *last* task of the Report Manager
> for a given month is to perform those steps for the upcoming month.
>
> Marvin Humphrey
>
>
> $ python3 report_runbook.py --apache-id=hsaputra --month=2
>
> ##################################################################
> # On the last Wednesday of the month, send an email to
> # general@incubator announcing the report timeline, using the
> # following content.
> ##################################################################
>
> February 2014 Incubator report timeline:
>
>     http://wiki.apache.org/incubator/February2014
>
>     Wed February 05 -- Podling reports due by end of day
>     Sun February 09 -- Shepherd reviews due by end of day
>     Sun February 09 -- Summary due by end of day
>     Tue February 11 -- Mentor signoff due by end of day
>     Wed February 12 -- Report submitted to Board
>     Wed February 19 -- 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'."
>
> ##################################################################
> # The Board report must contain a list of releases by the
> # Incubator project since the last report.  This can be assembled
> # manually from the history of our dist area.
> #
> # The date of each release is the date it appeared in our dist
> # area.  Since our report periods don't have hard boundaries,
> # the only way to know which reports made the cut last month and
> # which didn't is to check the last report.
> ##################################################################
>
> # History of our dist area since just before the last report:
> svn log -v -r {2014-01-01}:HEAD
> https://dist.apache.org/repos/dist/release/incubator
>
> ##################################################################
> # 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 February 2014
> #
> # 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.
> ##################################################################
>
> ##################################################################
> # Prepare next month's 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."
> ssh -t hsapu...@people.apache.org publish.pl incubator hsaputra
>
> # Assign shepherds.
> python3 assign_shepherds.py --month=3
> svn ci -m "Assign shepherds."
>
> # Generate report template and publish on the wiki.
> python3 clutch2report.py --month=3 --upload
>
> $
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Reply via email to