Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Publish as FPWD? #1

Open
6 tasks
marcoscaceres opened this issue Oct 17, 2019 · 3 comments
Open
6 tasks

Publish as FPWD? #1

marcoscaceres opened this issue Oct 17, 2019 · 3 comments
Assignees
@johanneswilm

Comments

@marcoscaceres
Copy link
Member

marcoscaceres commented Oct 17, 2019 •
edited

Given the progress on the spec, it would be good for us to prepare the document for a First Public Working Draft. In order us to do that, as per the W3C Process, we:

  • must record the group's decision to request advancement.
  • must provide public documentation of any Formal Objections.
  • should provide public documentation of changes that are not substantive.
  • should report any changes in dependencies with other groups.
  • should provide information about implementations known to the Working Group.
  • send out a request for wide review - cc @LJWatson.

@johanneswilm , if you agree, we can send out a Call for Consensus to publish to the WG (editing task force mailing list), which will address the first requirement above (and the second, as hopefully there will be no objections).

We shouldn't need anything for "documentation of changes that are not substantive", as we can point to the commit history. Our dependencies on other groups haven't changed, and the spec itself lists the known implementations.
@johanneswilm
Copy link
Collaborator

@marcoscaceres Yes, I agree that we should proceed with this as you suggested.

@marcoscaceres
Copy link
Member Author

Blocked on #2... when #2 is done, email will go out. Saving it here, as I already wrote it and don't want to lose it:

Hi All,
This is a Call for Consensus to publish the "ContentEditable" spec as a FWPD. You can find the Editor's draft here:
https://w3c.github.io/contentEditable/

If you support publication of this document, you don't need to do anything - silence is considered consent. But if you really feel the need to show support, please add a 👍 or ❤️ on Github:
https://github.com/w3c/contentEditable/issues/1

If you'd like to raise a Formal Objection to publishing this document, please do so by the Friday DATE of MONTH, 2019. Please include the rationale for your objection to its publication.

If you have other comments, suggestions, or found bugs, we invite you to file an issue on Github:
https://github.com/w3c/contentEditable/issues/

In the mean time, I'll work with the Editors to prepare the document for publication and possibly kick off the requests for wide review. We will do our best to get the spec out by December.

Kind regards,
Marcos

@gked gked mentioned this issue Jan 10, 2020
Closed
@johanneswilm
Copy link
Collaborator

As per Editing TF call 2020-01-10: @marcoscaceres can we move ahead with this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@johanneswilm johanneswilm

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@johanneswilm @marcoscaceres