Date   

Re: Change branch name in GitHub #communication #project

 

+1 to waiting for consensus and tooling to make this trivial on existing repos.

I will make a proposal to switch to main as the default branch name to the GA, and post an update when a decision is made.


Re: Request for comment before BONSAI 2020 General Assembly #dataliberation #communication

 

Here are my personal thoughts:

  • There is a lot of work being done in the USA by various federal agencies, coordinated by the US EPA and supported by GreenDelta. This includes reproducible inventory building (Electricity LCI, US EEIO), LCIA base data, and LCIA data formats and correspondence lists. It's difficult for me to keep up with all that is happening! In my opinion, BONSAI should support and benefit from all this activity - one clear way of doing this is to adopt data and data formats, instead of reinventing wheels.
  • PRé is (one of) the core initiators of the CDLCI project, which is trying to solve basically the same problem that BONSAI is (though through a different path). They are strong supporters of BONSAI, sponsored our 2019 hackathon, and have expressed strong interest in leveraging BONSAI in the future. They also see CDLCI as part of a data network, not as a stand alone project (see the attached slide). How can we benefit from this partner in an effective way, while preserving the BONSAI vision?
  • Similarly, UNEP is willing to sponsor and participate in a hackathon, as long as their work directly benefits GLAD.
  • There are a number of small problems where a little bit of work, combined with broad engagement from the community, could make everyone's life a lot easier. For example, at PSI we recently implemented ReCiPe 2016, which was incredibly painful, both in standardizing and correcting the names the ReCiPe team used, and in comparing our implementation with others. You can read the closed issues to see some colorful language. Is this an area where BONSAI ideas and already present technology could be applied?
I have no idea if it makes sense to try and hold an online hackathon - I see both sides here quite well. I am happy to follow the judgment of the community.

-Chris


Request for comment before BONSAI 2020 General Assembly #dataliberation #communication

 

Dear BONSAI community-

The 2020 general assembly will be held on Thursday, and is open to all paid members of BONSAI. Remember, active members qualify for a reduced enrollment rate of 50 - it isn't too late to sign up! Contact me personally for more info.

Before the GA, I would love to get some input from the broader community on where BONSAI is, what you think is realistic, and where you think BONSAI can be most effective. We had big plans for a funded hackathon before Corona shut everything down, and the energy of an in-person hackathon is difficult to reproduce online. Consequently, there hasn't been much forward movement on the BONSAI project as a whole (though if you follow the BONSAI churn email list you can see work continues: https://bonsai.groups.io/g/churn). Feel free to respond to this email with your thoughts, concerns, and ideas!

Yours,
Chris


Re: Change branch name in GitHub #communication #project

tomas Navarrete
 

1)
I saw that tweet from the current CEO Of Microsoft owned GitHub, and even CDNET seems to know from "internal sources" at github that it was not just a tweet. 
https://www.cnet.com/news/microsofts-github-is-removing-coding-terms-like-master-and-slave/
2)
The rename is for every clone and fork out there, for every developper that has collaborated, and for all the CI / CD services (Travis, Jenkins) and targets (PyPi, Conda) ... they are downstream. For example, certain build and publish (python packages let's say) actions are only taken on specific branches. Some of them, like "features" or "develop" are never "built" or published to a repository. This is usually configured in the CI / CD files _inside_ the repositories. So It's also a matter of modifying the actual contents of the repositories, not only the name.
3) 
I agree, it will take 5 minutes to the person creating the repository, until github comes up with a new default branch name.

a) The actual instructions you point to are to change what is known as the default branch. This could as well be "release". Not directly related to a new default branch name. _But_ indeed, this shows that you can right now use github with a new default branch name.
b)  and c) look to me like the perfect recipe to complicate a world that was already not very easy. Let's face it, git has been known to be more complicated than mercurial for example. The fact that you can do so many cool things with git like "pre-commit" hooks, templates, worktrees and so on, comes at the price of complexity of the tool. So if I can stay with a regular "git init" in _any_ remote headless server I can work with, (or a git clone) instead of having to create a new template plus remember the new default branch name of the particular organization (inside github for example) I will do it that way.


For BONSAI, when we talk practical terms this means less than 35 repositories, so I suppose the 5 minutes for every potential bonsai contributor can be safely spent. Hey, maybe once github finds the right way to push this down, they'll even allow groups or organization for an automatic way to do it for all their projects (after all, a git -m is relatively fast on the server side). However, don't forget that this means every clone out there of our repos might need an update. 

In my personal daily experience  I deal with gitlab.com / github.com / bitbucket.com / local gitlab instances daily, and, clearly this will be not just 5 minutes once (like this week for example). It's going to be 5 minutes daily for a few weeks.

