We'll be holding our bi-annual code sprint at the Science on Drupal Summer Lab in mid-July - look out for more details on the event itself in the next few days.
In the meantime, we're crowd-sourcing suggestions for the most cutting-edge new features or most pressing problems faced by those in the community using Drupal for science - whether it's for organizing research, data curation or public communication.
As either a user or developer of Drupal:
- Is there a science-specific task that's hard or impossible to accomplish in Drupal?
- Is there an existing module that's useful, but in need of maintenance or new features?
- Is there a specific issue on drupal.org that needs attention?
Please post your ideas and suggestions as a comment below or on our webform - by the end of next week, July 3rd. We'll then allow a week for a round of voting, up to July 10th - before the code sprint itself the following week.
You will also be able to vote on the existing stack of ideas and issues from our last sprint (see our Trello board). Still-active issues will be re-posted by their owners to the thread over the next few days, where you can +1 them.
On the day we'll match sprinters with your top tasks, and forge forward to improve Drupal for the science community.
Looking forward to seeing what comes up!
Comments
Codesprint proposal: DOIs for Drupal project
A potential focus area identified by participants during the 7/8 conference call (notes) - review the EZID API, then start laying out a low level module that allows Drupal to interface with the EZID API, bearing in mind similar efforts by Casey Grzecka at UCLA with ORCID
Also needed - input or ideas on how the project's UI and code architecture may interface with the Biblio module, whether the existing 1.x branch, or the new 3.x branch. Refer to the Project Charter and the more recent prioritized Functionality outline for details on the anticipated scope of this project.
Codesprint proposal: DataONE API
Focus for this sprint will be on developing the specification for interaction with the DataONE Member Node API. Contact Adam for more details - he'll be available and working on this from 3:30-5pm on sprint day.
Codesprint: Review and Testing of D.O Issues
There are a number of drupal.org issues that are up for testing or review - some are follow up testing of work done at our last code sprint, others are nominations of wider d.o issues. They cover a range of topics in our SemanticWeb, Mapping and WebServices tracks.
Here's the list, in no particular order:
If you'd like to punt one of these to the top of the list, let us know by commenting below.
Still time for suggestions and votes!
If you have a suggestion, there's still time to put it forward - either comment here, on our webform or write your idea on our board in person on the day.
If you'd like to back an existing project or issue, comment here and we'll +1 its "Community Engagement" score. Votes are welcome!
We'll prioritize based on a rough gauge of "Community Engagement" with each idea, but participants are welcome to work on whatever they chose based on their interests and skill set - there's always a need for a broad range of work.
Thanks! David