Meeting minutes
<maryjom> zakim ?
Announcements
maryjom: Chuck will be out the next couple of week
<bruce_bailey> Welcome Mike Pluke !!!
maryjom: welcome Mike Pluke who was the co-facilitator on the previous TF
did a quick round of introductions
<maryjom> https://
maryjom: the AGWG conducted a survey on the work statement and it was unanimously approved without changes
maryjom: the next step is the completion of the call to concensus. An email should come soon, we are encouraged to respond
maryjom: the goal of this meeting is to lear nhow to use GitHub and ensure we are comfortable with using GH
maryjom: we have our own WCAG2ICT repository, where our Note currently is
<Zakim> bruce_bailey, you wanted to ask about GitHub versus GitHub + VSC + GitDesktop
Bruce: want to refloat the idea that using GitHub can be easy but we are using it the hard way. We could be doing smaller markdown editor instead of HTML
MichaelC_: the way things I setup right now, we setup with what we had last time and how we have other documents with HTML. We can split the file into little files, if people would prefer Markdown, it can be setup that way although they would be a small learning curve for publishing
<maryjom> https://
maryjom: will cover basics of using GitHub and you can follow along and get started
<Sam> agree with Bruce that markdown is very easy to use to make edits and contribute
<bruce_bailey> i love PR and branches !!!
maryjom: even if we change to markdown, there are some basic stuff to learn like creating branches to propose changes
maryjom: you can use the web interface by going from the main and just go on the file that is on main
maryjom: First, lets create a branch. by selecting the main dropdown on the repo and using the textbox to type a branch name and using the create button
<ShawnT> shouldn't we fork?
maryjom: and then go to file > index.html. We might want to split out all of the sections of the document at some point
maryjom: everything has a beginning tag and end tag. each section has its own heading and then you create paragraphs. I would not worry about links
<MichaelC_> I think we can automate some of that cruft as well
maryjom: you can't use spaces or special char when creating a branch
<maryjom> https://
AnastasiaLanz: how do I get access to the repo
<bruce_bailey> Create your own branch from repo: main (button) drop down -> View all Branches -> New branch (green button at top right)
<ChrisLoiselle> https://
Discussed some issues with having permissions to create a branch
<ChrisLoiselle> new branch , green button , labeled as new branch
<AnastasiaLanz> You can only create a branch if you have access to the repository
MichaelC_: a branch is an alternate version of the document that was forked on a certain time. The typical reason we have to create a branch is to propose edits or additions to content. To create a branch you first want to make sure your branch is created from main. type the name of the new branch and it will create it. On a branch you should be working on a specific section, we might adopt naming protocols to indicate that, an[CUT]
MichaelC_: you make a PR
+1
Cara_Henderson: cannot create a branch
dmontalvo: we might need to fork?
MichaelC_: we don't want to get people involved in forks
MichaelC_: please send your user name to Daniel if you cannot create branches
pday_: I was not able to create a branch on the web UI but I could create a branch on desktop?
MichaelC_: you will need permissions to create a PR
maryjom_: to create a branch use the Main dropdown and then type the name of your branch with your <initials>-<thing you are working on>. This allows everyone to know what you are working on
<ShawnT> https://
maryjom_: everyone's ID is in the participants list for the taskforce
maryjom_: once you create the branch we select it to move to it
Mike_Pluke: on the app, I cannot get to the same page you are showing right now
maryjom_: GitHub Desktop, you change a repository from the Filter searchbar by searching for the repo. if you don't have that listed, then you first need to clone
maryjom_: to clone it, you can go to the Code button and select Open with GitHub Desktop
maryjom_: in GitHub Desktop you can then search the repo, and change your branch to the branch you created or create a new branch from the GitHub desktop UI
Mike_Pluke: how do I get to the same page you are showing?
maryjom_: if you have a code editor, like Visual Studio Code, you can use it to get the files and work from there. The list of files here would be the same as in the web UI for GitHub
<Zakim> bruce_bailey, you wanted to suggest View all branches from Main button drop down
<ShawnT> I think if we switch to markdown, the web interface will be a lot nicer
maryjom_: some folks will prefer the web interface and some will prefer the desktop one
bruce_bailey: if you go to the branch button, there is a button for view all branches and you can see your branches and active branches. Also if you don't have permissions you get a more robust message
<ChrisLoiselle> https://
<ChrisLoiselle> new branch , green button , labeled as new branch
GreggVan: for the ones that have no access to create branches, the New branch button is not there
maryjom_: once we have access, try creating a branch to get started
maryjom_: to make changes in the document in the web interface, select the edit split button (has a pencil) and select edit this file. There is also a button to open in GitHub desktop
GreggVan: can we make a video of this since we cannot follow?
maryjom_: if there is need for captioning, email me separately, please
<ChrisLoiselle> https://
maryjom_: you can search in the file by using cmd+F and then you can type changes by using basic HTML markup like <p> paragraph text </p>
maryjom_: some of the markup we use is headings <h1>, paragraphs <p>, lists <ul> and <li>, bold <strong>
maryjom_: after making a change, go to the bottom of the page and use the Commit changes section into your branch. And then you can make a Pull Request (PR)
maryjom_: the UI shows you a reminder if you have changes and there is a button to compare and create a PR. In the comments you can reference the issue that points to the work you are doing (by using #<number of the issue). and then select the Create a pull request button
maryjom_: you can assign reviewers to your PR
FernandaBonnin: you can preview your changes if you use an editor like Visual Studio Code
<Zakim> ShawnT, you wanted to speak on github when using the browser interface, github takes care of all the branching and forking for you
ShawnT: if we use the browser, it creates the repo for you and it will also create a fork for you if you don't have access to the repository. If we did switch to Markdown, it would also allow us to preview
<Zakim> pday_, you wanted to ask for clarification on differences between commit changes, pull requests, and issues.
pday_: what is the difference between commit changes, PR and issues?
<ChrisLoiselle> On issues, https://
<ChrisLoiselle> On pull requests, https://
maryjom_: issues are things that are open to track work, problems or public comments. When we do changes in the files we can refer to issues. Commit changes happens when you are making changes, its basically a save. One PR can have various commits
MichaelC_: if you are working on the command line, there is also a push. Your commits are only saved locally so you need to push your changes
<ChrisLoiselle> For what Michael mentioned regarding Pushing commits , https://
<ChrisLoiselle> https://
maryjom_: using GitHub desktop, making sure you are in the branch you have your edits, you can use the button on the left nav bar to commit the changes to your branch
maryjom_: I will make videos and post them so you can try it out for yourself, please try out before the meeting
maryjom_: and I will work with Michael on how to split up the file