I really dislike Discourse. It's a Ruby app, and it requires a ton of addons. It's bloated and slow, and since it uses virtual infinite scroll, it's very difficult to search within discussions.
https://www.techfuel.net/pyforum/default/index pyForum is based on web2py, though it looks like the project has been abandoned and it needs spam filtering / moderation. there's Uforum (http://www.uforum.nl/topic/active) for which there is no source and I don't know if the authors would be willing to share. Personally, my favorite it is a mix of python and javascript and it's called geiwiki. Of course it's not a forum, more like a tiddlywiki with discussion features added. That may be difficult to use, not recommended. Finally, last but not least, there's http://web2pyslices.pythonanywhere.com/home. It has a 'questions' function which will allow people to post questions and get answers, but it's not prominently featured. This site is geared towards showing you how to do neat stuff, yet the questions portion is not front and center so people don't use it. Also the format of it is not quite optimized for question asking and answering (those icons right next to each question are repetitive). In the running is stackoverflow.com which is widely used, already has a web2py tag, and the interface is ideal for asking questions as well as answering them. It even has gaming to incentivize people to answer questions. The only issues are, this forum is not promoted on the web2py main page, and thus there are a lot of unanswered questions. On Thursday, July 30, 2015 at 8:20:51 AM UTC-7, Anthony wrote: > > On Thursday, July 30, 2015 at 11:08:09 AM UTC-4, Richard wrote: >> >> Discourse seems really nice... It represents a lot of work... But as a >> "proof of concept" I think we should considering to use our own tool >> (web2py) to create our own mailing-list... Could we "seriously" be able to >> manage our own list and write our own app for this? This is a big undertake >> and maintenance contract... >> > > Although open source, Discourse is developed by a commercial enterprise > (they offer hosting), and so it represents a substantial amount of > development effort (though perhaps a web2py version could get a head start > by using the Discourse Ember.js front end and attempting to replicate the > Rails back end -- but if making a near exact copy, why bother?). For > someone, perhaps developing a commercially-backed web2py-based alternative > to Discourse would be worthwhile (though probably tough competition), but > for the web2py core developers, I think the time might be better spent on > (a) further developing web2py, (b) developing plugins and re-usable apps > for web2py, and (c) web3py. > > Anthony > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
