[OGo-Discuss] CMS Question [Was: New Website]

[Adam Tauno Williams]

--=-y5AS9LHuRevsWhtSYP2t
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

> > Indeed, just like I am still subscribed to this mailinglist not because
> > I have anything to do with OGo but just because I find it interesting t=
o
> > see the proceedings of a project like this ;). (okay and because I thin=
k
> > OGo is an interesting application/project).
> Just a thought on this. Following the project on the lists, is not a func=
tion=20
> of the docs site. If a user has an account on the docs site and its not b=
eing=20
> used, then obviousely there is no contribution from that account. Users c=
an=20
> still make valueable contributions via the various lists or monitor the=20
> projects progress via the same lists as its a separate registration proce=
ss.=20
> The accounts on docs were established so that people with interest could=20
> upload documentation. Comments, etc all go to or via the lists. So a=20
> reduction of some 1/3 of the accounts would greatly increase the performa=
nce=20
> of the system as well as reduce the need to prune all the spam that other=
s=20
> seem to be doing nicely now and reduce the workload on the admins.=20

Yep, pretty much my thinking.  But if it isn't easy...

> Finally a simple=20
> install system that is standardized to the degree possible to eliminate m=
ost=20
> of the distro variables. Not known if the later is possible however.=20

Other than the start/stop scripts and the evil things Debian does to
PostgreSQL (installing two versions side-by-side, etc...) I don't think
there is much in the way of "distro variables".   Once one is beyond
compiling I believe WMOGAG contains all the information required to
setup OGo,  although some points could be elaborated a bit more.  Most
of the frustration I see on the list is in regards to people insisting
on using installation repositories.  Since ours aren't well tested or
maintained my recommendation is to take them down;  just provide tar
balls of releases and nightlies.

I'll work on compilation instructions (for trunk).

--=-y5AS9LHuRevsWhtSYP2t
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)

iD8DBQBHM4eWLRePpNle04MRAtvnAJ9SvpfyLBT6Sek2UtlZnpZ8xiLHsACfeig+
t4MazahteNz2YOZI01KnBtw=
=k9I6
-----END PGP SIGNATURE-----

--=-y5AS9LHuRevsWhtSYP2t--