From Fedora Project Wiki
(start of new feature)
 
mNo edit summary
Line 4: Line 4:
<!-- The actual name of your feature page should look something like: Features/Your_Feature_Name.  This keeps all features in the same namespace -->
<!-- The actual name of your feature page should look something like: Features/Your_Feature_Name.  This keeps all features in the same namespace -->


= Features/DevelopersSetup =
= Features/ProjectSetupScripts =


== Summary ==
== Summary ==

Revision as of 08:52, 24 January 2013


Features/ProjectSetupScripts

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 mainly for beginners. The idea is install yum group, which will contain all development tools needed for the language (essential things) and setup skeleton project. It can contain syntax hightlight in vim, typical build tools, ...

After the project is created it can be by helper packed as rpm and sent to koji (if devel has FAS account). In future can be these tools used as backend for Eclipse plugins or other developer IDE. Also setting of deployment could be based on those scripts.

Languages:

  • C (phracek)
  • Ruby (vondruch)
  • Python (bkabrda)
  • Perl (mmaslano)
  • Java
  • 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, 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