I still can't see what the real value added on it. Everyone knows that there's a team behind it, so I can't see why "_team", also do we plan to create handles for "AeroGearPush", "AeroGearSecurity"...if yes, that makes sense. And "_project", well we know, it's a project, the "s" on @aerogears always gave to me the sense of a bunch of people behind this to make it happen.




On Thu, Feb 20, 2014 at 6:54 PM, Matthias Wessendorf <matzew@apache.org> wrote:
Actually, @aerogear_project makes sense (see @netty_project)


On Thu, Feb 20, 2014 at 10:35 PM, Matthias Wessendorf <matzew@apache.org> wrote:
@__aerogear or @_aerogear ?




On Thu, Feb 20, 2014 at 10:07 PM, Douglas Campos <qmx@qmx.me> wrote:
**If** we're really forced to change, I'd go with @aerogear_project

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






--
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



--

-- 
"The measure of a man is what he does with power" - Plato
-
@abstractj
-
Volenti Nihil Difficile