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 an idea to this page, read How to create an idea page for Summer Coding.
- 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 translude 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. | |||
oops.fedoraproject.org
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
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. | |||
DebuginfoFS integration with ABRT
QA:Summer Coding Ideas - DebuginfoFS integration with ABRT
Mediawiki QA improvements
QA:Summer Coding Ideas - Mediawiki QA improvements
Create AutoQA unit test suite
QA:Summer Coding Ideas - Create AutoQA unit test suite
Create python-bugzilla unit test framework
QA:Summer Coding Ideas - Create python-bugzilla unit test suite
Create kexec/kdump built-in unit test suite
QA:Summer Coding Ideas - Create kexec/dump unit test suite
Integrate QA metrics into Fedora Community portal
QA:Summer Coding Ideas - Integrate QA metrics into Fedora Community Portal