Meet our new Travel Fellowship Review Chair: Farah Zaib Khan

Farah presents CWLProv at GCCBOSC 2018

The next round of our OBF Travel Fellowships just ended on the 15th of December! This round we have introduced a Review Chair coming from the midst of our community that will help us in reviewing the applications. The role will be filled by Farah Zaib Khan, one of our OBF Travel Fellowship alumni. Farah has successfully applied for the Fellowship twice before. Thanks in part to this support, she has become a central community member both of the Bioinformatics Open Source Conference and the Open Bioinformatics Foundation itself.

Farah recently completed her PhD at The University of Melbourne, Australia. The OBF travel fellowship helped her interact with the Bioinformatics community during BOSC 2017 and GCCBOSC 2018 where she actively participated in the Codefests and other activities to shape her PhD work. Her PhD research is about the provenance and interoperability of bioinformatics workflows. The funding and support provided by OBF is acknowledged in the article recently submitted by her for publication.

We are happy to see that the Travel Fellowships help students and Early Career Researchers to participate and grow within the Open Bioinformatics community, as well as helping to increase the diversity of participants in Open Bioinformatics events.

Posted in Community, Travel Fellowship | Leave a comment

Biopython 1.73 released

Dear Biopythoneers,

Biopython 1.73 has been released and is available from our website and PyPI.

This release of Biopython supports Python 2.7, 3.4, 3.5 and 3.6. It has also been tested on PyPy2.7 v6.0.0 and PyPy3.5 v6.0.0.

As in recent releases, more of our code is now explicitly available under either our original “Biopython License Agreement”, or the very similar but more commonly used “3-Clause BSD License”.  See the LICENSE.rst file for more details.

The dictionary-like indexing in Bio.SeqIO and Bio.SearchIO will now explicitly preserve record order to match a behaviour change in the Python standard dict object. This means looping over the index will load the records in the on-disk order, which will be much faster (previously it would be effectively at random, based on the key hash sorting).

The “grant” matrix in Bio.SubsMat.MatrixInfo has been replaced as our original values taken from Gerhard Vogt’s old webpages at EMBL Heidelberg were discovered to be in error. The new values have been transformed following Vogt’s approach, taking the global maximum 215 minus the similarity scores from the original paper Grantham (1974), to give a distance measure.

Double-quote characters in GenBank feature qualifier values in Bio.SeqIO are now escaped as per the NCBI standard. Improperly escaped values trigger a warning on parsing.

There is a new command line wrapper for the BWA-MEM sequence mapper.

The string-based FASTA parsers in Bio.SeqIO.FastaIO have been optimised, which also speeds up parsing FASTA files using Bio.SeqIO.parse().

Additionally, a number of small bugs and typos have been fixed with further additions to the test suite, and there has been further work to follow the Python PEP8, PEP257 and best practice standard coding style.

Many thanks to the Biopython developers and community for making this release possible, especially the following contributors:

  • Alona Levy-Jurgenson (first contribution)
  • Ariel Aptekmann
  • Brandon Invergo
  • Catherine Lesuisse
  • Chris Rands
  • Darcy Mason (first contribution)
  • Devang Thakkar (first contribution)
  • Ivan Antonov (first contribution)
  • Jeremy LaBarage (first contribution)
  • Juraj Szász (first contribution)
  • Kai Blin
  • Konstantin Vdovkin (first contribution)
  • Manuel Nuno Melo (first contribution)
  • Maximilian Greil
  • Nick Negretti (first contribution)
  • Peter Cock
  • Rona Costello (first contribution)
  • Spencer Bliven
  • Wibowo ‘Bow’ Arindrarto
  • Yi Hsiao (first contribution)

For reference, checksums:

