id	summary	reporter	owner	description	type	status	priority	component	severity	resolution	keywords	cc	release
10633	Plans for further development?	rjollos	leihog	Hi, I'm the current maintainer of MasterTicketsPlugin, and I have grand plans for improving it :)\r\n\r\nI wanted to ask if you will continue to develop the TicketRelationsPlugin, and if there is some way we could combine our efforts. If TicketRelationsPlugin is just a stripped down version of MasterTicketsPlugin, then maybe we can make MasterTicketsPlugin more componetized so that it can satisfy your needs without requiring this fork. If you've found and fixed issues that originally existed in MasterTicketsPlugin, I'd really like to pull those back to MasterTicketsPlugin.\r\n\r\nI plan to add parent/child relations to MasterTicketsPlugin, so that it is not necessary to install both MasterTicketsPlugin and SubticketsPlugin or ChildTicketsPlugin. After the parent/child relations are added, then it won't make sense to call it MasterTicketsPlugin anymore. The perfect name for it would be TicketRelationsPlugin, which you now own on trac-hacks, and I'd really like to be able to use in the future.\r\n\r\nSo, please consider this a request for your feedback that also follows the rules of AdoptingHacks, meaning if I don't hear back in 2 weeks I can take over TicketRelationsPlugin maintainership. Of course, I plan to wait more than 2 weeks to hear back, and hope to hear back as discussion first is the best way to move forward.\r\n\r\nRegards,\r\n\r\n- Ryan	task	closed	normal	TicketRelationsPlugin	normal	wontfix	adoption-request	gmartin