I suggest we wait until
+ github.com proposes:
  - a way to do it from the web interface that matches a github wide policy
  - a huge communication campaign that warns all github users (professional / free-lance / occasional / consultant developers,  community managers, savy tech users, scientific programmers, you-name-it) of the *name* of the new default branch
+ a consensus [on a sensitive new default name] emerges:
  - from the BONSAI community (General Assembly, we're looking at you)
  - also from the wider git users community in the world

.. and optionally it would be interesting to hear from this "2 hit-wonder" guy named Linus Torvalds, on how he is going to deal with it. Not that we should follow his own practices, because the python community ones seem a bit less tyrannic. 

To sum up, I'm not against it. All I say is that we can decide now to GO or NO-GO on a BONSAI wide level for the change of the current default branch of all our github repositories (because they are all hosted there, but they are all just "git" repositories), but before executing this, let's see how the wider world community handles the case.

cheers,




Re: Change branch name in GitHub #communication #project

Matteo Lissandrini (AAU)
 

Hi Tomas,

I think I can reassure you on practical issues:

1) so Github is already working on this: https://twitter.com/natfriedman/status/1271253144442253312?ref_src=twsrc%5Etfw

2) the rename is maybe an issue for existing local branches/forks/clones with active changes, which I would guess are at best a handful.

3) when we create a new repo on github, creating the appropriate branch and delete master is probably a matter of five minutes?


Instructions to change the default branch exist already:

a) On github: https://help.github.com/en/github/administering-a-repository/setting-the-default-branch

b) On local&github: https://www.hanselman.com/blog/EasilyRenameYourGitDefaultBranchFromMasterToMain.aspx

c) automatically on new repos: https://superuser.com/a/1559582/762700

Thanks,
Matteo

---
Matteo Lissandrini

Department of Computer Science
Aalborg University

http://people.cs.aau.dk/~matteo






________________________________________
From: main@bonsai.groups.io <main@bonsai.groups.io> on behalf of tomas Navarrete via groups.io <tomas.navarrete=list.lu@groups.io>
Sent: 17 June 2020 17:07:20
To: main@bonsai.groups.io
Subject: Re: [bonsai] Change branch name in GitHub #communication #project

Dear All,

I totally understand the reason behind the wish to change names.
Now, beware that:

The default branch name in Git is master.
git-scm.com/book<https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell#ch03-git-branching>

so, every time we create a new repo, or initialize one, we'll need to update this behavior (MAYBE until github does something about it ... which is funny, because they kind of have a dominating position in the "free git hosting" namespace ;) )

For very practical reasons, I would stand against renaming existing repositories and only apply a name change on newly created ones, and loudly anounce this in the README of the repo.
If this (default branch name) is configurable, then we should look to implement a name that is fine with us.

cheers,


Re: Change branch name in GitHub #communication #project

tomas Navarrete
 

Dear All,

I totally understand the reason behind the wish to change names.
Now, beware that:

The default branch name in Git is master.
git-scm.com/book

so, every time we create a new repo, or initialize one, we'll need to update this behavior (MAYBE until github does something about it ... which is funny, because they kind of have a dominating position in the "free git hosting" namespace ;) )

For very practical reasons, I would stand against renaming existing repositories and only apply a name change on newly created ones, and loudly anounce this in the README of the repo.
If this (default branch name) is configurable, then we should look to implement a name that is fine with us.

cheers,


Re: Change branch name in GitHub #communication #project

Søren
 

I agree; I think 'main' actually is more precise (master has the connotation of dominance, irrespectively of the imperialist etymology) 


Re: Change branch name in GitHub #communication #project

Matteo Lissandrini (AAU)
 

Thanks for the support Massimo!

To be honest me neither, but alas the fact that *we* don't do that association is quite at the core of the matter.
As you say, it is definitely not about what we mean but about other people being unduly hurt.

Best,
Matteo

---
Matteo Lissandrini

Department of Computer Science
Aalborg University

http://people.cs.aau.dk/~matteo






________________________________________
From: main@bonsai.groups.io <main@bonsai.groups.io> on behalf of Massimo Pizzol via groups.io <massimo=plan.aau.dk@groups.io>
Sent: 16 June 2020 09:44:02
To: main@bonsai.groups.io
Subject: Re: [bonsai] Change branch name in GitHub #communication #project

To be completely honest, I had never before this mail associated the word “master-branch” to the master/slave relationship. But I can see some can make this association and find the name inappropriate.

It is OK for me to change the branch name to “main” or similar.

