From Fedora Project Wiki
< Changes
No edit summary |
No edit summary |
||
| Line 42: | Line 42: | ||
* Targeted release: [[ Fedora 20 ]] | * Targeted release: [[ Fedora 20 ]] | ||
* Last updated: 2013-07-15 | * Last updated: 2013-07-15 | ||
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | ||
Bugzilla states meaning as usual: | Bugzilla states meaning as usual: | ||
| Line 51: | Line 50: | ||
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | ||
--> | --> | ||
* Tracker bug: <will be assigned by the Wrangler> | |||
== Detailed Description == | == Detailed Description == | ||
| Line 60: | Line 60: | ||
== Scope == | == Scope == | ||
<!-- What work do the developers have to accomplish to complete the change in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do the developers have to accomplish to complete the change in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
* creating wizard for each specific part for devassistant backend | |||
* all information will be taken from devassistant engine | * Proposal owners: | ||
* | <!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
** | ** creating wizard for each specific part for devassistant backend | ||
** all information will be taken from devassistant engine | |||
* Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | |||
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | |||
* Release engineering: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | |||
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuid required? If a rel-eng ticket exists, add a link here. --> | |||
* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | |||
<!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. --> | |||
== Upgrade/compatibility impact == | == Upgrade/compatibility impact == | ||
| Line 96: | Line 104: | ||
== Contingency Plan == | == Contingency Plan == | ||
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | <!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | ||
* Contingency mechanism: None needed | |||
<!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | <!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | ||
* Contingency deadline: N/A (not a System Wide Change) | |||
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | <!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | ||
* Blocks release? N/A (not a System Wide Change), No | |||
== Documentation == | == Documentation == | ||
Revision as of 12:31, 15 July 2013
Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "edit" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "edit" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.
Developer Assistant GUI
Summary
The feature aims to provide GUI for devassistant package.
Owner
- Name: Petr Hracek
- Email: <phracek@redhat.com>
- Name: Bohuslav Kabrda
- Email: <bkabrda@redhat.com>
Current status
- Targeted release: Fedora 20
- Last updated: 2013-07-15
- Tracker bug: <will be assigned by the Wrangler>
Detailed Description
This feature aims to provide GUI frontend for devassistant package which currently only works on commandline.
Benefit to Fedora
Make development on Fedora easier for beginners who are afraid of/don't want to work with terminal.
Scope
- Proposal owners:
- creating wizard for each specific part for devassistant backend
- all information will be taken from devassistant engine
- Other developers: N/A (not a System Wide Change)
- Release engineering: N/A (not a System Wide Change)
- Policies and guidelines: N/A (not a System Wide Change)
Upgrade/compatibility impact
How To Test
Install "devassistant" package, run devassistant-gui and experiment.
User Experience
Developer Assistant GUI will be GUI tool for faster setting projects based on devassistant backend
Dependencies
Only devassistant package itself.
Contingency Plan
- Contingency mechanism: None needed
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), No
Documentation
Online documentation for GUI will be accessible at our current documentation site (https://developer-assistant.readthedocs.org), the same generated html documentation will also be accessible in a newly introduced devassistant-docs subpackage.
Release Notes
Developer Assistant GUI feature will provide graphical user interface for generating new projects using devassistant [[ https://fedoraproject.org/wiki/Features/DevelopersAssistant ]]. More in-depth release notes will be produced when we actually do the release.