$ md5sum biopython-1.73*
9bab1776b3f63cb2a81715e78abfb6e0  biopython-1.73-cp27-cp27m-macosx_10_6_intel.macosx_10_9_intel.macosx_10_9_x86_64.macosx_10_10_intel.macosx_10_10_x86_64.whl
a531f656ecae854adf1fc6021735c2a9  biopython-1.73-cp27-cp27m-manylinux1_i686.whl
27f5179f2493408d33e5322690f1bb7a  biopython-1.73-cp27-cp27m-manylinux1_x86_64.whl
41fdb1f257cdcd030a468e7339a6c6ab  biopython-1.73-cp27-cp27mu-manylinux1_i686.whl
bf23d2daae5c72c2d84058bce3acd7a2  biopython-1.73-cp27-cp27mu-manylinux1_x86_64.whl
d3cab98752b83cef121b7a1e8b81853c  biopython-1.73-cp27-cp27m-win32.whl
178be72d7b294a2a15c92630bbee2a81  biopython-1.73-cp27-cp27m-win_amd64.whl
32fc6184cbf21faca0776251570b2c58  biopython-1.73-cp34-cp34m-macosx_10_6_intel.macosx_10_9_intel.macosx_10_9_x86_64.macosx_10_10_intel.macosx_10_10_x86_64.whl
5c78b8210de0b511c208facf7325c7e6  biopython-1.73-cp34-cp34m-manylinux1_i686.whl
ae414b4666900567579cc92df4223521  biopython-1.73-cp34-cp34m-manylinux1_x86_64.whl
1b0d7ba1b4c097b318213431d9b6b99e  biopython-1.73-cp34-cp34m-win32.whl
04a91b6ea826596b0c8b643b743d176f  biopython-1.73-cp34-cp34m-win_amd64.whl
a8ecaa7bf30fd912536881228e754664  biopython-1.73-cp35-cp35m-macosx_10_6_intel.macosx_10_9_intel.macosx_10_9_x86_64.macosx_10_10_intel.macosx_10_10_x86_64.whl
0676a634a73e049903a4bc36e3b60fc3  biopython-1.73-cp35-cp35m-manylinux1_i686.whl
6d4ebb6131a611a71816b0208747de55  biopython-1.73-cp35-cp35m-manylinux1_x86_64.whl
65165d6551e43bdc18e0912935f9c7fd  biopython-1.73-cp35-cp35m-win32.whl
24c6352a143ea28c47bff5da754f0af9  biopython-1.73-cp35-cp35m-win_amd64.whl
d11a2c7ba85a9927815fb9b6dfd9a0ac  biopython-1.73-cp36-cp36m-macosx_10_6_intel.macosx_10_9_intel.macosx_10_9_x86_64.macosx_10_10_intel.macosx_10_10_x86_64.whl
8898e77221359b4d4280e42a53bfbc52  biopython-1.73-cp36-cp36m-manylinux1_i686.whl
fb8a38c943a9e80492ddb657e9d330a5  biopython-1.73-cp36-cp36m-manylinux1_x86_64.whl
1f49d1a5b492639008dd674b83a8bcb7  biopython-1.73-cp36-cp36m-win32.whl
f0dde83e1a7c27a107e6aeb253f29f08  biopython-1.73-cp36-cp36m-win_amd64.whl
e082d026d3bb894838e389f159a8362b  biopython-1.73-cp37-cp37m-macosx_10_6_intel.macosx_10_9_intel.macosx_10_9_x86_64.macosx_10_10_intel.macosx_10_10_x86_64.whl
0db98f888700a7e119f39f136687c3d1  biopython-1.73-cp37-cp37m-manylinux1_i686.whl
c92184fad3be8c8ba3cc3e8816603dc5  biopython-1.73-cp37-cp37m-manylinux1_x86_64.whl
58c58f52d514bd9a86df01da1db0d804  biopython-1.73-cp37-cp37m-win32.whl
e32acd6a4a2c703ee5ff34cd62f83124  biopython-1.73-cp37-cp37m-win_amd64.whl
d1d2e6154c2c89d6bb0e77f4a3578686  biopython-1.73.tar.gz
$ sha256sum biopython-1.73*
c43a47ad3397336aa7af5a0bb5ebec91aa2ae328b71421e550cf7e7f80d00f69  biopython-1.73-cp27-cp27m-macosx_10_6_intel.macosx_10_9_intel.macosx_10_9_x86_64.macosx_10_10_intel.macosx_10_10_x86_64.whl
0302d5be80850fbaa93789ab516d189c9400755901cfe566a324e8fea10ed39b  biopython-1.73-cp27-cp27m-manylinux1_i686.whl
e5b5666724cab7983aebeb593e52dd276ff9fdabb3669d57db8b5ea303a097a5  biopython-1.73-cp27-cp27m-manylinux1_x86_64.whl
21723d79a1d15e99c823b440dd37176259dffa686e2a015919ad255d89238491  biopython-1.73-cp27-cp27mu-manylinux1_i686.whl
85d53b91406aacfef673fb3cf24873d978654fa49d52b5ab4d9c3b0d06b003d6  biopython-1.73-cp27-cp27mu-manylinux1_x86_64.whl
c5beb53e2d5a5a573baaaa449a32d3adfb3d03bd7752adbcb20a62d6e8041e03  biopython-1.73-cp27-cp27m-win32.whl
add575d5b81eec95381a53ca8c042e9de9e506b24734ec773690247d997eaa69  biopython-1.73-cp27-cp27m-win_amd64.whl
59610b1639a7d9c1f36a5398e748c044c21f4285230fa79fcea2cafe835f9366  biopython-1.73-cp34-cp34m-macosx_10_6_intel.macosx_10_9_intel.macosx_10_9_x86_64.macosx_10_10_intel.macosx_10_10_x86_64.whl
1c4b55412c12b246b948c3bbb30e60a7b075da9770449371a731ac9987849381  biopython-1.73-cp34-cp34m-manylinux1_i686.whl
aed261f47f72d63292fdf4c81197fdbc150094a34e10176647a932c83e179db9  biopython-1.73-cp34-cp34m-manylinux1_x86_64.whl
3cc401c15a85829eb6ae01babb02fbe7828548709b4dcb6d5149e94d5173ed7c  biopython-1.73-cp34-cp34m-win32.whl
f49558bea021cc5243e50efb38d545842153cde276e14879d6d63222065c683d  biopython-1.73-cp34-cp34m-win_amd64.whl
a149ea816f21ef72e1b4e6f538b13141584bdc531f864c5f1eb8b8feed71ba06  biopython-1.73-cp35-cp35m-macosx_10_6_intel.macosx_10_9_intel.macosx_10_9_x86_64.macosx_10_10_intel.macosx_10_10_x86_64.whl
e7a03ae81b5507b3a668f81a58351c065fa6d8a0b77f772e183eb284c1cc4619  biopython-1.73-cp35-cp35m-manylinux1_i686.whl
fce8051b05d62d7d0ff7af0999f6874bd9af17f0613e6c8664ac20c93215345a  biopython-1.73-cp35-cp35m-manylinux1_x86_64.whl
99e6f78317c68b27a8b406c5595364005d43fee67f3b8ae20c3332588999442f  biopython-1.73-cp35-cp35m-win32.whl
839882c1929476538f9872e7fe6617c6fbcd65989483254817effbc388feead1  biopython-1.73-cp35-cp35m-win_amd64.whl
164b9958d1714f318015900f2689fcc08859f76b11484e8f91f1f29acb4b7465  biopython-1.73-cp36-cp36m-macosx_10_6_intel.macosx_10_9_intel.macosx_10_9_x86_64.macosx_10_10_intel.macosx_10_10_x86_64.whl
d120346e2eed46beaf1d0771826a18cee7c3155cc8c0dafc6ffffc74ac49e8fc  biopython-1.73-cp36-cp36m-manylinux1_i686.whl
92c0940c5c2a76b559538a4eb1fc0277d3e960209c537d5b74632fa87a51a810  biopython-1.73-cp36-cp36m-manylinux1_x86_64.whl
5542f847a860b90e742a1be8a9807aa57accacd2bccfb07b3f6511f85201af19  biopython-1.73-cp36-cp36m-win32.whl
ef69ed6acf7bee26c530e40a768d060f46eef228d06aa2ea89439d3c54759bd8  biopython-1.73-cp36-cp36m-win_amd64.whl
cfb44ba6cdfb1dbfc05b7e46f26286b37d35b2bb847868c9088e9b67060fd7be  biopython-1.73-cp37-cp37m-macosx_10_6_intel.macosx_10_9_intel.macosx_10_9_x86_64.macosx_10_10_intel.macosx_10_10_x86_64.whl
ede4e4335828a780dc2096fd0443c45efb3f8fcac741e544454997b978ad3cf3  biopython-1.73-cp37-cp37m-manylinux1_i686.whl
26f8ae8ddf06c85dab12f5aaff538593c7cec69102bb4ad968b3eb40a0477bf8  biopython-1.73-cp37-cp37m-manylinux1_x86_64.whl
93d79520586b48a2a77bec3a0623871b656c45dbb83c9b6834540f0a7232478e  biopython-1.73-cp37-cp37m-win32.whl
0fa9346c8ec144da12a556861090cfe5fbb6ecd89418d6358047b90def48e032  biopython-1.73-cp37-cp37m-win_amd64.whl
70c5cc27dc61c23d18bb33b6d38d70edc4b926033aea3b7434737c731c94a5e0  biopython-1.73.tar.gz
Posted in Biopython, Blogroll, Code, Community, Development, OBF Projects | Tagged , , , | Leave a comment

