OpenFATE/Screening team
From openSUSE
< OpenFATE
The openFATE screening team wants to keep openFATE as efficient as possible to assure best outcome for our distribution openSUSE. We're currently in the process of creating this team and are happy to attract more people to help here. Discussion will held at opensuse-project (at least for the beginning).
Contents |
[edit]
Tasks
- Feature screening
- check feature requests for duplicates
- Go through the list of unconfirmed features, get them into shape and set them to state new, so that a reasonable decision can be made, and all information is there to start an implementation.
- while screening check tags and add or remove tags where necessary (untagged features can be found here)
- does a feature lack important information
- Documentation
- set up a guide line how to use openFATE
- create/edit documentation where necessary
- Quality Assurance
- find people implementing features (features tagged "community effort")
- call for feature voting in a certain period to make clear which features are of high importance for the community
- Feedback
- find areas where openFATE should be improved
- work together with openFATE developers (contact: featureadmin at suse.de)
[edit]
Community Week (May 11-17)
- general presentation about openFATE
[edit]
What's missing to make the screening team efficiently work?
- team members need to get additional rights (eg. changing status of a feature, set people as info provider)
- implement an forwarding Service in openFATE. So the Screening Team can forward Features as Email.
we should create an List with possible Tags. I think we have different Tags as duplicate or namend similar.(All tags link in the tagcloud)
[edit]
Bi-weekly openFATE screening team meeting
Feel free to join our a bi-weekly team meeting in in IRC: Freenode channel #opensuse-project normally at 12pm UTC and is scheduled for 1 hour. For the next meeting and topics please look here
See the report of our March 18, 2009 report on mailing list archives.
[edit]

