The OpenOffice PMC had a productive meeting with Infrastructure at
ApacheCon a few days ago. As agreed, I'm sending my notes (sorry for the
delay). I'm putting everything together so that we can update this from
time to time and measure progress. (For the OpenOffice dev list: this
message contains updates on a lot of pending infrastructure actions,
please make sure to read it all).
1) Custom infrastructure: forum/wiki
Jan Iversen (jani) expressed his availability to take over from Andrea
in managing the virtual machines powering the OpenOffice Forum and Wiki.
So we will transition soon, and he will be free to reset permissions as
he sees fit. Limited sudo access (to restart the VM in case of need)
will still be available for the current administrators.
Next action: Jan to reconfigure access (this is already in progress)
2) Mac buildbot
It is ready (operating system), Andrew Rist is taking care of the setup
(buildbot "slave" software and its connection to the "master").
Next action: Andrew Rist to finish setup, then talk to Infra
3) Linux buildbot
A Centos 5 VM is ready, currently turned off. It was setup by jani
months ago. It is unclear who has access to it. We currently have the
basic system only, buildbot software still needs to be installed.
Next action: Infra to actually make the VM accessible so that the
project can install the missing parts.
4) Digitally signed releases (Windows)
Infra is ready with a digital signing service for Windows binaries; the
major difference with the current process is that digital signatures
will be recognized as valid by Windows.
We have a test signing server and a production signing server (both with
a "test" and "production" signing system). The production system should
not be abused since we have limited credits (or "signing events", each
of which can contain several binaries), but we can surely try signing
our 4.1.1 binaries for a start.
Missing a release manager, Andrea has the signing certificates. You can
send binaries to the signing server directly from a local machine (not
necessarily within the Apache network) and in case of issues the signing
event can be revoked.
Next action: Andrea to figure out how the service works and to start
playing with it, asking Infra if needed.
5) Digitally signed releases (Mac)
We are ready to produce digitally signed releases that will be accepted
by Mac OS too. But this is blocked by a legal issue, LEGAL-174:
https://issues.apache.org/jira/browse/LEGAL-174
Next action: Andrea to weigh in in LEGAL-174 to say that OpenOffice
would like to sign Mac binaries too.
6) E-mail functionality monitoring
Andrea states that the relatively long (about 1 week) e-mail outage we
had some months ago was a problem for the project work and image. A very
complete monitoring plan is being set up by Infra. Basic monitoring is
already active.
Next action: Infra to continue the setup of monitoring systems and blog
about it when appropriate.
7) Mailing lists setup
Despite many attempts and discussions on our mailing lists, the mailing
list setup is still problematic, since we allow unsubscribed posters to
post (moderated) but force the Reply-To to be the list. The preferred
setup for our lists is still Reply-To set to the list, but it would be
great to add the sender to Reply-To in case of unsubscribed posters.
Next action: Andrea to revive the conversation on the Infra lists,
digging the old threads and linking to them. CC pctony.
[Just for information, mailing lists can be moderated by non-committers]
8) Website
Site has to stay pure HTML, PHP is not an option. Jekyll
http://jekyllrb.com/ may be worth a look if we are to rebuild our site,
and other projects are using it. The so-called "sledgehammer" commits
(template updates triggering mass-rebuilds) are not expected to be a
problem any longer. The publish.pl script is minimally maintained,
Andrea reports it's not working but needs to check his setup better.
Next action: Andrea (or actually, anyone who is using it!) to check his
publish.pl and report to Infra if it's broken.
9) Blog
Roller is not nice or user-friendly for editors, and it is not linked to
Apache accounts so one has to create a separate account for it anyway.
If this move can increase participation, OpenOffice is free to move to
Wordpress (preferably a hosted version on wordpress.com) and have
blog.openoffice.org created and redirected to it (the current URL is
https://blogs.apache.org/OOo/ ).
Next action: OpenOffice dev list to assess whether a different setup can
increase the (currently very scarce, and limited to Andrea in the last 6
months) blogging activity in the project.
10) Translation server (Pootle)
We had a request from Michal Hrin (hrin), approved by lazy consensus by
the OpenOffice dev list, to become an administrator of the Pootle server
limited to the OpenOffice project(s). This is technically possible, and
Jan is a super-administrator there and can make those changes.
Next action: Jan to give Michal admin rights, limited to the OpenOffice
project [note: later conversations moved in the direction to evaluate
hosted solutions for Pootle, so this evaluation will probably be done
first].
11) Budget for 2015
If there is need of anything from Infra that requires to allocate a
budget, the OpenOffice PMC should ask for it in February 2015.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
