W3C home > Mailing lists > Public > public-test-infra@w3.org > April to June 2013

"Help" channels in terms of testing

From: HU, BIN <bh526r@att.com>
Date: Mon, 3 Jun 2013 18:01:43 +0000
To: public-test-infra <public-test-infra@w3.org>
Message-ID: <179FD336116F754C876A9347238FE29A01042000@WABOTH9MSGUSR8L.ITServices.sbc.com>
Hello my friends,

One of my tasks is to consolidate different channels of help in various aspects of testing in W3C. Here is the status quo AFAIK:

Our general testing effort has been discussed in this mailing list "public-test-infra@w3.org" and IRC channel "#test" and "#testing". However, there are other channels of testing related discussions [1] [2] [3] [4] [5] [6], and some are very active [1] [3] [6].

I want to have a discussion here about what is the best way to consolidate those resources, and provide everyone with a one-stop shopping experience if help or discussion is needed. Here are some initial thoughts:

- Option 1: Use one mailing list and one IRC channel, and topics is differentiated with prefix in email subject, e.g. [General], [CSS], [HTML], etc.
- Option 2: stay as-is today, but document all of the relevant resources in Github documentation site, so that everyone knows where to ask for help if needed
- Option 3: somewhere between Option 1 and Option 2, i.e. some inactive channel can be consolidated into one, while those active ones will continue to work as-is. Everything will be documented as one-stop shopping guides.

Let me know what you think, whether or not there are other options, and which option works the best to improve our work experience.

Thank you and I am looking forward to a good and constructive discussion


[1] CSS WG: Testing related discussions have been in both mailing list "public-css-testsuite@w3.org" and IRC channel "#css-test". 

[2] DAP WG: There have been few discussions of DAP related testing in "public-device-apis@w3.org". But nothing more.

[3] HTML WG Testing Task Force: Testing related discussions have been in both mailing list "public-html-testsuite@w3.org" and IRC channel "#htmlt".

[4] SysApps WG: The same situation as in DAP - there have been few discussions of DAP related testing in "public-sysapps@w3.org". But nothing more.

[5] Web and TV IG Testing Task Force: Testing related discussions have been in both mailing list "public-web-and-tv@w3.org" with prefix [Testing] and IRC channel "#webtv".

[6] WebApps WG: Testing related discussions have been in mailing list "public-webapps-testsuite@w3.org".

-----Original Message-----
From: Tobie Langel [mailto:tobie@w3.org] 
Sent: Thursday, May 30, 2013 9:43 AM
To: public-test-infra
Subject: Kickstarting the documentation authoring effort

Hi folks, 

I've set up a GitHub repository[1] to get started on the doc authoring effort.

The goal of the effort is to have all our cross-WG documentation needs for testing stored in one place, easily editable by the community.

In order to do this we need to centralize, update and improve existing documentation, and author new content when existing resources are lacking.

To kickstart this project, the Resource Center TF has helped gather a list of existing related docs[2] along with a second list of docs that need to be written. I converted the latter into GitHub issues[3]. Bin Hu's been assigned most of the work here (he volunteered), but I'm sure he'll appreciate your help. Please sync up on the issues directly if you want to pick up some work. Generally, that'll imply looking at the existing docs[2] to find relevant content, using an online service[4] to convert it to markdown, copyediting it, adding YAML front-matter to it[5], and sending a pull request. More info in our contributors' guide[6].

Note that we choose to go with Markdown files and a static site generator (Jekyll). This it has the advantages of being a highly portable solution and to be really well integrated with GitHhub making deployment and hosting trivial. (Don't worry, we'll still have our own domain name).

Initially the project will happen in two phases[7]:

1) we'll get the basic documentation ready for launch along with layout and design (more on the latter more in a follow-up email), and,
2) where appropriate, we'll remove/redirect/amend exiting content to make sure all content points to the new canonical source.

We'll work iteratively thereafter.

Happy to answer questions.


[1]: https://github.com/w3c/ttwf-docs
[2]: https://github.com/w3c/ttwf-docs/blob/gh-pages/RESOURCES.md
[3]: https://github.com/w3c/ttwf-docs/issues?labels=authoring&page=1&state=open
[4]: http://fuckyeahmarkdown.com/
[5]: http://jekyllrb.com/docs/frontmatter/
[6]: https://github.com/w3c/ttwf-docs/blob/gh-pages/CONTRIBUTING.md
[7]: https://github.com/w3c/ttwf-docs/issues/milestones

Received on Monday, 3 June 2013 18:02:25 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:34:08 UTC