On 11/20/12, jan iversen <j...@apache.org> wrote: > I agree with the views of Alexandro, you cannot do such a job (or any job) > without being committed. > > Question to Alexandro: if you did in the past, you have valuable > experience, so the most efficient thing would probably be that you continue > doing it, or is that not an option ?
At the moment I have some real life tasks that are taking much of my tasks. I also enrolled as mentor on Google Code-In (GSoC for kids) on a different FLOSS project. So I am not sure how commited I could be. Like I said I have experience with mediawiki, most of the security flaws went away by updating, and applying latest patches. That is why I suggest some research with the Mediawiki community, and bugzilla for possible (even if its experimental) patches. I would even go as far as sending a call for help email to see if any mediawiki dev/admin is interested in volunteering taking care of our wiki. But I think the current issue is not as high priority to go that far yet (I hope). > I volunteered because it seemed nobody else was interested, and my biggest > interest happens to be infrastructure and let other people do the real AOO > programs. > > Jan. > > > On 20 November 2012 23:01, Alexandro Colorado <j...@oooes.org> wrote: > >> On 11/20/12, tj <t...@apache.org> wrote: >> > On 11/20/2012 12:06, jan iversen wrote: >> >> Hi. >> >> >> >> Rob: >> >> What qualification would a Wiki maintainer need ? I used to maintain >> >> our >> >> business sites, which were PHP and AJAX based, with MySql behind, it >> that >> >> would fit, it is a job which I would volunteer for. >> > >> > Jan, >> > >> > A Wiki maintainer needs PHP and MySQL knowledge, and root access to the >> > wiki system (to be granted by Infra; JIRA ticket?). Most of the work is >> > simply making changes to the parameter file, LocalSettings.php. >> > However, >> > there is long-range work, too: preparing for upgrades, and some >> > short-term MySQL stuff. >> > >> > I will collect all the various maintenance items on a wiki page, >> > probably called "Pending Maintenance". If that doesn't scare you off, >> > your help will be greatly appreciated; Infra expects the AOO project to >> > do this level of maintenance ourselves, and it is quite beyond me. Let >> > me know. >> > >> > /tj/ >> >> I have mantained Mediawiki and other webapps in the past, one of the >> biggest challenges is the time resource on researching the right >> solution. From other projects, I think this is an automated attack on >> most of the mediawiki installations. I think the mantainer needs to be >> commited to the mediawiki project and read their security briefings >> and take tasks in accordance. >> >> However like you mention in the past, upgrading the Mediawiki site is >> non-trivial and I think we do need a testing server and be able to tdo >> rollbacks as needed and maybe provide extra securities to the backend. >> >> >> https://bugzilla.wikimedia.org/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=MediaWiki&content=spam >> >> Inedependent related bulletings include: >> MySQL: http://www.auscert.org.au/render.html?it=16590 >> >> -- >> Alexandro Colorado >> PPMC Apache OpenOffice >> http://es.openoffice.org >> > -- Alexandro Colorado PPMC Apache OpenOffice http://es.openoffice.org
