On Tue, Dec 10, 2013 at 01:33:11PM -0500, Michael K. Johnson wrote: > 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.
how would this happen practically? i suppose there would be an rmake instance running the jobs and all developers have access to that to be able to watch it and report the issues? > 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. my time is also limited, but i am willing to help. greetings, martin. -- eKita - the online platform for your entire academic life hackerspace beijing - http://qike.info -- chief engineer eKita.co pike programmer pike.lysator.liu.se caudium.net foresight developer realss.com foresightlinux.org unix sysadmin trainer developer societyserver.org Martin Bähr working in china http://societyserver.org/mbaehr/ _______________________________________________ Foresight-devel mailing list [email protected] https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
