Added by Ken VanDine, last edited by Michael K. Johnson on Apr 13, 2013  (view change) show comment

Labels:

roadmap roadmap Delete
todo todo Delete
release2 release2 Delete
developer developer Delete
goals goals Delete
resources resources Delete
releases releases Delete
Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.

Goals

The overarching development goal of Foresight Linux is to use Conary to deliver Linux to end users via incremental (rolling) – rather than strictly time based and monolithic – updates to the system, and to offer developers and packagers a pleasant and efficient platform with which to build and maintain their software of choice as well as custom respins.

The default desktop and development environment is currently focused on GNOME 2, but xfce and lxde environments are also maintained and available. GNOME 3 (and possibly Cinnamon) are contemplated in the relatively near future.

In general, we aim to stay as true as possible to the upstream Desktop Environments and try to keep distribution-specific patches to a minimum. The core parts of the Foresight Linux 2 platform are based on a combination of rPath Linux 2 and Fedora conventions and patches.

Status and Roadmap

Foresight Linux 2 continues to be maintained. The rPath Linux 2 base is no longer maintained, so to update packages from rPath Linux 2, they are promoted into Foresight and maintained in Foresight.

The next major release will be Foresight Linux 3. This will be a complete rebuild on a new repository to make it easy to mirror. It will provide the server-focused role originally met by rPath Linux 2 as well as the UI roles originally central to Foresight development.

Developer resources and communication

This section aims to help new developers to get a grasp on the fundamentals of developing with Foresight Linux.

  • Packaging explains everything needed to get started with creating/maintaining packages.
  • Foresight Linux 2.x - This document gives a high level overview of the development process in Foresight Linux 2.x
  • Testing Foresight
  • Licensing — Foresight's policy for software licensing

Discussing and monitoring development

  • Mailing-list: Foresight development and packaging discussion happens on the foresight-devel mailing-list
  • Commit-list: Commits to our repositories are tracked on the (read-only) foresight-commits mailing list / Atom feed
  • FITS: Changes in FITS are tracked on the (read-only) foresight-issues mailing list / Feeds
  • IRC channels on http://freenode.net for real time discussion:
    • #foresight-devel – primary developer hangout
    • #foresight-qa (bug days, doc-team etc.)
    • #conary – the conary developers monitor this channel
    • #foresight-alerts – aggregates Issues, Forum posts etc.
    • #foresight (user oriented channel)

Blockers

Critical Issues

Rather like to work on minor issues or even trival issues?