<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 20, 2013, at 11:07 PM, 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 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:0 0 0 .8ex;border-left:1px #ccc 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 style="">I *think* it would be good to have a separated repo for it.</div>
<div style=""><br></div><div style="">So, folks that want to use the SimplePush, and only SimplePush, could just add the "AG-SimplePush.js" to their project</div><div style="">(it could still have a dependency against Notifier, right?)</div></div></div></div></blockquote><div><br></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.<br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">
<div style=""><br></div><div style=""><br></div><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><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 style="">+1 for moving to its own repo</div><div><br></div><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><br></div><div>Thanks!</div></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>https://lists.jboss.org/mailman/listinfo/aerogear-dev</blockquote></div><br></body></html>