[keycloak-dev] New Keycloak repo in GitHub

[Stan Silvert]

Can we go ahead and make a final decision on this?  My code needs a 
home.  :-)

On 5/12/2015 2:03 PM, Stan Silvert wrote:
> On 5/12/2015 1:33 PM, Bill Burke wrote:
>> What's the reasoning for a separate repo?
> I thought we just discussed this in the meeting, but given the poor
> audio/video from my internet connection, I'm not surprised you would
> ask.  :-)  (I think I have it fixed now, btw)
>
> It started with the discussion below.  This stuff could go in either
> WildFly or Keycloak.  But WildFly is getting away from having these
> things in one uber repo.  Even Elytron itself is in its own repo.
>
> We could put it in Keycloak's repo, but I don't see any advantage. This
> stuff requires WildFly 10 and Java 8.  I'm not sure if we're ready to
> deal with that in the Keycloak repo yet.
>
> But I think the main question is, do we want Keycloak/Elytron
> integration to be tied to Keycloak releases?  If a WildFly release needs
> something from keycloak-eleytron integration then it's much easier to
> just do a release of the small repo than to do a full release of the
> entire Keycloak product.
>
> ----- Original Message -----
>
>> From: "Stan Silvert"<ssilvert at redhat.com>
>> To: "Stian Thorgersen"<stian at redhat.com>
>> Cc:mw-security-core at redhat.com
>> Sent: Tuesday, 12 May, 2015 1:25:15 PM
>> Subject: Re: Status Report - Week 19 2015
>>
>> On 5/12/2015 7:15 AM, Stian Thorgersen wrote:
>>> ----- Original Message -----
>>>> From: "Stan Silvert"<ssilvert at redhat.com>
>>>> To:mw-security-core at redhat.com
>>>> Sent: Tuesday, 12 May, 2015 1:11:40 PM
>>>> Subject: Status Report - Week 19 2015
>>>>
>>>> Accomplishments last week:
>>>> * Created presentation about feature packs for this week's team meeting
>>>> * Continue working on new subsystem that only exposes the
>>>> Keycloak/Elytron realm implementation.
>>>> * Created feature pack for the new subsystem
>>> Are these subsystems and feature packs going into Keycloak repo or WF repo?
>> Keycloak.  We're getting away from putting lots of stuff into the WF
>> repo.  Things get developed as independent pieces and then pulled into
>> the WF build as needed.
>>
>> Another alternative might be to put this into its own repo.
> Sounds like it might be best in a separate repo then. Can you make sure you use keycloak-dev to sync with others around this stuff? We've been missing you on the mailing list
>
>
>
>> On 5/12/2015 11:55 AM, Stan Silvert wrote:
>>> Can someone please create a new "elytron" repo under keycloak and give
>>> me full rights?
>>>
>>> This project will contain the new Keycloak/Elytron subsystem, along with
>>> Keycloak implementations of Elytron API's, and associated feature packs.
>>>
>>> Thanks,
>>>
>>> Stan
>>> _______________________________________________
>>> keycloak-dev mailing list
>>> keycloak-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>>>
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev