Date   

Request for help: Python library skeleton

 

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


Re: Hackathon communication programs

 

The people have spoken! You can see the results of the communication survey here: https://docs.google.com/forms/d/1uFFdmb4VY9DMr5IyQQu3u33y3I96qTPtBh0CufeyEfY/edit?usp=sharing
 
For *chatting*, we will use Slack. Here is the invitation link: https://join.slack.com/t/bonsai-open/shared_invite/enQtNTYwMzA2OTQ1MzgxLWY3YTJmMGJkMmVhNzMzOTg5YmVkOGVlY2Y0MWI0NzU4MTliMWFjM2M0NzhjN2NkY2ZmOTM5ZDkxYjYxOGM2MDY. Note: Even if you already have a Slack account, each channel requires a new password. Please join Slack, and leave a message in the hackathon-2019 channel to let us know that you can connect.
 
For video conferences, we will use Zoom.us. We will send out several test invitations to make sure everyone can connect successfully before the hackathon (Bo, do we have a paid plan?).


Re: Hackathon communication programs

Bo Weidema
 

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

Bo


Den 2019-02-25 kl. 15.16 skrev Chris Mutel:

For video conferences, we will use Zoom.us. We will send out several test invitations to make sure everyone can connect successfully before the hackathon (Bo, do we have a paid plan?).
--


Re: Hackathon communication programs

Bo Weidema
 

Hmm, no so promising:

screen dump
Den 2019-02-25 kl. 15.16 skrev Chris Mutel:

The people have spoken! You can see the results of the communication survey here: https://docs.google.com/forms/d/1uFFdmb4VY9DMr5IyQQu3u33y3I96qTPtBh0CufeyEfY/edit?usp=sharing
 
For *chatting*, we will use Slack. Here is the invitation link: https://join.slack.com/t/bonsai-open/shared_invite/enQtNTYwMzA2OTQ1MzgxLWY3YTJmMGJkMmVhNzMzOTg5YmVkOGVlY2Y0MWI0NzU4MTliMWFjM2M0NzhjN2NkY2ZmOTM5ZDkxYjYxOGM2MDY. Note: Even if you already have a Slack account, each channel requires a new password. Please join Slack, and leave a message in the hackathon-2019 channel to let us know that you can connect.
 
For video conferences, we will use Zoom.us. We will send out several test invitations to make sure everyone can connect successfully before the hackathon (Bo, do we have a paid plan?).
--


Re: Request for help: Python library skeleton

Matteo Lissandrini (AAU)
 

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


Re: Request for help: Python library skeleton

 

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
############################


Re: Hackathon communication programs

Tom
 

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


Re: Hackathon logistics

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.


Re: Hackathon logistics

cdgaete@...
 

Hi sophisticatedusername!

I am up for that. Let's discuss this later today while waiting for someone else who wants to join us.
Cheers
Carlos


On Tue, 26 Feb 2019 at 12:00, <sophisticatedusername@...> wrote:
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.


Re: Hackathon logistics

Agneta
 

Hi Tom

Thanks for taking the initiative. Matteo and I are participating from Aalborg university. We are willing to share the costs for accommodation.

regards
Agneta

