Date: Thu, 28 Mar 2024 06:20:59 +0000 (UTC)
Message-ID: <1010203503.18877.1711606864827@confluence>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_18876_1824006233.1711606859815"
------=_Part_18876_1824006233.1711606859815
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Attendees: Chris, Jim, Lynne, Scott, ajc, Kem, Cathy, Frossie, Brittany, Ve=
ljko, Zeljko, Simon, Peter, K-T, Darko, Heather
Call in number: 866 330 1200
Code: 518 2287#
Goto Meeting ID &nbs=
p;821-177-359
 =
;
Summa=
ry: no fundamental concerns were expressed in moving from Stash to Github a=
s long as SQuaRE can take the lead in moving the commit comments over and s=
hepherd the sims move to github. We would like to have a transition plan fo=
r the move to ensure that it goes smoothly and some help in setting up the =
workflows.
<=
/span>
<=
/span>
Agenda:
- A proposal to move to Github (Frossie)
- What are the =
benefits from Github
- It is the leading OS repository=
system. We would move to something else if Github was not the lead (or cea=
ses to be the leader in open source repositories). This provides visibility=
for developers and helps them with their careers (people look if you are o=
n Github)
- DM wants to move the discussion=
of the code into the code base to make us agnostic to the repository syste=
m
- What are the issues in moving f=
rom Stash
- Stash has a cleaner interface b=
ut most of the tools we use (e.g. Jira) work with stash and Atlasssian is b=
ursty in its development
- No option for multiple reviewers or the ability to approve (can hack th=
is functionality - set milesto=
nes via JIRA triggers and tag them to the API - but a hack)
- Pull requests from git hub inte=
rface to jira, email noise from notifications can be an issue but it is con=
figurable, not as streamline as stash,
- still need to close out issues =
on JIRA after the pull request but close commits in smart comments=
li>
- can't create branches from a JI=
RA agile issue
- Github has better anonymous acc=
ess (through pull requests)
- There are private repos for sen=
sitive material (you can also mirror the repos but that is fairly clumsy)=
span>
- Number of repos is large in DM =
(most of our repos don't build standalone). Not a lot of other groups outsi=
de of LSST have this issue
- Linux model has a hierarchy of =
repos - set of gate keepers who control each set of code
- could create a webpage to organ=
ize the repos
- What needs to happen to move
- At the git level it is just changing the remote (as we did to move to s=
tash)
- We need a transition plan that will document how things will move and w=
hen
- SQuaRE will provide support for the move (including moving comments in =
the current commits and reviews)
- SQuaRE will define the naming conventions for the repos so that they ar=
e easy to find (or set up a webpage that lists and organizes the repos)
- We will need to define the workflows and test them before the move
- SQuaRE has offered to provide developer support for all of the software=
efforts (not just DM) that work with its framework and any future transiti=
ons
From Chris Walter:
Because of the way things are setup there, wit=
hout a compact view of all of the repos I think some sort of good namespace=
for repo names is key. Then you can just start to type the name of the rep=
o in the search box and the github site immediately starts to narrow down t=
he repos to ones with that name.
For the sims repos this ins't a problem since they already start wit=
h "sims_". But the DM stuff doesn't. So, if DM transitions too =
I think DM needs some sort of similar name space prefix. Otherwise we=
will probably want separate organizations (LSST_Sims, LSST_DM etc) but I t=
hink one organization with descriptive name spaces is better.
Another thing to think about: what abou=
t contributed repos? Do we want a contrib_ area or should people just have =
keep things in their own github accounts? If so how do we track them?  =
;Also, I noticed through the API you can make web pages that show all of th=
e repos.
------=_Part_18876_1824006233.1711606859815--