Comments (19)
updates made via #100 , @maryjom let me know if this is correct.
from wcag2ict.
Hi @maryjom @ChrisLoiselle sorry for my late response.
My proposal would be.
- Editors, provided by respecConfig variable and done by @ChrisLoiselle
- Former editors (at the top of the document, provided by respecConfig variable and done by @ChrisLoiselle
- Acknowledgement section, an appendix at the end of the content generated manually from new markdown files
- Previous contributors
- Current participants in the WCAG2ICT Task Force
- Current participants in the WCAG Working Group that have actively reviewed and contributed
- Enabling founders
I would suggest to not list the previous TF and WG participants for the 2013 version, i thikn we could do a better job of synthesis by just listing the previous contributors. We'd have already quite a long section there anyway.
If you all agree with this, I could create the structure and the necessary md files and then @ChrisLoiselle and/or @maryjom could fil them in.
from wcag2ict.
@daniel-montalvo works for me if it works for @maryjom
from wcag2ict.
- do we have a list of former editors that I can pull from?
- is this something that can be automatically pulled in ?
- for the contributors and current contributors, can we pull that data directly from the WCAG2ICT group member list or should I be referencing elsewhere?
from wcag2ict.
from wcag2ict.
@GreggVan Thank you, great point. I've made a pull request to add a markdown file to the main branch. Confirming with @maryjom per editor process now, thank you !
from wcag2ict.
@ChrisLoiselle, wrong Shawn @mentioned?
from wcag2ict.
Perhaps, apologies.
from wcag2ict.
@ChrisLoiselle In the previous WCAG2ICT note, there is a list of editors and a list of authors. From what I can tell, editor/author lists are managed in the file respec-config.js. The W3C style guide gives tips on including former editors, but doesn't say if this is optional or required. I'm sure @michael-n-cooper or @daniel-montalvo could answer that.
If former editors are required/recommended, the code to use for adding former editors would be added after the editors (see example usage in WCAG's respec-config.js :
formerEditors: [ { name: "FirstName LastName", company: "Company name", w3cid: 5DigitIDCode }, { name: "Mary Jo Mueller", company: "IBM", w3cid: 33602 } ],
Here's the authors markup to put in that same file...after former editors:
authors: [ { name: "FirstName LastName", url: "http://example.org/", company: "Company name", companyURI: "http://example.com/" }, { name: "FirstName2 LastName2", url: "http://example2.org/", company: "Company name2", companyURI: "http://example2.com/" } ],
from wcag2ict.
@ChrisLoiselle WCAG also has an Acknowledgements appendix with some sub-sections that recognize "Participants of the AG WG active in the development of this document", "Other previously active WCAG WG participants and other contributors to WCAG 2.0, WCAG 2.1, or supporting resources", and "Enabling Funders". Here's a link to the WCAG source files for those sections so you can see the verbiage they use and methods for listing the participants.
The old WCAG2ICT had similar Acknowledgement sections. So if we wind up listing previous contributors you have the full list.
I'll have a conversation with Daniel and Chuck on Monday, 6 February to see what is required and/or recommended for us to do in the updated Working Group Note.
from wcag2ict.
@maryjom thanks, just noting that I've read what you have stated and I'll monitor.
from wcag2ict.
@daniel-montalvo I have merged in Chris' pull request to add in former editors as this looks good. Please comment on this issue what we should have in the updated Note's Acknowledgement sections. I've added checkboxes below where you can indicate what we should have.
Acknowledgements for current WCAG2ICT work and contributions:
- authors and/or contributors (and should those be at the top of the document under the editors as it was in the previous Note?)
- participants in the Task Force
- active participants in the AG WG who reviewed/approved the Note
- enabling funders
Do we need to continue to include any of the following acknowledgements from previous WCAG2ICT published Note:
- previous participants in the Task Force
- previous authors
- previous active participants in the AG WG who reviewed/approved the Note
- previous enabling funders (if the list is different from what we have for the current work)
For current participants and authors/contributors, can we obtain the list of using GitHub commands or commands to obtain TF participant list, or will we have to manually set up?
from wcag2ict.
@daniel-montalvo and @maryjom let me know what you'd like me to take action on regarding this issue, thank you!
from wcag2ict.
Oops....didn't mean to close this since the work is partially complete.
from wcag2ict.
@daniel-montalvo Are there enabling funders that need to be named? If so, who are they?
from wcag2ict.
Thanks @maryjom
That is a good catch. We should have that section as well. I'll will work on it.
from wcag2ict.
@daniel-montalvo or @maryjom are there any other open items on this? Original thread checkboxes appear to be done but there are commented checkboxes that are now still outstanding. Please let me know if there any action items to be assigned to me within the sub threaded comments.
from wcag2ict.
@ChrisLoiselle I'm going to address updating the lists again right before publishing the FPWD with a new issue - see #130. For now you can see that the AG WG participants section is in there with the folks that have been posting in our issues as we work on them. Will update with AG WG participants that responded to surveys before we publish the final note too. See issue #131.
I opened a separate issue for Daniel to add the enabling funders section, but he hasn't gotten to that yet. See #121. Other than that, the initial info in there is sufficient. Daniel seemed to think we didn't need the full list of AG WG members.
from wcag2ict.
All up-to-date and published in the FPWD. Will open a new issue for the next draft to be published with WCAG 2.2 incorporated.
from wcag2ict.
Related Issues (20)
- SC problematic for Closed functionality: SC 2.1.1 Keyboard HOT 2
- WCAG2ICT Task Force web page issues HOT 3
- Use of requires or required or requiring HOT 4
- Project task: Update contributors and company affiliations HOT 12
- Project task: Remove, update, or add editor's notes HOT 1
- Project task: Task force review of the draft and agreement to publish HOT 1
- Project task: Set up for AG WG review of latest editor's draft and newly added SC HOT 1
- Project task: Set up and track horizontal review of the draft HOT 4
- Project task: Create communication announcing publication and when comments are due HOT 2
- Project Task: Update the Status of this document and abstract HOT 7
- 4.1.1 Parsing is missing the WCAG 2.2 content in the built document HOT 1
- Remove "previous version" respec key HOT 3
- AG WG Review: 4.1.1 Parsing WCAG2ICT guidance HOT 4
- [Editorial] Take a pass for Oxford comma and decide whether or not to use HOT 3
- AG WG Review: 3.3.8 Accessible Authentication (Minimum) WCAG2ICT guidance HOT 3
- AG WG Review: 3.2.6 Consistent Help WCAG2ICT guidance
- AG WG Review: WCAG2ICT Guidance for Products with Closed Functionality HOT 4
- AG WG Review: WCAG2ICT editor's draft HOT 1
- Focus Not Obscured needs a note for non-web software HOT 4
- Feedback from Microsoft on wcag2ict Reflow notes 5 and 7 HOT 7
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from wcag2ict.