This repository has been archived by the owner on Oct 23, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Agenda Notes Monday January 29th 2018 11:00 AM
Michael Duda edited this page Jan 31, 2018
·
6 revisions
Date: 29 January 2018
Time: 11:00 MDT / 19:00 CET
Call-in number: 1-866-740-1260
Access Code: 4978161
- Discuss E3SM/MPAS repo set-up. Notes at: https://docs.google.com/document/d/1MGYIydK9ufuqfUySkbxcusPSPL9eGUphbot9-GP8DjE/edit?usp=sharing
- Other topics?
Monday, 8 January 2018 @ 11:00 MDT
Participants: Mark, Todd, Xylar, Bill, Michael, Matt, Adrian
- There is a need for some collaborators to work on private repos.
- If MPAS-Dev/MPAS is changed to be public, forks remain private but users with private forks get charged. Such a change would require communication with all developers with private forks, which is a downside.
- We can rename github repos. See https://help.github.com/articles/renaming-a-repository. If we renamed MPAS-Release (for example), we would need to inform users that they must change local repos that point to the new name.
- One option is to leave MPAS-Dev/MPAS as private, and then migrate needed branches to a new public repo (or renamed MPAS-Dev/MPAS-Release). Pro: users can continue private development on MPAS-Dev/MPAS with no notification. Con: All history of issues and pull requests will restart. Con: worse yet, a new repo would restart our numbering history for issues and PRs, so all old references to PRs and issues would no longer link, even though all those numbers are in the git log. Con: (really bad) there would be two of every issue/PR number, i.e. a #319 on both old and new repos, with no way to know which it is other than the date. There could be some hacky ways to transfer all issues between repos, see https://github.com/holman/ama/issues/413.
- The name of our working repo is important and should be considered carefully. For example, MPAS-Release implies that it is for releases only. MPAS-Public makes people wonder if there is a private one they can’t see.
- One option for a public/private split is to have framework be public and be a submodule in the core branches. Michael said he would prefer to look at other options to avoid the difficulty of submodules, and making sure each core is in sync with a framework on another branch.