2014-03-06

‎Requirements

← Older revision

Revision as of 01:43, 6 March 2014

Line 34:

Line 34:

 

*'''news page.''' ("...a spot this can link to...") An IdeaLab/News page, manually edited. Looks like one already exists at IdeaLab/Events, but it is not yet surfaced on the main page.

 

*'''news page.''' ("...a spot this can link to...") An IdeaLab/News page, manually edited. Looks like one already exists at IdeaLab/Events, but it is not yet surfaced on the main page.

 

*'''easy sharing.''' The commons.wiki POTY system allows people to share to social media by clicking on a button. We can look in to how they do it. We might also want to create simple pre-formatted text announcements that could be copy/pasted onto other wikis.

 

*'''easy sharing.''' The commons.wiki POTY system allows people to share to social media by clicking on a button. We can look in to how they do it. We might also want to create simple pre-formatted text announcements that could be copy/pasted onto other wikis.

 

+

<hr/>

 

 

 

===Role and skills ===

 

===Role and skills ===

Line 47:

Line 48:

 

*Selected skills are attached to their IdeaLab profile (as badges, attached to categories or some other tagging system?)

 

*Selected skills are attached to their IdeaLab profile (as badges, attached to categories or some other tagging system?)

 

*Ability to adjust roles on someone else's profile is also appreciated (ie, Siko adds committee tags to new member profiles, and changes past members to contributor status)

 

*Ability to adjust roles on someone else's profile is also appreciated (ie, Siko adds committee tags to new member profiles, and changes past members to contributor status)



 

 

 

 

;Design notes

 

;Design notes

Line 54:

Line 54:

 

:*Adding/removing badges after you’ve created your profile may need to be a more manual process, to give users the fine-grained control they expect. We may be able to make it easier by preloading an editintro with helpful instructions when you edit your profile.

 

:*Adding/removing badges after you’ve created your profile may need to be a more manual process, to give users the fine-grained control they expect. We may be able to make it easier by preloading an editintro with helpful instructions when you edit your profile.

 

:*Skill badges could the same architecture as role badges. However, skills should not be constrained the same way roles are, and we don’t want to create category cruft. Potentially a Lua template could parses wikitext in the ‘skills’ parameter of a profile and then list skills elsewhere.

 

:*Skill badges could the same architecture as role badges. However, skills should not be constrained the same way roles are, and we don’t want to create category cruft. Potentially a Lua template could parses wikitext in the ‘skills’ parameter of a profile and then list skills elsewhere.

 

+

<hr/>

 

 

 

===Making content and people easy to find ===

 

===Making content and people easy to find ===

Line 68:

Line 69:

 

