Hey,
On 25.10.2012 00:44, Jos Poortvliet wrote:
So how about it, can I get some 'stuff' about what was decided send to me for the final day/conference conclusions article??
Landing Page BoF: http://lists.opensuse.org/opensuse-web/2012-10/msg00026.html
Future of the OBS BoF: http://lists.opensuse.org/opensuse-buildservice/2012-10/msg00162.html
Henne
On Friday 26 October 2012 11:28:37 Henne Vogelsang wrote:
Hey,
On 25.10.2012 00:44, Jos Poortvliet wrote:
So how about it, can I get some 'stuff' about what was decided send to me for the final day/conference conclusions article??
Landing Page BoF: http://lists.opensuse.org/opensuse-web/2012-10/msg00026.html
Future of the OBS BoF: http://lists.opensuse.org/opensuse-buildservice/2012-10/msg00162.html
Henne
Thanks, I really appreciate this. Anyone else? I found a few things but it's a lot of work to sift through everything by hand!
Hello,
Am Dienstag, 6. November 2012 schrieb Jos Poortvliet:
Thanks, I really appreciate this. Anyone else? I found a few things but it's a lot of work to sift through everything by hand!
I have a non-report from the admin@ BoF ;-)
The admin@ BoF was more or less skipped (because we extended the www.o.o BoF). Instead I annoyed some people in the hallway track ;-)
Some notes: - the biggest problem is (surprise, surprise) time (to be exact: no/not enough time or a too big TODO list). This blocks several admin tasks that are considered "not too important" - at least in comparison with other items on the TODO list - one of the "not too important" things is the mailinglist merge/ shutdown, but I'm sure there are more - someone stepping up as admin for a part of the infrastructure is always welcome, but there might be practical problems like "allowing external people access to $server is difficult". Nevertheless - if you want to help, ask on admin@opensuse.org ;-) - some parts of the infrastructure don't have a maintainer, but it seems we don't have a list of the affected parts (and I'm not even sure if we have a complete list of the *.o.o infrastructure somewhere) - nobody knew something about the wiki update status (except the parts I already knew) - I'll have to ask Scott on the -web ML about the status
Regards,
Christian Boltz