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

Should participants in Working Groups be allowed to represent more than one organisation? #9

Closed
dwsinger opened this issue Apr 21, 2017 · 24 comments
Assignees
Labels
Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion DoC This has been referenced from a Disposition of Comments (or predates the use of DoCs)
Milestone

Comments

@dwsinger
Copy link
Contributor

Transferred from https://www.w3.org/community/w3process/track/issues/162
State: Open

@dwsinger
Copy link
Contributor Author

We need to ask for PSIG input and some actual cases.

@sandhawke
Copy link

One specific data point:

In one of my WGs (call it WG1), there's an IE who's the editor of a core spec. He works as a contract developer. I think he had a crowdfunded non-profit contract supporting some of this work, but then he kept doing it when that money ran out, if I understand right.

Meanwhile, in a completely different part of W3C (call it WG2), he recently got a contract with a Member Organization which includes representing them in WG2. That Member has no interest in WG1 and doesn't want to be associated with it.

So, we're left with him an IE in WG1 and a Member representative in WG2.

team-legal told me this was okay, as long as he disclosed, which he's done in WG1 at least.

Of course we also have the problem that the telecons for both groups are at the same time, but the Process can't help with that!

@chaals
Copy link
Contributor

chaals commented May 18, 2017

@sandhawke Thanks for the concrete data. As I understand it, since participation requirements - crucially including the patent policy - are generally scoped by Working Group.

So I think this question can be scoped down to cover someone who has 2 employers, and represents them both in the same WG.

The question of what their patent commitments are, or need to be, is I think for PSIG in the first instance, but my immediate take is that if they make commitments on behalf of both employers nobody will be unhappy.

The question of e.g. member access, and "related members" is, I think, reasonably straightforward. I'll follow up with another real case that touches on this.

If a Working Group uses votes to resolve a question, then I think whether a single person can hold two votes is material, although that section of the process is IMHO a mess - there are lots of helpful ideas about getting consensus, but there is nothing about what amounts to a Working Group decision, so it's basically left to the WG to assert that they have one, and the Director to agree or argue the case - which matters primarily in transition requests, and secondarily will be looked at more closely if there is actually dissent.

The Patent Policy can't be changed by this group. Nor is there anyone clearly able to push a change, although presumably at minimum the director could propose a change, ask for AC review and see what happens… This is a live issue given that there are some changes in the Process that affect at least the wording of the Patent Policy, such as moving the Last Call state to CR, although I don't think they are controversial in practice.

@chaals
Copy link
Contributor

chaals commented May 18, 2017

(Anec)Data point: Web Platform WG has participants who are contracted by other members to do certain pieces of work. They disclose these relationships according to the "related members" procedures, and it all seems OK.

In these cases, the participants do not claim to formally represent the related member. One possible outcome is that we actively ask them to do so, or even require it as a condition of participation, by changing the "related members" provisions, as well as removing the constraint that at the moment it is not allowed. There are other possible outcomes…

@dwsinger
Copy link
Contributor Author

I think that we may need to stick with 'they represent the organization whose AC rep appointed them to the WG' since it is that appointment process that confirms the org's involvement and agreement. So, I am curious, what is to stop two or more AC Reps from nominating the same person? I will ask the team.

As to whether their behavior is being controlled by some other entity than the nominating AC Rep's one, that's a question for chairs/team/other-participants. E.g. nominated by the AC Rep for 'Trouble for Hire Consulting Inc.' and then reveals that they are working 100% under contract to 'Nefarious Trolls PLC', one might hope that at that point the team/chair notice and suggest that the AC Rep for NT PLC nominate them, if they are a member. We cannot catch, in the process, all the ways that influence might be acquired.

@vfournier17
Copy link

I brought this up at PSIG on 6/12. Some different views were expressed, such as - (i) is this really an issue that needs to be addressed? (2) Could they provide some that show how the one person/one member language is problematic? (3) If it ain't broke, don't fix it. (4) there really isn't a compelling case either way. (5) this could come up with contractors who might represent more than one (small) company - each company can't afford their own person. (6) transparency is important - need to know who is representing who. In the end, PSIG had mixed views, and there wasn't a strong view one way or the other.

@dwsinger
Copy link
Contributor Author

we would prefer to wait for an actual problem here; not taking this up yet. Someone could ask for permission to be nominated by more than one member (AC Rep).

@dwsinger dwsinger removed the Active label Jun 14, 2017
@chaals
Copy link
Contributor