Updates are coming!

Brace yourselves - updates are coming

About a year ago, the OBF shared plans to get more involved with the open science community, and followed up by recruiting two board members for this purpose. Since then, we’ve tried to keep up momentum and community engagement – during GCCBOSC, we held an OBF Birds of Feather meeting, allowing members of the board to meet with attendees and discuss their needs and interests. As a result of this meeting, we ended up with our new community-designed logo and launched a community newsletter (incidentally, issue 2 of the newsletter is going to be released within the next few days – feel free to suggest a news item).

OBF + Outreachy Intern = Site Redesign

Our next step is the exciting announcement of a complete site redesign. Over the period of December 2018 – March 2019, Deepashree Deshmukh will be working as an Outreachy Intern, creating a purpose-built CMS powered website for the OBF.  We’d also like to thank all of the other fantastic applicants to this project. Contributors from around the world spent time, effort, and did some genuinely great work prototyping their designs during the application phase.

Currently, the OBF site is comprised of our blog, where you’re probably reading this, a GSoC mini-site, and our main MediaWiki-powered site. We’re looking forward to combining and refreshing these, hopefully resulting in an attractive and easily-updatable site that can function as a community-oriented hub. We’ll be sharing drafts as they evolve. If you have any thoughts or comments on what you’d like to see in the new site, feel free to leave a comment on this post.


