Anonymous user
Choosing a forum: Difference between revisions
→Results and Recommendations:
imported>Mark m (Protected "Choosing a forum" ([edit=sysop] (indefinite) [move=sysop] (indefinite))) |
imported>Mark |
||
| (11 intermediate revisions by the same user not shown) | |||
Line 1:
==
The most fully featured options appear to be between Vanilla, GroupServer, Phorum, and FUDforum.
Between Vanilla and Phorum, I have to say Vanilla wins hands down due to ease of installation, ability to embed within the current site, and activity of both the user and developer communities.
FUDforum is a very powerful option and could be great, however I personally think it is overkill for what OH needs.
GroupServer looks amazing, however I was unable to get it to install even after several hours of trying. There is a hosted option, however I couldn't quire determine if it was free or if there would be a cost.
At this stage, I don't feel that the django based forums are quite there yet, with the possible exception of the Q&A style forums, which we have established don't fit the use case for OH.
'''My recommendation would be using Vanilla and working on the cookie based login integration with the main OH site. While FUD is a reasonable option, it doesn't "look" quite right with the design of OH. This may come down to features vs how natural and clean we would want the forums to appear.'''
== Requirements: ==
Line 13 ⟶ 23:
== Options: ==
''' FUD Forum'''
http://fudforum.org/forum/ & related wiki http://cvs.prohost.org/
PHP based.
Does appear to offer login integration through some exposed PHP APIs. Not sure how we would sync the user databases and call the PHP code from within python, but I do understand it may be generally possible (see http://www.brool.com/index.php/hacks-python-calling-php).
Does appear to have a mailing list integration. From the notes on the config page: You can either schedule imports or pipe messages into the forum with procmail or postfix. Having never administered a mailing list personally, I don't know quite what this would entail.
Appears to have a pretty active community.
'''Install results:'''
* Very simple to install.
* Can use mysql, postgres, oracle, etc. fairly db agnostic.
* Has a classic look (ie lots of options and configuration).
* Doesn't look like it was intended to be embedded within another site.
Line 35 ⟶ 62:
Tutorial videos. http://www.screenr.com/user/vanilla
''' Install results: '''
* Dead simple to install.
* Uses mysql.
* Has an embedded theme/mode/plugin that allows integration with current site with one line of code.
* It can send email, but I couldn't find an option to post to the forum from an email.
* Lots of cool plugins.
* Very active community.
* There is a login integration plugin which uses cookies. Not sure how well it would work with OH.
Line 48 ⟶ 83:
If we had to write our own integration, would this make things easier?
Has a hosted option. http://onlinegroups.net/, but there would be no possibility of login integration.
At first glance, user manuals don’t really look all that clear or helpful.
Definitely has mailing list features.
Looks quite fully featured.
http://groupserver.org/groupserver/features/
Line 60 ⟶ 97:
* Requires running postfix for email integration.
* '''Tried for about 2 hours to get it installed and couldn't get past a buildout error with egenix-mx-base.'''
Line 78 ⟶ 113:
Mailing list plugin.
http://www.phorum.org/phorum5/read.php?62,129244,129244#msg-129244
''' Install results: '''
* Dead simple to install.
* Requires mysql.
* Can send emails.
* Mailing list plugin appears to be send only.
* Lots of plugins.
* Active community.
== Django Modules. Login integration would be automatic (I am assuming). ==
Line 101 ⟶ 145:
Email list integration?
'''Install results:'''
* Post from Asheesh that he didn't feel this style of Q&A was proper for the intent of the forum addition. No install required.
Line 130 ⟶ 175:
Has email subscription to threads, like most, but nothing specific to email list integration.
'''Install results:'''
* Installation of the module was pretty simple.
* Has third party requirements of markdown and django-common
* requires setting up templates before anything works, which I did not explore.
* Little to no documentation. No clue how to start with setting up templates or administrating the forum.
| |||