bocoup / wpt-docs

A clone of the web-platform-tests project to collaborate on documentation reorganization

Home Page:https://wpt-docs.readthedocs.io

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Feedback from fantasai

zcorpan opened this issue · comments

From @fantasai

On 3/27/19 10:04 AM, Simon Pieters wrote:

Hi!

At Bocoup we're currently working on improving documentation for web-platform-tests.

Hi zcorpan!

I'm really happy about this project. :) I think it's so important, both
for making tasks easier but even more for bringing the Web community
together and opening up standards work and browser involvement to more
people.

I'm reaching out to you to ask for:

  • your feedback on the direction we're planning
  • if you know about something that is an issue for you
  • if you would like to contribute to this effort in some other way
    ...
    I remember that you showed an email earlier about your thoughts of the existing docs and how it
    compares to the Mozilla QA docs that existed when you got involved. I think it would be cool to try
    to address this as part of our work. Can you share that email publicly, or just send it to me?

I think I incorporated those notes and some other comments into

https://onedrive.live.com/view.aspx?resid=5ACBE28A578FB511!3046539&ithint=file%2cdocx&authkey=!AGfEtPrXfjmgydA

But happy to send a copy to www-archive as well; I've forwarded it to
so many people already, both at Mozilla and WPT. :) I think you also
have a copy in your inbox dated 6 Nov 2017.

Here's the www-archive copy:
https://lists.w3.org/Archives/Public/www-archive/2019Mar/0003.html

I would like to make sure that we take into account any concerns for people in the CSS WG. Any thoughts?

I think the main things are to make sure the docs make the project
and its tools understandable and that they encourage contribution
from a wide range of people including the range from browser developers
to Web authors.

Also that they reasonably accommodate the types of tests that would be
needed to test CSS: testharness, but also reftests, manual tests when
necessary... which is something WPT isn't set up well to handle, but is
needed for things like media queries, blur radius, and other things
that can be regression-automated within a browser-specific subsystem but
are still needed as part of a real cross-browser conformance suite.