[aerogear-dev] [datasync] JIRA component name

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

[aerogear-dev] [datasync] JIRA component name

danielbevenius
Hi All,

we have created JIRA tasks for the data sync roadmaps [1][2]. 

While creating them we noticed that we are using different component names in JIRA for the our projects:

AEROGEAR:  
Uses 'data-sync' as the component name:

AGIOS
Uses 'sync' as the component name:

AGDROID
Uses 'datasync' as the component name:

AGJS
Uses 'data-sync' as the component name:

I would be nice to makes these consistent across the projects. Let me know which you prefer and I'll make the changes needed. 

I'm personally +1 for 'datasync'


_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev
Reply | Threaded
Open this post in threaded view
|

Re: [aerogear-dev] [datasync] JIRA component name

Matthias Wessendorf
instead of storing all sync items underneath the AEROGEAR instance, 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.

-Matthias

On Tue, Nov 11, 2014 at 6:38 AM, Daniel Bevenius <[hidden email]> wrote:
Hi All,

we have created JIRA tasks for the data sync roadmaps [1][2]. 

While creating them we noticed that we are using different component names in JIRA for the our projects:

AEROGEAR:  
Uses 'data-sync' as the component name:

AGIOS
Uses 'sync' as the component name:

AGDROID
Uses 'datasync' as the component name:

AGJS
Uses 'data-sync' as the component name:

I would be nice to makes these consistent across the projects. Let me know which you prefer and I'll make the changes needed. 

I'm personally +1 for 'datasync'


_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev
Reply | Threaded
Open this post in threaded view
|

Re: [aerogear-dev] [datasync] JIRA component name

danielbevenius
I'm fine with making an AGDATASYNC or AGSYNC JIRA instance if that is what is agreed upon. 

On 11 November 2014 08:00, Matthias Wessendorf <[hidden email]> wrote:
instead of storing all sync items underneath the AEROGEAR instance, 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.

-Matthias

On Tue, Nov 11, 2014 at 6:38 AM, Daniel Bevenius <[hidden email]> wrote:
Hi All,

we have created JIRA tasks for the data sync roadmaps [1][2]. 

While creating them we noticed that we are using different component names in JIRA for the our projects:

AEROGEAR:  
Uses 'data-sync' as the component name:

AGIOS
Uses 'sync' as the component name:

AGDROID
Uses 'datasync' as the component name:

AGJS
Uses 'data-sync' as the component name:

I would be nice to makes these consistent across the projects. Let me know which you prefer and I'll make the changes needed. 

I'm personally +1 for 'datasync'


_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev


_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev
Reply | Threaded
Open this post in threaded view
|

Re: [aerogear-dev] [datasync] JIRA component name

Erik Jan de Wit
Isn’t datasync a feature of AeroGear? Those this mean every feature is going to have it’s own JIRA? What is the rule?

On 11 Nov,2014, at 10:20 , Daniel Bevenius <[hidden email]> wrote:

I'm fine with making an AGDATASYNC or AGSYNC JIRA instance if that is what is agreed upon. 

On 11 November 2014 08:00, Matthias Wessendorf <[hidden email]> wrote:
instead of storing all sync items underneath the AEROGEAR instance, 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.

-Matthias

On Tue, Nov 11, 2014 at 6:38 AM, Daniel Bevenius <[hidden email]> wrote:
Hi All,

we have created JIRA tasks for the data sync roadmaps [1][2]. 

While creating them we noticed that we are using different component names in JIRA for the our projects:

AEROGEAR:  
Uses 'data-sync' as the component name:

AGIOS
Uses 'sync' as the component name:

AGDROID
Uses 'datasync' as the component name:

AGJS
Uses 'data-sync' as the component name:

I would be nice to makes these consistent across the projects. Let me know which you prefer and I'll make the changes needed. 

I'm personally +1 for 'datasync'


_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev


_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev
Reply | Threaded
Open this post in threaded view
|

Re: [aerogear-dev] [datasync] JIRA component name

Matthias Wessendorf


On Tue, Nov 11, 2014 at 10:23 AM, Erik Jan de Wit <[hidden email]> wrote:
Isn’t datasync a feature of AeroGear? Those this mean every feature is going to have it’s own JIRA? What is the rule?

not sure there is a rule :) 

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 
 

On 11 Nov,2014, at 10:20 , Daniel Bevenius <[hidden email]> wrote:

I'm fine with making an AGDATASYNC or AGSYNC JIRA instance if that is what is agreed upon. 

On 11 November 2014 08:00, Matthias Wessendorf <[hidden email]> wrote:
instead of storing all sync items underneath the AEROGEAR instance, 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.

-Matthias

On Tue, Nov 11, 2014 at 6:38 AM, Daniel Bevenius <[hidden email]> wrote:
Hi All,

we have created JIRA tasks for the data sync roadmaps [1][2]. 

While creating them we noticed that we are using different component names in JIRA for the our projects:

