You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Patricia Shanahan <pa...@acm.org> on 2016/09/05 00:03:16 UTC
Kay's activities
I think some of our troubles, including the Mac Buildbot issue, are
related to not identifying and picking up activities that were being
done by people who have left the project.
I asked Kay for some notes on her activities - posted here with her
permission:
> I'll do my best. Here goes -- in reverse order of my particiaption
>
> * buildbot script maintenance (recently Damajan and I). Before that,
> Herbert Duerr
>
> svn info:
> https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/openofficeorg.conf
>
> Checkout is via: svn co
> https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects
>
> which contains build scripts for all projects
>
> * monitoring BZ issues via issues@openoffice.apache.org mailing list
> Well presumably all developers do this.
>
> * monitoring commits via commits@openoffice.apache.org
>
> * subscription to infra
> Normally this is not a big deal, and it's a VERY BUSY list
>
> * trying to fix bugs when I can
> Well I am NOT a C++ programmer but was able to deal with stuff like
> makefile problems
>
> * editing info on the wiki occasionally
> https://wiki.openoffice.org/wiki/Main_Page
>
> * editing pages on the project web site
> http://openoffice.apache.org/
>
> *editing page on the end user web site
> http://www.openoffice.org/
>
> NOTE: Both the web sites above involve use of the ASF CMS and staging areas.
> See: http://openoffice.apache.org/website-local.html
>
> for details on what someone needs to do to deal with this.
> This is where I started with AOO --bringing over the old OpenOffice.org
> web site with Dave Fisher.
>
> * Updating the AOO update stuff when a new release comes out.
> We have an "update URL" in AOO that is like an app inside AOO that pulls
> new releases down for end users when I release comes up. Scripts are in:
> http://svn.apache.org/viewvc/openoffice/updates-site/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
RE: Kay's activities
Posted by "Dennis E. Hamilton" <de...@acm.org>.
Good, thanks for getting this.
The web site effort was extensive.
Kay was also the one who, along with Marcus, identify issues as blockers or to have their fixes ear-marked for 4.2.0. She did the same for 4.1.2. So she has done more than watch the bugzilla.
- Dennis
> -----Original Message-----
> From: Patricia Shanahan [mailto:pats@acm.org]
> Sent: Sunday, September 4, 2016 17:03
> To: dev@openoffice.apache.org
> Subject: Kay's activities
>
> I think some of our troubles, including the Mac Buildbot issue, are
> related to not identifying and picking up activities that were being
> done by people who have left the project.
[orcmid]
Yes, and some of that is because folks often just go dark and we don't know they've left. That is happening with list moderators too.
>
> I asked Kay for some notes on her activities - posted here with her
> permission:
>
> > I'll do my best. Here goes -- in reverse order of my particiaption
> >
> > * buildbot script maintenance (recently Damajan and I). Before that,
> > Herbert Duerr
> >
> > svn info:
> >
> https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildma
> ster/master1/projects/openofficeorg.conf
> >
> > Checkout is via: svn co
> >
> https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildma
> ster/master1/projects
> >
> > which contains build scripts for all projects
> >
> > * monitoring BZ issues via issues@openoffice.apache.org mailing list
> > Well presumably all developers do this.
> >
> > * monitoring commits via commits@openoffice.apache.org
> >
> > * subscription to infra
> > Normally this is not a big deal, and it's a VERY BUSY list
> >
> > * trying to fix bugs when I can
> > Well I am NOT a C++ programmer but was able to deal with stuff like
> > makefile problems
> >
> > * editing info on the wiki occasionally
> > https://wiki.openoffice.org/wiki/Main_Page
> >
> > * editing pages on the project web site
> > http://openoffice.apache.org/
> >
> > *editing page on the end user web site
> > http://www.openoffice.org/
> >
> > NOTE: Both the web sites above involve use of the ASF CMS and staging
> areas.
> > See: http://openoffice.apache.org/website-local.html
> >
> > for details on what someone needs to do to deal with this.
> > This is where I started with AOO --bringing over the old
> OpenOffice.org
> > web site with Dave Fisher.
> >
> > * Updating the AOO update stuff when a new release comes out.
> > We have an "update URL" in AOO that is like an app inside AOO that
> pulls
> > new releases down for end users when I release comes up. Scripts are
> in:
> > http://svn.apache.org/viewvc/openoffice/updates-site/
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Kay's activities
Posted by Marcus <ma...@wtnet.de>.
Thanks for getting this info. That will help in case someone will need this.
Marcus
Am 09/05/2016 02:03 AM, schrieb Patricia Shanahan:
> I think some of our troubles, including the Mac Buildbot issue, are
> related to not identifying and picking up activities that were being
> done by people who have left the project.
>
> I asked Kay for some notes on her activities - posted here with her
> permission:
>
>> I'll do my best. Here goes -- in reverse order of my particiaption
>>
>> * buildbot script maintenance (recently Damajan and I). Before that,
>> Herbert Duerr
>>
>> svn info:
>> https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/openofficeorg.conf
>>
>>
>> Checkout is via: svn co
>> https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects
>>
>>
>> which contains build scripts for all projects
>>
>> * monitoring BZ issues via issues@openoffice.apache.org mailing list
>> Well presumably all developers do this.
>>
>> * monitoring commits via commits@openoffice.apache.org
>>
>> * subscription to infra
>> Normally this is not a big deal, and it's a VERY BUSY list
>>
>> * trying to fix bugs when I can
>> Well I am NOT a C++ programmer but was able to deal with stuff like
>> makefile problems
>>
>> * editing info on the wiki occasionally
>> https://wiki.openoffice.org/wiki/Main_Page
>>
>> * editing pages on the project web site
>> http://openoffice.apache.org/
>>
>> *editing page on the end user web site
>> http://www.openoffice.org/
>>
>> NOTE: Both the web sites above involve use of the ASF CMS and staging
>> areas.
>> See: http://openoffice.apache.org/website-local.html
>>
>> for details on what someone needs to do to deal with this.
>> This is where I started with AOO --bringing over the old OpenOffice.org
>> web site with Dave Fisher.
>>
>> * Updating the AOO update stuff when a new release comes out.
>> We have an "update URL" in AOO that is like an app inside AOO that pulls
>> new releases down for end users when I release comes up. Scripts are in:
>> http://svn.apache.org/viewvc/openoffice/updates-site/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org