On 12/10/2013 01:33 PM, Michael K. Johnson wrote:
On Mon, Nov 18, 2013 at 08:40:38AM +0100, Mark Trompell wrote:
So we're down to the crossroad I feel, where we have to quickly decide
where we are heading. Do we want do revive foresight and jump on the
fl3 train or do we want to go on with our lifes and let foresight die.
Here's my problem: I know I will personally have limited time
available to participate in this process. So I would suggest doing
this only in concert with developers now at SAS who were previously
at rPath. In order to make this proposal, I'd need to know who of
the Foresight developers would be willing to run the import process,
noting and investigating failures in the import process, and working
through updates and fixes with those developers. To propose this
internally, I'd need to know who was volunteering to work on the
import process.
So: If you care enough about this that you'd be willing to help
drive the import process and help isolate bugs in the import process
so that we can build on top of an existing base, please respond,
either to the list or privately to me, so that I can propose this
internally at SAS.
Hello,
Count me in. Don't know how much time I will get though.
As me and my wife just got a baby boy recently. But will help out as
much as I can.
// Tomas Forsman
_______________________________________________
Foresight-devel mailing list
[email protected]
https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
