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

Login status is apparently now in FedID WG #43

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

martinthomson
Copy link
Contributor

See https://github.com/w3c-fedid/login-status

This is a proposal. We also need to discuss what to do with the repository. Should we archive it?

@johnwilander ?

See https://github.com/w3c-fedid/login-status

This is a *proposal*.  We also need to discuss what to do with the
repository.  Should we archive it?
@samuelgoto
Copy link

This is a proposal. We also need to discuss what to do with the repository. Should we archive it?

My personal preference, as I stated here is to:

  1. Re-use the privacycg repo but replace this explainer with this explainer, as agreed at TPAC last year
  2. Move the privacycg repo to the FedID WG

This maintains the privacy cg issues and commit history and has the most up to date agreed upon specification.

I don't mind losing that history is that's too much work and just archieveing it, but just wanted to be transparent about being OK too if we reused the privacy cg repo instead.

@erik-anderson
Copy link
Member

@samuelgoto and @johnwilander we're happy to help coordinate how you would like. We can move the repo over and you can figure out how to merge things from there, or you can get the copy in the privacycg org updated and then we can move it over.

Can you suggest next steps?

@samuelgoto
Copy link

Can you suggest next steps?

@johnwilander @johannhof @bvandersloot-mozilla and I met extensively at TPAC 2024 and @johannhof wrote down what we believe we agreed upon as a group (@johnwilander still to confirm) and where to go from here:

w3c-fedid/login-status#8

The very next step is to get @johnwilander to acknowledge that (Johann/Ben/Myself already have), and from there we could start executing on what @johannhof wrote down.

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

Successfully merging this pull request may close these issues.

3 participants