[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[E-devel] Continuing the website saga
Ok, haven't got a lot of responses (not that I gave it a huge amount of
time, I'm inpatent) but, a follow on email to what we want out of the site.
How do we get it.
Lets us assume, for now, XSM is our CMS of choice. It will handle the
static pages for all 'normal pages'. It will handle the news page
(which, will hopefully be able to be displayed on both the home page for
2-3 articles and in the news page, Handy?). The FAQ will be XSM. If we
want to hook up for the user to download the faq to their system we can
grab the .xml file XSM generates and post process if needed (Handy, can
we hook post processing scripts in so after a page is written out, fire
script?) and stick this into specific spots in the webserver.
The main docs pages will be in XSM. The API docs will be generated from
CVS, with links from XSM. The other docs that are in CVS will also be
autogen'd on commit with links from XSM.
That make sense as a starting point?
So, what does that leave us with to sort out.
1- User forums. The easiest is to grab something previously created and
use that. There are two issues.
a) do we want to migrate data from edevelop, if so, how.
b) user authentication. We want this to have the same authentication
So, we'll either need to modify this in the forum software, or do
some fancy footwork.
(XSM writes its user db and we parse that into the forum db, or
into LDAP or something?)
2- Wiki. Do we want a user wiki? Something for users to put their info
on, put up a page for
their efl apps, or their theme they're working on. If we want this,
again, how do we integrate
the user database with XSM. Probably a similar issue as 1. Which
Wiki software do we use?
3- Bug database. Basically same as above. How to integrate users, which
bug software to
use. We currently use Mantis. Do we stick with that? (Losing the
current bug data is
unacceptable so if we go to something else we _have_ to migrate.)
4- Release directory list. It sounds like we can hook php into XSM. This
page will then just
be controlled by XSM. (Assuming I'm correct on the XSM php front.)
I just thought of another feature we may want on the site. Autobuild
information. Every 10 min or something rebuild everything, put up page
with build errors, build warnings, etc. Possibly just a php script in
XSM or tinderbox?
Now. I _know_ everyone has their favorite bug database, favorite wiki
software. Favorite hand to use while touching themselves. Thats fine. I
want to here what you like. I only want to hear it _once_. I _don't_
want to hear you bitch about what someone else likes.
Right now, we need ideas on what to use and how we can hook the pieces
together. We don't want a giant mis-mash site. We also don't want to
write all this shit ourselves. How can we get this stuff to fit together
(And just as a disclaimer. I've been avoiding XSM like the plague due to
some early issues. I still think that we should use XSM as a _starting_
point. Once we've tried it on the new site with the other components
then we can decided if it holds wind. To which, I've started poking XSM