Offering to maintain MediaElement module [#1936860]

Comment #1

kingfisher64 CreditAttribution: kingfisher64 commented 14 March 2013 at 17:45

Priority:

Normal

» Major

I was wondering the same. Over a year since the last commit that normally suggests an abandoned or minimally maintained project not under active development state. :)

Log in or register to post comments

Comment #2

iva2k CreditAttribution: iva2k commented 14 March 2013 at 20:16

Title:

Is MediaElement module maintained?

» Offering to maintain MediaElement module

I am willing to become a maintainer of MediaElement module. I submitted a number of patches that address outstanding issues to this module's issue queue.

(following [#251466] steps).

Log in or register to post comments

Comment #3

kingfisher64 CreditAttribution: kingfisher64 commented 15 March 2013 at 11:40

You could file a request for an abandoned project. To make sure this is the case first though perhaps it would be a good idea to contact mfer directly though drupal.org.

Log in or register to post comments

Comment #4

mfer CreditAttribution: mfer commented 16 March 2013 at 15:10

Assigned:

Unassigned

» mfer

@iva2k thanks for your interest here. This is a module I care about and always feel bad I have not had the time to support. Let me look over your patches and work, check with Dave Reid, and verify a couple other things. If everything looks good I'll give you access soon (it will take a few days because of the weekend and a couple other things).

Log in or register to post comments

Comment #5

Dave Reid

he/him

English

Nebraska USA

CreditAttribution: Dave Reid commented 20 March 2013 at 19:53

The fact that a bunch of issues are needs review doesn't indicate that a project is unmaintained, it just means that no one else in the community is also reviewing/RTBC-ing issues. Currently there is only one RTBC issue in the queue. I see aside from this issue you've been involved in three others? Maybe I'm wondering if you have any other goals for the module beside committing existing patches? Because sometimes all that takes is an issue like this for a maintainer that isn't quite so active to get them to review the queue and get stuff moving once again. Personally, for modules that I co-maintain, I don't feel comfortable committing things that aren't RTBC.

Log in or register to post comments

Comment #6

iva2k CreditAttribution: iva2k commented 21 March 2013 at 02:43

Thanks for the response.

It is always a maintainer's choice to wait for RTBC or not, but it would be nice to indicate this choice somehow. There is nothing posted by the maintainers in any of "needs review" issues which creates an impression of total abandonment. A question "I'll commit if someone from community RTBC's" is one way to signal the expectation. Sometimes fixes are so trivial that I as a maintainer just commit them in my projects to avoid any delays. For a project with ~5k installs you won't see many RTBC posts, so it is a judgement call.

>Maybe I'm wondering if you have any other goals for the module beside committing existing patches?
What these would be, can you clarify? The module has great potential and I improved it for my installation. Just trying to contribute back, but no movement on patches creates a sense that they won't get in and the module will die a slow unmaintained death. No agenda here.

Log in or register to post comments

Comment #7

deggertsen CreditAttribution: deggertsen commented 3 April 2013 at 22:48

I agree with iva2k. Even if there isn't anything RTBC, just the fact that there hasn't been a commit in over a year makes a project look like it has been abandoned. Of course I don't really have anything I can argue here as I am not much help on the development side of things, but what is the hurt in allowing another maintainer on board who simply wants to help and is willing to push through some issues that the community would like to see completed? I guess there is the potential of a project being sabotaged, but isn't that what version control is all about?

Just my 2 cents for what it's worth. Love this module in any case. Thanks!