using Trac for osg
Jose L. Hidalgo
If osg is going to move from cvs to svn, maybe as Jan said in the osg
list:
A nice tool which works with Subversion is Trac:
http://trac.edgewall.org/ - it provides source browsing, wiki and
integrated bug tracker all in one without requiring a dedicated
database
(everything is stored as subversion project). I am running this for our
internal needs at the moment and it works great.
I'm not sure about the not requiring a database ( the Tracs I installed
need a database from mysql or a file with the database sqlite... ) I'm
not sure, but it is fantastic how trac integrates with Subversion.
Installing track we will have:
- subversion browser
- wiki -- > IMHO the osg wiki needs reorganization, clean, purge or
whatever... nobody uses html-frames and maybe you can consider start
moving on a new wiki (Trac has its own)
- tickets, milestones, roadmap, bugtracker in general --> thats
perfect to send tickets with problems, bugs, enhacements, and let
people try to solve them.
Other things I'm impressed with, are:
Track Links --> http://trac.edgewall.org/wiki/TracLinks : Can be used
in any part of the wiki to point a milestone, a pice of code, a
ticket... and *should* be used in subversion comments.
RSS -> http://trac.edgewall.org/wiki/TracRss : That allows people to
syndicate events (from code, pages,...)
Other things: mail notification, queries, reports....
Best Regards,
Jose L.
Robert Osfield
I'm open to using Trac, but I'm keen to take things slowly during the intial change over period.
The existing wiki has been very useful but a good wiki does need managing, prune, re-organsing to keep efficient. I have never had the time to do this and since me time has always got more and more contended as time goes on the changes of me suddenly having time for this is close to zero.
However, we have a community ;-)
For the new server I'd suggest :
1) move to svn,
2) migrate exsting PmWiki website
3) migrate mailman
Then when life has settled down, get 1.3 out the door, and once life settles down again start thinking about other technologies for the new server.
Robert.
Jan Ciger
Hash: SHA1
Hello,
Regarding to what Jose said about Trac:
> I'm not sure about the not requiring a database ( the Tracs I installed
> need a database from mysql or a file with the database sqlite... )
I think that he is right - I have forgotten about the database because
we are using sqlite and not something like MySQL. So, strictly speaking,
you do need a database, but not a database server :) On the other hand,
I have no clue how well sqlite will scale for many users :(
Regards,
Jan
- --
Jan Ciger
GPG public key: http://www.keyserver.net/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org
iD8DBQFFWgHzn11XseNj94gRAlkhAJ9uzLTqk0h3HTZXrG0OazrEinyRpQCg2YoD
lXkulJuOUNe2LZ5buiiZeuY=
=3C5+
-----END PGP SIGNATURE-----
Robert Osfield
Jan Ciger
Hash: SHA1
Robert Osfield wrote:
> One thing I'm considering is the using openscenegraph.net for ongoing
> experimentation, so things like Tracs could be experimented with there.
> First instance will be using openscenegraph.net for the new server, then
> move the openscenengraph.org domain across last.
>
That is a prudent thing to do, IMHO. Ideally, the new server will be up
and running and when everything is ready, you just change the DNS
records. After few days, if everything is going smooth, you just shut
down the old machine and everything is migrated over.
Jan
- --
Jan Ciger
GPG public key: http://www.keyserver.net/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org
iD8DBQFFWhg4n11XseNj94gRAqaAAKCHVKpxFnF46/CUNXRSCIIWNo2JeACgyrcT
MBf/Ekcb88Vaq0QSUD5spdQ=
=/mdK
-----END PGP SIGNATURE-----
Robert Osfield
Robert Osfield wrote:
> One thing I'm considering is the using openscenegraph.net for ongoing
> experimentation, so things like Tracs could be experimented with there.
> First instance will be using openscenegraph.net for the new server, then
> move the openscenengraph.org domain across last.
>
That is a prudent thing to do, IMHO. Ideally, the new server will be up
and running and when everything is ready, you just change the DNS
records. After few days, if everything is going smooth, you just shut
down the old machine and everything is migrated over.
There is one potential problem with this - current the mailing list goes under the openscenegraph.net domain. I think its possible to use cvs using openscenegraph.net right now as it just points to same server. So perhaps we should duplicate the wiki website, mailman then transfer the openscenegraph.net domain.
I'm fumbling my way through this stuff though, once we got a rough plan together I'm happy to defer to others for detailed planning of the transfer to those who will be getting their hands dirty on the server.
Look like we now have enough expertise between us to consider the move quite soon. Nothing can happen till I go an open an account with a new hosting organisation...
We've had several good reports of dreamhosting now. Would they support things like our present wiki and the possibility of moving to tracks.
I guess we need to itemise exactly what facilities we need.
Robert.
Jan Ciger
Hash: SHA1
Robert Osfield wrote:
> There is one potential problem with this - current the mailing list goes
> under the openscenegraph.net domain. I think its possible to use cvs using
> openscenegraph.net right now as it just points to same server. So perhaps
> we should duplicate the wiki website, mailman then transfer the
> openscenegraph.net domain.
What I meant is that you set the new server up under a temporary
hostname/domain and then switch the DNS once everything is ready.
> We've had several good reports of dreamhosting now. Would they support
> things like our present wiki and the possibility of moving to tracks.
I know that Dreamhost is supporting PHP, Python, Subversion out of the
box. I do not think they would care whether you are running Trac or a
wiki there if you can fit it into your account and use the existing
infrastructure (databases, web server).
> I guess we need to itemise exactly what facilities we need.
>
> Robert.
Perhaps a good start would be to make an inventory of the old server?
What is needed for sure:
1) Apache, perhaps with PHP
2) Python (for Mailman at least)
3) MTA (Postfix or something similar, again for Mailman)
4) Wiki (whichever one, may need PHP)
5) CVS and SVN server (CVS for migration)
What may be required:
1) Database (probably MySQL, wiki, Trac and some other things may need it)
2) Software for browsing mail archives
3) Software for browsing the repository (Trac has this for SVN, othewise
standalone solutions exist)
Regards,
Jan
- --
Jan Ciger
GPG public key: http://www.keyserver.net/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org
iD8DBQFFWh+7n11XseNj94gRAs3EAJ9qXRUolWfWbtEBVf58ja0MG7p3mACcDqgy
BgPCEvzqBSuBABurBLbLTsI=
=PhmD
-----END PGP SIGNATURE-----
Jose L. Hidalgo
Dreamhost for osg? but what kind of plan? I have a "crazy domain
plan" which works pretty well, I have to say that dreamhost is formed
by really good people (the support is really good) and they are really
really geek people (in the good way) and its very funny.... but It
isn't too slow? I suppose it depends on the plan, but... in my opinion
is too slow for such a big project.
For example there is no Trac support, maybe it will in the future, is
possible to install it (I've done it) but as you need to run your our
version of python, sqlite, svnwrappers for python, etc... its SLOW...
Another issue is that, supposing you don't contract a dedicated server,
you can create mailing list but not access directly so there is no way
to import the old mailman's mails.
Jose L.
Robert Osfield
bert,
Dreamhost for osg?
Possibly.
but what kind of plan? I have a "crazy domain
plan" which works pretty well, I have to say that dreamhost is formed
by really good people (the support is really good) and they are really
really geek people (in the good way) and its very funny.... but It
isn't too slow? I suppose it depends on the plan, but... in my opinion
is too slow for such a big project.
You positive feedback is mostly encouraging. Could you explain what you mena by too slow. Do you mean the server or the max bandwidth?
For example there is no Trac support, maybe it will in the future, is
possible to install it (I've done it) but as you need to run your our
version of python, sqlite, svnwrappers for python, etc... its SLOW...
What is the cause of the speed problem? Simply that one server itself is hosting too many different sits?
Another issue is that, supposing you don't contract a dedicated server,
you can create mailing list but not access directly so there is no way
to import the old mailman's mails.
I wonder if we be possible for dreamhost engineers to do the import of the old mailman mails for us.
Mathieu
Just joined this list and would like say that I've read many good
reports on www.hosted-projects.com (german company), they are
commercial but not so expensive and offer also migration services.
Anyone tested their offer ?
--Mathieu
Chris Hanson
> > Dreamhost for osg?Possibly.
> > Another issue is that, supposing you don't contract a dedicated server,
> > you can create mailing list but not access directly so there is no way
> > to import the old mailman's mails.I wonder if we be possible for dreamhost engineers to do the import of the
> old mailman mails for us.
I think Dreamhost could be used for the website portion, but could
not be used for the mailman duties, or CVS/SVN. DH does offer dedicated
servers, but I don' think it's cost-effective. I would also worry a
little bit about having the web server and the mail/CVS-SVN server be
different machines, since sometimes they need to interact with each
other and this can be more difficult when they are separate. I don't
believe DH will import an existing mailman setup, and I'm not sure
you'd want them to try.
I run my main website on DH and I don't have any speed problems. I
think I have run PmWiki on it at one point too, but I don't now.
I'm not sure what would be the cause of your slow experience with DH.
Robert, how much $ does OSG (you) contribute to Don's HE.net server
right now? This gives us a target budget.
> Robert.
Gordon Tomlinson
DH does support mailman whats the issue( I'm a dunce when it comes to mail main )
Also it does support CVS/SVN ( issue ???)
Just wondering what the issues are, obviously OSG will go to what works for it,
G.
Email : gor...@gordon-tomlinson.com
YIM/AIM : Gordon3dBrit
MSN IM : Gordon...@3dscenegraph.com
Website : www.3dscenegraph.com
__________________________________________________________
"Self defence is not a function of learning tricks
but is a function of how quickly and intensely one
can arouse one's instinct for survival"
- Master Tambo Tetsura
Eric Sokolowsky
> I think that he is right - I have forgotten about the database because
> we are using sqlite and not something like MySQL. So, strictly speaking,
> you do need a database, but not a database server :) On the other hand,
> I have no clue how well sqlite will scale for many users :(
We use sqlite on the backend of a service we provide on our website at
work (http://svs.gsfc.nasa.gov) that receives about 30,000 hits per day
and it has performed very well. Surely sqlite can handle the load svn
would place on it. Plus, installing and administering sqlite is so very
easy. I'm sure it can handle the task.
Chris Hanson
wrote:
> Dream host would certainly work for Web, FTP, Forums and Wiki's
> DH does support mailman whats the issue( I'm a dunce when it comes to mail
> main )
I was concerned about importing the existing mailman data into their
mailman system. It's a shared mail server, so they won't give you
complete access to it, and yo'd need rather extensive access to import
that data.
> Also it does support CVS/SVN ( issue ???)
I didn't think that was the case, but I was mistaken. DH does offer
CVS/SVN.
Dreamhost also does offer good MySQL via a shared server.