<div dir="ltr">For SimplePush we also created a separate instance, I think due to similar reasons. But again, if Dan is fine in using AEROGEAR intance, so it is. No hard rule on that </div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Nov 11, 2014 at 10:32 AM, Matthias Wessendorf <span dir="ltr"><<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</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"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Tue, Nov 11, 2014 at 10:23 AM, Erik Jan de Wit <span dir="ltr"><<a href="mailto:edewit@redhat.com" target="_blank">edewit@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Isn’t datasync a feature of AeroGear? Those this mean every feature is going to have it’s own JIRA? What is the rule?</div></blockquote><div><br></div></span><div>not sure there is a rule :) </div><div><br></div><div>but for push I found it easer and nice with the different versions, doing releases, planing etc in roadmap. If Dan wants to do that in AeroGear, that's fine </div><div><div class="h5"><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><div><div><br><div><div>On 11 Nov,2014, at 10:20 , Daniel Bevenius <<a href="mailto:daniel.bevenius@gmail.com" target="_blank">daniel.bevenius@gmail.com</a>> wrote:</div><br><blockquote type="cite"><div dir="ltr">I'm fine with making an AGDATASYNC or AGSYNC JIRA instance if that is what is agreed upon. </div><div class="gmail_extra"><br><div class="gmail_quote">On 11 November 2014 08:00, Matthias Wessendorf <span dir="ltr"><<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</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">instead of storing all sync items underneath the <span style="font-family:arial,sans-serif;font-size:13px">AEROGEAR instance, </span>we could have a AGDATASYNC JIRA instance. I think this makes it nicer to organize, especially with releases. That's what we did with AGPUSH for the 'push feature', which obviously is available across platforms.<div><br></div><div>-Matthias</div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On Tue, Nov 11, 2014 at 6:38 AM, Daniel Bevenius <span dir="ltr"><<a href="mailto:daniel.bevenius@gmail.com" target="_blank">daniel.bevenius@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr">Hi All,<div><br></div><div>we have created JIRA tasks for the data sync roadmaps [1][2]. </div><div><br></div><div>While creating them we noticed that we are using different component names in JIRA for the our projects:</div><div><br></div><div>AEROGEAR: </div><div>Uses 'data-sync' as the component name:</div><div><a href="https://issues.jboss.org/issues/?filter=12322676" target="_blank">https://issues.jboss.org/issues/?filter=12322676</a></div><div><br></div><div>AGIOS</div><div>Uses 'sync' as the component name:</div><div><a href="https://issues.jboss.org/issues/?filter=12322678" target="_blank">https://issues.jboss.org/issues/?filter=12322678</a><br></div><div><br></div><div>AGDROID</div><div>Uses 'datasync' as the component name:</div><div><a href="https://issues.jboss.org/issues/?filter=12322677" target="_blank">https://issues.jboss.org/issues/?filter=12322677</a><br></div><div><br></div><div>AGJS</div><div>Uses 'data-sync' as the component name:</div><div><a href="https://issues.jboss.org/issues/?filter=12322679" target="_blank">https://issues.jboss.org/issues/?filter=12322679</a><br></div><div><br></div><div>I would be nice to makes these consistent across the projects. Let me know which you prefer and I'll make the changes needed. </div><div><br></div><div>I'm personally +1 for 'datasync'</div><div><br></div><div>[1] <a href="http://aerogear.org/docs/planning/roadmaps/AeroGearDataSync" target="_blank">http://aerogear.org/docs/planning/roadmaps/AeroGearDataSync</a></div><div>[2] <a href="http://aerogear.org/docs/planning/roadmaps/AeroGearConflictResolution" target="_blank">http://aerogear.org/docs/planning/roadmaps/AeroGearConflictResolution</a><br></div></div>
<br></div></div>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><span><font color="#888888"><br></font></span></blockquote></div><span><font color="#888888"><br><br clear="all"><div><br></div>-- <br><div>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a></div>
</font></span></div>
<br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br></div>
_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></blockquote></div><br></div></div></div></div><br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div></div></div><div><div class="h5"><br><br clear="all"><div><br></div>-- <br><div>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a></div>
</div></div></div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a></div>
</div>