Hi Phillip, hi Hildo,
even though I applied for the ownership alone, there are some people who
will help me maintaining it. I work at DZ Bank in Germany and we're a team
of 3 (maybe 4) developers with ~20% perl development as part of our regular
job. We do application integration and the MQSeries module has been used at
the core of our runtime environment for 12 years. Currently we're revamping
the complete EAI platform. IIB will take over the role of the perl runtime
component, but for the toolset we decided to migrate all the shell scripts
as well as some old in-house developed C applications onto our perl stack.
So the MQSeries module will not only keep playing an important role, we
will even widen its use. We just started to work with the command interface
and soon it will be part of our deployment toolchain.
Last, but not least, we have Max Maischein (corion) at DZ Bank. He's not
only an experienced perl developer, but also a very active cpan
contributor. He's been very helpful already for all questions regarding
cpan releases and the perl community.
Alright... this was my "pitch". ;-)
You might wonder why the DZ Bank team hasn't officially asked for module
ownership. Well, my managers are very conservative when it comes to open
source software ("we're not a software company", "we don't need to
contribute to open source, be thankful that we allow to use it", "we need
an analysis from legal department for the involved risks ...oh, and by the
way: there's no-one in the legal department who has a clue about software
licensing", "we don't care that you studied law as a minor for 6 terms
yourself, we only care for approval by our legal department"), sometimes I
feel stuck in the '90s.
Cheers,
Thorsten
P.S.: Actually I wonder how you succeeded in convincing your managers at
Morgan Stanley of the open source commitment. It was more than 15 years
ago, right?! Most of them must have had the same reservations against open
source as my managers.
2017-03-26 17:37 GMT+02:00 Hildo Biersma <hildo.bier...@gmail.com>:
> I don't know the current situation at Morgan Stanley (I have been at
> Google since 2009), but I concur with Phil's assessment, and would be
> happy to sign off on a maintainer change.
>
> The module contains a lot of effort by Phil and me, and it'd be a
> terrible waste to let it rot.
>
> Hildo
>
> On Sun, Mar 26, 2017 at 11:00 AM, Phillip Moore
> <w.phillip.mo...@gmail.com> wrote:
> > <sigh>
> >
> > This is very sad, and as the original author of the code, I would like to
> > apologize on behalf of those who have inherited in from me. Except
> that I
> > have *NO* idea who that is. I wrote and owned this code from 1998 to
> 2002.
> > Hildo also left the project and Morgan Stanley a few years later, and the
> > engineering team that manages the MQSeries infrastructure Hildo and I
> > designed and deployed are the ones responsible for the CPAN distro now.
> > That team *was* pretty good, but they entire team quit or changed
> projects
> > in 2012, which explains the final release date.
> >
> > Now, I am going to be characteristically blunt here: all the good
> engineers
> > are gone from that team, and I don't think they are giving ANY priority
> to
> > maintaining the CPAN distribution, because none of them have any clue
> how.
> > If you have the skills and the interest in taking this over, I would be
> more
> > than happy to help broker getting the ownership transferred.
> >
> > If push comes to shove, I am pretty sure that if Hildo and I endorsed it,
> > the CPAN maintainers would make the change. I have followed the DBIC
> > ownership debacle from a distance, and I think that was handled extremely
> > professionally by David Golden, for example. Now, I honestly think that
> > the team in question is so deep underwater with everything we created
> (that
> > infrastructure and the management application we built are perhaps the
> most
> > successful work of my career, and they still use it), that they will most
> > likely be thrilled to give this up.
> >
> > Anyway, if it is not obvious, please keep this discussion entirely
> > confidential for now. I am putting the priorities of the open source
> > community before those of my employers here, and so taking a bit of
> > political risk by doing so. I am, for lack of clearly better judgment,
> > working at MS again right now, so I would appreciate you NOT sharing this
> > discussion publicly until it is appropriate to do so. This is also why
> I
> > am in the perfect spot to broker the ownership change.
> >
> > I am going to proactively reach out to Golden, and inquire about the
> process
> > here, as I don't think you will ever see another release if we don't, so
> I
> > will bring him into this discussion as well. Please give me about a
> week
> > to get the internal feedback on this.
> >
> >
> > On Sun, Mar 26, 2017 at 10:17 AM, Neil Bowers <neil.bow...@cogendo.com>
> > wrote:
> >>
> >> Hi Thorsten,
> >>
> >> I'd like to adopt the MQSeries module.
> >>
> >> A year ago I've uploaded a patch (bug id 113894), but nothing happened.
> >> Then I've sent a mail to mqser...@cpan.org, but received a bounce mail
> (user
> >> unknown) from Morgan Stanley's mail server. Now I have found another
> issue
> >> and sent a mail to this address again, but still the same bounce mail.
> The
> >> module has open bug reports that are 8 years old. And the last release
> was
> >> built in 2012.
> >>
> >> Now I have requested a PAUSE account and forked the read-only repo
> mirror
> >> on github (gitpan/MQSeries) into my own account
> (thorstenhirsch/MQSeries) in
> >> order to continue development.
> >>
> >> What are the next steps?
> >>
> >>
> >> The README for the distribution lists Hildo Biersma and W Phillip Moore,
> >> so they may know how you can get in touch with the current maintainer,
> or
> >> get co-maint permission. They’ve both got PAUSE accounts, so I’ve copied
> >> them on this email.
> >>
> >> Hildo & Phillip, do you know the status of this module, and who is the
> >> right person to decide if Thorsten can have co-maint?
> >>
> >> Cheers,
> >> Neil
> >>
> >
>
