Features/DevelopersAssistant

From FedoraProject

< Features
Revision as of 12:16, 24 January 2013 by Mmaslano (Talk | contribs)

Jump to: navigation, search


Contents

Features/DevelopersAssistant

Summary

Owner

  • Email: <jzeleny@redhat.com>
  • Email: <mmaslano@redhat.com>

(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.


Languages:

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

Benefit to Fedora

Make the development on Fedora easier for beginners.

Scope

  • Adding new (leaf) packages, which will contain setup scripts.
  • Comps - there will be new groups or adjustment of groups, which can make installation of developer tools for various languages easier.

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.

Dependencies

None needed at the moment.

Contingency Plan

Do not ship it if not ready.

Documentation

There will be blog posts.

Release Notes

Will be prepared.

Comments and Discussion