From Fedora Project Wiki
< Changes
No edit summary |
|||
| (11 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
<!-- Self Contained or System Wide Change Proposal? | <!-- Self Contained or System Wide Change Proposal? | ||
Use this guide to determine to which category your proposed change belongs to. | Use this guide to determine to which category your proposed change belongs to. | ||
| Line 42: | Line 40: | ||
* 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 48: | ||
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: [https://bugzilla.redhat.com/show_bug.cgi?id=998501 #998501] | |||
DeveloperAssistant GUI is done on the base of facelift discussion. | |||
Current problem is with cancelling of job (SOLVED) | |||
DeveloperAssistant creator GUI started. | |||
Basic draft of design will done during two weeks. | |||
== Detailed Description == | == Detailed Description == | ||
This feature aims to provide GUI frontend for devassistant package which currently only works on commandline. | This feature aims to provide GUI frontend for devassistant package which currently only works on commandline. | ||
Developer Assistant GUI is separated into three parts: | |||
Main GUI page contains matrix of languages and their subassistans (if are available). User see tooltips | |||
like what each language does. | |||
Next page contains information needed for project creation like project name, directory where project will be stored | |||
and several options (optional) which can be processed during the project creation. | |||
Options are provided by devassistant engine. | |||
The last page is log window where user see what action is currently processing and what actions were done. | |||
The project creation process can be stop by user request. | |||
After project creation user can look on github page (if was selected) and see what was uploaded into GitHub server. | |||
== Benefit to Fedora == | == Benefit to Fedora == | ||
| Line 60: | Line 79: | ||
== 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 | |||
** GUI for creating assistants and checking with some yaml checker. | |||
* 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 89: | Line 117: | ||
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | <!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
Developer Assistant GUI will be GUI tool for faster setting projects based on devassistant backend | Developer Assistant GUI will be GUI tool for faster setting projects based on devassistant backend. | ||
== Dependencies == | == Dependencies == | ||
| Line 96: | Line 124: | ||
== 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 == | ||
| Line 105: | Line 135: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
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. | 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 == | == Release Notes == | ||
| Line 113: | Line 142: | ||
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze. | Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze. | ||
--> | --> | ||
Developer Assistant GUI feature will provide graphical user interface for generating new projects using devassistant [[ | Developer Assistant GUI feature will provide graphical user interface for generating new projects using devassistant [[Features/DevelopersAssistant]]. More in-depth release notes will be produced when we actually do the release. | ||
[[Category: | [[Category:ChangeAcceptedF20]] | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
Latest revision as of 08:48, 26 August 2013
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
DeveloperAssistant GUI is done on the base of facelift discussion.
Current problem is with cancelling of job (SOLVED)
DeveloperAssistant creator GUI started.
Basic draft of design will done during two weeks.
Detailed Description
This feature aims to provide GUI frontend for devassistant package which currently only works on commandline.
Developer Assistant GUI is separated into three parts: Main GUI page contains matrix of languages and their subassistans (if are available). User see tooltips like what each language does. Next page contains information needed for project creation like project name, directory where project will be stored and several options (optional) which can be processed during the project creation.
Options are provided by devassistant engine.
The last page is log window where user see what action is currently processing and what actions were done. The project creation process can be stop by user request.
After project creation user can look on github page (if was selected) and see what was uploaded into GitHub server.
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
- GUI for creating assistants and checking with some yaml checker.
- 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 Features/DevelopersAssistant. More in-depth release notes will be produced when we actually do the release.