[aerogear-dev] AeroGear.org - a first thought on changing our roadmap docs

Mon Dec 15 09:23:22 EST 2014

On Mon, Dec 15, 2014 at 3:17 PM, Andres Galante <agalante at redhat.com> wrote:
>
> Can't we have some kind of aggregator that reads the roadmaps from JIRA
> and print it on the website?
>

Not sure. Since JIRA is the main tool to manage and plan releases, let's
link straight to it. That's also the place where users actually would file
tickets (e.g. bugs or feature requests)

-M

>
>
> ----- Original Message -----
> From: "Daniel Bevenius" <daniel.bevenius at gmail.com>
> To: "AeroGear Developer Mailing List" <aerogear-dev at lists.jboss.org>
> Sent: Monday, December 15, 2014 11:08:31 AM
> Subject: Re: [aerogear-dev] AeroGear.org - a first thought on changing our
> roadmap docs
>
> > First step: replace existing roadmaps with links to JIRAs, where
> possible.
>
> >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
> Sounds good!
>
> On 15 December 2014 at 15:05, Matthias Wessendorf < matzew at apache.org >
> wrote:
>
>
>
> Hey,
>
> 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
>
> First step: replace existing roadmaps with links to JIRAs, where possible.
>
> 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
>
>
>
> On Mon, Dec 15, 2014 at 2:40 PM, Bruno Oliveira < bruno at abstractj.org >
> wrote:
>
> Alright, let's think about the following scenario. I'm a newcomer, going
> aerogear.org to learn more about AeroGear and want to know what's planned
> for the future
> releases. Where should I look?
>
> On 2014-12-15, Matthias Wessendorf wrote:
> > On Mon, Dec 15, 2014 at 2:25 PM, Bruno Oliveira < bruno at abstractj.org >
> wrote:
> > >
> > > Speaking from the security side of the things, to me is impossible to
> > > have a feature driven roadmap, because it's a cross cutting concern.
> > >
> >
> > right :-)
> >
> > looking at [1] I see different types of roadmaps
> >
> > 1) Project roadmap
> > 2) Platform roadmaps (e.g. Android, Cordova, iOS and JS)
> > 3) cross cutting concerns (e.g. security)
> > 4) specific roadmaps (E.g. UPS/WebPush or even the WebSite roadmap)
> >
> >
> > And that's fine :) For now, I'd really just like to get rid of the pages
> > that basically duplicate info, available on JIRA :-)
> >
> >
> >
> >
> > >
> > > About removing the roadmap from website, as long as we make it clear
> > > por people outside AeroGear, I'm fine.
> > >
> > > On 2014-12-15, Matthias Wessendorf wrote:
> > > > Hi team,
> > > >
> > > > while thinking about restructuring our roadmaps, I was wondering
> about
> > > our
> > > > existing roadmaps on [1]. Overall I'd like to have the AG roadmaps
> more
> > > > feature driven, but that requires some more thoughts/changes?
> > > >
> > > > However, here is what I am wondering about...
> > > >
> > > > Most of our roadmaps we link to from [1], are really just pointing to
> > > > different JIRAs.
> > > >
> > > >
> > > > Let's take one example, UPS:
> > > > https://aerogear.org/docs/planning/roadmaps/UnifiedPush/
> > > >
> > > > Basically all info on the above page is present in JIRA (including
> the
> > > > 'archived' roadmap of older releases). Since JIRA should be the
> central
> > > > tool for planing releases, features and future versions, I think
> that our
> > > > roadmap docs are not adding too much value, since they repeat info
> that
> > > is
> > > > available on a different place (JIRA).
> > > >
> > > > Also, maintaining the roadmaps is tedious: You make a change on the
> > > actual
> > > > JIRA (e.g. move the date of a release or add a new feature). To keep
> the
> > > > roadmap up-to-date, you put the same info on the roadmap doc and
> send a
> > > PR.
> > > >
> > > >
> > > > Can we remove these roadmap docs?
> > > >
> > > > For UPS that would mean, that the link on [1] would go against:
> > > >
> > >
> https://issues.jboss.org/browse/AGPUSH?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel
> > > >
> > > > instead of here:
> > > > https://aerogear.org/docs/planning/roadmaps/UnifiedPush/
> > > >
> > > > -Matthias
> > > >
> > > > [1] https://aerogear.org/docs/planning/
> > > >
> > > >
> > > > --
> > > > Matthias Wessendorf
> > > >
> > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > sessions: http://www.slideshare.net/mwessendorf
> > > > twitter: http://twitter.com/mwessendorf
> > >
> > > > _______________________________________________
> > > > aerogear-dev mailing list
> > > > aerogear-dev at lists.jboss.org
> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >
> > >
> > > --
> > >
> > > abstractj
> > > PGP: 0x84DC9914
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >
> >
> >
> > --
> > Matthias Wessendorf
> >
> > blog: http://matthiaswessendorf.wordpress.com/
> > sessions: http://www.slideshare.net/mwessendorf
> > twitter: http://twitter.com/mwessendorf
>
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> --
>
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>

-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141215/7181f7f6/attachment.html 