[Biopython-dev] Biopython update talk at BOSC 2014
Wibowo Arindrarto
w.arindrarto at gmail.com
Thu Apr 3 20:57:07 EDT 2014
Hi Eric,
Thanks for the feedback. I have updated the abstract and you can
access it here: http://bit.ly/biopython_bosc_2014_02. In addition to
the changes you suggested, I added Michiel in the authors list as
well.
May I also ask what I should put as your affiliation :)? I think I
only have mine and Peter's at the moment, and I'm not sure if I could
get the most recent affiliations by scouring the web ;).
Best,
Bow
On Fri, Apr 4, 2014 at 12:18 AM, Eric Talevich <eric.talevich at gmail.com> wrote:
> Hi Bow,
>
> The abstract looks good. It's great to see you're carrying the torch this
> year.
>
> In the second paragraph, the sentence beginning "New features since version
> 1.62" confused me. Should this be "New features *in* version 1.62"? My
> recollection is that the listed features were actually introduced after
> 1.63, in which case that sentence would move to the end of the paragraph as
> "new features since version *1.63*". I'm looking at:
> http://news.open-bio.org/news/2013/08/biopython-1-62-released/
> http://news.open-bio.org/news/2013/12/biopython-1-63-released/
>
> Maybe you could streamline that paragraph to say that since BOSC 2013
> Biopython has successfully supported Python 2 and Python 3 (and Pypy and
> Jython 2.7) with a single codebase, and leave the details of the transition
> for the talk. Then describe the other changes/enhancements. Also, in the
> same paragraph: "various enhancements" could be swapped for "other
> significant enhancements".
>
> Cheers,
> Eric
>
>
> On Thu, Apr 3, 2014 at 12:06 AM, Wibowo Arindrarto <w.arindrarto at gmail.com>
> wrote:
>>
>> Hi everyone,
>>
>> I'm forwarding the previous message to the mailing list now. I just
>> realized that my message did not get through yesterday due to the
>> attachment :(. Apologies for the quite late check, should've checked
>> this earlier.
>>
>> I have now reuploaded our abstract here:
>> http://bit.ly/biopython_bosc_2014.
>>
>> As noted below, please let me know if there are additions / deletions
>> you would like me to make before the abstract is submitted.
>>
>> Best,
>> Bow
>>
>> On Wed, Apr 2, 2014 at 11:52 AM, Wibowo Arindrarto
>> <w.arindrarto at gmail.com> wrote:
>> > Hello everyone,
>> >
>> > I've finished the first draft of our update (attached). Please let me
>> > know if there are additions / deletions you would like me to make
>> > before I submit the abstract.
>> >
>> > Also, some things I would like to note:
>> >
>> > * I am missing the formal affiliations of everybody in the authors
>> > list except for me and Peter. Could you please send me your most
>> > recent affiliation?
>> >
>> > * I'm not sure about whether to include Tiago's recent Biopython
>> > docker container (I think it would be nice). Tiago, do we have the
>> > container up and running for our tests?
>> >
>> > Cheers,
>> > Bow
>> >
>> > On Tue, Apr 1, 2014 at 11:37 PM, Peter Cock <p.j.a.cock at googlemail.com>
>> > wrote:
>> >> On Mon, Mar 31, 2014 at 10:08 PM, Wibowo Arindrarto
>> >> <w.arindrarto at gmail.com> wrote:
>> >>> Hi Peter, everyone,
>> >>>
>> >>> A LaTeX template would be great :). I'm still preparing the abstract,
>> >>> should be ready for everyone to check soon.
>> >>>
>> >>> Cheers,
>> >>> Bow
>> >>
>> >> LaTeX template sent.
>> >>
>> >> I will be travelling the next few days and may be largely out of
>> >> email contact - so if you don't hear from me, don't worry and
>> >> submit the abstract anyway. I'm confident the others will have
>> >> good advice and suggestions (and I'm not the only one who
>> >> does email list moderation - but it might be simpler to send
>> >> round plain text and a link to the PDF if you want to show it
>> >> and not worry about the attachment triggering moderation).
>> >>
>> >> As usual this will get reviewed by the BOSC panel, and you'll
>> >> have a chance to revise the abstract at that point - for the
>> >> project updates is it OK if the initial text has a couple of details
>> >> "to be confirmed", like a summary of the forthcoming release
>> >> Biopython 1.64 (time for another thread, maybe we can aim
>> >> for the end of this month?).
>> >>
>> >> Thanks Bow,
>> >>
>> >> Peter
>> _______________________________________________
>> Biopython-dev mailing list
>> Biopython-dev at lists.open-bio.org
>> http://lists.open-bio.org/mailman/listinfo/biopython-dev
>
>
More information about the Biopython-dev
mailing list