29 March 2017 – 2 April 2017:Our very own InterMine Dev Workshop and Hackathon. Registrations are still open at the moment (21 Feb 2017), but the early bird room rate will be expiring in early March, so try not to delay if you’re planning on coming!
We’ll have several people out of the office – but not everyone – over the week before Christmas, starting from today (16 December). If you need to contact us, you may get a prompter response by emailing our lists (e.g. the dev list) which will reach all of us, rather than emailing individuals directly.
The annual InterMine office closure will be between 23rd December evening until 3rd January morning UK time. During this period no one will be in the office, and we may not be able to respond to emails, tweets, blogs, etc.
I’ve said this before, but I’ll proudly say it again: one of the greatest things about being open source is the community. People are continually creative and resourceful with the tools we’ve built, and we love seeing all the different things you guys do with InterMine. Here’s a quick roundup of some of the things we’ve seen so far this year:
Ever wondered what Model Organism Linked Data might look like? MOLD includes a queryable SPARQL endpoint and draws from multiple different InterMines to create a single dataset.
Tip: Make it generic
Generic tools are ones that aren’t hard-coded to a specific Mine or model. We’re always on the look out for new and exciting features, whether it’s a visualisation or a web service or a database tweak. If you think it’s good, you can email us to discuss it or simply create a pull request, and bask in glory forever after.
We’d love to see more!
This list is awesome (thanks everyone!!) but by no means conclusive. If you think we’ve missed something out, or you’re doing something new at the moment, drop us a line and we’ll add you to the next round up. We’d also love to hear from others who might be interested in guest-blogging an InterMine related feature.
Last week InterMine attended the first RSE (Research Software Engineer) conference (look at the picture…we are there!)
But what’s an RSE? In the Introduction main talk, the first day, Caroline Jay from the University of Manchester defines RSEs as “the coalface of ensuring that computational science is accurate, reliable and reproducible, and their views on making progress in this domain are therefore particularly valuable.” Particularly valuable because, as a slogan that everyone loved says, “Software can exist without a paper but a paper and the results can’t. If the software is wrong, the science is wrong”.
As promised by the organizers, the conference focused exclusively on the issues that affect people who write and use software in research, not people who write papers. In two days there were a lot of interesting talks and workshops about how research software engineers can grow a project for science, best practices, software development process, docker…
As InterMine team, we’ve contributed to the conference, sharing our story, what “open” really means to us, why we choose open source and how we try to be open. The image below shows our vision about Open Source.
We have also shared the best practices we’ve learned, over the years, in designing, writing and maintaining open source software for science, hoping that people embarking on their first open source project could benefit from these. [Slides from our talk]
We had a great time talking and meeting with a lot of very friendly and passionate people sharing idea, best practices, issues and doubts.
Thank UK-RSE folks for organizing a so great event!
Remember the big International InterMine meetup we were tentatively discussing a few months back? Thanks again to everyone who responded to the survey, as it helped us a lot. We’re still in the process of nailing down the details, but here’s the rough program we are expecting (with details potentially subject to change but hopefully they won’t…)
Wednesday 29th March 2017: Arrival at Berkley in preparation for the fun ahead. Hopefully there will be some limited accommodation on site available for early birds.
Thursday 30th and Friday 31st March 2017: The conference itself. Details to be confirmed.
Saturday 1st and Sunday 2nd April: Hackathon! Entirely optional. Put your thinking caps on and start looking for fun ideas.
We’ll post more details as things become concrete, and we’d love to hear from you if you have any ideas or thoughts regarding the conference and its content. We still need to think of a catchy name and hashtag for twitter!
Finally for now, we’d like to give massive thanks to the folks at JGI for helping us to coordinate this.