Modify

Opened 7 years ago

Closed 7 years ago

#7572 closed task (fixed)

RFC of primary maintainer

Reported by: Ryan J Ollos Owned by: Ryan J Ollos
Priority: normal Component: WikiTicketCalendarMacro
Severity: normal Keywords: maintainership
Cc: Steffen Hoffmann, Michael Renzmann Trac Release: 0.11

Description

I initially adopted both WikiCalendarMacro and WikiTicketCalendarMacro with the intention of integrating the many versions attached to project's wiki page to make one good version. To my pleasant surprise, hasienda completed this work before I got to it, leaving me time to work on other Trac things.

Steffen: should we transfer primary maintainership of this plugin to you so that all tickets opened against the plugin get assigned directly to you? This seems to make sense, because you have done all the work on the macro and I just CC you on any tickets so that you can work your magic on them. I'm okay with either maintainership situation, however.

Attachments (0)

Change History (6)

comment:1 Changed 7 years ago by Steffen Hoffmann

Keywords: maintainership added
Summary: Should we change the primary maintainer?RFC of primary maintainer

I've had zero problems working as co-maintainer here with you, but you already pointed out, that an official swap of positions could still improve communication. So I appreciate your offer and agree to take maintainership from you. I do so in the hope, that this will not change the intensity of discussion on improvements and other valuable aspects of our collaboration.

You may go ahead and might even do so with WikiCalendarMacro as well, since we're already working towards a merge of both into WikiTicketCalendarMacro code base (#7564), so soon I may take over de-facto control over WikiCalendarMacro anyway.

comment:2 in reply to:  1 Changed 7 years ago by Ryan J Ollos

Replying to hasienda:

I've had zero problems working as co-maintainer here with you, but you already pointed out, that an official swap of positions could still improve communication. So I appreciate your offer and agree to take maintainership from you. I do so in the hope, that this will not change the intensity of discussion on improvements and other valuable aspects of our collaboration.

Yes, definitely, I intend to remain involved and hope we can continue as things have been going. Just thinking that it makes more sense for you to be the primary on this one, since you are doing all the real work ;)

It makes sense to do the same with the WikiCalendarMacro as well.

I'll add another note to this ticket and CC otaku42, then we can proceed as outlined in AdoptingHacks#AfterAdoptingaHack.

comment:3 Changed 7 years ago by Ryan J Ollos

Cc: Michael Renzmann added
Status: newassigned

@Michael: I'm current maintainer of WikiCalendarMacro and WikiTicketCalendarMacro, and we'd like to transfer primary maintainership to hasienda. I've changed the component owner for both macros. hasienda currently has write access to WikiTicketCalendarMacro, but needs to be given write access to WikiCalendarMacro. Is anything else required to transfer maintainership beyond that?

comment:4 in reply to:  3 ; Changed 7 years ago by Michael Renzmann

Replying to rjollos:

hasienda [...] needs to be given write access to WikiCalendarMacro.

Done.

Is anything else required to transfer maintainership beyond that?

No, not from the admin side. However, there are some things that should be checked by the new maintainer, see here.

comment:5 Changed 7 years ago by Ryan J Ollos

Status: assignednew

comment:6 in reply to:  4 Changed 7 years ago by Ryan J Ollos

Resolution: fixed
Status: newclosed

Replying to otaku42:

No, not from the admin side. However, there are some things that should be checked by the new maintainer, see here.

Thanks, those steps are complete.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain Ryan J Ollos.
The resolution will be deleted.

Add Comment


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

 
Note: See TracTickets for help on using tickets.