Hi folks. We have a nice 4-bedroom apartment ready to book (10 mins walk from hackathon, outside space, sunlight), and just need a new 4th person.
Please message if you're possibly interested and I'll add you to the private Slack channel for details.

Ok thanks for the replies Carlos, Agneta & Matteo.
Following Matteo's point, I suggest we switch to a private Slack channel if that's ok with you all. See you there if you agree, or email with an alternative suggestion.
For other participants, please assume this apartment is now full unless we post again!
Cheers, Tom

I am interested in booking a shared apartment if anyone else is too?
This search shows some 3+ bedroom options within a ~10 minute walk of the hackathon location. We could get a nice place with a private bedroom each, for significantly under the 100 €/person/day budget. I'm happy to arrange the booking etc. and would like to stay until Saturday (for a relaxed check-out without encroaching on hackathon time, and to enjoy Barcelona Friday eve).
Please reply if you're interested, with preferences/requirements (or absence of them) if possible. I suggest this Friday (March 1) as the deadline for booking, to ensure we get a good place.

Hi Bo,
In your screenshot, it looks as though the link URL in the address bar is incomplete.

On Tue, 26 Feb 2019 at 09:33, Matteo Lissandrini (AAU) <matteo@cs.aau.dk> wrote:

Hi Chris,

a couple of questions:
what is this python skeleton for?
A module, an app, a web-app?

A normal library, with an optional command-line executable. The idea
is to have a common base, and also to make it easy for people who
aren't used to packaging to get up and running quickly. I have added
some basic stuff this morning.

I guess there may be multiple modules produced in the project for addressing distinct needs, shouldn't this decision be based on those considerations?

Also, I see a reference to pyhoe: last commit was ~7 years ago and has only 10 stars on github, is this a solid project for which to require a dependency?

Not a dependency, just an example of what a skeleton could look like :)

Thanks,
Matteo

--
############################
Chris Mutel
Technology Assessment Group, LEA
Paul Scherrer Institut
OHSA D22
5232 Villigen PSI
Switzerland
http://chris.mutel.org
Telefon: +41 56 310 5787
############################

Hi Chris,

a couple of questions:
what is this python skeleton for?
A module, an app, a web-app?
I guess there may be multiple modules produced in the project for addressing distinct needs, shouldn't this decision be based on those considerations?

Also, I see a reference to pyhoe:  last commit was ~7 years ago and has only 10 stars on github, is this a solid project for which to require a dependency?

Thanks,
Matteo

Hmm, no so promising:

Yes, we have a paid plan. Let me know when you want to have meetings scheduled.

Bo

Dear all-

Please help fill out https://github.com/BONSAMURAIS/python-skeleton. I think we should have at least the following:

