<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On May 21, 2013, at 7:34 AM, Kris Borchers <<a href="mailto:kris@redhat.com">kris@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On May 21, 2013, at 6:25 AM, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, May 21, 2013 at 1:21 PM, Kris Borchers <span dir="ltr"><<a href="mailto:kris@redhat.com" target="_blank">kris@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><div class="im">
<div>On May 20, 2013, at 11:07 PM, Matthias Wessendorf <<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>> wrote:</div><br><blockquote type="cite"><div dir="ltr"><br><div class="gmail_extra"><br>
<br><div class="gmail_quote">On Mon, May 20, 2013 at 10:14 PM, Kris Borchers <span dir="ltr"><<a href="mailto:kris@redhat.com" target="_blank">kris@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word">In our team meeting today, I brought up the question of whether or not the JavaScript clients for both SimplePush and Unified Push should live in folders under AeroGear.js or in their own repos. I would like to open this up to suggestions from the team. Please vote below.<div>
<br></div><div>SimplePush</div><div>Currently, this lives under AeroGear.js at <a href="https://github.com/aerogear/aerogear-js/tree/Notifier/src/simple-push" target="_blank">https://github.com/aerogear/aerogear-js/tree/Notifier/src/simple-push</a></div>
<div>IMO, this makes sense since it also has a hard dependency on Notifier which lives here <a href="https://github.com/aerogear/aerogear-js/tree/Notifier/src/notifier" target="_blank">https://github.com/aerogear/aerogear-js/tree/Notifier/src/notifier</a></div>
<div>I would vote this remain where it is. Please vote whether or not this should remain in the AeroGear.js repo.</div></div></blockquote><div><br></div><div><br></div><div>I *think* it would be good to have a separated repo for it.</div>
<div><br></div><div>So, folks that want to use the SimplePush, and only SimplePush, could just add the "AG-SimplePush.js" to their project</div><div>(it could still have a dependency against Notifier, right?)</div>
</div></div></div></blockquote><div><br></div></div>This would not make sense. This would mean instead of adding one file to their project, they would now need to add either a full or custom build of AeroGear with just Notifier first, then the SimplePush file. If it's in the same repo, then they can use our online custom build tool or use grunt themselves to build a custom version that just has SimplePush and Notifier if that's all they need.</div>
</div></blockquote><div><br></div><div><br></div><div style="">I mean, adding the "AG-SimplePush.js", which has all the dependencies, it requires. Perhaps this is more a distribution issue? Not sure.... Perhaps we just have to explictly say that "aerogear.js" implements the SimplePush (and more)</div></div></div></div></blockquote><div><br></div>I do not want to manage individual distributions for each feature or combination of features we offer. Right now I just want to determine where the source lives and to me it makes the most sense for it to live in the AeroGear repo to facilitate the build process without having to publish it somewhere as a file that doesn't work in order to pull it into AeroGear or to do a full, separate distribution of AeroGear to go along with it.</div><div><br></div><div>When it comes to distribution time, we could talk about modifications to the download builder to be able to link directly to a particular configuration or possibly link directly to a configured download. I don't think either would be too hard but I would need to talk to Luke since he built the existing builder.<br></div></div></blockquote><div><br></div><div>I think there is a JIRA actually for having "cached" builds, so this could go with that.</div><div><br></div><div>i'm plus one to the original suggestions</div><div><br></div><div><br></div><div><br></div><br><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">
<div style=""><br></div><div style="">-M</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div style="word-wrap:break-word"><div><div class="im"><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">
<div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word">
<div><br></div><div><br></div><div>
Unified Push</div><div>Currently, this lives under AeroGear.js at <a href="https://github.com/aerogear/aerogear-js/tree/Notifier/src/unified-push" target="_blank">https://github.com/aerogear/aerogear-js/tree/Notifier/src/unified-push</a></div>
<div>IMO, this is not necessary since it could be used independently from the rest of AeroGear. I would vote that this move to a separate repo. This would also mean that the client object's name would change since it is currently namespaced under AeroGear as AeroGear.UnifiedPushClient. I would suggest it be renamed to AGUnifiedPushClient and be added to a repo named aerogear/unified-push-js. Please vote for whether or not this should move and if it should, an object name and repo name.</div>
</div></blockquote><div><br></div><div><br></div><div>+1 for moving to its own repo</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div style="word-wrap:break-word"><div><br></div><div>Thanks!</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><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></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></div><br></div><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></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></div>
_______________________________________________<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">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></blockquote></div><br></div>_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/aerogear-dev</blockquote></div><br></body></html>