On Tue, Jul 06, 2010 at 01:05:40PM -0700, Noah Kantrowitz wrote: > This is neither required nor encouraged. I like seeing crazy new ideas tried
You sure had me thinking you wanted me to shut up... > out. I think it should just be done somewhere outside trunk. Heck, Trac No doubt, again, I have said the same thing on several occasions. (the exact same arguments are equally valid against GenericTrac, if not more, though but nobody seems to appreciate this point.) > necessarily evil, but the onus of proof falls on you to demonstrate you have > a better way, not us to say you don't. I don't mean you should fork Trac as Ah yes but this is why I am spilling my guts, and offering time on *modelling* as it is the part where I can possibly contribute something the team may not already possess. I am in principle not interested in the approach taken in code at all, just that you offload to the database those parts it was designed to do, and that will, by definition, simplify your code, whatever it does. > in start a whole new project, just copy the repo in github (which is called > forking there) and start hacking away. If in a few weeks you think you have > a much more elegant codebase, show us. You don't need to convince us of your > design with words, you need to do it with code, and I am happy to be so > convinced. And in the context of what I am really proposing (again, the damn model), I have already put up what I think is the correct core for the "ticket system", as it should be stored in a relational model (in code form), as stated in the very first post. You must realize that the issues raised are not solved in any of the proposals, including mine, but notably also not including the current plan as I can gather from the wiki, with stated goals of multiproject, distribution and generalization (that I have a huge interest in seeing come to life). I am not proposing *any* work that you haven't *already* planned to do. It's just a question of what approach to take to get it done, and if there is anything I can do to help. And thus I'm not going to do it all for you in a couple of weeks to show that a jet fighter can cross the Atlantic faster than a dead horse. It is not the design I am selling you, it is the approach. Terje -- 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.
