public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kurt Lieber <klieber@gentoo.org>
To: gentoo-dev@gentoo.org, gentoo-user@gentoo.org
Subject: [gentoo-dev] Migrating to a commercial PHP-based forums package for forums.gentoo.org
Date: Sat, 27 Sep 2003 20:38:00 -0400	[thread overview]
Message-ID: <20030928003755.GM7356@mail.lieber.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1950 bytes --]

As many of you have noticed, the forums have been having significant
performance problems lately.  Without going into the gory details, most of
these issues have to do with the inefficient way phpBB 2.0.x interacts with
the database.

Right now, the apache part of the forums are hosted on OSU's cluster of
dual xeon boxes and the database part is hosted by a dual xeon w/ 4GB of
RAM, so there is ample hardware behind us.  Adding more hardware is not
likely to be a tenable solution.  

We have a couple of options we're considering, none of which are ideal.
One option is to delete older posts and/or move them to an "archive"
section which would be unsearchable or really hard to search (which is,
imo, effectively deleting them because nobody is going to sift through all
that)

Another option is to migrate to an alternate forums package.  Specifically,
vBulletin, which has proven to be quite scalable and effective with larger
sites.  The main drawback to this is the fact that it is a commercial
software package, which tends to raise the ire of some of the more zealous
GNU folks out there.

So, my question to you is, how would you feel if we were to do this?
Horribly offended?  Saddened because there isn't a GPL'd program to meet
our needs, but pragmatic about the need to do *something*?  Or C, none of
the above?

Basically, the choice comes down to one of two things:

1) Lose some older posts and stay on a GPL-compatible package
2) Move to a commercial solution and keep all the posts.

Note that vBulletin *is* open source in that you have access to the source
code and can modify it.  It's just not Free.

Finally, to keep this process somewhat manageably, I ask that you make your
responses on the forums.  I've also set up a poll there so we can vote on
what should be done.  I will likely limit my responses to that discussion.

http://forums.gentoo.org/viewtopic.php?p=554174

--kurt

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2003-09-28  0:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-28  0:38 Kurt Lieber [this message]
2003-09-28  1:58 ` [gentoo-dev] Migrating to a commercial PHP-based forums package for forums.gentoo.org Sven Blumenstein
2003-09-28  2:08   ` Jon Portnoy
2003-09-28  9:50   ` Paul de Vrieze
2003-09-28 20:00 ` Bjorn Sodergren
2003-09-28 20:01   ` Jon Portnoy
2003-09-30 11:30 ` [gentoo-dev] " Sebastian Bergmann
2003-09-30 11:43   ` Mike Frysinger
2003-09-30 12:20     ` Stuart Herbert
2003-09-30 12:48     ` Sebastian Bergmann
2003-09-30 13:19       ` Stuart Herbert
2003-09-30 13:44         ` Sebastian Bergmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030928003755.GM7356@mail.lieber.org \
    --to=klieber@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=gentoo-user@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox