Difference between revisions of "Roadmap"

From GNUstepWiki
Jump to navigation Jump to search
Line 1: Line 1:
'''GNUstep has no roadmap...!'''
+
The roadmap is a living document- if you're a maintainer, please update it with your plans.
  
Anyway, here is small list of what has to be done. Refine the list, prioritize and build the roadmap. Perhaps some checklist would help...
+
== GNUstep 1.0 ==
 +
* Current Base, Make, & Back
 +
* GUI
 +
** Complete coding on all existing classes.
 +
** Improve printing support.
 +
** Correct any severe bugs.
 +
** Remove any classes which are not going to be finished for or included in the 1.0 release.
 +
* Development Environment:
 +
** Gorm 1.0.x
 +
** ProjectCenter 0.4.x
 +
* User apps
 +
** GWorkspace 0.7.x
  
== Version 1.0 (proposal) ==
+
== GNUstep 1.1 ==
 
+
* Integration of Camaelon into gui
The GNUstep 1.0 is a meta-package that wraps together several frameworks, tools and applications together. There are two packages. One package serves as a runtime environment for users who would like to run GNUstep applications and tools. The other serves for developers.
+
* Integration of WildMenus into gui
 
+
* Breakup of gui and base into component libraries
=== GNUstep 1.0 - runtime ===
+
* Make GNUstep more compliant with the FHS as an option
 
+
* Better Windows support
* make 1.10.0
+
* Nib support in gui and Gorm
* base 1.10.1
 
* GUI 0.9.4
 
* back 0.9.4
 
 
 
* Camaelon x.x.x (?)
 
* GWorkspace x.x.x (?)
 
* Terminal.app x.x.x (?)
 
 
 
=== GNUstep 1.0 - development environment ===
 
 
 
* ''packages from the runtime environment''
 
* Gorm 0.9.0
 
* ProjectCenter 0.4.2
 
* EasyDiff x.x.x
 
 
 
== Version 1.1 ==
 
 
 
== Unsorted TODO ==
 
 
 
* ease installation process (see [[GNUstep Installation Process]])
 
** what are potential platforms?
 
** what are their possibilities of installation?
 
** how can installation be combined for several platforms (one installation package for more linux distros, for example)
 
** how to distribute binary packages?
 
** what should be in the binary package?
 
** how should be the binary package installed? where? what should be configurable during installation?
 
** how to cope with more than one GNUstep environments installed?
 
 
 
* make GUI work on MS windows (see [[Portability]])
 
** what is broken?
 
** what needs to be done?
 
** who is working on it?
 
 
 
* what is the objective of GNUstep GUI/AppKit 1.0?
 
** what is missing?
 
** what does not work?
 
 
 
* what is the objective of GNUstep core 1.0?
 
** what is missing?
 
** what does not work?
 
  
 +
== Some considerations for the future ==
 
* Include distcc as part of the GNUstep developement environment, somewhat akin to XCode's distributed compilation.
 
* Include distcc as part of the GNUstep developement environment, somewhat akin to XCode's distributed compilation.
** Put [http://www.distcc.org] distcc in LiveCD for intel, then we can have a GNUstep compilation farm easily.
 
 
[[Category:Project procedures]]
 

Revision as of 05:54, 26 November 2005

The roadmap is a living document- if you're a maintainer, please update it with your plans.

GNUstep 1.0

  • Current Base, Make, & Back
  • GUI
    • Complete coding on all existing classes.
    • Improve printing support.
    • Correct any severe bugs.
    • Remove any classes which are not going to be finished for or included in the 1.0 release.
  • Development Environment:
    • Gorm 1.0.x
    • ProjectCenter 0.4.x
  • User apps
    • GWorkspace 0.7.x

GNUstep 1.1

  • Integration of Camaelon into gui
  • Integration of WildMenus into gui
  • Breakup of gui and base into component libraries
  • Make GNUstep more compliant with the FHS as an option
  • Better Windows support
  • Nib support in gui and Gorm

Some considerations for the future

  • Include distcc as part of the GNUstep developement environment, somewhat akin to XCode's distributed compilation.