Guide/notes/document sponsorship

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



During the Docs meeting tonight the issue of moving all documents
under a single fas group to grant access came up.

jjmcd brought up several issues - and I think they are worth
considering. More importantly he brought up a potential solution, that
I also think is worth considering. I'd encourage you to read through
the log if you weren't there.

Specifically as downsides to the proposal he enumerated the following:
* there is currently a progression from member -> committer ->
publisher - which we'd largely lose.
* currently new members tend to be 'frightened' by getting their first
document commit access, and giving it all in one fell swoop might
discourage contributors. (a new contributor echoed that he would feel
this way)

We discussed at length and said that the problems we were trying to solve were:
* Remove barriers to participation, particularly the 'need to find a
sponsor for $group during a hackfest' or to help someone get started
fresh.
* Make it easier for existing contributors to switch to a different
document/guide in the event there is some need or push such as the
recent work on the User Guide that laubersm led.

So jjmcd wisely noted that spreading sponsor powers around would solve
most of these problems. Heretofore, most of us have collected
memberships and sponsorship as needed. I'd like to propose at a
minimum (note that this isn't intended to be a rule or policy) that if
you own a document (release notes, a guide,
$other_repo_controlled_document) that you become a sponsor for all of
our documents. Additionally, someone who is comfortable with our
environment, and the processes should also get sponsor rights to all
of our documents to solve the above two problems.

One of the interesting things is that no one seemed concern about
granting access to people. We want to be pretty liberal with that.

So, I am bringing this to the list in hopes of generating more
discussion, and see if we want to do that moving forward.

Thoughts, comments, flames??

David Nalley
-- 
docs mailing list
docs@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/docs

[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Red Hat 9]     [Yosemite News]     [KDE Users]

  Powered by Linux