Interested in getting involved in Fedora QA? In addition to the many existing ways to get involved with QA, this page outlines new project ideas looking for an owner. The format of this page follows that used in Category:Summer_Coding_2010_ideas.
Process
- Think in terms of use cases
- If you provide a use case and some ideas of how to solve, you give more room for students to put in their own ideas and passion.
- Consider if that is possible for each of your project ideas.
- Prepare a project idea page
- Project pages are transcluded below
- To learn how to add this page see the example below, and refer to Template:Summer of Code Idea
- Use talk page to discuss ideas and proposals.
- Use the discussion tab (Talk:Name of idea) page for all discussion about an idea.
- Idea pages should be renamed as proposals when accepted, and all discussion about the proposal should also go in the talk page.
Idea page sample
Use the following syntax to define and transclude your idea to this page.
{{:QA:Summer Coding Ideas - Idea page sample}}
For example, using the above syntax would include the following page information.
Idea page sample
Status | Contact | Mentor | Skills |
---|---|---|---|
UNASSIGNED | rhe | kparal | python, unittest module |
Description | |||
This is sample summer of code. High level summary of the idea should go here. |
Ideas
Graphics card metrics gathering from SMOLT
Status | Contact | Mentor | Skills |
---|---|---|---|
UNASSIGNED | nobody | adamwill | Database and light scripting skills to massage data |
Description | |||
The smolt hardware profiler tool stores a wealth of information about Fedora systems at http://smolts.org. The current VIDEO device views do not provide a level of detail needed to assist decision making when a bug is filed. For instance, if a bug is filed against a particular video adapter, it's not possible to determine how many registered smolt users that bug would impact or what range of sub-devices might be affected by the issue. Having a better view into the SMOLT data would also be very helpful when developing test plans and providing test coverage metrics. For additional information, see blog post and list post for details.
|
Build oops.fedoraproject.org problem reporting site
Status | Contact | Mentor | Skills |
---|---|---|---|
UNASSIGNED | nobody | wwoods | python, TurboGears, web development |
Description | |||
More details |
Automate Packaging Review Guidelines
Status | Contact | Mentor | Skills |
---|---|---|---|
IDEA | jlaska | jlaska | basic python and bash programming, rpm |
Description | |||
Including new software in Fedora involves a submission process to assess how well the software is packaged according to the packaging guidelines. The packaging guidelines are exhaustive, and it's far too much for a reviewer to remember each and every step. Especially a new fedora package contributor. Many of the review steps are items for which a script or automated test could be performed by the packager (or package reviewer). It seems like it would be beneficial to provide a more consistent package review experience by automating many steps of the package review process, and possibly adjust the workflow to support packagers self-reviewing their packages using the script. |
QA:Summer Coding Ideas - DebuginfoFS integration with ABRT
QA:Summer Coding Ideas - Mediawiki QA improvements
QA:Summer Coding Ideas - Create AutoQA unit test suite
QA:Summer Coding Ideas - Create python-bugzilla unit test suite
QA:Summer Coding Ideas - Create kexec/dump unit test suite
QA:Summer Coding Ideas - Integrate QA metrics into Fedora Community Portal
AutoQA detect false positives
Status | Contact | Mentor | Skills |
---|---|---|---|
IDEA | nobody | nobody | python, searching best solutions, working with big data-sets |
Description | |||
Generally this task would be about going through all the false positives AutoQA reported and figuring a method how not to run into the issue again and how to detect, if something changes. AutoQA needs to filter out this issues and not report them. |
AutoQA interface to other Fedora systems
Status | Contact | Mentor | Skills |
---|---|---|---|
IDEA | nobody | nobody | python |
Description | |||
Add possibility for AutoQA to interact with other Fedora systems like Bugzilla and Bodhi. Investigate AutoQA process, suggest best places and possibilities to implement it, incorporate feedback and if needed get involved in other projects to get required functionality implemented. |
AutoQA add anti-virus check
Status | Contact | Mentor | Skills |
---|---|---|---|
IDEA | nobody | nobody | python |
Description | |||
Use clamav anti-virus checker to extend chains of checks in AutoQA. Explore AutoQA process and include this test into the relevant part of it. |
Improve rpmguard
Status | Contact | Mentor | Skills |
---|---|---|---|
UNASSIGNED | kparal | kparal | python programming, rpm |
Description | |||
rpmguard is a tool for comparing two RPM packages and printing important differences between them. The basic functionality works, but there are a lot of things that could be improved. Short list is in here, but is it possible to think up any further suitable improvement. |
Popularity contest for Fedora
Status | Contact | Mentor | Skills |
---|---|---|---|
UNASSIGNED | nobody | nobody | rpm, ? |
Description | |||
Implement something like Debian Popularity Contest (Ubuntu) for Fedora. Read more at devel-list. |