Re: [libreoffice-projects] [Proposal] A central employment-office-like web structure for TDF/LibO volunteers

2011-05-16 Thread Gianluca Turconi

Sophie Gautier wrote:

Yes. I'm more for a wiki than a bugzilla, unless you know one that has a
very nice interface and is not frightening for non technical contributors.


Sincerely, I hate bugzilla. :)

For non technical people it's a real barrier for contribution, IMO.

However, summing up this initial brainstorming discussion:

1) a central employment-office-like web structure for TDF/LibO 
volunteers *may* improve efficiency in recruiting new contributors when 
maintainers and current contributors ask for help;


2) such web structure should be as easier as possible (likely a wiki) 
and as visible as possible (a user must be able to choose how and what 
to contribute in just few clicks), with a main division between 
technical (code) and non-technical (everything else) requests for help. 
Subsections may exist according to the requested skills to complete a 
particular task and/or the estimated time to complete a task so that a 
wannabe contributor can choose the most suitable task to which contribute.


3) in order not to overload the current maintainers that ask for help in 
the centralized system, we can:
   3a) appoint some volunteers (coordinators) who will work as 
intermediaries between the current maintainer/contributors and the 
wannabe contributors *by posting* the received requests for help into 
the central system and *by confirming* the external offers or the 
completion of a task;
   3b) appoint some volunteers who will work like moderators do in 
mailing list *by checking* (for consistency, tagging, form, and so on) 
the requests for help *already directly* posted by the 
maintainers/contributors into the central system.


If we agree about this initial draft of the project, we may try to ask 
in webs...@libreoffice.org if/how/where it's possible to implement this 
idea and, above all, we should ask in other projects ML (all?) how much 
consensus there is about this idea, because, who knows, current 
contributors may prefer fragmentation (even language based one) rather 
than centralization.


BTW, I'm still puzzled from the @libreoffice.org @documentfoundation.org 
and @lists.freedesktop.org division for mailing lists. It's nearly a 
nightmare for a potential contributor to understand where to write and 
why. :(


Regards,

Gianluca
--
Lettura gratuita o acquisto di libri e racconti di fantascienza,
fantasy, horror, noir, narrativa fantastica e tradizionale:
http://www.letturefantastiche.com/

--
Unsubscribe instructions: E-mail to projects+h...@libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/www/projects/
All messages sent to this list will be publicly archived and cannot be deleted


[libreoffice-projects] Who has issues dialling in?

2011-05-16 Thread Florian Effenberger

Hello,

I received feedback that dialing in to our conference calls is a problem 
from some countries, either as the number is busy all of the time, or as 
there is no direct dial-in.


As noted previously, the Skype gateway has limitations. We're currently 
investigating in improving it, but we cannot promise anything right now. 
You know, proprietary software... ;-)


What I would like to ask all of you is to send feedback if you have 
problems with dialing in, so we can evaluate the problematic numbers, or 
take care of getting local dial-in numbers.


So far I know about issues with the UK and Slovenian numbers, and about 
a missing number in India.


Thanks,
Florian

--
Florian Effenberger flo...@documentfoundation.org
Steering Committee and Founding Member of The Document Foundation
Tel: +49 8341 99660880 | Mobile: +49 151 14424108
Skype: floeff | Twitter/Identi.ca: @floeff

--
Unsubscribe instructions: E-mail to projects+h...@libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/www/projects/
All messages sent to this list will be publicly archived and cannot be deleted