On Sep 7, 2013, at 4:46 AM, Andrea Pescetti wrote: > On 23/08/2013 janI wrote: >> On 22 August 2013 23:51, Alexandro Colorado<[email protected]> wrote: >>>>> just get a final confirmation if there a 'go' on the Wiki logo update >>>>> which >>>>> was reverted due to a regression by infra when setting the SVN. >> Infra did not revert anything. >> As you very well know the revert on wiki was done by me, because >> a) the logos was installed in a wrong place, that made updates very >> difficult >> b) the standard procedure to make a backup/commit was not followed >> All something that had nothing to do with consensus, but how admins work on >> the vm. > > I'm coming late to this part of the discussion, but this was definitely the > right thing to do. We care about a professional-level maintenance of our > Infrastructure (and actually Apache Infra demands and enforces it). Everyone > can make mistakes, but when we can correct them we must do so. And this is > the "technical" part.
I agree. My default position is that I support Jan's sysadmin work. For me silence is assent. I'll make it clear here. > >> I respects these concerns and feel reel consensus is >> much more important than a technicality, even if it takes 400+ hours. >> As vm-admin, I will not install a new logo and/or change html/css before I >> see a broad acceptance. Other vm-admins might feel different. > > And now coming to the "community" part: this was very right too. An > administrator must check consensus before doing changes. And consensus > reaching may well take weeks (the larger and simpler the issue -and this is > "large" since it affects several sites and "simple" since everybody can have > a say- the longer the discussion). > > The important thing is that eventually we get things done! Hagar restarted > the constructive discussion at > http://forum.openoffice.org/en/forum/viewtopic.php?f=50&t=63523 recently and > I hope we can move forward there. When the decision is made please bring it back here and flag it with a [CONSENSUS] subject tag. We can then test that here and then proceed after the consensus is proven. Either way we should be vetting the new html, it's look, etc. The sysadmin team is then responsible for implementation on MWiki and forums and communication about that to the appropriate lists. The admin team is responsible for maintaining these servers and needs to manage all configuration changes in a manner that any server can be rebuilt from scratch using private svn archives including a runbook and data backups. This has to be co-ordinated. A change that is apparently simple and seemingly 10 minutes is not. Sysadmins are correct to insist on process here. Volunteer sysadmins even more so. Don't expect them to be happy if you make them "volunteer" when they have real plans and other activities. But, Alexandro seems to want to discuss a full branding change to all AOO assets if that is so then that decision must be made on this list, is much larger and it requires a full proposal with willingness to discuss everyone's ideas. In that case the co-ordination is large and complete consensus followed by a conversion plan is required. - Sysadmin team MWiki Forums - Committers Websites - Infra / bz admins Bugzilla - PMC / Infra CWiki Blogs - Sourceforge Extensions Templates Regards, Dave > > Regards, > Andrea. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
