I'd like to be made an official co-maintainer of AmazonS3. Considering the work I've done on my re-write of AmazonS3, I'm clearly qualified. I'll be happy to work on clearing up the issue queue, fixing actual bugs, and implementing requested features.

Comments

fugazi’s picture

fugazi commented

I would be happy if this module would live farther and faster. I'm not a programmer and rely on you. Therefore, it can only be beneficial from a co maintainer of the experience has added to take. coredumperror I thank you for your commitment and would be glad if the implementation is done quickly.

Sorry for my bad english

justafish’s picture

justafish
she/her
Primary language English
Location London, UK
commented
Status: Active » Closed (won't fix)

Hi,

Thanks for your request, I'm happy with the current co-maintainers of the project however.

coredumperror’s picture

coredumperror commented
Status: Closed (won't fix) » Active

Might I ask the real reason that you're making this decision? It's obviously not that you're happy with the co-maintainers, considering that the only one on the project last committed code nearly a year ago. There are also 66 open issues, which makes it clear that there isn't currently enough man hours available to keep this project well-maintained.

I will be able to spend work hours on this project, since my company relies heavily on this module for our website. As you can see on the Date iCal issue queue, I'm also very attentive to new issues, and do my best to resolve them quickly.

As a co-maintainer, I will help this project mature into a stronger, more stable, and more feature-rich module.

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

I would not say the following statement is true:

There are also 66 open issues, which makes it clear that there isn't currently enough man hours available to keep this project well-maintained.

And only 32 of them are bug reports. Only 20 of them are issues that are in a needs work state or higher. And only two issues that are RTBC. That sounds pretty healthy contrib project by my metrics, but maybe not yours.

fugazi’s picture

fugazi commented

I'm speechless, I do not understand, can not all work together on a project.

If someone wants to help and be aware offers, why not to accept with. Is there a policy with them I do not know.

I appreciate the volunteers working on drupal and the modules, and I have already spent many beers. But now I do not understand why this is being discussed whether that is good or not good.

It is quite obvious that someone has the time to make his work available. Why not work together.

Sorry my english is bad and I hope that my writing does not arrive wrong.

coredumperror’s picture

coredumperror commented

Well, since you're not interested in collaborating with me, and next to none of your code is left over in my version, I'll just go ahead and post my own contrib module. I'm calling it S3 File System, and it's currently in sandbox status here.

justafish’s picture

justafish
she/her
Primary language English
Location London, UK
commented
Status: Active » Fixed

@coredumperror declining to assign you as a maintainer does not mean someone isn't interested in collaborating with you, that's not how issue queues work. If you want to discuss this further, feel free to ping me in IRC.

Also, thank you for the shout out on your module's description page, however I'm a she not a he.

Good luck with your new module!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.