On Mon, May 27, 2013 at 1:56 PM, Bruno Oliveira <bruno@abstractj.org> wrote:
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?

something like "add HTTP Basic to iOS"
 

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

And here?

like add "HOTP to iOS"
 

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

yeah, that's good.
The generic, overall, story is hammered into the AGSEC, and details are hammered into the specific JIRA instances
e.g. AGDROID / AGIOS etc
 

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

I like it, and it also goes well with my suggested components, I think
 

>
>
> -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@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
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