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.

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

Signing the participation agreement as an individual #62

Closed
sideshowbarker opened this issue Feb 1, 2018 · 15 comments
Closed

Signing the participation agreement as an individual #62

sideshowbarker opened this issue Feb 1, 2018 · 15 comments
Assignees

Comments

@sideshowbarker
Copy link

I’d like to sign the participation agreement as an individual but the “I represent that I do not work in the field of web technologies as an employee, contractor, or agent of another person or legal entity” language in the current agreement appears to prevent me from doing that.

I’m not authorized to sign an agreement like this on behalf of my employer as a whole. But anyway I’ve always participated in WHATWG work in a personal capacity and made my contributions in a personal capacity, and my contract with my employer doesn’t prevent me from agreeing on my own to any copyright grant on my contributions nor to royalty-free licensing of my contributions.

@michaelchampion
Copy link
Contributor

@sideshowbarker who's your actual employer, Keio University? Or are you a contractor? (W3C is not a legal entity, so I know you don't work for it).

@sideshowbarker
Copy link
Author

Yeah, my employer is Keio University.

@othermaciej
Copy link
Contributor

The WHATWG has discussed this, and we'd really like to figure out a way for W3C staff to participate. ?Nothing to announce yet but I wanted to say for the record that we have discussed it.

@chris-morgan
Copy link

chris-morgan commented Dec 17, 2019

The current ruling prevents many people such as myself from contributing. See some discussion in whatwg/html#5156, which I am now forced to abandon.

I am employed by a company that deals in web tech, but I attempted to contribute in my own time to correct an error I encountered while working on a project of my own, completely distinct from my employer. I cannot get my employer to sign the agreement and contribute the patch, because they hold no rights to the Contribution, and it is excessively onerous to set up some kind of copyright assignment or equivalent license grant of my own work to my employer so that I could submit the patch as an employee of that company. Yet I am not permitted to sign the agreement as an individual.

In short, catch-22, neither of the categories applies to me, and I am not permitted to contribute.

@sideshowbarker
Copy link
Author

