On 6/11/06, Max Ischenko <[EMAIL PROTECTED]> wrote: > I agree with Jorge. Full-blown project environment for a 50-200 lines of > widget code is kind of overkill. We may want to copy wordpress/track-hacks > model, when there is a single common environment with sliced for multiple > projects.
I think that's an oversimplification. A useful widget that is only a small amount of code likely includes a fair bit of JavaScript (and possibly CSS and image files). They'll have their own release timings and whatnot. So, they would need their own trunk/branches/tags (though that can certainly exist within a single repository that has appropriate permissions set.) I *do* agree that they don't necessarily need their own complete Trac... but, if there's a lot of widgets, you could end up with a Trac that has 100 components in it. Maybe what's needed is pretty simple: a home in an svn repository, and a wiki home page with contact info for the author. If the widget's big enough to need a Trac, then it would make sense to get one. Kevin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-trunk -~----------~----~----~----~------~----~------~--~---
