Re: Default branch name in GitHub

Thanks for all the feedback. I also discussed this at the planning meeting today and was met with similar responses. I plan to begin migration to “main” for all of our non-archived git repositories. The process isn’t difficult but we have a lot of repos, so it may take some time. If you have

Considering a move from IRC to Matrix / Element

Hi all, Colin, Gio, Justin, and myself have been exploring Matrix / Element as an alternative to IRC for IDRC and Fluid Project chat. Mozilla made the switch from IRC

Re: Default branch name in GitHub

+1 On 2020-10-20 9:52 a.m., Colin Clark wrote: > I think “main” is a good name too. I’m glad this is only a convention > in Git so we’re free to choose.  > > Colin > >> On Oct 20, 2020, at 9:49 AM, Giovanni Tirloni wrote: >> >>  >> +1 from me! >> >> Another helpful blog >> post:  >>

Re: Changes to Atlassian products

I wonder if the ILDH related issues are a good place to start with migrating from JIRA to GitHub Issues. We have been tracking issues for websites in GitHub Issues more recently and the ILDH currently has JIRAs tracked in two or three different JIRA projects. Also we’re starting to work on that

Re: Changes to Atlassian products

Hi Justin and Gio, Thanks for looking into this. It sounds like realistically we may have a few different kinds of projects. Some have thousands of issues with lots of detail, discussion, and history associated with them. Others may have a smaller pool of issues. Maybe for that latter

RE: New Floeproject.org wireframe and site map

Apologies for the duplicate emails to list. Please ignore this email (delayed delivery due to oversized attachment). Thanks! -Jon. From: fluid-work On Behalf Of Jonathan Hung Sent: October 16, 2020 3:18 PM To: fluid-work@lists.idrc.ocad.ca Subject: New Floeproject.org wireframe and site map

Re: Default branch name in GitHub

I think “main” is a good name too. I’m glad this is only a convention in Git so we’re free to choose. Colin > On Oct 20, 2020, at 9:49 AM, Giovanni Tirloni wrote: > >  > +1 from me! > > Another helpful blog post: >

Re: Default branch name in GitHub

+1 from me! Another helpful blog post: https://www.hanselman.com/blog/easily-rename-your-git-default-branch-from-master-to-main From: fluid-work on behalf of Ned Zimmerman Sent: Tuesday, October 20, 2020 10:30 To: Michelle D'Souza ; Justin Obara Cc:

Re: Default branch name in GitHub

I’m in full support of this! Cheers, Ned — Ned Zimmerman (he/him) Senior Inclusive Developer Inclusive Design Research Centre, OCAD University https://idrc.ocadu.ca From: fluid-work Date: Tuesday, October 20, 2020 at 10:29 AM To: Justin Obara Cc: fluid-work@lists.idrc.ocad.ca Subject: Re:

Re: Default branch name in GitHub

Let’s switch to using “main”. It’s easy to do and more inclusive. https://dev.to/afrodevgirl/replacing-master-with-main-in-github-2fjf Michelle > On Oct 20, 2020, at 9:17 AM, Justin Obara wrote: > > While this has

Default branch name in GitHub

While this has actually been in effect since Oct 1 I just now realized that by default GitHub creates new repositories using “main” instead of “master”. I’m not intending to weigh in on the naming debate here, but I do think we need consistency. For details about the name change and how to

Re: Changes to Atlassian products

Gio and I spoke a bit in the fluid-work IRC channel this morning. Below is a quick summary: People aren’t happy about forced migration and lack of custom domains for Atlassian Cloud Atlassian said they’d review the