Chris Forsythe wrote: > Ilias Lazaridis wrote: > > >As the trac team has enouth work to do, I would like to work further on > >this, taking existent trac-team requirements and tickets in account. > > > > > Since you've made the point that the trac team has enough work to do, > wouldn't it be better to attach your patches to existing tickets in the > edgewall trac or submit new tickets with patches attached, since that's > how the trac team seems to work?
please review the thread. I've already tried this way, but I cannot wait days - especially when doing commercial work. > The way you're doing this seems like a lot of overhead to me. it seems just so. Just review the provided links, especially: REQUEST - Branch for Query Module http://groups.google.com/group/trac-dev/browse_frm/thread/3f749fb8ebcad0cd/# and take in account that not only the trac-team has limited time and resources. using a decentral branch seems the simplest way of 'doing fulltime development without repository access'. - And finally, as a summary: I suggest to contribute fulltime development work to the trac project, this time whilst using a decentral branch. The team can review the larger scale work (from within the publicly available repository), and applying the changes (or whole subsystems) to the trunk. . --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" 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/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
