On Sep 24, 2012, at 4:34 AM, Rob Weir wrote: > On Mon, Sep 24, 2012 at 5:37 AM, sebb <seb...@gmail.com> wrote: >> On 24 September 2012 03:50, Rob Weir <rabas...@gmail.com> wrote: >>> On Sep 23, 2012, at 10:15 PM, "Dennis E. Hamilton" <orc...@apache.org> >>> wrote: >>> >>>> Rob, >>>> >>>> I recently took a look at >>>> <http://incubator.apache.org/projects/openofficeorg.html> to see if I >>>> could derive that list from the Roster. >>>> >>>> What gave me pause is that the list is apparently maintained in XML. I >>>> could not find anywhere that MarkDown is used. Is that correct? >>>> >>> >>> Correct. It is XML. It used to require that I check out the whole >>> directory, update the XML, run an ant script to generate the HTML and >>> then check in both the XML and HTML. This is much simplified by the >>> CMS which does the template generation behind the scenes. >>> >>> >>>> I could still mechanically derive the XML elements that are used now, >>>> although it is a bit more complicated than search and replace on a CSV of >>>> an extract of the roster. If I were to do that, I would also indicate who >>>> is on the PPMC. >>>> >>>> Any suggestions? >>> >>> I'm not sure we need to maintain that "status file" once we graduate. >>> I think it is more of a podling tracking thing. So it might be >> >> Yes, it is for active podlings only. No need to update it once >> graduated, though it does need to be completed before graduation. >> >> The other file that needs to be updated by podlings is podlings.xml. >> >> Note that >> >> http://people.apache.org/committers-by-project.html#ooo >> >> is created automatically from the SVN authz file (where podling >> committers are listed) plus LDAP groups. >> >>> simplest if we just manually update it for now. But longer term it >>> would be good to be able to generate a page for the project website >>> from the Roster. The ODF Toolkit has an XSLTRunner component that >>> could be used for this. >> >> Not sure that's necessary. You could just link to the appropriate >> sections in the above file. >> > > Is there any easy way to track PMC membership? Maybe that be derived > from the authz for the eventual /pmc/openoffice tree? Eventually we > want an easy way to generate a roster that lists committers but also > identifies PMC members.
Sebb answered, but sometimes examples are needed. PMCs have authz as well. Here is the page for the POI PMC: http://people.apache.org/committers-by-project.html#poi-pmc Regards, Dave > > -Rob > > >>> -Rob >>> >>>> >>>> - Dennis >>>> >>>> -----Original Message----- >>>> From: Rob Weir [mailto:robw...@apache.org] >>>> Sent: Sunday, September 23, 2012 17:41 >>>> To: ooo-dev@incubator.apache.org >>>> Subject: Re: New committer: Chen ZuoJun >>>> >>>> On Sun, Sep 23, 2012 at 1:13 PM, Dennis E. Hamilton <orc...@apache.org> >>>> wrote: >>>>> The Apache OpenOffice PPMC announces the addition of committer >>>>> Chen ZuoJun, zjchen@ apache.org >>>>> >>>>> The list of all current podling committers is at: >>>>> <http://people.apache.org/committers-by-project.html#ooo>. >>>> >>>> And one other place: >>>> http://incubator.apache.org/projects/openofficeorg.html >>>> >>>> That page is part of the IPMC's tracking of podling status and feeds >>>> into their "Status of the Clutch" report: >>>> http://incubator.apache.org/clutch.html >>>> >>>> Some may recall that we had a reporter use the "status of the clutch" >>>> report to claim that the project was not growing. That was when we >>>> were not updating the report. Since that is the official IPMC view of >>>> the podlings, it is important that we keep this information >>>> up-to-date, until the project graduates. >>>> >>>> I was updating this status page whenever a new committer was voted in. >>>> It would be great if someone else could take this over now. >>>> >>>> When a new committer is added, the status file needs to be updated in >>>> two places. >>>> >>>> 1) Added as a News item. Automation depends on the wording, so don't >>>> be clever. Just follow the examples there. >>>> >>>> 2) Added in the list of committers. >>>> >>>> This can most easily be edited via the Apache CMS. >>>> >>>> [ ... ] >>>>
