From pjotr.public14 at thebird.nl Sat Oct 24 10:55:20 2009 From: pjotr.public14 at thebird.nl (Pjotr Prins) Date: Sat, 24 Oct 2009 16:55:20 +0200 Subject: [BioLib-dev] Plan to 1.0 Message-ID: <20091024145520.GA5075@thebird.nl> Moving forward with Biolib ========================== To ascertain Biolib starts getting used on a wider scale some effort is required. The main point now is that we have a usable proof-of-concept, but it needs to be consolidated with documentation and installable packages. I propose to go through the following (smallish steps): . Test Perl mappings for Affyio and Staden on Linux, Windows and OSX . Source 1.0 package on website . Debian binary package for Perl . OSX binary package for Perl . Native windows download for Perl . Create Perl tutorial for Affyio and Staden At this point we have something that can be easily used, and we can look at further integration with BioPerl. Thereafter I would like to include libsequence and Bio++ functionality for Perl. That would require the Bio++ mapping, as well as Tutorials for both. I am deciding on Perl first to guarantee focus for the project (the Ruby and Python stuff will come relatively easily after). I can use help for OSX and Windows - testing on different flavours. When this is done (biolib-perl-1.0) I hope people get interested in additional functionality and languages. Everyone OK with this? Pj. From cjfields at illinois.edu Sat Oct 24 13:07:14 2009 From: cjfields at illinois.edu (Chris Fields) Date: Sat, 24 Oct 2009 12:07:14 -0500 Subject: [BioLib-dev] Plan to 1.0 In-Reply-To: <20091024145520.GA5075@thebird.nl> References: <20091024145520.GA5075@thebird.nl> Message-ID: <800CFFCA-2722-4642-A9F6-A071AE789AC0@illinois.edu> Sounds reasonable to me. You might want to post your thoughts to the bioperl list; I'm sure you'll find (beyond me) others who would be interested. chris On Oct 24, 2009, at 9:55 AM, Pjotr Prins wrote: > Moving forward with Biolib > ========================== > > To ascertain Biolib starts getting used on a wider scale some effort > is required. The main point now is that we have a usable > proof-of-concept, but it needs to be consolidated with documentation > and installable packages. I propose to go through the following > (smallish steps): > > . Test Perl mappings for Affyio and Staden on Linux, Windows and OSX > . Source 1.0 package on website > . Debian binary package for Perl > . OSX binary package for Perl > . Native windows download for Perl > . Create Perl tutorial for Affyio and Staden > > At this point we have something that can be easily used, and we can > look at further integration with BioPerl. Thereafter I would like to > include libsequence and Bio++ functionality for Perl. That would > require the Bio++ mapping, as well as Tutorials for both. > > I am deciding on Perl first to guarantee focus for the project (the > Ruby and Python stuff will come relatively easily after). I can use > help for OSX and Windows - testing on different flavours. > > When this is done (biolib-perl-1.0) I hope people get interested in > additional functionality and languages. > > Everyone OK with this? > > Pj. > _______________________________________________ > BioLib-dev mailing list > BioLib-dev at lists.open-bio.org > http://lists.open-bio.org/mailman/listinfo/biolib-dev From pjotr.public14 at thebird.nl Sat Oct 24 14:55:20 2009 From: pjotr.public14 at thebird.nl (Pjotr Prins) Date: Sat, 24 Oct 2009 16:55:20 +0200 Subject: [BioLib-dev] Plan to 1.0 Message-ID: <20091024145520.GA5075@thebird.nl> Moving forward with Biolib ========================== To ascertain Biolib starts getting used on a wider scale some effort is required. The main point now is that we have a usable proof-of-concept, but it needs to be consolidated with documentation and installable packages. I propose to go through the following (smallish steps): . Test Perl mappings for Affyio and Staden on Linux, Windows and OSX . Source 1.0 package on website . Debian binary package for Perl . OSX binary package for Perl . Native windows download for Perl . Create Perl tutorial for Affyio and Staden At this point we have something that can be easily used, and we can look at further integration with BioPerl. Thereafter I would like to include libsequence and Bio++ functionality for Perl. That would require the Bio++ mapping, as well as Tutorials for both. I am deciding on Perl first to guarantee focus for the project (the Ruby and Python stuff will come relatively easily after). I can use help for OSX and Windows - testing on different flavours. When this is done (biolib-perl-1.0) I hope people get interested in additional functionality and languages. Everyone OK with this? Pj. From cjfields at illinois.edu Sat Oct 24 17:07:14 2009 From: cjfields at illinois.edu (Chris Fields) Date: Sat, 24 Oct 2009 12:07:14 -0500 Subject: [BioLib-dev] Plan to 1.0 In-Reply-To: <20091024145520.GA5075@thebird.nl> References: <20091024145520.GA5075@thebird.nl> Message-ID: <800CFFCA-2722-4642-A9F6-A071AE789AC0@illinois.edu> Sounds reasonable to me. You might want to post your thoughts to the bioperl list; I'm sure you'll find (beyond me) others who would be interested. chris On Oct 24, 2009, at 9:55 AM, Pjotr Prins wrote: > Moving forward with Biolib > ========================== > > To ascertain Biolib starts getting used on a wider scale some effort > is required. The main point now is that we have a usable > proof-of-concept, but it needs to be consolidated with documentation > and installable packages. I propose to go through the following > (smallish steps): > > . Test Perl mappings for Affyio and Staden on Linux, Windows and OSX > . Source 1.0 package on website > . Debian binary package for Perl > . OSX binary package for Perl > . Native windows download for Perl > . Create Perl tutorial for Affyio and Staden > > At this point we have something that can be easily used, and we can > look at further integration with BioPerl. Thereafter I would like to > include libsequence and Bio++ functionality for Perl. That would > require the Bio++ mapping, as well as Tutorials for both. > > I am deciding on Perl first to guarantee focus for the project (the > Ruby and Python stuff will come relatively easily after). I can use > help for OSX and Windows - testing on different flavours. > > When this is done (biolib-perl-1.0) I hope people get interested in > additional functionality and languages. > > Everyone OK with this? > > Pj. > _______________________________________________ > BioLib-dev mailing list > BioLib-dev at lists.open-bio.org > http://lists.open-bio.org/mailman/listinfo/biolib-dev