<div dir="ltr">I think it would be better to just have a page on the website or in the docs that lists extensions. Having a github repository means we'll need to review and merge PRs for extensions. We just don't have the capacity to do so.</div><div class="gmail_extra"><br><div class="gmail_quote">On 11 July 2016 at 10:22, Thomas Darimont <span dir="ltr"><<a href="mailto:thomas.darimont@googlemail.com" target="_blank">thomas.darimont@googlemail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hello Group,<div><br></div><div>I was wondering whether it would make sense have some kind of </div><div>community backed keycloak-extensions organisation on github in order </div><div>to collect various extensions to Keycloak.</div><div><br></div><div>This organisation could contain repositories with community curated extensions </div><div>that would be independently released from keycloak with installation descriptions </div><div>with JBoss CLI scripts for installing them.</div><div><br></div><div>For instance:</div><div>- FederationProviders</div><div>- EventListeners</div><div>- Authenticators</div><div>- RequiredActions</div><div>- Themes</div><div>- Docker Containers</div><div><br></div><div>Cheers,</div><div>Thomas</div></div>
<br>_______________________________________________<br>
keycloak-dev mailing list<br>
<a href="mailto:keycloak-dev@lists.jboss.org">keycloak-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/keycloak-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-dev</a><br></blockquote></div><br></div>