On Feb 4, 12:01 am, Benjamin Lau <[email protected]> wrote: > My question would be is: how would this be integrated with trac? > Using snowy as is (or making use of Tomboy Online) would pretty much > create a separate repository for all of your notes... From my > ... > will probably happen... until the person responsible gets busy). An > extension for Tomboy to interact with Trac directly might be a better > option (plugin to expose some interfaces and a plugin for Tomboy to > talk to it).
This. :) My goal was not to direct him away from Trac for the solution, but get him thinking about ways to integrate these two backends. Maybe then I can win too! Writing a ticket <-> Snowy sync engine has been on my TODO list for a bit now. It'd probably make sense to have a new Note resource just as well, although this choice (who has time for both, raise hand! ok, nobody.) probably needs some additional thought. It might perhaps be possible to re-use Snowy's backend code with little modification. > My goal with trac has always been to try and get all of my company's > relevant data either into trac (pages, tickets, blog posts, etc) or +1 > this hasn't been 100% successful. Many of the people in my company > don't like trac's UI and started putting stuff all over the place > which seriously reduced trac's utility (we have data in shares, wedav > repositories, google docs and google sites). And this has created a > host of problems. I'm not sure if the problem is due to trac actually > being difficult to use or us not being willing to commit resources for > improving the user experience. This was enough to spark me to finally file http://trac.edgewall.org/ticket/10012, also been on the TODO list for too long. -- 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.
