Confirmed users
630
edits
(Created page with "<div style="background:#FDD;border:5px solid #C88; margin: 1em auto; padding: .5em 1.2em;"> '''NOTE:''' ''This page is a draft and its content is discuss on [https://groups.go...") |
No edit summary |
||
| Line 3: | Line 3: | ||
</div> | </div> | ||
== Open questions == | |||
In order to get a solid onboarding pathway, the following questions needs to be discussed. | |||
* | * Do we want new users to be vouch and give them more initial right? | ||
** What level of automation do we want to put into this pathway? | ** ''The actual number of people asking for a new account seams to make this hardly sustainable''. | ||
* What level of automation do we want to put into this pathway? | |||
** A way to soften constrain? | |||
** A way to push user to the next level? all of them? | |||
** A way to push candidates to upgrade to those who can promote them? | |||
*** Could it be possible to do it by hand by reviewing editors contribution at regular intervals? | |||
* Do we want a process to downgrade privileges? | |||
== Draft process == | |||
The following steps describe the suggested process to onboard a user from simple reader up to a full MDN administrator. | |||
'''NOTE:''' ''Every point flagged with ''New Feature'' are things that are not yet available on the Kuma platform and will requires some dev work.'' | |||
=== Step 1: MDN Reader === | === Step 1: MDN Reader === | ||
| Line 29: | Line 36: | ||
** Can edit existing contents | ** Can edit existing contents | ||
** Can revert its own edits | ** Can revert its own edits | ||
** Can access beta display features | ** Can access beta display features (''new feature'') | ||
* Extra constrains: | * Extra constrains: | ||
** Can edit only once every 5min | ** Can edit only once every 5min (''new feature'') | ||
** Cannot edit more than 20 times a day | ** Cannot edit more than 20 times a day (''new feature'') | ||
** All change are checked with spam filters | ** Cannot add external link to their edits (''new feature'') | ||
** All change are checked with spam filters (''new feature'') | |||
* Condition to soften constrains: | * Condition to soften constrains: | ||
** ''TBD'' | ** ''TBD'' (''new feature'') | ||
* Condition to reach next step | * Condition to reach next step | ||
** Must introduce themselves on IRC or mailing list | ** Must introduce themselves on IRC or mailing list | ||
** Must be manually upgraded by a ''Core contributor'' or an ''Admin'' | ** Must be manually upgraded by a ''Core contributor'' or an ''Admin'' (''new feature'' for core contributor) | ||
=== Step 3: Regular editor === | === Step 3: Regular editor === | ||
| Line 47: | Line 55: | ||
** Can create tags | ** Can create tags | ||
** Can validate review requests | ** Can validate review requests | ||
** Can access beta edit features | ** Can access beta edit features (''new feature'') | ||
* Extra constrains: | * Extra constrains: | ||
** Can edit only once every 2min | ** Can edit only once every 2min (''new feature'') | ||
** Can create content only every 5min | ** Can create content only every 5min (''new feature'') | ||
** No more limit to the number of edit or creation | ** No more limit to the number of edit or creation | ||
* Condition to soften constrains: | * Condition to soften constrains: | ||
** ''TBD'' | ** ''TBD'' (''new feature'') | ||
* Condition to reach next level | * Condition to reach next level | ||
** Must be manually upgraded by an Admin | ** Must be manually upgraded by an Admin | ||
| Line 74: | Line 82: | ||
** Can edit kuma macro | ** Can edit kuma macro | ||
** Can upgrade new editors | ** Can upgrade new editors | ||
** Can ban users | ** Can ban users (''new feature'') | ||
* Condition to reach next level | * Condition to reach next level | ||
** Must be vouch by two Admin | ** Must be vouch by two Admin | ||