--
Agneta Ghose, PhD 
Post doc, The Danish Centre for Environmental Assessment  
Aalborg University
Rendsburggade 14
Aalborg 9000
Denmark 
( +45 93 56 2051



Re: Hackathon logistics

Matteo Lissandrini (AAU)
 

Thanks for proposing this,
Agneta and I are willing to share an apartment as well.

One detail, I will leave on Friday, I hope this will not be a big issue.

On a different note, since this emails are public, I am not 100% comfortable on sharing all these logistics details on a public space.

Thanks,
Matteo


On Tue, 26 Feb 2019, 12:47 Carlos David Gaete, <cdgaete@...> wrote:
Hi sophisticatedusername!

I am up for that. Let's discuss this later today while waiting for someone else who wants to join us.
Cheers
Carlos

On Tue, 26 Feb 2019 at 12:00, <sophisticatedusername@...> wrote:
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.


Re: Hackathon logistics

Tom
 

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


Re: Hackathon logistics

Tom
 

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.


IT requirements for the hackathon

 

1. I will be providing a small NAS/git server to facilitate collaboration during the hackathon, in case our internet goes down or is not a good as we think. On this box, I will have the EXIOBASE data and the developed correspondence tables to/from the different classification systems that we will be using. Please suggest any other data that you think would be helpful!

Note that this NAS is a Raspberry Pi, and so it can't do any really difficult tasks.

2. We have a server at Univ. Aalborg running a Jena (http://jena.apache.org/) database. However, we would also like to be able to deploy web apps as subdomains of bonsai.uno. Bo, how much flexibility do we have here? It would be good to have public documentation of the BONSAI architecture, including registrar, hosting of bonsai.uno, etc.

3. Are there any other IT needs or suggestions?


Default BONSAI licenses

 

We should choose a default license for the code and data produced by the hackathon. My first suggestion would be BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause) for source code, and Creative Commons attribution international for the data (https://creativecommons.org/licenses/by/4.0/).

- Why not GPL/CC non-commercial? At this point I don't see a reason to adopt a more restrictive license that could limit the spread of BONSAI's ideas and technologies into the private sector.

- Why not CC share-alike? Again, potentially excluding potential contributors seem premature at this stage of the project.

However, this is just my opinion!!! For the work that you do, you can of course choose what licenses to use. And this is a controversial subject, so feel free to express your opinion.


Re: Default BONSAI licenses

Brandon Kuczenski
 

I second BSD.

On Fri, Mar 1, 2019 at 12:09 AM Chris Mutel <cmutel@...> wrote:
We should choose a default license for the code and data produced by the hackathon. My first suggestion would be BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause) for source code, and Creative Commons attribution international for the data (https://creativecommons.org/licenses/by/4.0/).

- Why not GPL/CC non-commercial? At this point I don't see a reason to adopt a more restrictive license that could limit the spread of BONSAI's ideas and technologies into the private sector.

- Why not CC share-alike? Again, potentially excluding potential contributors seem premature at this stage of the project.

However, this is just my opinion!!! For the work that you do, you can of course choose what licenses to use. And this is a controversial subject, so feel free to express your opinion.



--
Brandon Kuczenski, Ph.D.
Associate Researcher

University of California at Santa Barbara
Institute for Social, Behavioral, and Economic Research
Santa Barbara, CA 93106-5131

email: bkuczenski@...


Re: Hackathon communication programs

 

Dear all-

I would like to clarify the reason and anticipated use of the different communication channels that we have for the hackathon and in the future.

BONSAI is not just open data, but open development, and multiple people have already commented that the development of the existing BONSAI content is not open. For example, the wiki provides a list of selected ontologies, but no record of the debate that led to this selection. We need to do better, and that means true transparency in decision making on a small- and large-scale.

Mailing list:

Main place of discussion for BONSAI topics, especially for those which require a bit of thinking and broader community engagement. Indexed and archived, easily discoverable via web searches.

LinkedIn:

Used by management to disseminate BONSAI announcements to a wider professional network. Not for discussion, can be ignored by most BONSAI participants.

Slack:

Used for quick messages or coordination, primarily during the hackathon itself. Especially useful for coordinating smaller teams. Technical debates should primarily occur via Github issues for the repository in question.

Zoom.us:

Used for videoconferencing. ASAP we will start routinely recording and posting these conferences (opportunity for one of you to volunteer and write a guide).

bonsai.uno:

Read-only introductory content

https://github.com/BONSAMURAIS/bonsai

Should only be used for the wiki - other content types should each be in its own repository.

Other Github repositories

Technical discussion of bugs, feature suggestions, and design decisions (via the projects board and issues)

Tom Millross will be doing an audit of our current communication channels, and making suggestions to be gentle with people new to BONSAI, before the hackathon.

As always, your suggestions and comments are welcome!


Re: Default BONSAI licenses

Matteo Lissandrini (AAU)
 

I'm fine with BSD for code.

I wanted to ask this before,  how does the  EXIOBASE EULA [1] affects this project?


Cheers,
Matteo


[1]https://www.exiobase.eu/index.php/terms-of-use






From: hackathon2019@bonsai.groups.io [hackathon2019@bonsai.groups.io] on behalf of Brandon Kuczenski via Groups.Io [bkuczenski@...]
Sent: Friday, March 01, 2019 9:13 AM
To: hackathon2019@bonsai.groups.io
Subject: Re: [hackathon2019] Default BONSAI licenses

I second BSD.

On Fri, Mar 1, 2019 at 12:09 AM Chris Mutel <cmutel@...> wrote:
We should choose a default license for the code and data produced by the hackathon. My first suggestion would be BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause) for source code, and Creative Commons attribution international for the data (https://creativecommons.org/licenses/by/4.0/).

- Why not GPL/CC non-commercial? At this point I don't see a reason to adopt a more restrictive license that could limit the spread of BONSAI's ideas and technologies into the private sector.

- Why not CC share-alike? Again, potentially excluding potential contributors seem premature at this stage of the project.

However, this is just my opinion!!! For the work that you do, you can of course choose what licenses to use. And this is a controversial subject, so feel free to express your opinion.



--
Brandon Kuczenski, Ph.D.
Associate Researcher

University of California at Santa Barbara
Institute for Social, Behavioral, and Economic Research
Santa Barbara, CA 93106-5131

email: bkuczenski@...


Re: Default BONSAI licenses

 

On Fri, 1 Mar 2019 at 10:09, Matteo Lissandrini (AAU) <matteo@cs.aau.dk> wrote:

I'm fine with BSD for code.

I wanted to ask this before, how does the EXIOBASE EULA [1] affects this project?


Cheers,
Matteo


[1]https://www.exiobase.eu/index.php/terms-of-use





________________________________
From: hackathon2019@bonsai.groups.io [hackathon2019@bonsai.groups.io] on behalf of Brandon Kuczenski via Groups.Io [bkuczenski=ucsb.edu@groups.io]
Sent: Friday, March 01, 2019 9:13 AM
To: hackathon2019@bonsai.groups.io
Subject: Re: [hackathon2019] Default BONSAI licenses

I second BSD.

On Fri, Mar 1, 2019 at 12:09 AM Chris Mutel <cmutel@gmail.com> wrote:

We should choose a default license for the code and data produced by the hackathon. My first suggestion would be BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause) for source code, and Creative Commons attribution international for the data (https://creativecommons.org/licenses/by/4.0/).

- Why not GPL/CC non-commercial? At this point I don't see a reason to adopt a more restrictive license that could limit the spread of BONSAI's ideas and technologies into the private sector.

- Why not CC share-alike? Again, potentially excluding potential contributors seem premature at this stage of the project.

However, this is just my opinion!!! For the work that you do, you can of course choose what licenses to use. And this is a controversial subject, so feel free to express your opinion.


--
Brandon Kuczenski, Ph.D.
Associate Researcher

University of California at Santa Barbara
Institute for Social, Behavioral, and Economic Research
Santa Barbara, CA 93106-5131

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


Re: Default BONSAI licenses

Matteo Lissandrini (AAU)
 

I missed that, thanks!

Nice, so for the data we shall use the CC share-alike as well?

Best,
Matteo

________________________________________
From: hackathon2019@bonsai.groups.io [hackathon2019@bonsai.groups.io] on behalf of Chris Mutel via Groups.Io [cmutel=gmail.com@groups.io]
Sent: Friday, March 01, 2019 10:16 AM
To: hackathon2019@bonsai.groups.io
Subject: Re: [hackathon2019] Default BONSAI licenses

EXIOBASE is now CC, see
https://www.exiobase.eu/index.php/data-download/exiobase3hyb

On Fri, 1 Mar 2019 at 10:09, Matteo Lissandrini (AAU) <matteo@cs.aau.dk> wrote:

I'm fine with BSD for code.

I wanted to ask this before, how does the EXIOBASE EULA [1] affects this project?


Cheers,
Matteo


[1]https://www.exiobase.eu/index.php/terms-of-use





________________________________
From: hackathon2019@bonsai.groups.io [hackathon2019@bonsai.groups.io] on behalf of Brandon Kuczenski via Groups.Io [bkuczenski=ucsb.edu@groups.io]
Sent: Friday, March 01, 2019 9:13 AM
To: hackathon2019@bonsai.groups.io
Subject: Re: [hackathon2019] Default BONSAI licenses

I second BSD.

On Fri, Mar 1, 2019 at 12:09 AM Chris Mutel <cmutel@gmail.com> wrote:

We should choose a default license for the code and data produced by the hackathon. My first suggestion would be BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause) for source code, and Creative Commons attribution international for the data (https://creativecommons.org/licenses/by/4.0/).

- Why not GPL/CC non-commercial? At this point I don't see a reason to adopt a more restrictive license that could limit the spread of BONSAI's ideas and technologies into the private sector.

- Why not CC share-alike? Again, potentially excluding potential contributors seem premature at this stage of the project.

However, this is just my opinion!!! For the work that you do, you can of course choose what licenses to use. And this is a controversial subject, so feel free to express your opinion.


--
Brandon Kuczenski, Ph.D.
Associate Researcher

University of California at Santa Barbara
Institute for Social, Behavioral, and Economic Research
Santa Barbara, CA 93106-5131

email: bkuczenski@ucsb.edu


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

21 - 40 of 273