I like the idea of the Cheeshop and more the one of different TRACs, but on the three options given, hosting TRACs is not as easy, Cheeshop and google are free.hosting a TRAC isn't. dejavu doesn't seem an option if you need to wait for an invite code for every project.
I'd rather stick on Cheeshop and keep a listing on code.djangoproject.com also the idea of keeping all small chunks like templatetags,filters and so in a single project seems really reasonable.
my 0.02
Marc.
On 9/8/06,
Jeff Forcier <[EMAIL PROTECTED]> wrote:
>From exploring Google Code a short bit, I'm not positive it's the best
medium, at least if we want any decent discussion or Web-based
documentation. Yes, one could hold discussions via the Issues, but
that's pretty gimpy for any discussion that does not fit well as a
trouble ticket. And one could just have "local" documentation in as
files included with the source code, but that's also not ideal, IMO.
I guess in my mind a Djangoforge would be a collection of Trac
instances (see e.g. code.djangoproject.com), where each project has a
wiki for discussion and documentation, source code management, etc.
That would work best for a collection of full apps. It works less well
for smaller, more atomic items like templatetags, although I suppose
one would just collect those into a handful of other Tracs (i.e. one
for templatetags and filters, one for unofficial patches/modifications
to the core Django codebase, etc).
--
The probability of failure of a (computer) system is exponentially proportional to the physical distance between it and the one who could fix it. -- Martin F. Krafft
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---