Basically it does not cost us any effort, and if this can avoid other people feel bad then…why not.

Massimo

From: <main@bonsai.groups.io> on behalf of "Matteo Lissandrini (AAU) via groups.io" <matteo=cs.aau.dk@groups.io>
Reply-To: "main@bonsai.groups.io" <main@bonsai.groups.io>
Date: Tuesday, 16 June 2020 at 09.32
To: "main@bonsai.groups.io" <main@bonsai.groups.io>
Subject: [bonsai] Change branch name in GitHub #communication #project

Hi all,
I would like to propose we change branch names in our github repositories away from `master`.

Here some more pointers about this proposal.

```
Language and words have a power and, unfortunately, some words and terminology we have historically used in technology (and in everyday conversation) are not neutral - they have an inadvertent and inherent ability to hurt some sections of our society.
```
https://dev.to/horus_kol/renaming-your-master-branch-2a37


```
Master-slave is an oppressive metaphor that will and should never become fully detached from history. Aside from being unprofessional and oppressive it stifles participation according to Eglash: “If the master-slave metaphor affected these tough-minded engineers who had the gumption to make it through a technical career back in the days when they may have been the only black persons in their classes, what impact might it have on black students who are debating whether or not to enter science and technology careers at all?”
```
https://tools.ietf.org/id/draft-knodel-terminology-00.html


I believe is in everybody's interest to move to a more inclusive language.

Best,
Matteo


Re: Change branch name in GitHub #communication #project

Massimo Pizzol
 

To be completely honest, I had never before this mail associated the word “master-branch” to the master/slave relationship. But I can see some can make this association and find the name inappropriate.


It is OK for me to change the branch name to “main” or similar.

 

Basically it does not cost us any effort, and if this can avoid other people feel bad then…why not.

 

Massimo

 

From: <main@bonsai.groups.io> on behalf of "Matteo Lissandrini (AAU) via groups.io" <matteo@...>
Reply-To: "main@bonsai.groups.io" <main@bonsai.groups.io>
Date: Tuesday, 16 June 2020 at 09.32
To: "main@bonsai.groups.io" <main@bonsai.groups.io>
Subject: [bonsai] Change branch name in GitHub #communication #project

 

Hi all,
I would like to propose we change branch names in our github repositories away from `master`.

Here some more pointers about this proposal.

```
Language and words have a power and, unfortunately, some words and terminology we have historically used in technology (and in everyday conversation) are not neutral - they have an inadvertent and inherent ability to hurt some sections of our society.
```
https://dev.to/horus_kol/renaming-your-master-branch-2a37


```
Master-slave is an oppressive metaphor that will and should never become fully detached from history. Aside from being unprofessional and oppressive it stifles participation according to Eglash: “If the master-slave metaphor affected these tough-minded engineers who had the gumption to make it through a technical career back in the days when they may have been the only black persons in their classes, what impact might it have on black students who are debating whether or not to enter science and technology careers at all?”
```
https://tools.ietf.org/id/draft-knodel-terminology-00.html


I believe is in everybody's  interest to move to a more inclusive language.

Best,
Matteo


Change branch name in GitHub #communication #project

Matteo Lissandrini (AAU)
 

Hi all,
I would like to propose we change branch names in our github repositories away from `master`.

Here some more pointers about this proposal.

```
Language and words have a power and, unfortunately, some words and terminology we have historically used in technology (and in everyday conversation) are not neutral - they have an inadvertent and inherent ability to hurt some sections of our society.
```
https://dev.to/horus_kol/renaming-your-master-branch-2a37


```
Master-slave is an oppressive metaphor that will and should never become fully detached from history. Aside from being unprofessional and oppressive it stifles participation according to Eglash: “If the master-slave metaphor affected these tough-minded engineers who had the gumption to make it through a technical career back in the days when they may have been the only black persons in their classes, what impact might it have on black students who are debating whether or not to enter science and technology careers at all?”
```
https://tools.ietf.org/id/draft-knodel-terminology-00.html


I believe is in everybody's  interest to move to a more inclusive language.

Best,
Matteo


Re: CI Deploy failed #infrastructure #rdf #ontology

Matteo Lissandrini (AAU)
 

Amazing, thanks a lot!

---
Matteo Lissandrini

Department of Computer Science
Aalborg University

http://people.cs.aau.dk/~matteo






________________________________________
From: main@bonsai.groups.io <main@bonsai.groups.io> on behalf of tomas Navarrete via groups.io <tomas.navarrete=list.lu@groups.io>
Sent: 05 May 2020 15:15:09
To: main@bonsai.groups.io
Subject: Re: [bonsai] CI Deploy failed #infrastructure #rdf #ontology

