Added by Ken VanDine, last edited by António Meireles [aka doniphon] on Jun 14, 2010  (view change)

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 deliver a polished Desktop Linux end-user experience 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 focused around GNOME, but an Xfce respin is also offered (Mark Trompell)
and a KDE SC group is also available.

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.

Status and Roadmap

In August of 2009, we began focusing on getting 2.1.2 ready for release. It was based around
the GNOME 2.26.x desktop and was slated to be the last release in the 2.1.x branch.

However, we had massive issues gettng the Fedora Core 8-era forked Anaconda installer version we use
to play nice with our newer kernel versions, which substantially delayed the respinning of new ISOs.

With GNOME 2.28 and GNOME 2.30 landing any minute out now, we have shifted focus towards Foresight Linux 2.3.x
(for a while referred to as 2.2), which will likely be the last version of FL based on rPath Linux.

Developer resources and communication

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

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
  • 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?