nonsie, Thanks for this awesome contribution! Since I read in another issue that you have no time for that no more, I am willing to maintain it. Many users are waiting for a D7 release. I already brought up link module successfully to get ready for D7 release last weeks, awaited by 10+ users, and I am willing to do the same here since I think this would be an awesome contribution to the Drupal community having i18n and Domain Access working fully together finally (this module is missing for language domains).

Let me know what you think of it, if you still read this. We also may should merge it with Domain Internationalization.

nonsie++

best regards from Berlin.
Digidog

Comments

mac_weber’s picture

Project: Domain Locale » Drupal.org site moderators
Version: 6.x-1.x-dev »
Component: Miscellaneous » Project ownership

This issue was created more than 1 year ago and the port to D7 is still only on #1124726: Domain Locale: D7 port also for more than 1 year.

I am offering to be a Maintainer of Domain Locale and push the changes I've made. In addition, I've sent an e-mail to nonsie using the contact page, but I had no reply until now.

I have made many improvements to the code on the issue I listed, including security and coding standards. Moreover, I also started working on exporting this module as a Feature.

I am moving this issue to to webmasters, as it is clear nonsie did a GREAT job in this module, but she does not have time to maintain it now.

link to the project: Domain Locale

sreynen’s picture

Status: Active » Fixed

I changed the project owner to Mac_Weber.

mac_weber’s picture

Thank you. I will push my changes on the next days =)

nonsie’s picture

Just to be clear I have no recollection ever receiving an email from Mac_Weber about maintaining Domain Locale. I received one from Digidog but it didn't go anywhere.
Thanks for letting me know after the fact.

mac_weber’s picture

nonsie, I sent the e-mail on Thu, Dec 6, 2012 at 10:28 AM. I sent it via d.o contact form and I have a copy of it.

Just restating that this issue was opened on November 1, 2011 at 8:06am. More than 1 year ago, and your last commit to the project was also more than 1 year ago, and most of the code I pushed for the D7 port was waiting on the issue queue for the same time. So, you cannot complain you got to know after the fact.

You are still on the maintainers list and you can help a lot improving this module, if you have time for it.

sreynen’s picture

For reference, the Drupal community policy on abandoned projects is here: http://drupal.org/node/251466

If anyone thinks that policy wasn't followed, let's talk about it here. If someone disagrees with the policy itself, on the other hand, that's probably better discussed in a separate issue, since it has wider effects than this one case.

nonsie’s picture

So essentially it comes down to this. You say you sent me an email. You did not post anything in the issue queue about getting commit access.
In fact this is the first post in Domain Locale issue queue you posted. Go figure.

sreynen’s picture

This issue was in the project queue from November 1, 2011 until December 14, 2012, before it was moved to the webmasters queue.

nonsie’s picture

According to the policy - "File an issue in that project's queue under the "support request" category stating your request to take over maintainership. ".
Mac_Weber did not post anything along those lines. I have not received any messages via #drupal or #drupal-support.

To summarize - I have no issues with giving commit access to people who have the time and interest to contribute code. However what I do not appreciate is logging in one day and discovering this thread. Since it was moved out of Domain Locale issue queue I did not receive any notifications about the maintainer change until that moment. I might still have the ability to commit code to the project but I have no access to the project page itself. So from my perspective - what am I supposed to think?

sreynen’s picture

nonsie, I don't think it's true that there was never an issue in the project queue. Comment #1 on this issue shows it was moved from the project queue, and the dates show it was there for over a year. If you think that's inaccurate, please explain why.

But if that's accurate, then the policy was followed. If the issue was in the queue for over a year and you just didn't see it, that's exactly how the current policy is designed to work. The current definition of an "abandoned project" is effectively any project that the maintainers don't look at for 2 weeks. If you disagree with that policy, again, I encourage you to open a separate issue so more people will see your disagreement. The few people following this issue are in no position to change the community policy.

sreynen’s picture

Beyond the policy and process involved, what steps should we take going forward here? nonsie, do you want more access? Do you want Mac_Weber to have less access? If so, what specifically?

nonsie’s picture

Comment #1 was posted by a user who had not made any previous posts in the project. This thread was posted by another user who indeed expressed interest in contributing but did not follow through.

So if this is what this policy indeed states - if you do not close a request that does not result in granting access to a project and any user posting on the issue is therefore automatically granted maintainership of said module then please remove me from this project altogether. I can no longer maintain this project as it stands.

sreynen’s picture

I've never interpreted the policy to mean that the same person has to do every step, but I can see how it could be read like that, and I'm not at all interested in setting policy beyond what the community has agreed to. It would be great to clarify the policy with a wider community discussion, and I'll be happy to start that discussion if no one else does first.

Meanwhile, what about #11? What specifically do you want to see happen now?

mac_weber’s picture

@nonsie

  • this project had a functional port to D7 waiting on the issue queue for more than 1 year.
  • All issues had no reply for more than 1 year
  • this issue offering to help maintaining the project was opened more than 1 year ago and it was still open when I moved it.
  • Moreover, the project was tagged as Maintenance fixes only, yet no fixes were commit in this time.
  • [edit] I had sent an e-mail to nonsie asking to help on maintenance and I got no reply. (I have a copy of the e-mail)
    [edit] There is no requirement on the policy to have posted before on the issue queue to move an issue to webmasters.
    [edit] I had code ready to push when I moved the issue to webmastes.
    [edit] before nonsie complaints I already had released the D7 port and some fixes. This demonstrates I am really interested on maintaining the project.

All the policies about abandoned projects were followed.

Then I really don't understand why you don't want to allow other people to maintain and update the project. I am not stealing your code, you are the original author! However, it is a open community using GPL2, and many people was waiting for this D7 port and other improvements. You have to understand that 1 year with no updates and no replies to the issue queue is a long time and should be considered an unsupported (abandoned) project.

If you are feeling interested in contributing and maintaining the project you are still on the maintainers list. Again, I'm not trying to steal the code or get credit for your work.

Status: Fixed » Closed (fixed)

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

Anonymous’s picture

Issue summary: View changes

comment

Project: Drupal.org site moderators » Drupal.org project ownership
Component: Project ownership » Ownership transfer