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

did:github has been removed from the registry #94

Closed
OR13 opened this issue Jul 24, 2020 · 14 comments
Closed

did:github has been removed from the registry #94

OR13 opened this issue Jul 24, 2020 · 14 comments
Assignees

Comments

@OR13
Copy link
Contributor

OR13 commented Jul 24, 2020

I created this did method, and registered it prior the acquisition. its pretty experimental, and almost isomorphic to did:web (I believe with some tweaking, it might be better to make it just a variant on did:web.

cc @csuwildcat @selfissued please share with the appropriate folks.

@OR13
Copy link
Contributor Author

OR13 commented Jul 27, 2021

@timcappalli any objections to this? any comments? I am inclined to leave it, and also happy to update the registration endpoint if there is ever a need to.

@OR13
Copy link
Contributor Author

OR13 commented Jul 27, 2021

Suggest closing in 1 week if no feedback is received.

@iherman
Copy link
Member

iherman commented Jul 28, 2021

The issue was discussed in a meeting on 2021-07-27

  • no resolutions were taken
View the transcript

3.9. Microsoft has approved did:github or it has been removed from the registry (issue did-spec-registries#94)

See github issue did-spec-registries#94.

Orie Steele: I feel like I should withdraw did:github, we have did:web now... I kinda don't want to remove it, but I don't want to get us in trouble.

Brent Zundel: We have created the registry to register extensions, to date I'm not aware of any opposition from Microsoft on did:github, I think that opposition would need to appear before we act to remove the DID Method unless the author of the DID Method wishes to pre-emptively do so.

@csuwildcat
Copy link
Contributor

I'd have to sync with the GitHub teams to see if any care - I'll see if I can make contact with the right folks.

@OR13
Copy link
Contributor Author

OR13 commented Oct 19, 2021

I've received no feedback on this, and cannot do anything to move this forward.

@msporny
Copy link
Member

msporny commented Oct 19, 2021

We should remove did:github from the registry if we don't have explicit permission from Microsoft. You can "Log in with Github" or you can log in with "did:github", and that could be perceived as a trademark violation if you don't have approval from Microsoft.

Based on the DID Method registration process, the default action is to remove this from the registry.

@OR13
Copy link
Contributor Author

OR13 commented Oct 19, 2021

I can take the action to remove it form the registry.

@OR13
Copy link
Contributor Author

OR13 commented Oct 19, 2021

#345

@iherman
Copy link
Member

iherman commented Oct 19, 2021

The issue was discussed in a meeting on 2021-10-19

  • no resolutions were taken
View the transcript

5.4. Microsoft has approved did:github or it has been removed from the registry (issue did-spec-registries#94)

See github issue did-spec-registries#94.

Orie Steele: i've reached out to MSFT about this multiple times, no feedback, i say we close and re-open if concerns get raised

Manu Sporny: i think we should be more worried about the trademark issue

Orie Steele: comment in the thread?

Ted Thibodeau Jr.: i think the trademark issue is being misconstrued a bit-- if there were a trademarked DID METHOD, sure, but a trademark in another sector does not apply to this sector
… and did methods can be named after trademarked words if the trademark doesn't include esoteric namespaces

Manu Sporny: but "login with github" is a thing, i think it's too close for comfort!

Daniel Burnett: ok this is what we wanted-- discussion leads to either closing or a PR

Orie Steele: everything manu said should be in the issue, and now it's in the issue
… so it's ready for PR now
… i can work with that

Ryan Grant: thanks Orie!

Daniel Burnett: this kind of progress helps, looking forward to seeing everyone again next week at our regular (LATE) time


@kdenhartog
Copy link
Member

@OR13 might be the organizational friction that's still getting sorted between MSFT and Github. Have you tried reaching out directly to the GH team through their https://github.com/github/feedback repo?

@TallTed
Copy link
Member

TallTed commented Oct 26, 2021

The title of this issue is very confusing. Perhaps it could be rephrased?

@OR13
Copy link
Contributor Author

OR13 commented Oct 27, 2021

I added the entry, I removed the entry, I'm closing this issue.

@OR13 OR13 closed this as completed Oct 27, 2021
@TallTed
Copy link
Member

TallTed commented Oct 27, 2021

@OR13 -- I'm asking for the title of this (and I've asked for titles of other) issue to be changed because anyone reviewing a list of closed issues will have to drill into this (and those other) issues to discover what was really the issue, which time sink should not be required.

@OR13 OR13 changed the title Microsoft has approved did:github or it has been removed from the registry did:github has been removed from the registry Oct 27, 2021
@OR13
Copy link
Contributor Author

OR13 commented Oct 27, 2021

@TallTed you are welcome to suggest titles for any issues you think should be rephrased... I have tried to clarify the title for future readers, but if you have a better suggestion please make it in a comment so I can address it.

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

No branches or pull requests

6 participants