- From: Eric Eggert <ee@w3.org>
- Date: Thu, 10 Oct 2019 15:29:51 +0200
- To: "Shadi Abou-Zahra" <shadi@w3.org>
- Cc: "Hidde de Vries" <hidde@w3.org>, wai-eo-editors@w3.org
I don’t feel like investing more time into the discussion. Testing process is very general. CI and deployment are also not a “buzzwords” but proper specialized terminology, as much as CMS is. The suggested wording is good enough for me. On 10 Oct 2019, at 15:25, Shadi Abou-Zahra wrote: > You initially suggested "deploy process", which I expanded to "testing > process". You are not speaking of "continuous integration (CI)", which > is another buzzword (besides "continuous deployment (CD)", "continuous > testing (CT)", etc.). I add this to the agenda to get further input. > > Many thanks, > Shadi > > > On 10/10/2019 15:17, Eric Eggert wrote: >> It works but it does not address my specific comment, which, at this >> point, I don’t want to further pursue. If we don’t want to >> mention CI, which would help many development teams, then this OK for >> me. >> >> 👋 Eric >> >>> >>> On 10. Oct 2019, at 14:52, Shadi Abou-Zahra <shadi@w3.org> wrote: >>> >>> I changed the sequence now to: >>> >>> "Tools can be integrated into different work environments. For >>> example, into your web browser, content management system (C-M-S), >>> code editor, or your testing process." >>> >>> Hope this works now? >>> >>> Best, >>> Shadi >>> >>> >>> On 08/10/2019 09:56, Hidde de Vries wrote: >>>>>> On 8 Oct 2019, at 09:10, Eric Eggert <ee@w3.org >>>>>> <mailto:ee@w3.org>> wrote: >>>>> >>>>> Project managers should know what a deploy process & continuous >>>>> testing is, they have to plan for both. >>>>> >>>>> I don't think there is a way to make that more understandable for >>>>> “non-techies” as we can’t make JavaScript, code editor, >>>>> content management system or web browser more understandable for >>>>> “non-techies”. For “non-techies”, all of those words are >>>>> jargon. And that‘s ok imho because we said ”work >>>>> environments” first. >>>> Yep, I believe deploy process and continuous testing (or >>>> “continuous deployment”) should be understandable for most >>>> project managers. Agreed it is a bit jargonny, but in the same >>>> sense as “content management system” and “web browser”. >>>> Fwiw, I've also heard the term a lot from project managers whom (I >>>> suspected) did not necessarily know what it means (so I think the >>>> group of people who know that it exists is larger than the group of >>>> people who know what it is). >>>> Examples of the terminology used in the wild: >>>> - Atlassian, makers of project management tooling, don't shy away >>>> from the terminology on their homepage >>>> <https://www.atlassian.com/>, and product pages >>>> <https://www.atlassian.com/software/bamboo> >>>> - Gitlab, another project (or more like: source code) management >>>> solution <https://gitlab.com> even use the abbreviation “CI” as >>>> one of the first things on their homepage >>> >>> -- >>> Shadi Abou-Zahra - http://www.w3.org/People/shadi/ >>> Accessibility Strategy and Technology Specialist >>> Web Accessibility Initiative (WAI) >>> World Wide Web Consortium (W3C) >> > > -- > Shadi Abou-Zahra - http://www.w3.org/People/shadi/ > Accessibility Strategy and Technology Specialist > Web Accessibility Initiative (WAI) > World Wide Web Consortium (W3C) -- Eric Eggert Web Accessibility Specialist Web Accessibility Initiative (WAI) at World Wide Web Consortium (W3C)
Received on Thursday, 10 October 2019 13:29:56 UTC