From Fedora Project Wiki
No edit summary
Line 39: Line 39:
* Targeted release: [[ Fedora 20 ]]  
* Targeted release: [[ Fedora 20 ]]  
* Last updated: 2013-07-15
* Last updated: 2013-07-15
* Percentage of completion: 50%
<!-- 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 47: 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: <will be assigned by the Wrangler>


== Detailed Description ==
== Detailed Description ==
Line 57: Line 57:
== 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
* Proposal owners:
* all information will be taken from devassistant engine
<!-- 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?-->
** selecting type of project per language
 
** specification project path and name
* Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
** specification what extension will be used during project generation
<!-- 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?-->
** showing log window with all actions in tree dialog
 
* 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 91: Line 85:
<!-- 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 -->
N/A (not a System Wide Change)
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


Line 107: Line 100:


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)
Man pages will be primary source for documentation.


== Release Notes ==
== Release Notes ==

Revision as of 10:14, 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.


Developer Assistant GUI

Summary

The feature aims to provide GUI for back end devassistant package.

Owner

Current status

  • Targeted release: Fedora 20
  • Last updated: 2013-07-15
  • Percentage of completion: 50%

Detailed Description

This feature aims to provide GUI front end for back end devassistant package which is command line utility.

Benefit to Fedora

Make the development on Fedora easier for beginners from window managers

Scope

  • creating wizard for each specific part for devassistant backend
  • all information will be taken from devassistant engine
    • selecting type of project per language
    • specification project path and name
    • specification what extension will be used during project generation
    • showing log window with all actions in tree dialog

Upgrade/compatibility impact

How To Test

Try to install package containing setup for your favourite language.

User Experience

Developer Assistant GUI will be GUI tool for faster setting projects based on devassistant backend

Dependencies

devassistant package

Contingency Plan

Do not ship the result if not ready. Since the feature is not required for anything else in the system, there will be no complications if not shipped.

Documentation

Man pages will be primary source for documentation.

Release Notes

Developer Assistant GUI feature will provide graphical user interface for back end devassistant feature [[ https://fedoraproject.org/wiki/Features/DevelopersAssistant ]]

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/DeveloperAssistantGUI&oldid=344929"