<div dir="ltr"><div>Dear BP developers,<br><br></div>We have packaged the initial release (1.0) of bp-utils, which contains two bioperl-based utilities: "bioseq" and "bioaln" (another two utilities, "biopop" and "biotree", are in pre-release cleaning-up)<br><br><a href="https://github.com/bioperl/bp-utils/blob/master/bp-utils-current-release.tar.gz">https://github.com/bioperl/bp-utils/blob/master/bp-utils-current-release.tar.gz</a><br><br><div>For project description, rationale, and call for developers, please see:<br><br><a href="https://github.com/bioperl/bp-utils/blob/master/README.md">https://github.com/bioperl/bp-utils/blob/master/README.md</a><br><br></div><div>Thanks Chris and other for setting up the github access. Please feel free to email me for any feedback and bugs.<br><br></div><div>cheers,<br></div><div><br>-- <br>Weigang Qiu <br></div><div><br></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Dec 12, 2014 at 9:59 PM, Fields, Christopher J <span dir="ltr"><<a href="mailto:cjfields@illinois.edu" target="_blank">cjfields@illinois.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div style="word-wrap:break-word">
Hi Weigang,
<div><br>
</div>
<div>I wonder whether it would be better to have a separate bputils repo in the BioPerl space. This would allow development to continue w/o tying it directly to a release, and I think would solve the exposure problem much more so than having it included in
the main bioperl-live repo. We could also feasibly include it as part of the main CPAN bioperl release, maybe by simply linking to it as a git submodule and packaging it up.</div>
<div><br>
</div>
<div>chris</div>
<div><br>
<div><div><div class="h5">
<div>On Dec 9, 2014, at 3:01 PM, Weigang Qiu <<a href="mailto:weigangq@gmail.com" target="_blank">weigangq@gmail.com</a>> wrote:</div>
<br>
</div></div><blockquote type="cite"><div><div class="h5">
<div dir="ltr">Dear BioPerl developers,<br>
<br>
I intend to share & (eventually) publish a suite of bioperl-based command-line utilities my lab has developed & found very useful in the past 10 years:<br>
<br>
<a href="http://diverge.hunter.cuny.edu/labwiki/Bioutils" target="_blank">http://diverge.hunter.cuny.edu/labwiki/Bioutils</a><br>
<br>
Hilmar encouraged me to get some feedback & advice from the bioperl-L on how to package and release it properly.<br>
<br>
My specific questions are:<br>
<br>
1. While it goes naturally with bioperl releases, but I would like it to be more exposed than hidden inside the bp-scripts folder. Do you think these utilities are useful enough to be housed in a separate folder (e.g., "bputils") by itself? I have a developer's
account but I haven't commit anything for years.<br>
<br>
2. How to make it sustainable (and attract new developers) since we are constantly revising and adding methods. It would be great if become a part of bioperl-live.<br>
<br>
Any advice and facilitation will be appreciated!<br>
<br>
Thanks,<br>
-- <br>
Weigang Qiu, Ph.D. <br>
Department of Biological Sciences<br>
Hunter College of the City University of New York<br>
695 Park Avenue, New York, NY 10065<br>
Office: <a href="tel:1-212-772-5296" value="+12127725296" target="_blank">1-212-772-5296</a> (Room 839 Hunter North Building)<br>
Lab: <a href="tel:1-212-772-5721" value="+12127725721" target="_blank">1-212-772-5721</a> (Room 830 Hunter North Building)<br>
Web:<a href="http://diverge.hunter.cuny.edu/labwiki/" target="_blank">http://diverge.hunter.cuny.edu/labwiki/</a><br>
<div><br>
</div>
</div></div></div><span class="">
_______________________________________________<br>
Bioperl-l mailing list<br>
<a href="mailto:Bioperl-l@mailman.open-bio.org" target="_blank">Bioperl-l@mailman.open-bio.org</a><br>
<a href="http://mailman.open-bio.org/mailman/listinfo/bioperl-l" target="_blank">http://mailman.open-bio.org/mailman/listinfo/bioperl-l</a></span></blockquote>
</div>
<br>
</div>
</div>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature">Weigang Qiu <br></div>
</div></div></div></div>