<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On May 24, 2013, at 7:31 AM, Lucas Holmquist <<a href="mailto:lholmqui@redhat.com">lholmqui@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=us-ascii"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On May 23, 2013, at 4:04 PM, Kris Borchers <<a href="mailto:kris@redhat.com">kris@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><br>On May 23, 2013, at 2:50 PM, Jay Balunas <<a href="mailto:jbalunas@redhat.com">jbalunas@redhat.com</a>> wrote:<br><br><blockquote type="cite"><br>On May 23, 2013, at 3:09 PM, Kris Borchers wrote:<br><br><blockquote type="cite">Today I went to move the JS roadmap from a gist to the website. I have determined that I hate our roadmap section. It's messy and will not be maintainable going forward. I would like to make a proposal for some updates before I dive in.<br></blockquote><br>Completely agree - our docs sections really needs to be revisited!<br><br><blockquote type="cite"><br>First, there is no need for versioning on the index page. It is a roadmap so it should just represent the road ahead and be updated as things change. Once we have passed a milestone, it can be removed since it is no longer on the roadmap or has been moved to a new milestone.<br></blockquote><br>I completely agree with the versioning on the index page itself.<br><br>For the specific roadmap pages, perhaps a suggestion here, for major/minor releases like we have planned on the way to 2.0 would it make sense to mark releases as completed? Or perhaps move to the bottom of the specific page (not sure that feels right to me though)? <br></blockquote><br>I would rather just remove anything that isn't "the future" from a roadmap. What I would suggest is maybe we could add a section to the site for change logs. That way we can post complete lists of features implemented in a version release. That way we get the best of both worlds, a clean path forward and a pretty picture of where we've been. Thoughts?<br></blockquote><div><br></div><div>+1 to change logs.</div><div><br></div><div>that was my initial thought when i read the first email</div><div><br></div><div>maybe something like this</div><div><br></div><div><a href="http://backbonejs.org/#changelog">http://backbonejs.org/#changelog</a></div><div><br></div><div><br></div><div>but on a separate page. </div></div></div></blockquote><div><br></div>Yeah, that is similar to the format I was thinking. Keeping it simple and clean like that should make them easier to automate as well.<br><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br><blockquote type="cite"><blockquote type="cite"><br><blockquote type="cite"><br>That in itself will clean things up greatly. After that I would just do some minor tweaks to the layout of the index page, etc and I think we will be better off. Thoughts?<br></blockquote><br>Yes, please feel free to tweak this as needed! We'll need to revisit the whole thing at some point here as well.<br><br>One other related item to discuss is to revamp the overall roadmap for the project - perhaps break the page into columns with one side being a high level overview (like the roadmap email from qmx), and the other be the links to the details for the tech?<br><br><blockquote type="cite"><br>I can go ahead and make the changes and send a PR for discussion if that would work better for people as well.<br></blockquote><br>+1 <br><br><blockquote type="cite"><br>Kris<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">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote><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">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote><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">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></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>