Hello this thread is for the project maintainer.

Are you actually putting any effort into this project anymore? Because i would like to offer to take over the maintainance. I have rewritten checkout in bigger parts to work much more robust, and it is working in production for arround ~3 months now.

If i get now answer in 3 days i would like to requestion a maintainer overtake in the webmaster thread.

So if you are the maintainer of this project, please drop a short line in here and explain your goals with this project.

Thank you!

Comments

rapsli’s picture

rapsli commented

Interested in taking the module to the next step aswell. It would be a bummer to start a new module and just bring more confusion.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Title: Status request / offering help as maintainer » Offering help as maintainer
Version: 6.x-2.2 » 6.x-2.x-dev
Category: support » task
Priority: Critical » Normal

huh? This thread would be very embarrassing for me, if I'd be the maintainer.

What's the rush in here? Also, "rewritten in bigger parts"... -- where are your contributions then?

http://drupal.org/project/issues/search/checkout?participant=EugenMayer
http://drupal.org/project/issues/search/checkout?participant=rapsli

I count 2 issues each, from which one is this issue.

Please read http://drupal.org/node/363367 before creating such issues.

At least for now, I'd recommend to mark this issue won't fix. Co-maintainership can be re-considered at any time.

eugenmayer’s picture

eugenmayer commented
Title: Offering help as maintainer » Status request / Offering help as maintainer
Version: 6.x-2.x-dev » 6.x-2.2
Category: task » support
Priority: Normal » Critical

Sun could you please simply stop acting without any further investigation? I cant even see a reason to act here for you.

The current maintainer did not check in any code into this project at all (he had time since ~july?), so what shall we actually wait for? Motivate him?

Being the co-maintainers and waiting for him to dig out? Sorry, but i think we have someone with a lost interest and we just try to avoid a fork of this project. And actually some of the people have reasonable interest on this project - some dont.

And if you look for the contributions, then actually read the issues! Well read all those open issues with tons of patches to check for all the contributions which are not in the dev / head / whatever.

Thanks.

rapsli’s picture

rapsli commented

Oky. ... a month has passed. Nothing has happened. I don't want co-maintainership, but I would love to see this module moving on, and yes I totally agree with Eugen. The current version here doesn't work at all. The one Eugen has provided works almost like a charm (there is one bug we have found so far).

Does the current maintainer have an opinion? I think there was plenty of time for him...

smk-ka’s picture

smk-ka commented

@sun
Could you add Eugen to the list of maintainers? If so, please do it. While the code quality is a bit weak at times, it seems to be the fastest way to bring this project forward.

@Eugen
Please create a new branch before starting to commit.

Thanks.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Status: Active » Fixed

Done.

eugenmayer’s picture

eugenmayer commented

Hmm cant see iam the maintainer, cannot change the "CVS access". Would add some Co-Maintainer then

eugenmayer’s picture

eugenmayer commented
Status: Fixed » Needs review
sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Status: Needs review » Fixed

Yes, you have been added as co-maintainer. CVS access can only be edited by the primary project maintainer.

eugenmayer’s picture

eugenmayer commented
Status: Fixed » Needs review

Sorry, but i cant see the "maintainer" maintain anything at all? So i cant see a point beeing the Co-Maintainer actually.

Sure, if i just help out, iam the co mainainer. But actually iam not "helping out" in case of making addition. The way it looks like is, i will be the only one working on this project.
smk-ka or whoever is the maintainer currently, i would like to hear a statement on this.

Thank you

eugenmayer’s picture

eugenmayer commented

Anaother week gone without the author caring to much about this issue. The only thing needed is one or two sentences about how he will get involved-
The activtity in this thread gives a clue on how this could work out.

Iam sorry for that but i will fork checkout, we wasted time enaugh waiting for the authors answer, for ideas.

This issue can be closed (am i allowed?)

rapsli’s picture

rapsli commented

too bad... but I guess that's the way. I'm curious what the new name is going to be like ;) advanced checkout, content locking

khad’s picture

khad commented

Eugen,
please post the name of your new module here before closing this thread - I don't want to miss when it becomes available!

eugenmayer’s picture

eugenmayer commented

khad the new module can be find under http://drupal.org/project/content_lock

Before closing this issue please remove my rights to commit to module here. Thank you

smk-ka’s picture

smk-ka commented

@Eugen
Did you already try to contact Joel? As he's the only one who can ack the transfer of the module to someone else. Or, if unsuccessful, initiate a request to take over an abandoned module? There must be precise instructions somewhere, just don't know where right now...

dave reid’s picture

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

Why exactly did this require a fork if you were given CVS access????????

eugenmayer’s picture

eugenmayer commented

at both @15 @16 .. its simply a bit late reacting. I was taking my time for this but people did not had to much interest.

Dave if you want to know the reasons, PM me.

eugenmayer’s picture

eugenmayer commented

Well i summarized the case in #711110: Difference from Checkout?. So if someone is interested in seeing the reasons i had ( from my perspective ), you can read them up there. Otherwise this issue can be closed or whatever.

robby.smith’s picture

robby.smith commented

Is there anyone to continue the work for this module Checkout (Content Locking)? Or is this module being discontinued? =(

eugenmayer’s picture

eugenmayer commented

Robby i think this module has been discontinued for quiet some time now and it does not seem that this would change here. You can find the fork of this module which is continued quiet activly here:

http://drupal.org/project/content_lock

robby.smith’s picture

robby.smith commented

Thanks! I will definitely be checking out content_lock module

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Title: Status request / Offering help as maintainer » Offering to maintain Checkout (Content locking)
Version: 6.x-2.2 » 6.x-2.x-dev
Priority: Critical » Normal
Issue summary: View changes
Status: Needs review » Closed (outdated)

I am closing this issue, as EugenMayer has been added as co-maintainer.