AEROGEAR:  
Uses 'data-sync' as the component name:

AGIOS
Uses 'sync' as the component name:

AGDROID
Uses 'datasync' as the component name:

AGJS
Uses 'data-sync' as the component name:

I would be nice to makes these consistent across the projects. Let me know which you prefer and I'll make the changes needed. 

I'm personally +1 for 'datasync'


_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev


_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev
Reply | Threaded
Open this post in threaded view
|

Re: [aerogear-dev] [datasync] JIRA component name

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

On Tue, Nov 11, 2014 at 10:32 AM, Matthias Wessendorf <[hidden email]> wrote:


On Tue, Nov 11, 2014 at 10:23 AM, Erik Jan de Wit <[hidden email]> wrote:
Isn’t datasync a feature of AeroGear? Those this mean every feature is going to have it’s own JIRA? What is the rule?

not sure there is a rule :) 

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 
 

On 11 Nov,2014, at 10:20 , Daniel Bevenius <[hidden email]> wrote:

I'm fine with making an AGDATASYNC or AGSYNC JIRA instance if that is what is agreed upon. 

On 11 November 2014 08:00, Matthias Wessendorf <[hidden email]> wrote:
instead of storing all sync items underneath the AEROGEAR instance, 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.

-Matthias

On Tue, Nov 11, 2014 at 6:38 AM, Daniel Bevenius <[hidden email]> wrote:
Hi All,

we have created JIRA tasks for the data sync roadmaps [1][2]. 

While creating them we noticed that we are using different component names in JIRA for the our projects:

AEROGEAR:  
Uses 'data-sync' as the component name:

AGIOS
Uses 'sync' as the component name:

AGDROID
Uses 'datasync' as the component name:

AGJS
Uses 'data-sync' as the component name:

I would be nice to makes these consistent across the projects. Let me know which you prefer and I'll make the changes needed. 

I'm personally +1 for 'datasync'


_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev


_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev
qmx
Reply | Threaded
Open this post in threaded view
|

Re: [aerogear-dev] [datasync] JIRA component name

qmx
Administrator
In reply to this post by Matthias Wessendorf
Don't forget the JIRA "column" size limit, you might get a not so cool name :(
--
qmx
_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev
Reply | Threaded
Open this post in threaded view
|

Re: [aerogear-dev] [datasync] JIRA component name

Matthias Wessendorf
AGSYNC ? :)

On Tue, Nov 11, 2014 at 10:34 AM, Douglas Campos <[hidden email]> wrote:
Don't forget the JIRA "column" size limit, you might get a not so cool name :(
--
qmx
_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev
Reply | Threaded
Open this post in threaded view
|

Re: [aerogear-dev] [datasync] JIRA component name

Bruno Oliveira
+1 AGSYNC



abstractj
PGP: 0x84DC9914


On Tue, Nov 11, 2014 at 7:39 AM, Matthias Wessendorf <[hidden email]> wrote:

AGSYNC ? :)

On Tue, Nov 11, 2014 at 10:34 AM, Douglas Campos <[hidden email]> wrote:
Don't forget the JIRA "column" size limit, you might get a not so cool name :(
--
qmx
_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--


_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev
Reply | Threaded
Open this post in threaded view
|

Re: [aerogear-dev] [datasync] JIRA component name

Luke Holmquist
+1 AGSYNC


but if that isn’t available, then i vote for GETTOTHACHOPPA 

On Nov 11, 2014, at 5:52 AM, Bruno Oliveira <[hidden email]> wrote:

+1 AGSYNC



abstractj
PGP: 0x84DC9914


On Tue, Nov 11, 2014 at 7:39 AM, Matthias Wessendorf <[hidden email]> wrote:

AGSYNC ? :)

On Tue, Nov 11, 2014 at 10:34 AM, Douglas Campos <[hidden email]> wrote:
Don't forget the JIRA "column" size limit, you might get a not so cool name :(
--
qmx
_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev


_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev
Reply | Threaded
Open this post in threaded view
|

Re: [aerogear-dev] [datasync] JIRA component name

Summers Pittman
On 11/11/2014 07:58 AM, Lucas Holmquist wrote:
+1 AGSYNC
+1, but only because I am rocking the 90s boy band blonde right now.


but if that isn’t available, then i vote for GETTOTHACHOPPA 

On Nov 11, 2014, at 5:52 AM, Bruno Oliveira <[hidden email]> wrote:

+1 AGSYNC



abstractj
PGP: 0x84DC9914


On Tue, Nov 11, 2014 at 7:39 AM, Matthias Wessendorf <[hidden email]> wrote:

AGSYNC ? :)

On Tue, Nov 11, 2014 at 10:34 AM, Douglas Campos <[hidden email]> wrote:
Don't forget the JIRA "column" size limit, you might get a not so cool name :(
--
qmx
_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev


-- 
Summers Pittman
>>Phone:404 941 4698
>>Java is my crack.

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev