[Openid-specs-ab] Contributing RP libraries to the Connect WG

Wed Jun 6 18:25:16 UTC 2018

+1 on use of openid org and prefixed repo names + the use of READMEs

Best,
Filip

Odesláno z iPhonu

6. 6. 2018 v 20:20, William Denniss via Openid-specs-ab <openid-specs-ab at lists.openid.net>:

> Creating multiple GitHub "orgs" creates a lot of management overhead just to get a hierarchy. I've never heard of a project using multiple GitHub orgs, with one for each language. I don't even think a hierarchy is all that important, or expected by users. We didn't structure AppAuth under a hierarchy, but we created http://AppAuth.io as a single landing page that we could direct people to which has served us well.  If discoverability is the concern, then you could create a marketing page like we did and/or just link to each of the sister repos at the top of each README.
> 
> I don't know all the finer details of your effort here, so I hesitate to comment – but as an outsider personally I think Mike's earlier proposal (flat structure) made the most sense. An alternative would be to have one repository per language with sub-folders for the sub-libraries, depending on how tightly coupled the sub-libraries are.
> 
> 
>> On Wed, Jun 6, 2018 at 11:08 AM, Mike Jones via Openid-specs-ab <openid-specs-ab at lists.openid.net> wrote:
>> Roland says that having a project hierarchy isn’t supported by GitHub.  If anyone knows differently, please speak up now.  Otherwise, based on Roland’s input, I think we’ll go with names like these.
>> 
>>  
>> 
>> https://github.com/openid-JWTConnect-Python/cryptojwt-python
>> 
>> https://github.com/openid-JWTConnect-Python/oidcmsg-python
>> 
>> https://github.com/openid-JWTConnect-Python/oidcservice-python
>> 
>> https://github.com/openid-JWTConnect-Python/oidcrp-python
>> 
>>  
>> 
>> Once we have the list of maintainers for the Python project, I’ll plan to create https://github.com/openid-JWTConnect-Python/ and then Roland can make the contribution.
>> 
>>  
>> 
>>                                                        -- Mike
>> 
>>  
>> 
>> From: George Fletcher <gffletch at aol.com> 
>> Sent: Wednesday, June 6, 2018 7:50 AM
>> To: Roland Hedberg <roland at catalogix.se>; Mike Jones <Michael.Jones at microsoft.com>
>> 
>> 
>> Cc: openid-specs-ab at lists.openid.net
>> Subject: Re: [Openid-specs-ab] Contributing RP libraries to the Connect WG
>>  
>> 
>> I'm assuming the ability to nest packages under a hierarchy is something that GitHub doesn't support?
>> 
>> https://github.com/openid
>>     /JWTConnect-Python
>>         /CryptoJWT
>>         /OidcMsg
>>         /OidcService
>>         /OidcRP
>>     /JWTConnect-Java
>>         ...
>> 
>> Thanks,
>> George
>> 
>> On 6/6/18 1:29 AM, Roland Hedberg via Openid-specs-ab wrote:
>> 
>> I’m sorry to say that it doesn’t make sense to me.
>> 
>>  
>> 
>> To put all the different projects under one hat makes it very hard to find them, they are all jumbled together.
>> 
>> There is no way that separate projects, and they are separate projects, can present themselves and work as a project.
>> 
>> And as already has been hinted these project will be extended. Keeping them all in a heap will make it
>> 
>> extremely hard to track what’s going on where.
>> 
>> 
>> 
>> 
>> On 6 Jun 2018, at 02:04, Mike Jones via Openid-specs-ab <openid-specs-ab at lists.openid.net> wrote:
>> 
>>  
>> 
>> Keeping things under github.com/openid/ makes sense to me, so I appreciate your proposal, Thomas.  However, it would be good to have a common name as part of the names of all of these packages – just as the AppAuth libraries do.  That common name, to date, has been JWTConnect.  So how about this possible name set?
>> 
>>  
>> 
>> https://github.com/openid/JWTConnect-Python-CryptoJWT
>> 
>> https://github.com/openid/JWTConnect-Python-OidcMsg
>> 
>> https://github.com/openid/JWTConnect-Python-OidcService
>> 
>> https://github.com/openid/JWTConnect-Python-OidcRP
>> 
>>  
>> 
>> https://github.com/openid/JWTConnect-Java-CryptoJWT
>> 
>> https://github.com/openid/JWTConnect-Java-OidcMsg
>> 
>> https://github.com/openid/JWTConnect-Java-OidcService
>> 
>> https://github.com/openid/JWTConnect-Java-OidcRP
>> 
>>  
>> 
>> https://github.com/openid/JWTConnect-JS-CryptoJWT
>> 
>> https://github.com/openid/JWTConnect-JS-OidcMsg
>> 
>> https://github.com/openid/JWTConnect-JS-OidcService
>> 
>> https://github.com/openid/JWTConnect-JS-OidcRP
>> 
>>  
>> 
>>                                                                 -- Mike
>> 
>>  
>> 
>> From: Thomas Broyer <t.broyer at gmail.com> 
>> Sent: Tuesday, June 5, 2018 7:54 AM
>> To: Mike Jones <Michael.Jones at microsoft.com>
>> Cc: openid-specs-ab at lists.openid.net
>> Subject: Re: [Openid-specs-ab] Contributing RP libraries to the Connect WG
>> 
>>  
>> 
>> I don't get why you'd have (even less want) to create separate organizations. Couldn't all those projects live ingithub.com/openid ?
>> 
>> github.com/openid/cryptojwt-python
>> github.com/openid/cryptojwt-java
>> 
>> github.com/openid/cryptojwt-js
>> 
>> github.com/openid/oidcmsg-python
>> github.com/openid/oidcmsg-java
>> 
>> github.com/openid/oidcmsg-js
>> 
>> github.com/openid/oidcservice-python
>> github.com/openid/oidcservice-java
>> 
>> github.com/openid/oidcservice-js
>> 
>> github.com/openid/oidcrp-python
>> github.com/openid/oidcrp-java
>> 
>> github.com/openid/oidcrp-js
>> 
>>  
>> 
>>  
>> 
>> On Fri, Jun 1, 2018 at 9:45 PM Mike Jones via Openid-specs-ab <openid-specs-ab at lists.openid.net> wrote:
>> 
>> Roland pointed this out to me:
>> 
>> Since each of these contains more the one package this won’t work.  Each one must be a project which means that what we should use is:
>> 
>>  
>> 
>> https://github.com/openid-JWTConnect-Python
>> 
>> https://github.com/openid-JWTConnect-Java
>> 
>> https://github.com/openid-JWTConnect-JS
>> 
>>  
>> 
>> After asking about what the packages in each project would be, the current set of proposed names are:
>> 
>>  
>> 
>> https://github.com/openid-JWTConnect-Python/cryptojwt-python
>> https://github.com/openid-JWTConnect-Python/oidcmsg-python
>> https://github.com/openid-JWTConnect-Python/oidcservice-python
>> https://github.com/openid-JWTConnect-Python/oidcrp-python
>> 
>> https://github.com/openid-JWTConnect-Java/cryptojwt-java
>> https://github.com/openid-JWTConnect-Java/oidcmsg-java
>> https://github.com/openid-JWTConnect-Java/oidcservice-java
>> https://github.com/openid-JWTConnect-Java/oidcrp-java
>> 
>> 
>> https://github.com/openid-JWTConnect-JS/cryptojwt-js
>> https://github.com/openid-JWTConnect-JS/oidcmsg-js
>> https://github.com/openid-JWTConnect-JS/oidcservice-js
>> https://github.com/openid-JWTConnect-JS/oidcrp-js
>> 
>>  
>> 
>> Further comments from the working group are welcome.
>> 
>>  
>> 
>>                                                                 -- Mike
>> 
>>  
>> 
>> From: Mike Jones 
>> Sent: Thursday, May 31, 2018 12:26 PM
>> To: 'openid-specs-ab at lists.openid.net' <openid-specs-ab at lists.openid.net>
>> Cc: Roland Hedberg <roland at catalogix.se>; Luke Camery <lcamery at google.com>; adawes at google.com
>> Subject: Contributing RP libraries to the Connect WG
>> 
>>  
>> 
>> As many of you know, Google has commissioned the creation of high-quality JWT/OpenID Connect RP libraries in Python, Java, and JavaScript.  Just as the AppAuth libraries were previously contributed to the OpenID Connect working group, Google would like to contribute these to the working group when they are ready.  The Python library has already achieved certification and is ready.
>> 
>>  
>> 
>> As board secretary, I’ve been working with them on some of the logistics of this.  The proposed GitHub project names are:
>> 
>>  
>> 
>> https://github.com/openid/JWTConnect-Python
>> 
>> https://github.com/openid/JWTConnect-Java
>> 
>> https://github.com/openid/JWTConnect-JS
>> 
>>  
>> 
>> These are intentionally somewhat parallel to these existing project names:
>> 
>>  
>> 
>> https://github.com/openid/AppAuth-Android
>> 
>> https://github.com/openid/AppAuth-iOS
>> 
>> https://github.com/openid/AppAuth-JS
>> 
>>  
>> 
>> Core maintainers/committers/reviewers would be identified for each library at the time of its contribution.  Roland Hedberg would be in this set for the Python library.
>> 
>>  
>> 
>> This note is to inform the working group of this possibility and to solicit feedback from the working group, since these would become a project of the working group.
>> 
>>  
>> 
>>                                                                 --- Mike
>> 
>>  
>> 
>>  
>> 
>>  
>> 
>> _______________________________________________
>> Openid-specs-ab mailing list
>> Openid-specs-ab at lists.openid.net
>> http://lists.openid.net/mailman/listinfo/openid-specs-ab
>> 
>> _______________________________________________
>> Openid-specs-ab mailing list
>> Openid-specs-ab at lists.openid.net
>> http://lists.openid.net/mailman/listinfo/openid-specs-ab
>> 
>>  
>> 
>> — Roland
>> 
>>  
>> 
>> The higher up you go, the more mistakes you are allowed. Right at the top, if you make enough of them, it's considered to be your style. 
>> 
>> -Fred Astaire, dancer, actor, singer, musician, and choreographer (10 May 1899-1987)
>> 
>>  
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________
>> Openid-specs-ab mailing list
>> Openid-specs-ab at lists.openid.net
>> http://lists.openid.net/mailman/listinfo/openid-specs-ab
>>  
>> 
>> 
>> _______________________________________________
>> Openid-specs-ab mailing list
>> Openid-specs-ab at lists.openid.net
>> http://lists.openid.net/mailman/listinfo/openid-specs-ab
>> 
> 
> _______________________________________________
> Openid-specs-ab mailing list
> Openid-specs-ab at lists.openid.net
> http://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/20180606/f2c5257f/attachment.html>