* Simple instructions on what needs to be changed/updated from the skeleton
* Instructions on how to set up Travis, Appveyor, and coveralls (or suitable replacements)
* Instructions on how to set up CI code quality
* Docs directory using Sphinx
* Tests directory using pytest
* CI scripts needed for conda packaging (see https://github.com/OcelotProject/Ocelot/tree/master/ci) and automatic uploading (plus instructions)
* Normal python directory structure

under the SCRUM methodology, we would also need a product owner: someone capable of prioritizing the user stories / tasks

"Bo Weidema" ---02/25/2019 09:58:03 AM---My skills are probably best suited for working on the formalisation of the ontology, as outlined by

From: "Bo Weidema" <bo.weidema@...>
To: hackathon2019@bonsai.groups.io
Date: 02/25/2019 09:58 AM
Subject: Re: [hackathon2019] Hackthon management/software development philosophy
Sent by: hackathon2019@bonsai.groups.io

---

My skills are probably best suited for working on the formalisation of the ontology, as outlined by Matteo.

Bo

Den 2019-02-25 kl. 09.33 skrev tomas Navarrete:

- Now that the list of participants a bit more "stable", I suggest we start identifying skills and interests so that we can create teams (and eventually make them responsible for the user stories)

--

My skills are probably best suited for working on the formalisation of the ontology, as outlined by Matteo.

Bo

+1 for Docker ... but, on which components ? The RDF server + database ?

+1 also for the PR workflow (this is a defacto standard)

As for language, no one will deny that python is almost a de facto standard around the community, but we must not forget that the point is using the right tool for the right job.
Testing, quick prototyping in my mind is very easy with python (hence it's de facto standard). It requires much less boilerplate to be up and running. The downside would be in the docker side: miniconda3 images are huge compared to a java runtime


+1000 setting up the python repo with directory structure metadata. Like this, providing testing scripts would be easier, as well as letting others the option to work on forks and accept PRs after right code review.

This last point seems important to me because it will help to identify the concrete deliverables ;)


"Chris Mutel" ---02/23/2019 09:05:11 AM---Some more specific questions/suggestions: - Expectation/requirement for CI testing?

From: "Chris Mutel" <cmutel@...>
To: hackathon2019@bonsai.groups.io
Date: 02/23/2019 09:05 AM
Subject: Re: [hackathon2019] Hackthon management/software development philosophy
Sent by: hackathon2019@bonsai.groups.io

---

Some more specific questions/suggestions:

- Expectation/requirement for CI testing?
- Expectation/requirement that people follow the Github PR workflow
(https://guides.github.com/introduction/flow/)?
- Expectation/requirement on implementation language?
- Expectation/requirement on (automatic) containerization? Standardize
on Docker or something else?
- Set up Python repo with expected directory structure, metadata, and
guides on how to set up docs/CI/etc.

I have the impression that SCRUM is maybe a little too much when dealing with teams of less than 6 members. Luckily, we may end up being more than 6 ;)

- I think we can follow a light version of SCRUM, maybe with less stand-up meetings and more work (since our sprint may be too small). Something like Trello could be used to asign tasks/user stories and keep track of who is participating in which one.

- Now that the list of participants a bit more "stable", I suggest we start identifying skills and interests so that we can create teams (and eventually make them responsible for the user stories)

- As for quality, we could use sonar metrics as the tool ( https://www.sonarsource.com/products/codeanalyzers/sonarpython.html )  + define a base threshold for coverage. The drawback is that we would need to get used to do some checking before pushing code.

More importantly, I think that we must first to production and secondly to quality in this phase where we want to "see that it works".




"Chris Mutel" ---02/23/2019 08:01:52 AM---Thanks for Brandon and Tomas for bringing up the principle of test-driven development. I agree that

From: "Chris Mutel" <cmutel@...>
To: hackathon2019@bonsai.groups.io
Date: 02/23/2019 08:01 AM
Subject: [hackathon2019] Hackthon management/software development philosophy
Sent by: hackathon2019@bonsai.groups.io

---

Thanks for Brandon and Tomas for bringing up the principle of test-driven development. I agree that this approach is absolutely correct, but I want to open up the broader question of hackthon task management and resource planning - do we want to formally adopt something like SCRUM (https://www.scrum.org/resources/what-is-scrum)? Having participated in several hackathon-type events, I have seen several examples of poor resource management.

I would very much appreciate someone volunteering to take the lead here, and create a small working group that will development a guidance document (in the Github repo) and prepare a presentation for Monday morning (March 25) introducing the approach agreed upon to the rest of the group.

I see the following key questions:
- How strict do we want to be following a particular system?
- How can we make sure that software/other efforts aren't duplicated?
- How can we make sure that each persons capabilities are being used effectively and in line with their interests?
- What tools can we use to improve the quality and usability of the code produced (e.g. TDD/BDD, documentation)?

We can create a hashtag (https://groupsio.zendesk.com/hc/en-us/articles/202739265-Hashtags) for this discussion so people not directly involved can more easily filter it.

Hi all,

I though would be appropriate for me to help with the definition of the deliverables.
I think task "a) Matching of EXIOBASE to the BONSAI ontology set, and import into an RDF database"
would be the crucial one.

For that to be successful, that is, for the RDF data to be accessible, understandable, maintainable, expandable, and - very importantly- interoperable, we would require to move from the description of the ontology here

https://github.com/BONSAMURAIS/bonsai/wiki/Data-Storage#specify-minimum-core-data-and-metadata-formats

to a proper ontology definition + an RDF Schema.
These should be mapped and matched with existing standards and vocabularies, in particular I suggest the QB[1] and QB4OLAP [2] as vocabularies, and to link to established ontologies like GeoNames [6].

Hence, on the side of the domain experts, I would imagine the first deliverables to be pictures like the one here [3] for the ontology and here [4,5] for the schema.
These are to be accompanied with a set of URI and RDF predicates which will constitute the BONSAI vocabulary.
With similar pictorial representation and the provided URI/predicates, it would be easy for any programmer to provide the required RDF specification and translation code for the data, and for anyone else to understand and re-use or link to the data you are publishing.

The decisions about how to structure those are the crucial point where those familiar with the data and the domain can clearly provide the "added-value".

I hope the above is useful to you, and please let me know whether I should elaborate in more details about anything.
I'll be happy to help you navigate the technicalities of the specifications of course.

Best,
Matteo




[1] https://www.w3.org/TR/vocab-data-cube/
[2] https://github.com/lorenae/qb4olap/wiki
[3] http://kbpedia.org/knowledge-graph/
[4] http://tcga.deri.ie/
[5] http://qweb.cs.aau.dk/qboairbase/
[6] http://www.geonames.org/ontology/documentation.html

Some more specific questions/suggestions:

- Expectation/requirement for CI testing?
- Expectation/requirement that people follow the Github PR workflow
(https://guides.github.com/introduction/flow/)?
- Expectation/requirement on implementation language?
- Expectation/requirement on (automatic) containerization? Standardize
on Docker or something else?
- Set up Python repo with expected directory structure, metadata, and
guides on how to set up docs/CI/etc.

On Sat, 23 Feb 2019 at 08:01, Chris Mutel via Groups.Io
<cmutel=gmail.com@groups.io> wrote:

Thanks for Brandon and Tomas for bringing up the principle of test-driven development. I agree that this approach is absolutely correct, but I want to open up the broader question of hackthon task management and resource planning - do we want to formally adopt something like SCRUM (https://www.scrum.org/resources/what-is-scrum)? Having participated in several hackathon-type events, I have seen several examples of poor resource management.

I would very much appreciate someone volunteering to take the lead here, and create a small working group that will development a guidance document (in the Github repo) and prepare a presentation for Monday morning (March 25) introducing the approach agreed upon to the rest of the group.

I see the following key questions:
- How strict do we want to be following a particular system?
- How can we make sure that software/other efforts aren't duplicated?
- How can we make sure that each persons capabilities are being used effectively and in line with their interests?
- What tools can we use to improve the quality and usability of the code produced (e.g. TDD/BDD, documentation)?

We can create a hashtag (https://groupsio.zendesk.com/hc/en-us/articles/202739265-Hashtags) for this discussion so people not directly involved can more easily filter it.

--
############################
Chris Mutel
Technology Assessment Group, LEA
Paul Scherrer Institut
OHSA D22
5232 Villigen PSI
Switzerland
http://chris.mutel.org
Telefon: +41 56 310 5787
############################