<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body>
<div>
<div>
<div dir="ltr">Huge +1 from me.</div>
</div>
<div id="ms-outlook-mobile-signature">
<div><br>
</div>
Get <a href="https://aka.ms/o0ukef">Outlook for iOS</a></div>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Openid-specs-ab <openid-specs-ab-bounces@lists.openid.net> on behalf of Jeremie Miller via Openid-specs-ab <openid-specs-ab@lists.openid.net><br>
<b>Sent:</b> Tuesday, January 10, 2023 4:59:47 PM<br>
<b>To:</b> Artifact Binding/Connect Working Group <openid-specs-ab@lists.openid.net><br>
<b>Cc:</b> Jeremie Miller <jmiller@pingidentity.com><br>
<b>Subject:</b> [Openid-specs-ab] Migrating source control to github?</font>
<div> </div>
</div>
<div>
<div dir="ltr">I wanted to put out a feeler to this group on interest in migrating from bitbucket to github for the OpenID4VC family of specs.
<div><br>
</div>
<div>The reason I'm only suggesting migrating a subset of the larger connect repository is two-fold:</div>
<div>1 - They're younger specs and the team managing them right now is pretty active and focused</div>
<div>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)</div>
<div><br>
</div>
<div>If there's interest and no blockers, I'm also volunteering to help do the work of the migration.</div>
<div><br>
</div>
<div>Thanks!</div>
<div><br>
</div>
<div>Jer</div>
<div><br>
</div>
</div>
<br>
<i style="margin:0px; padding:0px; border:0px; outline:0px; vertical-align:baseline; background:rgb(255,255,255); color:rgb(85,85,85)"><span style="margin:0px; padding:0px; border:0px; outline:0px; vertical-align:baseline; background:transparent; font-weight:600"><font size="2">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.</font></span></i></div>
</body>
</html>