So... I thought about this a bit.

all the listed aerogear-security-* repos did push releases out to maven central. Even we are no longer doing anything there, the stuff is available and it might be used. Therefore, let's just keep the repos, incase users need to fork/patch it.

It does not hurt to have these repos, right ? 

Regarding the TODO, SP quickstarts and the kitchensink, I think it's fine to make delete them.... I think :-))

On Tue, Nov 10, 2015 at 1:11 PM, Matthias Wessendorf <matzew@apache.org> wrote:

Hi,

looking over our repos, for some stats and page views, I noticed a few that are deprecated, since a quite a while

https://github.com/aerogear/aerogear-simplepush-unifiedpush-quickstart

https://github.com/aerogear/aerogear-simplepush-quickstart

https://github.com/aerogear/aerogear-aerodoc-backend

https://github.com/aerogear/aerogear-security-hawk

https://github.com/aerogear/aerogear-android-todo

https://github.com/aerogear/aerogear-security-picketlink

https://github.com/aerogear/aerogear-security

https://github.com/aerogear/aerogear-security-shiro

https://github.com/aerogear/aerogear-jaxrs-demo

https://github.com/aerogear/TODO

Also, very much out of date (no?) are the following:

https://github.com/aerogear/aerogear-security-picketbox

https://github.com/aerogear/kitchensink-aerogear-js

What's the plan here? Just remove them, or keep it... and just leave as is.

Thanks,

Matthias

--

Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

--

Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev