>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). --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
