Date: Thu, 28 Mar 2024 17:42:56 -0400 (EDT)
Message-ID: <767792278.29002.1711662176671@lyrasis1-roc-mp1>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_29001_1484338368.1711662176671"
------=_Part_29001_1484338368.1711662176671
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
2020-07-02 Ontology Interest Group Call -- GitHub
2020-07-02 Ontology Interest Group Call -- GitHub
Thursday, July 2, 2020, 10 AM US Eastern Time
Connec=
tion Info
To join the online meeting:
Attendees=
h1>
Resources
Ontology Interest Group Google Folder https://drive.google.com/drive/u/0/folders/1RGBh4=
fDZdzpJdwyiUMO8OPWwkcmVYrI0
Google Doc for meeting notes: https://bit.ly/2YPPBwq
Attendees=
Agenda
- Github for Ontology work=20
- Where?
- How/process: issues/forks/pull requests
- Useful background/training/help guides
- Questions, comments
- What's next?
Notes
- Github for Ontology work
- VIVO Processes: https://github.com/vivo-project/VIVO/wiki/Git---GitHub-Processes
- General idea: It=E2=80=99s just a bunch of files
- We work in the open
- Folder structure will be needed (ontology group can develop).&nbs=
p; ODK was too complex.
- Where?
- ADO in mconlon17/ado on =
Github
- AEON in TIBonto/aeon on Github<=
/li>
- LANG in vivo-community=
/language-ontology on Github
- VIVO.owl (single file) in vivo-proje=
ct/vivo on GitHub
- Github vivo-ontology-lab (organization) unused
- How/process: issues/forks/branches/pull requests
- Fork to personal Github
- Clone personal fork to local
- Edit the local clone
- The remote is a connection from the local clone to github. =
You typically have a connection to your fork. You can create a remote=
to the canonical source.
- A branch creates a snapshot and is a safe place to work. Co=
de is isolated.
- Changes can be in three states:
- Local only
- Git add -- =E2=80=9Cplan to commit; staging=E2=80=9D
- Git commit -- creates a bundle of changes to the fork
- Git pull request from the fork to the remote
- Principles
- Never work in master
- Always work in a branch
- Clean work: Issue -> branch -> push to fork -> pul=
l request to remote; One issue at a time.
- Github desktop makes this easier.
- A pull might have 8 commits -- fixing typos, making changes reque=
st by reviewers, etc. A single commit (squash merge produces a single=
commit to the master branch) keeps the master branch commit history clean =
-- each commit is associated with a unit of work.
- Useful background/training/help guides
- A comparison of branching and forking: https://support.atlassian.c=
om/bitbucket-cloud/docs/branch-or-fork-your-repository/&nb=
sp;
- Some suggestions
- If you are not using GitHub desktop, it might be helpful=
li>
- Recommend to review in detail the VIVO repo wiki document: https://github.com/vivo-p=
roject/VIVO/wiki/Git---GitHub-Processes
- We=E2=80=99re going to need to practice
------=_Part_29001_1484338368.1711662176671--