chaals commented Jul 12, 2017

There are actual people, who are known to be working for more than one W3C member simultaneously on the same work, in current Working Groups.

As far as I can tell, someone might ask to be nominated by more than one AC rep, but according to the current Process W3C would have to deny that request since it is not allowed.

chaals added a commit that referenced this issue Jul 12, 2017
fix #9

This removes the constraint that a participant cannot represent more than one member.
@vfournier17
Copy link

vfournier17 commented Jul 12, 2017 via email

@dwsinger
Copy link
Contributor Author

dwsinger commented Jul 12, 2017 via email

@vfournier17
Copy link

This could work. How do we confirm (b)?

@dwsinger
Copy link
Contributor Author

I would expect the member-visible list of participants, partic. when sorted by Member Organization, to show the same person under two member orgs. https://www.w3.org/2000/09/dbwg/details?group=42434&order=org is an example

@michaelchampion
Copy link

I'm not understanding why there is a problem worth changing the Process to solve. With no changes to the Process or implementation, both Mordor and Lucifer join the WG. Either Mordor or Lucifer appoint Leovigild as a rep, and he/she/it discloses both affiliations. The AC reps for both get notified of exclusion opportunities. Others can track patent commitments because they come from members who have joined WGS not from reps they may okay not appoint.

@dwsinger
Copy link
Contributor Author

If only Mordred joins the WG, why would Lucifer get notifications?

I think it's way simple to say "if you want to represent two orgs, get an account associated with each org"

@michaelchampion
Copy link

Both joined the WG and thus have traceable patent commitments. Only one appoints a rep, but that is procedurally distinct from joining a working group.

I don't object to the one person two email addresses hack... I'm just not sure there is a problem worth the effort to solve here.

@dwsinger
Copy link
Contributor Author

OK, so there are (at least) two no-change solutions:
a) both orgs join the WG, only one nominates the delegate, and the delegate self-reveals the interest
b) the delegate gets two accounts on the W3C site, one for each org, and they each nominate the delegate under their account

Given this, I doubt we need systems or process changes.

@chaals
Copy link
Contributor

chaals commented Jul 13, 2017

Your option b) seems to contradict the Process as written:

A participant must represent at most one organization

I'm not sure how to read that to allow someone to be nominated by more than one organisation.

I agree that option a) works in terms of Process and Patent Policy.

It seems suboptimal to insist that is the only possible way to do it, and outlaw both b) and actually having a system that just let the one person be recorded as representing two organisations.

@dwsinger
Copy link
Contributor Author

Sorry, I was assuming we went with your PR to delete that restriction, but otherwise, we seem to have two working options.

@dwsinger
Copy link
Contributor Author

This seems worth pursuing but lacking consensus and active worked examples, it's not a 2018 priority.

@dwsinger
Copy link
Contributor Author

dwsinger commented Aug 23, 2017

see also #27, closed in favor of this one

@vfournier17
Copy link

So, is the resolution to leave the language as is? That is our preference.

@chaals
Copy link
Contributor

chaals commented Sep 11, 2017

I prefer to make the change, but it is unclear to me if we have a resolution on that. There is not an obvious consensus, but my understanding is that I am the only one who wants to resolve this now, and consequently it is not going to change in the current revision :(

@dwsinger
Copy link
Contributor Author

I don't think we have consensus on the problem/use cases, or on the scope of the proposed fix, or the urgency, so at the moment it's not on our priority list...

frivoal added a commit to frivoal/w3process that referenced this issue Oct 2, 2018
@frivoal
Copy link
Collaborator

frivoal commented Oct 2, 2018

We've had PR #54 as a proposal to this for a while, but could not get consensus on it. Based on the discussions there, I've made #219 as an alternative proposal.

@frivoal frivoal added Needs Review Agenda+ Marks issues that are ready for discussion on the call labels Oct 2, 2018
@frivoal frivoal self-assigned this Oct 2, 2018
@frivoal frivoal removed Agenda+ Marks issues that are ready for discussion on the call Needs Review labels Oct 3, 2018
@frivoal frivoal added Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion DoC This has been referenced from a Disposition of Comments (or predates the use of DoCs) labels Dec 8, 2018
@frivoal frivoal added this to the Process 2019 milestone May 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion DoC This has been referenced from a Disposition of Comments (or predates the use of DoCs)
Projects
None yet
Development

No branches or pull requests

6 participants