Mozillians/TaskBoard: Difference between revisions
Line 23: | Line 23: | ||
'''Current Avenues''' | '''Current Avenues''' | ||
* Bugzilla - Using Bugzilla's REST API, the app will grab any bugs with the whiteboard entry of "[good first bug]" and display information (i.e. mentor, product/component, timelines/deadlines, coding experience needed, etc.) as necessary. | * Bugzilla - Using Bugzilla's REST API, the app will grab any bugs with the whiteboard entry of "[good first bug]" and display information (i.e. mentor, product/component, timelines/deadlines, coding experience needed, etc.) as necessary. | ||
* GitHub - Using GitHub's issue API | * GitHub - Using [http://developer.github.com/v3/issues/ GitHub's issue API], we should show any issues shown on /mozilla organization repos within the taskboard. | ||
=== Administration === | === Administration === | ||
* add, edit, remove (their own and all) | * add, edit, remove (their own and all) |
Revision as of 18:22, 11 November 2011
Summary
Mozilla's sub-communities of Add-ons, QA, L10n, Support and more have been good at providing opportunities to those who find their way into them. This approach works for new and potential contributors who know what sort of tasks they'd like to work on. Though, for those who are unsure of what they would be interested or skilled to help with, it's not particularly helpful. So, the idea is to uplift basic introductory tasks across all sub-communities into a public-facing list of activities which are sortable and filterable list (i.e. much like a Job Board).
Goals
- Increase the number of tasks completed within the Mozilla community
- Increase the number of contributors performing tasks within the Mozilla community
- Increase contributors awareness of sub-community tasks
Non-Goals
- Become the taskboard for all tasks in the entire Mozilla community
Features
List Options
- fields shown, filters, sorting options
Task Vacuum
The Mozilla community has a number of avenues which offer contributors tasks to get involved (e.g. Bugzilla's "good first bugs", SUMO's "un-answered threads", AMO's "add-ons not reviewed"). Further, we have external project-hosting sites such as Github that have a number of issue trackers which are still tasks to perform in the Mozilla community. We don't need to re-invent the wheel and force team leads and community leads to create new tasks within this app; these tasks should be automagically populated onto the list (and off when they're completed).
Current Avenues
- Bugzilla - Using Bugzilla's REST API, the app will grab any bugs with the whiteboard entry of "[good first bug]" and display information (i.e. mentor, product/component, timelines/deadlines, coding experience needed, etc.) as necessary.
- GitHub - Using GitHub's issue API, we should show any issues shown on /mozilla organization repos within the taskboard.
Administration
- add, edit, remove (their own and all)