On 21 Jun 2006, at 22:09, Ralph Douglass wrote: > > The company I'm working for wants to start providing Typo as a > service, > so I have resources to put towards fixing bugs and applying the > patches > submitted on trac. I would love to commit our fixes to trunk. How > would you propose I go about demonstrating b and c?
Just submit your patches as tickets in Trac Ralph. If they're fine and include tests so all the maintainers have to do is check them in ... well they'll get tired of it and think about giving you commit access. But Anybody can provide patches for Typo. Look in Trac at the '[PATCH]' tickets. You don't need commit access for that. People need to remember that commit access is for the whole community. I might hate the AJAX for sidebars in the admin panel and write a patch that rips that out. I would then just provide it as a ticket on trac and not ask for commit access for it because some people like the AJAX for the sidebars. Mind you if I was refactoring the core code to make it sleeker and leaner then the whole community would benefit from that and that would be included in trunk. The only thing I'd be wary about is your company may want to take Typo in a direction that the community doesn't want to go in. Not saying they would of course - just raising the point. Gary _______________________________________________ Typo-list mailing list [email protected] http://rubyforge.org/mailman/listinfo/typo-list
