IMPORTANT - Group, roles, and hackathon preparation
The hackathon starts in less than two weeks, and in order for it to be successful we will need to be well coordinated. A few working groups have made some real progress, but I don't see any forward movement on most of the others. Please already start thinking and discussing how the skills of the different team members can fit together, how each team member can have agency, and how team management can include remote participants.
To be more specific: By Friday, March 15, please add your group to the hackathon readme, with a brief description of what to expect before and during the hackathon. Ideally there would also be a Github repo, project management, etc. as well.
Stefano and Rutger, I don't see your responses to the working group poll.
Miguel R, there has been substantial discussion on the BONSAI ontology - we would love to get your inputs!
Dear team participants:
Thanks for signing up! To have an effective hackathon, each team needs to have a detailed plan of what they can realistically accomplish, and prepare adequately beforehand. A common problem in hackathons is that a few people take charge of the project core, and the rest don't really know what needs to be done or how they can contribute. Therefore, please already start thinking and discussing how the skills of the different team members can fit together, how each team member can have agency, and how team management can include remote participants.
I have tried to create a graph of project team dependencies. This is just something I came up with on a Sunday morning, you can edit it here (but you will need graphviz installed to generate a new image). Due to the high level of interdependency in the hackathon, please add a section to the hackathon readme with your project team organization as soon as possible.
It is time to choose a task or two and start working. Please complete the following ASAP:
In each of the following groups, I need someone to volunteer to serve as the coordinator. This person will be responsible for organizing the groups work, and completing any deliverables due before the hackathon.
The following are only my suggestions - each group can decide on their own how they will work together. You canalso self-organize and create your own working groups! See some ideas in the stretch goals here: https://github.com/BONSAMURAIS/hackathon-2019#outputs
A framework for building Python libraries that helps people get started quickly. https://github.com/BONSAMURAIS/python-skeleton.
There is some content there already, needs to have some issues closed and then be tested.
The bentso working group depends on this to be finished, so completion of at least the first stage well before the hackathon start is a priority.
Output: Github repo
Suggested coordinator: Bo
We will try to reuse existing ontologies as much as possible, but some custom ontology development is inevitable. Key discussion points for this group:
Suggested coordinator: Agneta
No pressure or anything, but this is the most important working group, as other groups depend on it to produce results in a timely manner.
This group will select the overall framework and specific ontologies to be used in the hackathon, and communicate them in a human- and computer-readable fashion. Should include outputs from the BONSAI ontology working group.
Output: New github repo with first version of rdf/turtle/whatever, and discussion in issues as to what was chosen and why, before the hackathon start. Updating the bonsai wiki can come during or after the hackathon.
Suggested coordinator: Brandon
Technical guidelines and examples for interoperable life cycle inventory models models that also meet the standards that Brandon has developed.
Should proceed in accordance with bentso, which will be an example of these best practices.
Output: New github repo with standards and discussion. Not due before hackathon start.
Software development methodology
Suggested coordinator: Tomas
Getting started guide
Suggested coordinator: Tom
Output: New github repo with guides that can be finished in ~15 minutes before start of hackathon.
Suggested coordinator: Rutger
Conversion from RDF to SimaPro CSV
Output: Documentation of SimaPro CSV format, and library to convert to/from RDF by end of hackathon.
Suggested coordinator: Chris
BONSAI living model for European electricity via ENTSO-E API.
Output: Working model by the end of the hackathon. Basic querying functionality should be available before hackathon start.
Usable correspondence tables between different schemas, e.g. EXIOBASE/ecoinvent/BONSAI RDF.
I will send out a separate email with a poll with option to sign up for the different groups.