<div dir="ltr"><h3 style="margin:0px 0px 10px;padding:0px;font-size:18px;color:rgb(0,0,0);font-family:Helvetica,arial,freesans,clean,sans-serif"><span style="font-size:14px;font-weight:normal;line-height:20px">What about the following</span><br>
</h3><div><span style="font-size:14px;font-weight:normal;line-height:20px"><br></span></div><div><span style="font-size:14px;font-weight:normal;line-height:20px"><br></span></div><h3 style="margin:0px 0px 10px;padding:0px;font-size:18px;color:rgb(0,0,0);font-family:Helvetica,arial,freesans,clean,sans-serif">
Specific Components</h3><p style="margin:0px 0px 15px;color:rgb(0,0,0);font-family:Helvetica,arial,freesans,clean,sans-serif;font-size:13.63636302947998px;line-height:20px">The following are very specific to a certain part of the "work":</p>
<ul style="margin:15px 0px;padding:0px 0px 0px 30px;color:rgb(0,0,0);font-family:Helvetica,arial,freesans,clean,sans-serif;font-size:13.63636302947998px;line-height:20px"><li>UnifiedPush-server</li><li>UnifiedPush-ios</li>
<li>UnifiedPush-android</li><li>UnifiedPush-javascript</li><li>UnifiedPush-admin</li><li>UnifiedPush-java(-sender)</li><li>UnifiedPush-aps</li><li>UnifiedPush-gcm</li><li>UnifiedPush-simplePush (=== connection TO (various) SP networks)</li>
<li>SimplePush-server</li><li>SimplePush-javascript (=== client, I think there is only a JS client)</li></ul><p style="margin:15px 0px;color:rgb(0,0,0);font-family:Helvetica,arial,freesans,clean,sans-serif;font-size:13.63636302947998px;line-height:20px">
<br></p><p style="margin:15px 0px;color:rgb(0,0,0);font-family:Helvetica,arial,freesans,clean,sans-serif;font-size:13.63636302947998px;line-height:20px">Now, various of the above "component" have similar concerns, like <em>security</em> or <em>documentation</em>.</p>
<h3 style="margin:20px 0px 10px;padding:0px;font-size:18px;color:rgb(0,0,0);font-family:Helvetica,arial,freesans,clean,sans-serif"><a name="generic-components-eg-used-like-a-tag" class="" href="https://gist.github.com/matzew/90c9f6837eee6cb074cc#generic-components-eg-used-like-a-tag" style="color:rgb(65,131,196);text-decoration:none;display:block;padding-left:30px"></a>Generic components (e.g. used like a tag)</h3>
<ul style="margin:15px 0px;padding:0px 0px 0px 30px;color:rgb(0,0,0);font-family:Helvetica,arial,freesans,clean,sans-serif;font-size:13.63636302947998px;line-height:20px"><li>security</li><li>Documentation</li><li>Examples</li>
<li>PushNetwork (e.g. when investigating for adding new supported ones...)</li><li>OpenShift (support for UP / SP)</li><li>Tooling (== Tooling / RAD )</li></ul><p style="margin-top:15px;margin-right:0px;margin-left:0px;color:rgb(0,0,0);font-family:Helvetica,arial,freesans,clean,sans-serif;font-size:13.63636302947998px;line-height:20px;margin-bottom:0px!important">
Perhaps these are really more <em>tags</em>, but I am fine in "abusing" these components as tags.</p></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, May 20, 2013 at 9:37 PM, Jay Balunas <span dir="ltr"><<a href="mailto:jbalunas@redhat.com" target="_blank">jbalunas@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">+1 - I added a comment related to this.<br>
<br>
Also, I'm not sure if Jira has "Component Themes" like it has other things, but there will be a lot of shared components between the various AG Jira's. I think it will be important to be consistent where possible (capitalization, abbreviations, naming, etc...).<br>
<div class="HOEnZb"><div class="h5"><br>
On May 20, 2013, at 3:23 PM, Bruno Oliveira wrote:<br>
<br>
> Not sure what's the main idea, but for security we can do something like:<br>
><br>
> AGPUSH-your-favorite-component-here, security<br>
><br>
> If we start to create new components for security per project, it will<br>
> add more confusion. At least to me.<br>
><br>
> Matthias Wessendorf wrote:<br>
>> Howdy,<br>
>><br>
>> added a few comments<br>
>><br>
>><br>
>> On Fri, May 17, 2013 at 8:52 AM, Daniel Bevenius<br>
>> <<a href="mailto:daniel.bevenius@gmail.com">daniel.bevenius@gmail.com</a> <mailto:<a href="mailto:daniel.bevenius@gmail.com">daniel.bevenius@gmail.com</a>>> wrote:<br>
>><br>
>> Looks good!<br>
>><br>
>><br>
>> On 16 May 2013 18:38, Kris Borchers <<a href="mailto:kris@redhat.com">kris@redhat.com</a><br>
>> <mailto:<a href="mailto:kris@redhat.com">kris@redhat.com</a>>> wrote:<br>
>><br>
>> Hey all,<br>
>><br>
>> Please take a look at<br>
>> <a href="https://issues.jboss.org/browse/AGPUSH-11" target="_blank">https://issues.jboss.org/browse/AGPUSH-11</a> and let me know if you<br>
>> would add/change/remove any suggested components I have<br>
>> suggested there.<br>
>><br>
>> Thanks!<br>
>><br>
>> _______________________________________________<br>
>> aerogear-dev mailing list<br>
>> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a> <mailto:<a href="mailto:aerogear-dev@lists.jboss.org">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>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> aerogear-dev mailing list<br>
>> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a> <mailto:<a href="mailto:aerogear-dev@lists.jboss.org">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>
>><br>
>><br>
>><br>
>><br>
>> --<br>
>> 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><br>
>><br>
>> _______________________________________________<br>
>> aerogear-dev mailing list<br>
>> <a href="mailto:aerogear-dev@lists.jboss.org">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>
> _______________________________________________<br>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org">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>
<br>
<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">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>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>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>