> > There doesn't necessarily have to be a formal-road-map "process" in > existence, for there to be a "road-map-section" in the web2py website.
For example, I like how Redmine's road-map section is structured: > http://www.redmine.org/projects/redmine/roadmap > I think you would need a formal process to determine which items will make it into which releases. > As for announcement, I disagree - That's another duplication-of-efforts > and multiplication that creates confusion > Not sure what you mean about duplication. If you have something to announce, post about it here. - if there is already an maintained tweeter-feed, that it should be used - > embedding a tweeter feed into a website is common and trivial nowadays - > people expect it. > Well, it's probably not quite active enough now to justify, but that sounds fine. Note, the feed is currently displayed on the home page of the admin app. > Book-updates should be linked-into from that tweeter-feed. > For now, you can subscribe to the feed for the repo commits: https://github.com/mdipierro/web2py-book/commits/master (you can also subscribe to commits to the main web2py repo as well as to postings to the Google Code issues list if you're interested). You wouldn't want that automated to Twitter, though, as many are just fixing typos or making small changes. Keep in mind, this whole thing is run by volunteers (and not volunteers who are paid by a company to "volunteer," as with some open source projects), so you might have to temper your expectations a bit. In many cases, if you want something done, you'll likely have to be the one to do it (or at least put significant effort into initiating it). The fact that it hasn't already been done likely means that no one else has yet been willing to make the effort. So, if you want a Twitter feed on the home page, send Massimo a patch for the "examples" app. If you would like timely, centralized announcements, maybe volunteer to coordinate and manage that. Note, I don't want to discourage you or anyone from making observations about pain points or suggestions for improvement -- constructive feedback is always helpful. Just be mindful about how you present the feedback, given that you are asking volunteers to give up more of their time to make your life easier. :-) Anthony -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
