Everyone,

I've been sidetracked by IRL and haven't had the mojo to get the minutes
from the last Focus meeting done. And since a few of you have asked for
them, and since eMBee suggested that I posted the log, here it is along
with my summary (I don't know if the list scrubs attachments):

* Michael K. Johnson's proposal[1] for making 'Boots, a Fedora Remix' a
Foresight sub project was accepted 4-1. This means that Boots will be
hosted on Foresight infra, which should make it easier for non-rPath
people to contribute.

** Paul Cutler mentioned that it is imperative that we clearly
differentiate FL3 (from source) from Boots (binary import) in our
marketing.

** As part of the Boots discussion, Ken expressed interest in creating a
Ubuntu Remix similar to Boots. Paul Cutler noted that perhaps it would
be wise to just focus on Boots for now and put the experience gained
there to use for a future Ubuntu binary import.


* 2.1.2 ISO release: Given how old our current Anaconda installer is and
the resulting install issues on newer hardware, António would prefer to
not release an ISO for 2.1.2 and instead focus on getting Anaconda up to
speed so that we can do a nice 2.2 release w/GNOME 2.28. We will likely
do 2-qa/2-devel cuts to make sure we have a working installer.

** In the mean time, Mark Trompell and elliot are making progress with
updating Anaconda

** As part of that discussion, there was talk of making the GNOME Dev
Kit easily installable in /opt in Foresight, possibly as a package and
perhaps even with an easy KVM setup. Currently, the GDK is short on
man-power, so if we want to make it a vector for new Foresight
developers, we need to lend jesse and bertux a hand.

**  Ken voiced his support for the short term goal of focusing on
growing the developer base (power users and developers), with the
understanding that the long term goal is still to make a distribution
for the end user that 'just works'.


* Ken asked for the opportunity to detail how his priorities have
changed, which as we know has left him with less time to work on
Foresight. This will not change for the foreseeable future, but he
insisted that he still loves Foresight and that he still considers it
'his baby' as he put it.


* The vote for giving members @foresightlinux.org mail-addresses and 
let them speak on behalf of Foresight-the-project was postponed after it
became clear that there isn't consensus on the distinction between being
a developer and a member. It was decided to have a discussion on the
-devel ML on building the community instead for the time being.


* It was decided to migrate the User Guide to the new GNOME
documentation tool/format (Mallard) and moving it to a dvcs. Og Maciel
has stepped forward and made the UG available at
http://github.com/omaciel/foresight-user-guide/tree/master - Paul Cutler
noted that he won't be able to drive the effort due to other commitments
but will be happy to share his expertise if we have questions.  The
current UG is in maintenance only mode (version increases, links to
online content).

_______________________________________________
Foresight-devel mailing list
Foresight-devel@lists.rpath.org
http://lists.rpath.org/mailman/listinfo/foresight-devel

Reply via email to