Meeting minutes
zakim scribe, jongunderson
Home Page
MK: I have a PR from last week
MK: MM reviewed the changes
JG: I can provide a review after the call
MK: If JG approves I will push to main
MK: Anything Rich?
Rich: Looks good
JumpTo updates
MK: We are updating in PR #131
MK: Fixes bugs
MK: Rich can you review the changes
MK: I need help with the scroll to bottom issue
Rich: I will get a reviewer tomorrow
MK: It touched 150 files
Rich: It is all the files with the JumpTo in, so we need to go back and testing
Rich: Hopefully merge tomorrow when Shaun gets back
Seth: We have made some changes
Seth: What about fixes
Seth: What about changes in the future
Seth: What ever version we use we want to track changes
MK: We have a version right now, and we can make changes ourselves
JN: Do we have a dependency on 4.2?
JN: We have our own version
MK: I cannot find anyting about BSD about versioning
Milestone planning
MK: Want to provide information where we are going next
MK: Especially in the Jeckle repo, we will have a project to track the progress
MK: Milestones for that quarter
<Matt_King> Q2 milestone for site build repo: https://
MK: If you look at this milesont, you can see a descrption
MK: We will track how we are progressing through these milestones
<Matt_King> q3 milestone: https://
MK: I put in high level goals, a proposal, we need to line up with Q3 goals
MK: How I am structuring for our priorities
MK: I just want to make sure the issues in the project board are in this
Rich: We need to move everything forward
Ricj: There are 5 items in the backlog
MK: If we don't finish them we will carry forward
MK: Since we are in trensistion from a PR to a website, so there is some smoke and mirros here
MK: There is code quality work...
MK: There is aligning with ARIA 1.3 ....
MK: We still have content we need for ARIA 1.1
MK: How do we have useful conversations about priorities and how the group will shape the priorities
MK: Otherwise should the editors set the priorities and shephard the group to those priorities
MK: Any thoughts?
MK: Are we off track becasue we are not doing X or Y
JN: What you got seems good
MK: I will just keep trying to do this
MK: I did write something about APG
MK: Our original goal was to describe ARIA
JN: People expect something different
MK: You shouldn't have to go to more than one place to build an accordian
MK: I wrote something up, on how we pritorize and what the bocoup team works on
MK: That's all for milestones now
MK: In the description of the milestone in the Q3, in the heading and you expand it, setting the build process that transforms...
Rich: Alright
MK: Building out the about section, coverage report and the quality reports, and then developing an automated change history
MK: Being able to see the history of changes in a user friendly way
MK: The WAI site has an example of this
MK: I want to discuss the timing of the study, not necessarily this quarter
MK: We need to talk about as a group
MK: That gets back to content, we want content for ARIA 1.3, and we have milestones
MK: We don't need to talk about that in detail, time lines?
JN: I will be talking to Valarie, we need to get cors-aam to rec and then it goes evergreen
MK: Is ARIA 1.2 blocked by core-aam?
JN: Yes, I have been bugging MC about getting a wide review out, doing what we can
MK: I need to have a planning with Valerie for 1.3
JN: Valarie is better on planning than I am, so that should help
MK: We will come back to this
JN: Hopeflly connect with Valerie next week
MK: Some ARIA 1.3 is ready
JN: I am out for 3 weeks in July
JN: Next year I can get a sabatical
discussion of vacation time....
Rich: We do have the outstanding issue of re-directs, I sen you an e-mail
MK: Sould we talk about it?
JN: We need to announce something about what we are doing
Redirects
RichL Talked to W3C webmaster and he said what he has done
Rich: This material is out of date, and then a link to new material
Rich: W3C does not want to do automatic redirects on dated content
JN: What about examples, they are just broken
Rich: The pages are still there, but they have been removed from being served
Rich: I am going down the dated path to get a redirected to latest content
MK: If you look in the URL there is a date
JN: If someone had the non-dated version, why wouldn't that automatically redirect?
Rich: I am looking at the timeliness of the solution, this is the fastest way
Seth: Are they OK re-directing the non-dated short links
Seth: There is a non-dated modal dialog, and they were comfortable redirecting them
Rich: Description of short links they are comfortable re-directing
Rich: If the task force want to the time
MK: What if we give them mappings
Rich: I gave them the mappings
SethL I am happy generating them
RichL I mean time for a solution, if it is urgent
MK: We are getting complaints about the non-dated links to non-dated examples. exact same mapping
MK: we eitehr get a warning or an automatic redirect
Rich: I will pose the question, and see what he says
MK: Let's move forward on 1.1 and 1.2 as quick as possible
MK: Later we can decide if it is worth it on the dated ones
MK We just don't want search engines to continue mining them
MK: I wonder how the warning works with screen readers
Rich: He provided me with an example of the redirect
<Rich_Noah> This is an example of the warning: https://
Seth: To some extent the dated examples have always been out of date
MK: In 1.1 and 1.2 the content is in those dated pages
MK: You don't see the date
Seth: If the distinction is important, we will make a buch a chnages, but not fixed all the links out there
Seth: I think the clean URL are a higher priority than the dated
MK: Rich I am happy you are in direct contact, let's try to get some amount of progress
Rich: I will not be able to contact until tomorrow morning