Rob wrote:
> Thank you, yes, that's helpful.
>
> Are the hacks you made easy/obvious or available somewhere? I'm a
> developer but really don't have much time to cobble together a system.
>
> How much work is it to implement a new project under your #1 option?
pretty easy. Just create a new envi
On Nov 4, 2:17 pm, Rob <[EMAIL PROTECTED]> wrote:
> I have been using assembla for code and project management, and since
> they've dumped their free model and I do work for non profits, that's
> a dead end. I'm investigating other options.
>
> It seems that Trac is a reasonable alternative. I h
Hi
My apologies. I read this incorrectly. I was under the impression that
both options 1 and 2 were implemented, with option 2 'overseeing' the other
projects created.
Thanks,
Cher.
On Wed, Nov 5, 2008 at 9:28 AM, Cher B <[EMAIL PROTECTED]> wrote:
> Hi
>
> We too are interested in multiple pr
Thank you, yes, that's helpful.
Are the hacks you made easy/obvious or available somewhere? I'm a
developer but really don't have much time to cobble together a system.
How much work is it to implement a new project under your #1 option?
Like you, I can see the value in both approaches dependi
Hi
We too are interested in multiple projects, so Iain can you please clarify
something for me
Iian Wrote:
--2. One trac environment, add a custom field. ie. only one
--/var/lib/trac/proj but I've edited [ticket-custom] to add a select box
--for listing the different projects. I've also edi
Hi!
Rob wrote:
> Do I need a separate Trac
> installation for each project?
we use Trac for multiple projects in two different ways, for two
different reasons. There are of course other ways of doing it, this is
just what we do:
1. Multiple trac environments. ie. /var/lib/trac/proj1
/var/
