Webdev/Web Production/Community: Difference between revisions

No edit summary
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
[[Category:Webdev|Processes]]
[[Category:Webdev|Processes]]
{{LastUpdated}}
{{LastUpdated}}
{{Draft}}


== Background ==
== Background ==
Line 15: Line 14:
** [[Webdev/Web_Production/Community/Conversion Points|Conversion Points]]
** [[Webdev/Web_Production/Community/Conversion Points|Conversion Points]]


== ToDos ==
== Meetings! ==
A spot for things without a spot.
* [https://romana.etherpad.mozilla.org/2014-09-25-community 2014-09-25 Check-In]
* [https://romana.etherpad.mozilla.org/2014-07-25-community 2014-07-25 CBT Check-In]
* [https://romana.etherpad.mozilla.org/2014-07-21-community 2014-07-21 WebProd Community Initial Meeting]


Alex had some great suggestions on the above -- which I am capturing here until we figure out exactly what we want to do.
== Project Task Board ==
[https://mozilla.kanbanery.com/projects/35030/board/?key=b652aaa1d5028c0bf5a335b7e0f7f1e7955a8ff8 Public Kanban Board]


# Contribute wiki and project hubs are duplicative and confusing. Suggest contribute wiki be much simpler and move/organize this content onto the project hubs.
== ToDos ==
# Based on the above project hubs could do with some cleaning up.
[https://romana.etherpad.mozilla.org/Community-Outstanding-Issues Outstanding Issues Etherpad]
# We will need a way of explaining easily to new contributors how a task goes from card to live code. We will need to touch on bugzilla and kanbanery
# Github presents an untapped areas for new contributors. Our github repos are not very friendly nor do they drive contributions -- they do the opposite. "If people are looking at our repos whats the best way to get the to contribute"
canmove, Confirmed users
2,745

edits