Betafarm/Roadmap: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 11: Line 11:
__NOTOC__
__NOTOC__


== Get Involved ==
Our code is in [[Github|https://github.com/mozilla/betafarm]]. We are using Github issues and [[Pivotal Tracker|https://www.pivotaltracker.com/projects/284775]] to track our work. Discussion about Betafarm should be directed to the Mozilla Labs [[Google Group|http://groups.google.com/group/mozilla-labs]].
== Features ==


== Get Involved ==
There are a number of features we would like to see in Betafarm:
 
* Projects should be able to host a plugin or demo directory to showcase work done by project and community members.
* Drumbeat.org hosted a series of challenges for the [[Knight Mozilla News Technology Partnership|https://drumbeat.org/en-US/journalism/]]. This functionality should be ported to Betafarm so that projects can launch challenges to collect ideas and feedback from the community.
* Enhancements to the Events section of Betafarm. A user should be able to find events in their area, and RSVP to those events, possibly integrating with a 3rd party event management system (e.g. Lanyrd, EventBrite).
* Users should be able to search projects, users, events, etc.
* Projects should be able to specify ways that people can get involved (e.g. testers, developers). Users should be able to easily find interesting projects that they can meaningfully contribute to.
 
== Q3 Priorities ==
 
=== Plugin / Demo directory ===
* Projects should be able to enable a directory that will appear in the subnav of their project page.
* Users should be able to submit a demo / plugin / extension to be considered for inclusion in the directory.
* Project members should be able to approve or reject user submissions.


== Product Priorities ==
== Q4 Priorities ==
* Plugin / Demo Directory for Projects
* Port challenges functionality from Drumbeat to Betafarm
* Enhancements to Event management


=== Challenge functionality ===
* Project members should be able to launch a challenge. A challenges has a title, description, guidelines for submissions, and a start date / end date.
* Users can make submissions to a challenge. A submission has a title and description. The description should allow some limited HTML with support for image uploads and video embedding.
* Some mechanism should be provided for reviewing challenge submissions and selecting a winner or winners.


== Q3 2011 ==
=== Event Enhancements ===
* Plugin / Demo directory
* A user should be able to easily discover events in their area.
* Event enhancements
* A user should be able to filter events by location and date.
* Event functionality should integrate with a popular 3rd party event management system if possible (e.g. EventBrite, Lanyrd, Plancast).


== Q4 2011 ==
=== Search ===
* Challenge functionality
* As the list of projects, blog posts, users, events, challenges with a presence on Betafarm grows, it'll become necessary to allow users to search and filter.
* Port from drumbeat.org with Dan Sinker and Dees as stakeholders
* Consider categories and tags for projects, users, events, etc.
* Search should be intuitive. If a user starts typing "Project", we should assist by auto-populating a keyword that limits the results to projects (for example).

Revision as of 03:31, 17 August 2011

LabsLogo.png Betafarm Roadmap
Owner: Paul Osman Updated: 2011-08-17

Betafarm is the new home for Mozilla Labs, Foundation and Research projects on the web. It is an attempt to present a single reference point for all innovation projects at Mozilla.

Betafarm is written in Python and uses the Django web application development framework.


Get Involved

Our code is in https://github.com/mozilla/betafarm. We are using Github issues and https://www.pivotaltracker.com/projects/284775 to track our work. Discussion about Betafarm should be directed to the Mozilla Labs http://groups.google.com/group/mozilla-labs.

Features

There are a number of features we would like to see in Betafarm:

  • Projects should be able to host a plugin or demo directory to showcase work done by project and community members.
  • Drumbeat.org hosted a series of challenges for the https://drumbeat.org/en-US/journalism/. This functionality should be ported to Betafarm so that projects can launch challenges to collect ideas and feedback from the community.
  • Enhancements to the Events section of Betafarm. A user should be able to find events in their area, and RSVP to those events, possibly integrating with a 3rd party event management system (e.g. Lanyrd, EventBrite).
  • Users should be able to search projects, users, events, etc.
  • Projects should be able to specify ways that people can get involved (e.g. testers, developers). Users should be able to easily find interesting projects that they can meaningfully contribute to.

Q3 Priorities

Plugin / Demo directory

  • Projects should be able to enable a directory that will appear in the subnav of their project page.
  • Users should be able to submit a demo / plugin / extension to be considered for inclusion in the directory.
  • Project members should be able to approve or reject user submissions.

Q4 Priorities

Challenge functionality

  • Project members should be able to launch a challenge. A challenges has a title, description, guidelines for submissions, and a start date / end date.
  • Users can make submissions to a challenge. A submission has a title and description. The description should allow some limited HTML with support for image uploads and video embedding.
  • Some mechanism should be provided for reviewing challenge submissions and selecting a winner or winners.

Event Enhancements

  • A user should be able to easily discover events in their area.
  • A user should be able to filter events by location and date.
  • Event functionality should integrate with a popular 3rd party event management system if possible (e.g. EventBrite, Lanyrd, Plancast).

Search

  • As the list of projects, blog posts, users, events, challenges with a presence on Betafarm grows, it'll become necessary to allow users to search and filter.
  • Consider categories and tags for projects, users, events, etc.
  • Search should be intuitive. If a user starts typing "Project", we should assist by auto-populating a keyword that limits the results to projects (for example).