The VM was blocked in a reboot cycle. I will investigate later why.

After rebooting the VM, I triggered a new build ( #50 ) and it passed,

I'm now verifying the state of the services.


Re: CI Deploy failed #infrastructure #rdf #ontology

tomas Navarrete
 

The VM was blocked in a reboot cycle. I will investigate later  why.

After rebooting the VM, I triggered a new build ( #50 ) and it passed,

I'm now verifying the state of the services.


Re: CI Deploy failed #infrastructure #rdf #ontology

Matteo Lissandrini (AAU)
 

I think we can move to a resource in AAU

---
Matteo Lissandrini

Department of Computer Science
Aalborg University

http://people.cs.aau.dk/~matteo






________________________________________
From: main@bonsai.groups.io <main@bonsai.groups.io> on behalf of tomas Navarrete via groups.io <tomas.navarrete=list.lu@groups.io>
Sent: 05 May 2020 12:39:06
To: main@bonsai.groups.io
Subject: Re: [bonsai] CI Deploy failed #infrastructure #rdf #ontology

* The server is a virtual machine hosted at digitalocean (see screenshot below)

* I received a notification on maintenance on the "FRA1" network (where our VM is located) [see text below]

* the error on the deploy is at the moment of executing rsync (I'm _guessing_ right now that this is network related)

_more live updates on slack_ and I will post here once I have a solution.


Start: 2020-05-12 22:00 UTC
End: 2020-05-12 22:30 UTC

Hello,

During the above window, the networking team will be performing some proactive work in FRA1 for further expansion.

Expected Impact:



[cid:attach_0_160C1BA0F610D4B8_4780@groups.io]


Re: CI Deploy failed #infrastructure #rdf #ontology

tomas Navarrete
 

* The server is a virtual machine hosted at digitalocean (see screenshot below)

* I received a notification on maintenance on the "FRA1" network (where our VM is located) [see text below]

* the error on the deploy is at the moment of executing rsync (I'm _guessing_ right now that this is network related)

_more live updates on slack_ and I will post here once I have a solution.


Start: 2020-05-12 22:00 UTC
End: 2020-05-12 22:30 UTC

Hello,

During the above window, the networking team will be performing some proactive work in FRA1 for further expansion.

Expected Impact:




Re: CI Deploy failed #infrastructure #rdf #ontology

tomas Navarrete
 

I'm on it.

-----main@bonsai.groups.io escribió: -----
Para: main@bonsai.groups.io
De: "Matteo Lissandrini (AAU)"
Enviado por: main@bonsai.groups.io
Fecha: 05/05/2020 11:23
Asunto: [bonsai] CI Deploy failed #infrastructure #rdf #ontology

Hi all, Tomas,
the automatic deploy of the ontology is failing and we cannot understand why,
see here:
https://travis-ci.org/BONSAMURAIS/ontology

Do you have any idea?

Thanks,
Matteo


Re: CI Deploy failed #infrastructure #rdf #ontology

Matteo Lissandrini (AAU)
 

https://bukk.it/error.jpg

---
Matteo Lissandrini

Department of Computer Science
Aalborg University

http://people.cs.aau.dk/~matteo






________________________________________
From: main@bonsai.groups.io <main@bonsai.groups.io> on behalf of romain via groups.io <r_s=me.com@groups.io>
Sent: 05 May 2020 11:43:22
To: main@bonsai.groups.io
Subject: Re: [bonsai] CI Deploy failed #infrastructure #rdf #ontology

The error is quite clear though:

unexplained error


Re: CI Deploy failed #infrastructure #rdf #ontology

romain
 

The error is quite clear though:

unexplained error


CI Deploy failed #infrastructure #rdf #ontology

Matteo Lissandrini (AAU)
 

Hi all, Tomas,
the automatic deploy of the ontology is failing and we cannot understand why,
see here:
https://travis-ci.org/BONSAMURAIS/ontology

Do you have any idea?

Thanks,
Matteo


Re: Spring 2020 hackathon proposal rough draft RFC #communication

arturdonaldson@...
 

Hi there,

I am new to BONSAI after learning about it through the lca-net website. Just like to register my interest in your hackathon, probably attending digitally given the current travel situation.

All the best,
Artur
--
Research Assistant, Centre for Environmental Policy, ICL
Consultant LCAWorks

London, UK


Re: Spring 2020 hackathon proposal rough draft RFC #communication

 

First draft is finished. I will be sending this to potential granting agencies/people on Friday, March 6; please provide comments (if any) before that, either on the mailing list, or by editing the text directly.

Thanks, Chris

41 - 60 of 303