-
Notifications
You must be signed in to change notification settings - Fork 56
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
Update Simeon's affiliation #564
Conversation
@@ -228,7 +228,7 @@ standardization in an appropriate venue. | |||
|
|||
The Chairs of the WebExtensions Community Group are: | |||
|
|||
* Simeon Vincent, Independent (and before at Google) | |||
* Simeon Vincent, Mozilla (previously Google) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we include more specific dates in affiliation, possibly including the Independent affiliation? That would make it easier to rate the affiilation of older comments.
Even if we don't include the date, one could also bisect the meeting notes to find the date of "official" affiliation changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have never heard of that practice in other groups, have you?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't have enough experience in other groups to give an authorative answer. I asked the question, because "previously" is vague and becomes increasingly less relevant in the future. I have no issues with keeping the text as is though.
I looked up a name of someone involved in standards whose affiliation changed (Opera -> Mozilla -> Apple), and in that example only the latest/current company is mentioned.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think adding a date would be helpful. Different browser vendors have different opinions, such as: whether to support service worker or event page and webRequest in MV3. It can be confusing if a person's perspective completely reverses due to a change in company affiliation. Adding a date can help others understand it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Keeping historical information for each participant inline feels like it could get unwieldy. The Privacy Interest Group has some relevant prior art; the About section of their charter has a table with the date of and short description of each change. Perhaps we could do something like this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've created #584 to track adding change history to the charter.
SHA: 057312c Reason: push, by dotproto Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
SHA: 057312c Reason: push, by dotproto Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
I just updated my affiliation in the W3C to reflect that I'm working more closely with Mozilla. This PR updates the charter to reflect that change.