Posted in Community, Website | Tagged , , , | 2 Comments

OBF membership form fixed

We recently discovered that the application to join the OBF (linked from the OBF membership page) was not working. It broke some time after August 31. We have now replaced it and it is working once again.

If you applied for OBF membership between September 1 and yesterday, please go to the new form ( and resubmit your application. We apologize for the inconvenience!

Posted in Uncategorized | Leave a comment

The color of bioinformatics: what is it and how can it be modified?

This is a guest blog post from Tendai Mutangadura, who was supported by the ongoing Open Bioinformatics Foundation travel fellowship program to attend the GCCBOSC 2018 meeting in Portland, June 2018. The OBF’s Travel Fellowship program continues to help open source bioinformatics software developers with funding to attend conferences or workshops. This was one of three awards from our April 2018 travel fellowships call. Our August call recently closed, the current call closes 15 December 2018, you might want to apply?

When I was selected as one of 3 recipients of the April 2018 OBF Travel Fellowships, I wanted this to signify a turning point in my career. I expected to meet and interact with many great minds in open science and bioinformatics, and the GCC-BOSC 2018 meeting in beautiful Portland exceeded my expectations. Because I was travelling light and had been to Portland once before, I chose to use public transport from PDX to get to Reed College, the meeting venue. This afforded me a mini tour of Portland before getting to the serious but fun business of the meeting. When I stepped off the Reed College bus stop, I flagged down the first person I saw to ask for directions to the registration venue, and this person was none other than Anton, one of the scientists instrumental in the development of the Galaxy project. Great start. As we chatted en route to the registration place, I took the opportunity to brag to him that I had recently figured out the causal mutation associated with a neurodegenerative disease in one of our whole-genome-sequenced dogs using the web-based Galaxy platform.

I attended as many training sessions related to Galaxy on Day 1 of training as I could. I have been a Galaxy platform user for >3 years and had previously attended the GCC 2016, so it was great to meet new and old acquaintances this time round. I even had the opportunity to get help with aspects of my Jetstream account virtual machines during one of the two CollaborationFest days that I attended. I found the CollaborationFest very useful in making new contacts and discussing potential future collaborations.

On Day 2 of Training, the highlights of my training, based my bioinformatics needs, included a 2.5 hour GATK training session and the bcbio workshop. In the latter, Brad Chapman, starring here, talked about and demonstrated how communities can work together to make giant strides in developing robust open source software pipelines and making these freely accessible to anyone, everyone, anywhere. For someone like me, for whom having access to computing resources and setting aside the time to focus on developing or tweaking code as part of my day job can sometimes be an uphill struggle, the bcbio workshop was a godsend. Bcbio allows me to do my day job duties and do bioinformatics too. After the meeting, I immediately contacted one of my XSEDE Extended Collaborative Support Services (ECSS) team members, Phil Blood, to discuss the possibility of putting together a species agnostic variant-calling pipeline. I have already started this project using my XSEDE start-up grant computing resources allocation on Bridges, at the Pittsburgh Supercomputing Center (PSC). So far, I have been off to a good start. For those who may not be aware of the many great free computing resources out there, such resources exist, as I have alluded to above, for anyone to take advantage of.

Now, a light-hearted reference to a serious (according to me), but common observation at conferences such as but definitely not limited to GCC-BOSC: the lack of diversity of attendees. This is what prompted me to title my blog post the way I did. My first answer was (metaphorically speaking) that the color of bioinformatics should be ‘rainbow’. But when I googled ‘rainbow colors’ it occurred to me that the colors black and white are not part of the rainbow. I also refreshed my rusty optical physics and got explanations why this is the case. Now, to get back on track, would it not be wonderful if more people of color were involved in this bioinformatics revolution? What can be done to redress this current state of affairs? Thumbs up to the OBF for recognizing and doing something about this lack of diversity by creating the OBF Travel Fellowship! For my part, when and if I complete any pipeline(s) based on bcbio code, I plan to publish a collection of such pipelines online as self-paced tutorials (the website will go live soon) in a very user-friendly format targeted to those who are command line challenged, from any community, to encourage them to get started in bioinformatics analyses, or at least analyze their own data without buying expensive commercial packages. This would be my way, albeit at very small scale, of democratizing bioinformatics. One of the advantages of involving people with as diverse backgrounds as possible with basic training in bioinformatics and genomics is that this may help reduce mistrusts linked to unfortunate historical incidents such as the Tuskegee experiments, not only for countries like the US but anywhere around the world where similar types of mistrust may exist.

Posted in Blogroll, BOSC/ISMB, Community, OBF, Travel Fellowship, Uncategorized | Tagged , , , , , , | Leave a comment

City of roses they call it – Portland Oregon (USA)

This gallery contains 3 photos.

How should I start describing the fruitful experience in this amazing city… First time ever in Portland, second time attending BOSC… I knew I was signing up for a great time but did not know much about the uncanny beauty … Continue reading

More Galleries | Leave a comment

Taking Turns

BOSC 2019 will be part of ISMB 2019

Every year until 2018, BOSC was part of the annual ISMB conference as a community of special interest (COSI, formerly known as a SIG, Special Interest Group). As part of our continuing quest to broaden and deepen the BOSC community, we decided to perform an experiment this year by partnering with the Galaxy Community Conference rather than with ISMB. As we reported, the experiment was a success–participants were overwhelmingly positive about the experience, and the conference did attract a somewhat different mix of attendees than in past years. However, we also concluded that there are some advantages to meeting with ISMB–for example, it attracts more students and postdocs, and the presence of other COSI tracks provides a wider range of scientific topics. Moreover, unlike the GCC 2018 venue, the venue already chosen for GCC 2019 has a number of drawbacks: we wouldn’t be able to run similarly-sized parallel sessions; registration prices wouldn’t be as affordable as in 2018; and the venue would not be able to accommodate the larger (160 people) and longer (four days) CollaborationFest that was one of the highlights of GCCBOSC 2018.

For these and other reasons, the BOSC organizing committee concluded that the best way to serve the broadest community of potential BOSC attendees will be to partner with ISMB some years and GCC some years. We therefore plan to hold BOSC 2019 in Basel as part of ISMB. We hope to partner with GCC in 2020 at a North American site to be determined, or in 2021 in Europe.

Wherever we hold future BOSCs, you can be sure that they will include a wide range of topics in open science and open source bioinformatics, and we hope that they will draw an ever-diversifying mix of attendees. As always, we welcome your feedback about what you liked in past BOSCs and your suggestions for the future. Feel free to email us ( or tweet (@OBF_BOSC).

Posted in Blogroll, BOSC/ISMB, Community, OBF, Uncategorized | Tagged , , , , , | Leave a comment

GCCBOSC 2018 post-meeting report

This year, the Galaxy Community Conference (GCC) and the Bioinformatics Community Conference (BOSC) met together to form the first Bioinformatics Community Conference. At GCCBOSC 2018, participants were able to meet and collaborate with a broad community of bioinformatics developers and users who focus on open, interoperable software tools and libraries that facilitate scientific research.

Held in June 2018 at Reed College in Portland, Oregon, GCCBOSC attracted nearly 300 participants from around the world. The meeting started with two days of training workshops (Figure 1). The main meeting had some parallel sessions and some joint sessions, including well-received keynote talks by Tracy Teal, Fernando Pérez and Lucia Peixoto, as well as a panel discussion about documentation and training. Posters, demos and Birds of a Feather sessions (BoFs) gave participants opportunities to engage in discussions about topics of mutual interest. After the main meeting, many attendees stayed for up to four additional collaboration days (the CollaborationFest, or CoFest).

Figure 1. Participants at one of the GCCBOSC training workshops. (All GCCBOSC photographs in this post are from Bérénice Batut’s Flickr album, under a CC-BY-SA license.)

Figures 2,3. Attendees and presenters mingled at the poster/demo sessions.

Figure 4. CoFest attendees assembled for morning meetings before breaking into smaller groups to work on collaborative projects.

There was wide agreement among GCCBOSC participants that the meeting was informative, productive and enjoyable. Comments from participants in the post-meeting survey included, “Loved the mix of communities!”, “Location was great,” and “Nice conference. Nice atmosphere. Nice people. I really enjoyed it. Thanks!”. The training workshops and extended CoFest were mentioned by participants as great features of the meeting. Most of the survey respondents who had previously attended a GCC or BOSC rated this year’s meeting as similar or better than past meetings (Figure 5). The main complaint was that the parallel GCC and BOSC sessions forced attendees to choose between them–an embarrassment of riches.

Figure 5: Responses to post-GCCBOSC survey questions from those who had been to previous GCCs or previous BOSCs.

Although post-meeting feedback was almost entirely positive, we did receive two reports of behavior at GCCBOSC that the reporter perceived as not consistent with the spirit of the Code of Conduct. These were handled by the GCCBOSC organizing committee, and everyone involved is satisfied with the outcome. The discussions held by the organizers around these issues led us to re-examine the CoC and think about how we might want to revise it for future meetings. Your input on this topic (or anything regarding GCCBOSC) is welcome.

We are grateful to all those who helped make GCCBOSC 2018 a success: the organizers, presenters, workshop leaders, participants, and our generous sponsors, including Platinum sponsor Google Cloud and Gold sponsor Lenovo + Intel. Thanks in part to sponsor funding, we were able to offer subsidized child care and an onsite lactation room that enabled a speaker who would otherwise have been unable to attend to bring her four-month-old baby and participate actively in the meeting.

Whether or not you attended GCCBOSC 2018, we look forward to interacting with you in the future!

Posted in BOSC/ISMB, Community, Uncategorized | Tagged , , , | Leave a comment

Following up from BOSC’s OBF Birds of a Feather meeting

It was really great to meet so many of you at GCCBOSC this year! We will soon have a couple of Travel Fellowship blog posts talking about the conference, so we won’t provide too much of a general overview at this point, but we would like to share a little more about one of the Bird of Feather (BoF) events we ran – specifically the OBF community BoF.

The aim of this BoF was to engage anyone who was:

  • Curious about the OBF
  • Interested in suggesting ideas
  • Wanting to help or get more involved with the OBF

The OBF BoF started with a pre-dinner round where we all introduced ourselves and why we were interested in the OBF, and a second round after a quick bite and relocating inside – Portland can get chilly fast in the evening!

Motivations for participating in the BoF included a desire to help people who come from a software background learn more about the biology / bioinformatics side of things. Other participants shared the feeling that they loved the conference but weren’t sure how to take home the “open / good practices make for better software and better research” message we were trying to share.

We ended up with lot of brainstorming and helpful discussions – here are some of the topics.

OBF logo and site

The OBF logo is over a decade old now and looks a little… dated. When we floated the idea of redesigning it at the meeting, we didn’t expect to have sketches roughed out by several attendees before the end of the BoF meeting! We’ve ended up with three different design sets, which you can check out or comment on in this GitHub issue. We’re also considering updating the entire OBF site, if we can find someone to work on that (possibly a summer intern).

Increasing year-round sense of community

For many people, BOSC and the OBF are approximately the same thing – which makes sense, since BOSC is one of the biggest and most noticable things we do. We’d like to support open bioinformatics all year, though. Possible ways we could do this:

  • Local OBF / bioinformatics meetups or hackathons. If the OBF created guidelines for this, would you be interested in running a group in your area?
  • Newsletters with project updates, interesting open / bioinformatics news, events, etc.
  • “How to be open in bioinformatics” webinar – a sort of “open 101” for projects that are interested in being open but aren’t sure where to start. This would be a nice way to kick-start projects that want to present a poster or talk at BOSC but don’t yet meet the openness requirements. (Note that anyone is allowed to attend BOSC, whether or not they have any open repositories – it’s only presenting that mandates a fully open project.)

Joining the OBF as a project or individual

A pertinent question asked at the BoF was: why join, as an individual? Many people have attended BOSC multiple times and even been heavily involved in the community without officially being in the rolls of registered members. The primary reason to join is the ability for membership to vote on issues pertaining to the OBF. In the next few months, we’re hoping to run a vote on changing OBF bylaws pertaining to how projects join, as well as a plain to adopt a Code of Conduct that may apply to both the OBF and its member projects. If this matters to you because A) you care about a project that might be joining soon (there are a couple!) or B) you’d like to see the OBF adopt a more explicit behaviour standard in the form of a CoC, please join the OBF so you can vote!

Get involved

After reading all this, if you’re interested in helping out with any of the ideas or initiatives suggested, please follow up by any of these mechanisms:

  • Open an issue on our OBF-docs repo – this is our preferred method as it allows others to chime in easily and is less transient than a tweet.
  • Leaving a comment on this post!
  • Tweet to @obf_news

Also – please don’t forget to join the OBF if you haven’t already. Any BOSC attendee automatically qualifies for membership, and even if you haven’t attended BOSC before, if you’re reading this post there’s a good chance you’ll fulfil the requirements anyway. Details are in the form!


Posted in BOSC/ISMB, Community | Tagged , , | Leave a comment