[CentOS-docs] Potential loss of a wiki contributor.

Sat May 9 09:51:53 UTC 2009
Dag Wieers <dag at centos.org>

On Fri, 8 May 2009, Karanbir Singh wrote:

> On 05/08/2009 05:39 PM, Dag Wieers wrote:
>>    - If your mail arrived on the list and you did not get any response,
>>      contact person1 or person2 to make sure we can fix this as soon as
>>      possible
> I'd rather we dont do that, it creates a direct dep on a specific person
> leading to the sort of issue here. I think people should be encouraged
> to resend a reminder to the mailing list itself. That way its visible to
> everyone and if there is a problem, there are resources that can be
> brought in to handle the problem.

Yes, I agree. That was my initial thought as well, but since there was an 
existing escalating path (AdminGroup) I thought we may wanted to keep it 
for the same reason.

>> I would also like to add some links eg. where to create a login, a link to
>> the archive, etc...
> Sounds good. Actually looking at that page with my 'dunce' cap on, the
> page looks a bit cluttered, there might be too much info on that one
> page which could also cause an issue. What does everyone think ? Should
> that / Could that page be split up into smaller nuggets ? Could the info
> be better organised ?

I think we should not give too many directions on that wiki-contribution 
section, just the steps should suffice. And then we can add on the 
UserPreferences an improved section on what new users can expect and what 
they ought to do to get commit access.

Because I expect a large part of the potential contributors just create an 
account on the wiki without going via the Contribute page anyhow. It makes 
more sense to have the bulk of instructions on that page.

> btw, w.r.t subscriptions to the list, we can always just have a form
> that someone fills in that does some behind-the-scenes stuff, including
> subscribe the person to the list. or is that just asking for a spam
> honeypot ?

That would be even better, but I can live with what we have right now. 
Definitely put it on the project TODO list as a nice-to-have feature.

Maybe time to maintain such a public generic TODO list ? The bug-tracker 
could be used for organisational/infrastructural work and discussions. I 
never was a proponent to use mantis for this, but lacking something else 
it might just work if we provide good views.

--   dag wieers,  dag at centos.org,  http://dag.wieers.com/   --
[Any errors in spelling, tact or fact are transmission errors]