[Openid-specs-ab] Migrating source control to github?

[Mike Jones]

As discussed during a working group call (I think in December), there’s an appetite for moving *all* Connect specs to the GitHub repository github.com/openid/connect at the same time.  We should move them all because then we maintain the benefit of having a single issue tracker for the working group.  If we had to use different issue trackers for different specs, that would be an ongoing source of confusion.  It would also make it more difficult to chair calls, since we’d have to triage issues and PRs across multiple repositories.

When we move, issues will all migrate.  PRs will not migrate.  Therefore, we should be mindful about when to migrate so as to minimize the number of open PRs.  The consensus when we last discussed this is that the right time to migrate is after we publish proposed Implementer’s Drafts for the OpenID4VC specs.  (The OpenID Connect Federation editors can also try to ensure that most/all of the Federation PRs are merged at the same time.)

So if any of you need more motivations to review OpenID4VC issues and PRs and get us to proposed Implementer’s Drafts, take into account that you doing so will accelerate our migration to GitHub. 😊  Let’s promptly advance the OpenID4VC specs!

                                                       -- Mike

From: Openid-specs-ab <openid-specs-ab-bounces at lists.openid.net> On Behalf Of Joseph Heenan via Openid-specs-ab
Sent: Wednesday, January 11, 2023 2:36 AM
To: Artifact Binding/Connect Working Group <openid-specs-ab at lists.openid.net>
Cc: Joseph Heenan <joseph at authlete.com>
Subject: Re: [Openid-specs-ab] Migrating source control to github?

Hi Jeremie

I think I’d be in favour of this.

There’s precedent for this, the OIDF shared signals and events group already moved to GitHub:

https://github.com/openid/sse

I think whether each WG has one repo per WG (as currently on bitbucket and as SSE currently do on GitHub) or one per spec (as you are I think suggesting) is a slightly more nuanced discussion.

Thanks

Joseph


On 11 Jan 2023, at 00:59, Jeremie Miller via Openid-specs-ab <openid-specs-ab at lists.openid.net<mailto:openid-specs-ab at lists.openid.net>> wrote:

I wanted to put out a feeler to this group on interest in migrating from bitbucket to github for the OpenID4VC family of specs.

The reason I'm only suggesting migrating a subset of the larger connect repository is two-fold:
1 - They're younger specs and the team managing them right now is pretty active and focused
2 - Github orgs would allow for a connect or OpenID parent with individual repos for the various specs similar to other specification efforts using github (more focused issue trackers, permissions, build automations, etc)

If there's interest and no blockers, I'm also volunteering to help do the work of the migration.

Thanks!

Jer


CONFIDENTIALITY NOTICE: This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited.  If you have received this communication in error, please notify the sender immediately by e-mail and delete the message and any file attachments from your computer. Thank you._______________________________________________
Openid-specs-ab mailing list
Openid-specs-ab at lists.openid.net<mailto:Openid-specs-ab at lists.openid.net>
https://lists.openid.net/mailman/listinfo/openid-specs-ab

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20230111/be1034a7/attachment.html>