I noticed that the new reporter output now contains "LDAP" in a way
that makes it sound like "LDAP" is the project name. Is this
intentional? It seems awkward and unnecessary to have "LDAP" in
there instead of "PMC", and when I read the first report containing
that verbiage, I thought there was was copy&paste error in the report.
=============
LDAP committee/Committership changes
Changes within the last 3 months:
→ Hazem Saleh was added to the LDAP committee on Fri May 15 2015
→ Latest LDAP committee addition: Fri May 15 2015 (Hazem Saleh)
→ Bill Lucy was added as a committer on Tue Jun 23 2015
→ Ross Clewley was added as a committer on Mon May 18 2015
→ Thomas Andraschko was added as a committer on Thu Jul 02 2015
→ Dennis Kieselhorst was added as a committer on Mon May 11 2015
→ Latest committer addition: Thu Jul 02 2015 (Thomas Andraschko)
→ Currently 76 committers and 39 LDAP committee members.
==============
When I ran my report earlier, it said:
==============
## PMC/Committership changes:
- Currently 76 committers and 39 PMC members in the project.
- Hazem Saleh was added to the PMC on Fri May 15 2015
- New commmitters:
- Bill Lucy was added as a committer on Tue Jun 23 2015
- Ross Clewley was added as a committer on Mon May 18 2015
- Thomas Andraschko was added as a committer on Thu Jul 02 2015
- Dennis Kieselhorst was added as a committer on Mon May 11 2015
==============
On Thu, Jul 2, 2015 at 4:47 AM, sebb <seb...@gmail.com> wrote:
> On 2 July 2015 at 07:22, Hervé BOUTEMY <herve.bout...@free.fr> wrote:
>> Le mercredi 1 juillet 2015 09:10:42 sebb a écrit :
>>> On 1 July 2015 at 07:02, Hervé BOUTEMY <herve.bout...@free.fr> wrote:
>>> > I asked about it one week ago (with analysis of the VM state), but got no
>>> > answer.
>>> > Seems the only one to know is Daniel, and he doesn't check this ML or
>>> > doesn't have time.
>>> >
>>> > I have access to the VM: it was given for projects-new.
>>> > Technically, I can change reporter too, but since we're starting from an
>>> > unexpected status (no svn checkout, files on the VM that are not part of
>>> > svn),
>>> If you can create a copy of the files on the VM I could ensure any
>>> local changes are reflected in SVN.
>> dump available in people.apache.org:/home/hboutemy/reporter.apache.org.tgz
>>
>>> It would help also to have details of the crontab entries.
>> # m h dom mon dow command
>> 00 00 * * * cd /var/www/projects.apache.org/scripts/cronjobs && python3.4
>> podlings.py
>> 00 00 * * * cd /var/www/projects.apache.org/scripts/cronjobs && python3.4
>> parsecommitters.py
>> 00 00 * * * cd /var/www/projects.apache.org/scripts/cronjobs && python3.4
>> parsechairs.py
>> 00 00 * * * cd /var/www/projects.apache.org/scripts/cronjobs && python3.4
>> countaccounts.py
>> 00 00 * * * cd /var/www/projects.apache.org/scripts/cronjobs && python3.4
>> parsereleases.py
>> 00 4,12,20 * * * cd /var/www/reporter.apache.org/data && python3.4
>> parsepmcs.py
>> 00 01 * * * cd /var/www/reporter.apache.org/ && python mailglomper.py
>> 00 09 * * * cd /var/www/reporter.apache.org/ && python readjira.py
>> 00 12 * * * curl "(removed)" >
>> /var/www/reporter.apache.org/data/mailinglists.json
>>
>>
>>
>> once content is checked against waht is in svn, we could probably copy and
>> run
>> pubsubber.py from projects.a.o so svn updates are propagated to the vm
>
> Thanks a lot.
>
> I have now been given access as well, once I set up OPIE.
>
> I hope to find some time soon to synch. the on disk changes.
> Then we can look at improvements.
>
>> Regards,
>>
>> Hervé
>>
>>>
>>> > I didn't want to change the VM content without asking before.
>>> >
>>> >
>>> > At the moment, I want to finish projects new switch: then I'll probably
>>> > have more time to help on reporter.
>>> >
>>> > Regards,
>>> >
>>> > Hervé
>>> >
>>> > Le mardi 30 juin 2015 01:20:46 sebb a écrit :
>>> >> Reporter.apache.org is showing misleading PMC membership data.
>>> >>
>>> >> As this is used in board reports, it really ought to be fixed ASAP.
>>> >>
>>> >> However the fixes I made to SVN have not been applied, and there is no
>>> >> documentation I could find on how the host has been set up - nor how
>>> >> the faulty data is generated.
>>> >>
>>> >> Who is responsible for maintaining the host and updating the software on
>>> >> it?
>>
