Curtis Madsen & Nicholas Roehner
Nona was created to address an issue with academic software concerning the software development cycle: built, develop, publish and then get lost as people move around in academia. However, academics can work with Nona to get feedback and develop a community which can help with the maintenance process of your software.
How do you participate? http://nonasoftware.org and browse currently-available software. Software is broken down into specification, design, data management and integration types. You can transfer the software to Nona and have them host it, or you can host the software and they will provide a link to both the homepage and the github or similar repository.
When you’re ready to submit software to Nona, you start by choosing a license (to work with Nona, you must have an Open Source license). Then you provide a link to the github repo (or simply give a tarball to Nona, who will put it on github). Nona will provide promotional materials, FAQs, forums etc for your software.
In February 2017 there will be a 2 1/2 day hackathon (Nona Works) where they bring together biologists and computer scientists.
Please note that this post is merely my notes on the presentation. I may have made mistakes: these notes are not guaranteed to be correct. Unless explicitly stated, they represent neither my opinions nor the opinions of my employers. Any errors you can assume to be mine and not the speaker’s. I’m happy to correct any errors you may spot – just let me know!