(Initial Document) |
(Add Miro Hrončok into Development team) |
||
| Line 37: | Line 37: | ||
[[User:Cverna|Clement Verna]] | [[User:Cverna|Clement Verna]] | ||
[[User:Churchyard | Miro Hrončok ]] | |||
== Assumptions and Questions== | == Assumptions and Questions== | ||
Revision as of 11:42, 26 February 2019
Document Details
- Status:WORKING DRAFT:
- Point of contact: Clément Verna
- Implementation Schedule: TBD
- Release Date: TBD
Goals
Fedora Badges has not been actively developed for a few years now. This document aims to define the steps needed to give a second life to the project by identifying the technical blockers that slow down Fedora Badges development within the Fedora community. This document should also help with the gathering of ideas on how to improve Fedora Badges and or new possible features.
Fedora Badges has been developed and maintained by the Fedora Engineering Team (now Community Platform Engineering ) but one of the goal of this work is to make the maintenance and development of the application easier to allow more engagement from the community.
People involved
There is already a strong community of designer involved in the project, we need to build a stronger community around the application development and maintenance. Anybody willing to help in welcome ;-)
Designers
Development & Maintenance
Assumptions and Questions
Are there any assumptions for completing this work?
Initial Stories
A minimum user story list should be prepared here to facilitate Task Breakdown. The user story describes the type of user, what they want and why. A user story helps to create a simplified description of a requirement. Format should be:
As a < type of user >, I want < some goal > so that < some reason >.
Personas
- Designer : A designer is creating artwork associated to a badge.
- Administrator : A user that can create, give, edit, delete badges
- Contributor: A user that would like to create a new badge.
- Developer: Someone that develop and maintain the application.