From Fedora Project Wiki

< Features

Revision as of 12:45, 24 January 2013 by Jzeleny (talk | contribs) (Contingency Plan)




  • Email: <>
  • Email: <>

(Please add yourself if you are responsible for some part of it).

Current status

  • Targeted release: Fedora 19
  • Last updated: 2013-1-23
  • Percentage of completion: 2%

Detailed Description

This feature aims on setting up development environment for various languages. Target groups include beginning developers but also experienced developers not used to GNU/Linux as well as experienced Linux developers not used to Fedora.

This feature will cover a basic set of tasks which will prepare Fedora for later additions. The first part of the feature is a review of comps groups which would lead to better granularity of package sets necessary for development in different languages. Another part is about providing tool or tools for simple start of a project in terms of creating project template based on different languages and/or frameworks which the project should use.

There are other optional activities like vim/eclipse/emacs/... plugins, integration of rpm build tools, .... These optional parts are not goal for F19 but they will be integrated in time.


  • C (phracek)
  • Ruby (vondruch)
  • Python (bkabrda)
  • Perl (mmaslano)
  • PHP
  • Java (msrb)
  • Javascript

Benefit to Fedora

Make the development on Fedora easier for beginners.


  • Adding new (leaf) packages, which will contain setup scripts.
  • Comps: a review of existing development-related package groups will take place
    • cleanup of some groups will be necessary
    • new groups might be created to meet the demand for per-language tool and library sets

How To Test

Try to install package containing setup for your favourite language.

User Experience

Entry barrier for development on Linux should be lower. Inexperienced users will be able to setup their development faster.


None needed at the moment.

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. Changes in comps groups will be consulted before pushed and if necessary, changes can be simply reverted.


There will be blog posts.

Release Notes

Will be prepared.

Comments and Discussion