*Dynamic searching/sorting could be accomplished with a gadget like [[commons:Help:FastCCI|FastCCI]] (code [https://github.com/Commonists/fastcci here]). That may be costly to develop. We can probably create engaging reports of Ideas/People/Categories using Lua, or Lua + GrantsBot. These would be easy to keep up to date, and easy to browse, but not dynamic quite the same way.

 

*Dynamic searching/sorting could be accomplished with a gadget like [[commons:Help:FastCCI|FastCCI]] (code [https://github.com/Commonists/fastcci here]). That may be costly to develop. We can probably create engaging reports of Ideas/People/Categories using Lua, or Lua + GrantsBot. These would be easy to keep up to date, and easy to browse, but not dynamic quite the same way.

 

**'''Listing roles on ideas.''' This should be straightforward to do with a structured idea-creation workflow (probably using a GuidedTour). People set what roles they need when they create their idea (filling in form fields instead of template parameters). This adds a category to the page (like we have now): "Ideas that need developers" or something.

 

**'''Listing roles on ideas.''' This should be straightforward to do with a structured idea-creation workflow (probably using a GuidedTour). People set what roles they need when they create their idea (filling in form fields instead of template parameters). This adds a category to the page (like we have now): "Ideas that need developers" or something.



+

<hr/>

 

 

 

=== Join, endorse, and comment ===

 

=== Join, endorse, and comment ===

Line 84:

Line 85:

 

*Would be great if we could allow them to change their username to their home wiki instead if they prefer

 

*Would be great if we could allow them to change their username to their home wiki instead if they prefer

 

*When they hit submit, their name and comment are added to the list of endorsements

 

*When they hit submit, their name and comment are added to the list of endorsements



 

 

 

 

;Design notes

 

;Design notes

Line 93:

Line 93:

 

*'''Commenting on an idea.''' The talk page works fine here, but we should have strong calls to action to encourage people to comment, especially if they have ''joined'' or ''endorsed''.

 

*'''Commenting on an idea.''' The talk page works fine here, but we should have strong calls to action to encourage people to comment, especially if they have ''joined'' or ''endorsed''.

 

*'''Endorsing an idea.''' Would also be good to add the page to someone's watchlist. Endorsements should be listed as timestamped signatures. Could also display these in aggregate somewhere on the idea page in a counter, or elsewhere on the IdeaLab as part of a dashboard. This should be doable in Lua.

 

*'''Endorsing an idea.''' Would also be good to add the page to someone's watchlist. Endorsements should be listed as timestamped signatures. Could also display these in aggregate somewhere on the idea page in a counter, or elsewhere on the IdeaLab as part of a dashboard. This should be doable in Lua.



+

<hr/>

 

 

 

===Recognition===

 

===Recognition===

Line 105:

Line 105:

 

*'''Recognition for joiners.''' List projects they have joined in their profile (best to do this automatically). How can this be accomplished at low cost?

 

*'''Recognition for joiners.''' List projects they have joined in their profile (best to do this automatically). How can this be accomplished at low cost?

 

*'''Recognition for commenters.''' If they have a profile, include counts of ideas they have commented on. If no profile, TBD

 

*'''Recognition for commenters.''' If they have a profile, include counts of ideas they have commented on. If no profile, TBD

 

+

<hr/>

 

 

 

===Creating an idea===

 

===Creating an idea===

Line 119:

Line 120:

 

*The [[mw:Extension:GuidedTours|Guided Tours]] extension seems ideally suited for use as an Idea-creation [[w:Wizard_(software)|wizard]]. Using a structured workflow like this will allow us to help people complete all the complex steps necessary to set up a good proposal. It also allows us to "show them around" the Idea page, and suggest next steps. Full spec in progress on the Build/Tools page.

 

*The [[mw:Extension:GuidedTours|Guided Tours]] extension seems ideally suited for use as an Idea-creation [[w:Wizard_(software)|wizard]]. Using a structured workflow like this will allow us to help people complete all the complex steps necessary to set up a good proposal. It also allows us to "show them around" the Idea page, and suggest next steps. Full spec in progress on the Build/Tools page.

 

*This is high priority work for both design and development: if this is the only new tool we create during this sprint, we will still have substantially improved the lab.

 

*This is high priority work for both design and development: if this is the only new tool we create during this sprint, we will still have substantially improved the lab.

 

+

<hr/>

 

 

 

===Kit for growing ideas into project plans===

 

===Kit for growing ideas into project plans===

Line 135:

Line 137:

 

:*the bot creates a PEG page with the same name, adds the relevant PEG page template, and dumps the relevant Idea text into it

 

:*the bot creates a PEG page with the same name, adds the relevant PEG page template, and dumps the relevant Idea text into it

 

:*when the category first appears on the Idea page, a banner is displayed on the page saying that this Idea is being submitted as a PEG, links to the PEG version of the page. This should be fairly straightforward in Lua.

 

:*when the category first appears on the Idea page, a banner is displayed on the page saying that this Idea is being submitted as a PEG, links to the PEG version of the page. This should be fairly straightforward in Lua.

 

+

<hr/>

 

 

 

===Learning & research===

 

===Learning & research===

Show more