It’s worth noting here that at https://tc39.es/agreements/contributor/, in contrast to the WHATWG Participant Agreement, TC39 has a Contributor License Agreement form that explicitly allows a contributor to assert that they, individually, have the right to provide all contributions they are making — outside of whatever organization they may happen to be employed by. Specifically:

  • The TC39 CLA has no language anything like the part of the WHATWG Participant Agreement that’d require TC39 individual contributors to assert that they don’t work “in the field of web technologies” or anything similar.

  • the CLA form has this language:

    I confirm that I have the right to provide all contributions I will make, and if I am making a contribution on behalf of an organization, I confirm that I have the right to make this contribution on behalf of my organization and to bind my organization to the obligations below

    So the CLA explicitly acknowledges and allows for the case where an contributor, even if employed by some organization (implicitly including employment “in the field of web technologies” or any other field), can assert they as an individual “have the right to provide all contributions I will make” and are contributing individually and not on behalf of any organization. (That is, exactly the case @chris-morgan describes in Signing the participation agreement as an individual #62 (comment) and that I’ve described for myself in the issue description here.)


Note also: the TC39 CLA further distinguishes between normative and non-normative changes, and signing the CLA at all is explicitly only required for contributors who are contributing normative changes; the top of the form says (emphasis added):

It is required in the following cases:

  • To attend a TC39 meeting as an invited expert and participate in committee discussion
  • To contribute a normative change to an ECMA-262, ECMA-402 or a proposal repository under the tc39 organization

@michaelcpuckett
Copy link

I am also an employed web developer who does not want to participate on behalf on my company. The W3C community group rules allow me to join as an individual if my employer has explicitly given me permission to do so, which they did. They were also willing to sign a document granting me permission, if needed.

My guess is that the vast majority of web developers are unable to participate under the current rules. This seems antithetical to the WHATWG's principles of openness, utility, efficiency and freedom.

I suggest this gets brought up again by the steering committee.

@michaelchampion
Copy link
Contributor

I was on the Steering Group for 2 years, and I regret we didn't make more progress on this issue during my tenure. I believe the SG is close to a resolution that should work for more individuals whose employers approve of them working in WHATWG but are unwilling to invest the legal resources needed to sign the Entity Agreement. But this is more complicated than it sounds:

  • There's no clear way to distinguish between non-normative and normative changes in legal language. There are (admittedly corner) cases where something as trivial as punctuation or capitalization can change the normative sense of some text. Also, individuals can always suggest non-normative changes in Issues rather than Pull Requests without needing to make a formal patent commitment, so it's not clear how serious a problem this is for the community.

  • The most compelling "threat models" for patent policies involve litigation by small players whose main asset is a patent, and non-practicing entities ("trolls") who acquire their patents if the business doesn't succeed. What might seem like corner cases to engineers might be exploited by trolls and cost big companies implementing specs millions and millions of dollars. So attorneys are risk averse about patents even though few major companies use patents "offensively" in the web platform space anymore.

  • Finally, the lawyers advising the SG companies work for each other's biggest competitors, so are extremely careful not to agree to a policy that could put one at a disadvantage compared to the others.

That said, the WHATWG community should keep encouraging the SG to find a solution, and to keep pointing to other standards organizations that have solved this problem in a way big company attorneys can live with!

@annevk
Copy link
Member

annevk commented Mar 24, 2020

Also, individuals can always suggest non-normative changes in Issues rather than Pull Requests without needing to make a formal patent commitment, so it's not clear how serious a problem this is for the community.

I think it's a serious problem, for what it's worth. We have people put effort into contributing a (pretty much always simple, without legal implications) fix only to belatedly realize it cannot be accepted because they cannot successfully navigate the Participation Agreement. This turns people away and they are unlikely to return after such an experience.

It's also somewhat absurd we have this high bar whereas for "equivalent" W3C efforts such changes are routinely merged.

@michaelchampion
Copy link
Contributor

As a former SG member, I agree it's a problem that is turning people away. The root of the issue is that if you ask a lawyer, almost nothing is "without legal implications."

I suspect the SG would be interested in hearing from anyone who has PRs accepted in W3C land but has trouble navigating the participation agreement. The idea was to allow anyone who can make IPR commitments to W3C specs, either as a member or invited expert, to make equivalent commitments to WHATWG specs.

@foolip
Copy link
Member

foolip commented Jun 2, 2020

The SG discussed in #126, summarized as these two options:

  • Case-by-case exceptions allowed for people employed by academic institutions (W3C does something similar for invited experts)
  • Exception for all W3C staff

Assigning to @travisleithead per the action item in those notes.

@chris-morgan
Copy link

So… no? Those options sound to me like they will solve the problem for very few people that are actually in this situation.

@dbaron
Copy link
Member

dbaron commented Jun 3, 2020

I'd note that:

  • they do address the situation that was the topic of the first four comments in this issue
  • other situations may be addressed by the discussion in Non-normative changes #63.

@othermaciej
Copy link
Contributor

We have landed changes that clarify what it means to "work in the field of web technologies". This should help some people who would like to join as an individual. In particular, being employed as a web developer is not enough, by itself, to count as "working in the field of web technologies".

We realize this doesn't cover everyone, but perhaps it will help some of those following this issue.

@annevk
Copy link
Member

annevk commented Apr 30, 2021

Now that we have an invitation policy this can be closed: https://blog.whatwg.org/update-from-the-steering-group. (As noted by David above #63 tracks remaining cases.)

@annevk annevk closed this as completed Apr 30, 2021
@annevk annevk removed the agenda On the agenda for the next SG meeting label Apr 30, 2021
@sideshowbarker
Copy link
Author

Thanks to the SG and thanks individually to everybody involved in coming up with the invitation policy. I can imagine it must have taken a lot of work to get it through the necessary machinery, but I think the benefits from it are going to make it well worth the effort it took. This is a really big win for the community.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

9 participants