<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jan 20, 2015 at 9:58 PM, Corinne Krych <span dir="ltr"><<a href="mailto:corinnekrych@gmail.com" target="_blank">corinnekrych@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
> On 20 Jan 2015, at 17:01, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:<br>
><br>
> Hi,<br>
><br>
> for all of our different push offerings, we have a central landing page ([1]), and soon that page will also list our work on the WebPush spec ([2])<br>
> Since this model is quite handy, having a centralized landing page, I'd propose we do that for other features, like OAuth2 and Sync as well.<br>
><br>
><br>
> With the new design, the "feature" is more a module, which is fine. The Screenshot of the modules page ([3]), we list all of our feature, or more modules ;-)<br>
> While for PUSH we have more than just one repo (UPS, SimplePush and now WebPush + demos), I think the getting started should go to a 'feature' (or module) landing page. For AeroGearPush that would be [1], or something similar. Basically, on this "module landing page", I'd like to list all relevant GH repos, link to JIRA and perhaps other resources.<br>
><br>
> Any thoughts?<br>
><br>
><br>
> Now, taking a different example, sync, we would list these repos:<br>
><br>
> iOS:<br>
> <a href="https://github.com/aerogear/aerogear-ios-sync" target="_blank">https://github.com/aerogear/aerogear-ios-sync</a><br>
> <a href="https://github.com/aerogear/aerogear-ios-sync-client" target="_blank">https://github.com/aerogear/aerogear-ios-sync-client</a><br>
> <a href="https://github.com/aerogear/aerogear-ios-sync-demo" target="_blank">https://github.com/aerogear/aerogear-ios-sync-demo</a><br>
><br>
> Android:<br>
> <a href="https://github.com/aerogear/aerogear-android-sync" target="_blank">https://github.com/aerogear/aerogear-android-sync</a><br>
><br>
> JS:<br>
> <a href="https://github.com/aerogear/aerogear-js" target="_blank">https://github.com/aerogear/aerogear-js</a> (part of the lib)<br>
> <a href="https://github.com/aerogear/aerogear-js-cookbook" target="_blank">https://github.com/aerogear/aerogear-js-cookbook</a> (a sync demo, based on node)<br>
><br>
> Sync-Server:<br>
> <a href="https://github.com/aerogear/aerogear-sync-server" target="_blank">https://github.com/aerogear/aerogear-sync-server</a><br>
><br>
><br>
> + linking to the JIRAs tracked for the different Sync milestones (currently the ones with the 'sync-1.0.0.alpha.1' label)<br>
><br>
<br>
</span>Do you mean adding a fifth button “List of JIRA tickets" after “github repo” or this JIRA button is only accessible via Doc->roadmap menu?<br></blockquote><div><br></div><div>I think it is a good thing to have another link, to all the upcoming JIRAs from a 'feature' or 'modules' page. Users of the current bits may be also interested, to some degree, into what's coming next.</div><div><br></div><div>While a 'link' from Docs/Roadmaps is good as well.</div><div><br></div><div>-M</div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=""><br>
><br>
> When we have clear "module" entry or landing pages, it's easy for new users, to get an understanding what it is all about. Instead of jump around on the site (which is why we generally do the new site :-))<br>
><br>
><br>
> Does that make sense ?<br>
><br>
><br>
> -Matthias<br>
><br>
> [1] <a href="https://aerogear.org/push/" target="_blank">https://aerogear.org/push/</a><br>
> [2] <a href="https://github.com/aerogear/aerogear.org/pull/468" target="_blank">https://github.com/aerogear/aerogear.org/pull/468</a><br>
> [3] <a href="https://www.dropbox.com/s/zypkqd3nn3wma9w/Screen%20Shot%202015-01-20%20at%2016.38.33.png?dl=0" target="_blank">https://www.dropbox.com/s/zypkqd3nn3wma9w/Screen%20Shot%202015-01-20%20at%2016.38.33.png?dl=0</a><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>
</span>> _______________________________________________<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></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></div>