Modify

#10633 closed task (wontfix)

Plans for further development?

Reported by: rjollos Owned by: leihog
Priority: normal Component: TicketRelationsPlugin
Severity: normal Keywords: adoption-request
Cc: gmartin Trac Release:

Description

Hi, I'm the current maintainer of MasterTicketsPlugin, and I have grand plans for improving it :)

I 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.

I 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.

So, 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.

Regards,

  • Ryan

Attachments (0)

Change History (3)

comment:1 Changed 22 months ago by rjollos

  • Keywords adoption-request added

comment:2 Changed 22 months ago by leihog

Hi Ryan,

I don't have any plans for my plugin and you are right in your guess that it was just a stripped version of MasterTickets. Since I'm running trac on a virtual machine with limited resources I wanted all plugins to be as bare bone as possible.

I'm not willing to give up ownership of the plugin but I'm not a stranger to collaboration. Personally I have no use for the extra features you are planing to add but I'm not against adding them to TicketRelations if it can be done in a clean and modular way.

It's been awhile since I last edited the code but if I recall correctly I removed some dependencies and made the plugin work without it creating it's own table. Although the offered functionality is basically the same (minus the overview/graph thing), I might have changed the code quite a bit so I suggest you start by forking my plugin on Github and then we take it from there.

Leif

comment:3 Changed 22 months ago by rjollos

  • Resolution set to wontfix
  • Status changed from new to closed

Hi Leif, Thanks for getting back to me. As I've already made significant improvements to the MasterTicketsPlugin, it would just be a lot of additional effort for me to fork your plugin and try to incorporate my existing into your plugin, which is now behind MasterTicketsPlugin. Since I was primarily interested in the name anyway, I'll just choose something different but similar when I rename MasterTicketsPlugin, such as TracTicketRelationsPlugin.

Thank you for your time,

  • Ryan

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.