Re: Assorting of docs which "need changes"

Great ideas, Abhimanyu,

I agree that we need a better way for contributors to find pages that need
contributions!  There are a number of different projects underway that
should make this easier:


   - readiness markers on every reference page, indicating how complete
   they are.
   - http://docs.webplatform.org/wiki/Property:State has links to search
      results for each readiness state, so you could for example start
on the 18
      "out of date" articles, or figure out what needs to be done to
move the 709
      "almost ready" articles into the "ready to use" category

      - the Examples Needed and Needs Summary values of the Content quality
   flag property, which are added automatically if a template expects this
   information but it isn't there.
   - Examples Needed:
      http://docs.webplatform.org/wiki/Special:SearchByProperty?title=Special%3ASearchByProperty&property=Content+quality+flag&value=Examples+Needed
      - Needs Summary:
      http://docs.webplatform.org/wiki/Special:SearchByProperty?title=Special%3ASearchByProperty&property=Content+quality+flag&value=Needs+Summary

      - a new commenting/annotations system, due to roll out in the next
   few weeks, which will make it easier to search all comments that editors
   and readers have left, so we can effectively use the comment system to flag
   needed changes.

   - The issue tracker, currently being overhauled to make it easier to
   keep track of major infrastructure and organizational changes (although it
   wouldn't be used for small changes affecting only one page; the new
   annotations system should handle that).
      - http://project.webplatform.org/

I hope that gets you started for now in finding work that needs to be done.
 But you're right, the system could be improved considerably -- both to
coordinate all these features into a single interface, and to make sure
users understand they are there and how to use them.

If you have ideas about how to do that, it is definitely worth discussion.
 And hopefully, action!

Amelia BR



On 18 September 2014 07:11, abhimanyu0003 <abhimanyu@japanaddicts.org>
wrote:

> Mozilla docs have a special feature. Many articles are automatically
> marked 'Need changes' according to multiple factors. We can enhance it by
> introducing user feedback. This way, articles that have something wrong
> could be filtered, like pebbles through the sand... okay just ignore
> that...
>
> We'll have to think of many "factors" which will do it. Simple feedback
> mechanisms installed on the user-end, special training to moderators
> (maybe) are some I can think of. Like back at Mozilla, moderators keep
> marking and flagging posts that need changes and they also give a reason.
> Now of course, that's a browser website, so most stuff are like "update it
> after new bug release" or "add more details to this page" or "add a Linux
> screenshot of the remove history dialog box" etc. but I guess that's still
> a cool mechanism. In fact, I've edited many docs on the basis of the same
> Need Changes page at Mozilla.
>
> I guess we need more discussion?
>
> ---
> </Abhimanyu>
>