Overall looks good, few comments inline, because I'm really concerned about overlappings. Matthias Wessendorf wrote: > Hello, > > what about the following components for the AGIOS instance: > > * Pipe > * Authentication Which kind of task should be created here?

> * Push (?) ===> This is already covered in AGPUSH. Really needed here > (too) ? > * sync > * offline > * otp And here?

> * Xcode > * cocoapods > * travis > > More as a generic "tag" > * documentation > * example > * security Maybe is a good idea to follow the same approach from AeroGear, make use of "security" as a generic tag and to the specifics like otp, authentication...etc create a link between AGIOS and AGSEC. For example: * AGIOS-1-Add HOTP support to aerogear-otp-ios (security) ** AGSEC-28 HOTP support (otp)

Not sure if my thought is the best approach, but is my suggestion.

> > > -Matthias > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

I do not know whether we really need the cocoapods and travis with components. Cocoapods for example will be used only when we release a new version? Matthias Wessendorf wrote: > Hello, > > what about the following components for the AGIOS instance: > > * Pipe > * Authentication > * Push (?) ===> This is already covered in AGPUSH. Really needed here > (too) ? > * sync > * offline > * otp > * Xcode > * cocoapods > * travis > > More as a generic "tag" > * documentation > * example > * security > > > -Matthias _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

+1 Matthias Wessendorf wrote: > * travis/ci => issues with the build server (not meaning "compile errors") > * CocoaPods -> If something changes there (e.g. updates/enhancements on > the Podfile, or the Podspec itself) > > > > On Mon, May 27, 2013 at 8:10 PM, Daniel Passos <daniel(a)passos.me > <mailto:daniel@passos.me>> wrote: > > I do not know whether we really need the cocoapods and travis with > components. Cocoapods for example will be used only when we release a > new version? > > Matthias Wessendorf wrote: > > Hello, > > > > what about the following components for the AGIOS instance: > > > > * Pipe > > * Authentication > > * Push (?) ===> This is already covered in AGPUSH. Really needed > here > > (too) ? > > * sync > > * offline > > * otp > > * Xcode > > * cocoapods > > * travis > > > > More as a generic "tag" > > * documentation > > * example > > * security > > > > > > -Matthias > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org <mailto: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(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev