<div dir="ltr"><div>><span style="font-size:13px">First step: replace existing roadmaps with links to JIRAs, where possible.</span></div><div style="font-size:13px"><br></div><div style="font-size:13px">>Next step: re-think the entire roadmaps section. I am currently on that, and it's not 100% yet clear, what's best. Once I have more on this, I will share thoughts</div>Sounds good!</div><div class="gmail_extra"><br><div class="gmail_quote">On 15 December 2014 at 15:05, Matthias Wessendorf <span dir="ltr"><<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hey,<div><br></div><div>that's what I am currently looking at - by doing the analysis of the site, I noticed that our current roadmap docs just duplicate info from JIRA</div><div><br></div><div>First step: replace existing roadmaps with links to JIRAs, where possible.</div><div><br></div><div>Next step: re-think the entire roadmaps section. I am currently on that, and it's not 100% yet clear, what's best. Once I have more on this, I will share thoughts</div><div><div><br></div><div><br></div></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Dec 15, 2014 at 2:40 PM, Bruno Oliveira <span dir="ltr"><<a href="mailto:bruno@abstractj.org" target="_blank">bruno@abstractj.org</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Alright, let's think about the following scenario. I'm a newcomer, going<br>
<a href="http://aerogear.org" target="_blank">aerogear.org</a> to learn more about AeroGear and want to know what's planned for the future<br>
releases. Where should I look?<br>
<div><div><br>
On 2014-12-15, Matthias Wessendorf wrote:<br>
> On Mon, Dec 15, 2014 at 2:25 PM, Bruno Oliveira <<a href="mailto:bruno@abstractj.org" target="_blank">bruno@abstractj.org</a>> wrote:<br>
> ><br>
> > Speaking from the security side of the things, to me is impossible to<br>
> > have a feature driven roadmap, because it's a cross cutting concern.<br>
> ><br>
><br>
> right :-)<br>
><br>
> looking at [1] I see different types of roadmaps<br>
><br>
> 1) Project roadmap<br>
> 2) Platform roadmaps (e.g. Android, Cordova, iOS and JS)<br>
> 3) cross cutting concerns (e.g. security)<br>
> 4) specific roadmaps (E.g. UPS/WebPush or even the WebSite roadmap)<br>
><br>
><br>
> And that's fine :) For now, I'd really just like to get rid of the pages<br>
> that basically duplicate info, available on JIRA :-)<br>
><br>
><br>
><br>
><br>
> ><br>
> > About removing the roadmap from website, as long as we make it clear<br>
> > por people outside AeroGear, I'm fine.<br>
> ><br>
> > On 2014-12-15, Matthias Wessendorf wrote:<br>
> > > Hi team,<br>
> > ><br>
> > > while thinking about restructuring our roadmaps, I was wondering about<br>
> > our<br>
> > > existing roadmaps on [1]. Overall I'd like to have the AG roadmaps more<br>
> > > feature driven, but that requires some more thoughts/changes?<br>
> > ><br>
> > > However, here is what I am wondering about...<br>
> > ><br>
> > > Most of our roadmaps we link to from [1], are really just pointing to<br>
> > > different JIRAs.<br>
> > ><br>
> > ><br>
> > > Let's take one example, UPS:<br>
> > > <a href="https://aerogear.org/docs/planning/roadmaps/UnifiedPush/" target="_blank">https://aerogear.org/docs/planning/roadmaps/UnifiedPush/</a><br>
> > ><br>
> > > Basically all info on the above page is present in JIRA (including the<br>
> > > 'archived' roadmap of older releases). Since JIRA should be the central<br>
> > > tool for planing releases, features and future versions, I think that our<br>
> > > roadmap docs are not adding too much value, since they repeat info that<br>
> > is<br>
> > > available on a different place (JIRA).<br>
> > ><br>
> > > Also, maintaining the roadmaps is tedious: You make a change on the<br>
> > actual<br>
> > > JIRA (e.g. move the date of a release or add a new feature). To keep the<br>
> > > roadmap up-to-date, you put the same info on the roadmap doc and send a<br>
> > PR.<br>
> > ><br>
> > ><br>
> > > Can we remove these roadmap docs?<br>
> > ><br>
> > > For UPS that would mean, that the link on [1] would go against:<br>
> > ><br>
> > <a href="https://issues.jboss.org/browse/AGPUSH?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel" target="_blank">https://issues.jboss.org/browse/AGPUSH?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel</a><br>
> > ><br>
> > > instead of here:<br>
> > > <a href="https://aerogear.org/docs/planning/roadmaps/UnifiedPush/" target="_blank">https://aerogear.org/docs/planning/roadmaps/UnifiedPush/</a><br>
> > ><br>
> > > -Matthias<br>
> > ><br>
> > > [1] <a href="https://aerogear.org/docs/planning/" target="_blank">https://aerogear.org/docs/planning/</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>
> ><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>
> ><br>
> ><br>
> > --<br>
> ><br>
> > abstractj<br>
> > PGP: 0x84DC9914<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>
> ><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" 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>
<br>
<br>
--<br>
<br>
abstractj<br>
PGP: 0x84DC9914<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>
</div></div></blockquote></div><br clear="all"><div><br></div>-- <br><div>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></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></div>