Hi Aryeh, All - Aryeh's response below clarifies my last question about
the relationship between the HTML Editing APIs CG and WebApps.
I think the main points are:
* The members of the HTML Editing APIs CG do not think the HTML Editing
APIs spec is ready for Recommendation track (and I don't believe anyone
that responded to this thread suggested/recommended otherwise).
* Given at least some parts of the spec originated in the HTML5 spec,
this functionality is within the scope of WebApps' charter (as amended
in 2010).
* The HTML Editing CG would like to use public-webapps (and not their
list) for its discussions because so many of the interested parties are
already subscribed.
* Contributions to specifications produced by the HTML Editing CG are
governed by the Community Group CLA and the CG is responsible for
ensuring that all Contributions come from participants that have agreed
to the CLA for that group.
With this understanding, and having not noticed any objections to
Aryeh's proposal, I think we should consider Aryeh's proposal as accepted.
-AB
On 9/22/11 5:54 PM, ext Aryeh Gregor wrote:
On Thu, Sep 22, 2011 at 2:44 PM, Arthur Barstow<art.bars...@nokia.com> wrote:
It appears you are intentionally using "comments" here to differentiate
"contributions". Is that right?
Right.
I ask because, as I understand the CG process: before a person can make a
contribution to a CG spec, they must agree to a CLA for all of the CG's
specs; and a CG is only supposed to accept contributions from its CG
members.
If your CG uses WebApps' list, how will contributions from non-CG people be
managed/tracked and how will the FSA be managed e.g. if non-CG contributions
are accepted?
I spoke with Ian Jacobs about this. He clarified that "contributions"
only means spec text. To date, I've written all actual spec text
myself, and I expect this to continue. It's usual that only the
editor writes the actual text of the specifications they edit. If for
some reason I wanted to accept spec text from someone else, they'd
have to submit it through the CG and we'd ensure it was properly
tracked for legal reasons. As I understand it, it couldn't be
submitted on public-webapps, but that's not a problem -- I just want
to use public-webapps for discussion.
