On 23 December 2013 00:20, Rob Weir <robw...@apache.org> wrote: > On Sun, Dec 22, 2013 at 11:27 AM, jan i <j...@apache.org> wrote: > > Hi > > > > based on a polite push from a good infra colleague, I have decided to > > present yet another proposal for maintaining ooo-wiki2-vm.a.o and > > ooo-forums.a.o (I already maintain translate-vm2.a.o since this is a > shared > > service). > > > > This will be proposal number 6, therefore I have allowed myself to cut > all > > the indirect language. The last proposal was not rejected, but another > > admin and 2 other PMC spoke directly against it, as a consequence I saw > it > > as impossible to implement. > > > > I ask for lazy consensus before january 2 2014. Meaning anyone who have > > anything against the proposal please speak up before that date. Since the > > proposal has a direct influence on the vm-team, the proposal needs a > > positive indication from the members of this group in order to be > decided. > > > > ===== proposal ===== > > > > Wiki.o.o is maintained by wiki users given administrator status. This > > includes monitoring users/submissions and watching/controlling spam. > > > > The single forums on forum.o.o is maintained/moderated by forum users > given > > administrator status. This includes activating new users, monitoring > > users/submissions and watching/controlling spam. > > > > All request for changes in the application (mediawiki, php2bb) > > configuration, like new images, new plugins or general setup, must be > > mailed to this list (dev@), with a lazy consensus decision of min. 72 > > hours. The sysadm will without further instruction implement the changes > as > > soon as possible (depending on sysadm availability) after the decision is > > final. > > > > In the case of phpBB changes, it would probably make sense, from the > forum perspective, for the person requesting the change to post a link > to the dev list thread to the forum as well, in the Site Feedback > section? I think we want the dev list to be the place where the > discussion happens, but it would be fair to give notice on the forums > as well. >
then the forum admins will hopefully take it to dev@ where we can agree on it. Lazy consensus can only happen on ML and its important for me to be able to trace why changes are made (just think of the logo change without consensus). > > > > The sysadm has the responsibility to keep the vms including applications > > updated and configured in accordance with the infra guidelines and be > > responsive to wishes from the community. > > > > The sysadm is the contact point to infra, and is expected to be online on > > #asfinfra on a daily basis, or at least check if there are any calls for > > attention. > > > > Downtime (excluding emergencies) will be announced on this list (dev@) > at > > least 72 hours in advance. The appl. admins are expected to inform the > > respective user groups. > > > > In order to ensure the highest availability of our servers, we have a > > vm-team, globally distributed. Members of the vm-team team are expected > to > > react on mail alerts (from nagios/circonus) during normal daytime. The > > vm-team can: > > - stop/start the application > > - reboot the server > > In case of an incident, please sent an email to the team, so we all know > > what happened. > > > > Does this require a vm-team email alias? or would it be handled > informally? > I cannot speak for others, but I have a simple group in my mail client, I dont need an alias. I might for formulated that a bit sloppy. The idea is if a vm-team member e.g. reboots a server then an email explaining what happened will be good. I would prefer (but have no strong opinion) that users of the services use dev@, otherwise it might be seen as a suppport channel. In case we make the addr. public, we need a ML for tracking purposes. > > > The sysadm decides when to upgrade/change the vm. Help from any member of > > the vm-team is appreciated as long as it is coordinated in advance (a > > direct mail with response is sufficient). > > > > I suggest myself for sysadm, and jsc, pescetti, arist and imacat for > > vm-team. Of course my suggestion depends on the willingness of the > > mentioned people. > > > > Might be worth saying how new sysadms and vm-team members are added. > I assume both require approval of the PMC. Maybe new sysadmins > require approval from Infra as well? > vm-team members are in my opinion added if the other vm-team members dont object, but I have nothing against a formal PMC approval. sysadm, require approval of the PMC, otherwise infra will not consider giving them karma. But let me be very explicit, there are more than enough sysadms. Lets first get this to work, then we can start considering what happens if I get hit by a car. > > > ========================= > > > > I have on purpose not written anything about what happens if the > agreement > > is not followed, I assume people who agree to it also follow it. IMHO its > > important that the vm-team positively agrees. > > > > If anybody else want the role of sysadm, I will be happy to step down, > and > > assist as vm-team member. > > > > Are you thinking that the sysadmin role can be only a single person? > Or would it be reasonable to have more than one, so there is always a > backup? Having more than one requires additional coordination, of > course. > sysadm is a single person, help from the vm-team is of course appreciated. More than one sysadm is a mess, where we either have lots of coordination or things float, nothing I believe in. The vm-team is the backup, and dont forget my fellow infra members, who for sure will give a helping hand if I am on vacation etc. The advantage is that we have a so called runbook, enabling other infra members to help in a critical situation. rgds jan I. > > Thanks for writing this up (again!). I appreciate the professional > approach to maintaining services like these that are essential for so > many of our users. > > In any case, although I have some thoughts I shared above, I'm +1 for > the proposal overall. I wish I could offer more than moral support > for this effort, but this is not where my skills are > > . > > Regards, > > -Rob > > > I wish you all some relaxing days. > > > > rgds > > jan I. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
