13:38:18 <RRSAgent> RRSAgent has joined #wcag2ict
13:38:18 <RRSAgent> logging to https://www.w3.org/2022/10/20-wcag2ict-irc
13:38:20 <Zakim> RRSAgent, make logs Public
13:38:22 <Zakim> please title this meeting ("meeting: ..."), maryjom
13:38:25 <maryjom> zakim, clear agenda
13:38:25 <Zakim> agenda cleared
13:38:34 <maryjom> chair: Mary Jo Mueller
13:38:45 <maryjom> meeting: WCAG2ICT Task Force Teleconference
13:39:04 <maryjom> agenda+ Announcements
13:39:12 <maryjom> Agenda+ GitHub training
13:50:48 <pday_> pday_ has joined #wcag2ict
13:56:24 <ThorstenKatzmann> ThorstenKatzmann has joined #wcag2ict
13:56:31 <bruce_bailey> bruce_bailey has joined #wcag2ict
13:56:50 <ChrisLoiselle> present+
13:57:16 <Devanshu> Devanshu has joined #wcag2ict
13:57:18 <pday_> present+
13:57:51 <bruce_bailey> present+
13:57:52 <ShawnT> present+
13:58:07 <GreggVan> GreggVan has joined #WCAG2ICT
13:58:14 <GreggVan> present+
13:58:21 <shadi> shadi has joined #wcag2ict
13:58:27 <shadi> present+
13:58:53 <ThorstenKatzmann> present+
13:58:55 <bruce_bailey> hakim set a timer for 50 min
13:59:15 <bruce_bailey> zakim set a timer for 50 min
13:59:49 <bruce_bailey> zakim, set a timer for 50 min
13:59:49 <Zakim> I don't understand 'set a timer for 50 min', bruce_bailey
13:59:54 <ChrisLoiselle> Zakim, set a time for 50 min
13:59:55 <Zakim> I don't understand 'set a time for 50 min', ChrisLoiselle
14:00:07 <maryjom> zakim ?
14:00:18 <ChrisLoiselle> Zakim, set a timer for 50 min
14:00:18 <Zakim> I don't understand 'set a timer for 50 min', ChrisLoiselle
14:00:29 <BryanTrogdon> BryanTrogdon has joined #wcag2ict
14:00:37 <bruce_bailey> s/hakim set a timer for 50 min//
14:00:39 <Cara_Henderson> Cara_Henderson has joined #wcag2ict
14:00:52 <FernandaBonnin> FernandaBonnin has joined #WCAG2ICT
14:00:58 <bruce_bailey> s/zakim set a timer for 50 min//
14:01:03 <FernandaBonnin> present+
14:01:11 <Judy> present+
14:01:27 <Cara_Henderson> present+
14:01:35 <Devanshu> present+
14:01:49 <FernandaBonnin> scribe+ FernandaBonnin
14:01:59 <Mike_Pluke> Mike_Pluke has joined #wcag2ict
14:02:11 <Mike_Pluke> present+
14:02:17 <FernandaBonnin> zakim, next item
14:02:17 <Zakim> agendum 1 -- Announcements -- taken up [from maryjom]
14:02:36 <maryjom> regrets: Chuck Adams
14:03:08 <FernandaBonnin> maryjom: Chuck will be out the next couple of week
14:03:13 <olivia-hogan-stark> olivia-hogan-stark has joined #wcag2ict
14:03:46 <bruce_bailey> Welcome Mike Pluke !!!
14:03:57 <FernandaBonnin> maryjom: welcome Mike Pluke who was the co-facilitator on the previous TF
14:04:01 <olivia-hogan-stark> present+
14:04:59 <FernandaBonnin> did a quick round of introductions
14:05:33 <LauraBMiller> LauraBMiller has joined #WCAG2ICT
14:05:41 <BryanTrogdon> present+
14:05:41 <LauraBMiller> present+
14:08:03 <maryjom> https://www.w3.org/2022/10/18-ag-minutes.html#item01
14:08:05 <MichaelC> present+
14:08:09 <FernandaBonnin> maryjom: the AGWG conducted a survey on the work statement and it was unanimously approved without changes
14:08:11 <Sam> Sam has joined #wcag2ict
14:08:36 <FernandaBonnin> maryjom: the next step is the completion of the call to concensus. An email should come soon, we are encouraged to respond
14:09:04 <MichaelC_> MichaelC_ has joined #wcag2ict
14:09:07 <FernandaBonnin> maryjom: the goal of this meeting is to lear nhow to use GitHub and ensure we are comfortable with using GH
14:09:44 <bruce_bailey> q+ to ask about GitHub versus GitHub + VSC + GitDesktop
14:09:54 <FernandaBonnin> maryjom: we have our own WCAG2ICT repository, where our Note currently is
14:09:54 <maryjom> ack bruce_bailey
14:09:54 <Zakim> bruce_bailey, you wanted to ask about GitHub versus GitHub + VSC + GitDesktop
14:10:46 <MichaelC_> q+
14:10:47 <FernandaBonnin> 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
14:12:05 <MichaelC_> ack me
14:12:05 <FernandaBonnin> 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
14:12:35 <maryjom> https://github.com/w3c/wcag2ict
14:12:39 <FernandaBonnin> maryjom: will cover basics of using GitHub and you can follow along and get started
14:12:44 <Sam> agree with Bruce that markdown is very easy to use to make edits and contribute
14:13:12 <bruce_bailey> i love PR and branches !!!
14:13:16 <FernandaBonnin> maryjom: even if we change to markdown, there are some basic stuff to learn like creating branches to propose changes
14:14:00 <FernandaBonnin> maryjom: you can use the web interface by going from the main and just go on the file that is on main
14:14:18 <bruce_bailey> q+
14:14:31 <bruce_bailey> ack me
14:15:02 <AnastasiaLanz> AnastasiaLanz has joined #wcag2ict
14:15:10 <AnastasiaLanz> present+
14:15:16 <FernandaBonnin> 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
14:15:22 <Sam> present+
14:15:52 <ShawnT> shouldn't we fork?
14:16:22 <Cara_Henderson> q+
14:16:33 <FernandaBonnin> maryjom: and then go to file > index.html. We might want to split out all of the sections of the document at some point
14:17:34 <FernandaBonnin> 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
14:17:52 <MichaelC_> I think we can automate some of that cruft as well
14:17:57 <FernandaBonnin> ack Cara_Henderson
14:17:59 <maryjom> ack cara
14:18:52 <AnastasiaLanz> q+
14:19:17 <maryjom> ack AnastasiaLanz
14:19:21 <FernandaBonnin> maryjom:  you can't use spaces or special char when creating a branch
14:19:29 <maryjom> https://github.com/w3c/wcag2ict
14:19:49 <Cara_Henderson> q+
14:20:02 <FernandaBonnin> AnastasiaLanz: how do I get access to the repo
14:20:16 <bruce_bailey> Create your own branch from repo:  main (button) drop down -> View all Branches -> New branch (green button at top right)
14:20:39 <maryjom_> maryjom_ has joined #wcag2ict
14:21:41 <ChrisLoiselle> https://github.com/w3c/wcag2ict/branches
14:21:51 <FernandaBonnin> Discussed some issues with having permissions to create a branch
14:22:09 <ChrisLoiselle> new branch , green button , labeled as new branch
14:23:19 <pday_> q+
14:24:09 <AnastasiaLanz> You can only create a branch if you have access to the repository
14:25:16 <FernandaBonnin> 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]
14:25:25 <FernandaBonnin> MichaelC_: you make a PR
14:25:28 <maryjom_> q?
14:25:32 <maryjom_> ack cara
14:25:50 <FernandaBonnin> +1
14:26:09 <FernandaBonnin> Cara_Henderson: cannot create a branch
14:26:17 <ShawnT> q+ to speak on forking
14:26:33 <ShawnT> q-
14:26:36 <FernandaBonnin> dmontalvo: we might need to fork?
14:26:50 <FernandaBonnin> MichaelC_: we don't want to get people involved in forks
14:27:14 <FernandaBonnin> MichaelC_: please send your user name to Daniel if you cannot create branches
14:27:39 <maryjom_> ack pday_
14:28:07 <FernandaBonnin> pday_: I was not able to create a branch on the web UI but I could create a branch on desktop?
14:28:30 <FernandaBonnin> MichaelC_: you will need permissions to create a PR
14:29:54 <FernandaBonnin> 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
14:30:41 <ShawnT> https://www.w3.org/groups/tf/wcag2ict/participants
14:30:44 <FernandaBonnin> maryjom_: everyone's ID is in the participants list for the taskforce
14:30:55 <Mike_Pluke> q+
14:31:33 <bruce_bailey> q+ to suggest View all branches from Main button drop down
14:32:02 <maryjom_> ack mike
14:32:06 <maryjom_> ack Mike_Pluke
14:32:09 <FernandaBonnin> maryjom_: once you create the branch we select it to move to it
14:32:31 <FernandaBonnin> Mike_Pluke: on the app, I cannot get to the same page you are showing right now
14:33:40 <FernandaBonnin> 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
14:34:02 <FernandaBonnin> maryjom_: to clone it, you can go to the Code button and select Open with GitHub Desktop
14:35:00 <FernandaBonnin> 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
14:35:32 <FernandaBonnin> Mike_Pluke: how do I get to the same page you are showing?
14:36:31 <maryjom_> q?
14:36:31 <FernandaBonnin> 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
14:36:50 <maryjom_> ack bruce_bailey
14:36:50 <Zakim> bruce_bailey, you wanted to suggest View all branches from Main button drop down
14:37:41 <ShawnT> I think if we switch to markdown, the web interface will be a lot nicer
14:37:42 <FernandaBonnin> maryjom_: some folks will prefer the web interface and some will prefer the desktop one
14:37:43 <FernandaBonnin> q+
14:38:39 <FernandaBonnin> 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
14:38:55 <ChrisLoiselle> https://github.com/w3c/wcag2ict/branches
14:39:27 <ChrisLoiselle> new branch , green button , labeled as new branch
14:40:04 <FernandaBonnin> GreggVan: for the ones that have no access to create branches, the New branch button is not there
14:40:10 <ShawnT> q?
14:40:29 <FernandaBonnin> maryjom_: once we have access, try creating a branch to get started
14:42:06 <FernandaBonnin> 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
14:42:29 <FernandaBonnin> GreggVan: can we make a video of this since we cannot follow?
14:43:05 <FernandaBonnin> maryjom_: if there is need for captioning, email me separately, please
14:43:06 <ShawnT> q+ to speak on github when using the browser interface, github takes care of all the branching and forking for you
14:43:50 <ChrisLoiselle> https://docs.github.com/en is a great resource for all of this too
14:44:24 <FernandaBonnin> 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>
14:44:47 <ChrisLoiselle> https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository
14:45:13 <FernandaBonnin> maryjom_: some of the markup we use is headings <h1>, paragraphs <p>, lists <ul> and <li>, bold <strong>
14:46:18 <FernandaBonnin> 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)
14:47:27 <FernandaBonnin> 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
14:47:59 <FernandaBonnin> q?
14:48:02 <pday_> q+ to ask for clarification on differences between commit changes, pull requests, and issues.
14:48:51 <maryjom_> ack FernandaBonnin
14:49:18 <FernandaBonnin> maryjom_: you can assign reviewers to your PR
14:49:43 <FernandaBonnin> FernandaBonnin: you can preview your changes if you use an editor like Visual Studio Code
14:50:17 <maryjom_> ack shawn
14:50:17 <Zakim> ShawnT, you wanted to speak on github when using the browser interface, github takes care of all the branching and forking for you
14:51:23 <FernandaBonnin> 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
14:51:58 <maryjom_> ack pday_
14:51:58 <Zakim> pday_, you wanted to ask for clarification on differences between commit changes, pull requests, and issues.
14:52:25 <FernandaBonnin> pday_: what is the difference between commit changes, PR and issues?
14:53:32 <ChrisLoiselle> On issues, https://docs.github.com/en/issues is a great guide
14:54:03 <ChrisLoiselle> On pull requests, https://docs.github.com/en/pull-requests
14:54:11 <MichaelC_> q+
14:54:25 <FernandaBonnin> 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
14:54:28 <maryjom_> ack MichaelC_
14:55:08 <FernandaBonnin> 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
14:55:36 <ChrisLoiselle> For what Michael mentioned regarding Pushing commits , https://docs.github.com/en/get-started/using-git/pushing-commits-to-a-remote-repository
14:56:02 <ChrisLoiselle> https://docs.github.com/en/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/pushing-changes-to-github
14:56:52 <FernandaBonnin> 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
14:56:58 <FernandaBonnin> q?
14:57:00 <maryjom_> q?
14:57:52 <FernandaBonnin> maryjom_: I will make videos and post them so you can try it out for yourself, please try out before the meeting
14:58:17 <FernandaBonnin> maryjom_: and I will work with Michael on how to split up the file
14:58:27 <FernandaBonnin> rrsagent, make minutes
14:58:27 <RRSAgent> I have made the request to generate https://www.w3.org/2022/10/20-wcag2ict-minutes.html FernandaBonnin
14:58:34 <FernandaBonnin> zakim, bye
14:58:34 <Zakim> leaving.  As of this point the attendees have been ChrisLoiselle, pday_, bruce_bailey, ShawnT, GreggVan, shadi, ThorstenKatzmann, FernandaBonnin, Judy, Cara_Henderson, Devanshu,
14:58:34 <Zakim> Zakim has left #wcag2ict
14:58:38 <Zakim> ... Mike_Pluke, olivia-hogan-stark, BryanTrogdon, LauraBMiller, MichaelC, AnastasiaLanz, Sam
14:58:54 <pday_> pday_ has left #wcag2ict
14:59:05 <maryjom_> rrsagent, make minutes
14:59:05 <RRSAgent> I have made the request to generate https://www.w3.org/2022/10/20-wcag2ict-minutes.html maryjom_
16:32:46 <ShawnT> ShawnT has joined #wcag2ict
17:32:08 <maryjom> maryjom has joined #wcag2ict
17:43:08 <maryjom> maryjom has joined #wcag2ict
18:19:47 <maryjom_> maryjom_ has joined #wcag2ict
20:19:15 <ShawnT> ShawnT has joined #wcag2ict
21:33:18 <ShawnT> ShawnT has joined #wcag2ict
22:42:29 <ShawnT> ShawnT has joined #wcag2ict
22:54:28 <ShawnT> ShawnT has joined #wcag2ict