Hi there,

Just wondering why some projects like http://drupal.org/project/tagadelic seem to think they're special and have all their code and, more annoyingly, issue queue hosted on github instead of drupal.org. Arrogant comments like this https://github.com/berkes/tagadelic/issues/25 from the module maintainers don't really help either..

As a maintainer of several d.o. projects and having put every effort into adhering to Drupal policies, I find this really unacceptable.. IMO the project guidelines could have a clause in them to prevent such things from happening, but well, depends on what you think about it.

Cheers,
Martin

Comments

silverwing’s picture

silverwing CreditAttribution: silverwing commented

Just saw this issue and I have to say I also find it unacceptable. Sending users to another site for basic support shouldn't happen.

Although I believe this is mostly an isolated issue (are there any other projects that do this?) I really don't want to see support outsourced.

mikey_p’s picture

mikey_p CreditAttribution: mikey_p commented

Why not allow offsite issues, is there any benefit to forcing issues on d.o? If i was that user I would just forget drupal.org entirely and move all my code and workflow to github and abandon the drupal.org project page.

arski’s picture

arski CreditAttribution: arski commented

There is a reason why drupal.org is offering module maintainers space to host their modules under certain conditions - it guarantees drupal users that the 3rd party modules adhere to a certain level of standards, plus it also means that all the issues are easily connectable and that one does not need multiple accounts to ask for support, download releases etc..

By your suggestion, everyone could start hosting their drupal modules on their private sites and then one would need 10000000 accounts to submit tickets etc.. and in general it would make things just completely unorganized.

So I think there are really enough reasons to keep modules on drupal.org. If someone doesn't want to host his module here - fine, but then don't make use of d.o's module catalogue.

mikey_p’s picture

mikey_p CreditAttribution: mikey_p commented

When the git migration was in progress one of the things that lots of people were excited about was that we'd see lots of folks moving back to Drupal.org after moving their projects to github, and in general we'd be a much more open and supporting ecosystem since *anyone* could start a project (sandbox) without having to go through any approval process, etc.

Since then, all I've seen is community policy to the opposite effect. All we are trying to do seems to be to lock the community down more and impose a certain will on how projects are maintained and managed. In the case of the tagadelic module, there are still downloadable releases on d.o built from the code hosted here.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
CreditAttribution: greggles commented
Title: Add drupal.org-hosted project issue queues to project requirements » [Policy] Add drupal.org-hosted project issue queues to project requirements

I think this is unfortunate that he prefers to work on github, but I don't see any problem as long as the code is periodically synched back. The response on https://github.com/berkes/tagadelic/issues/25 actually doesn't seem particularly arrogant to me.

There are other projects that also have issues disabled, such as the recently created ginkgo http://drupal.org/project/ginkgo

So, from my perspective this issue is a "works as designed."

arski’s picture

arski CreditAttribution: arski commented

OK, so basically you're happy with developers hosting their modules anywhere - might as well move my 4 projects out to 4 different repositories - have fun creating more and more useless accounts on different sites, dear users. (I am exaggerating on purpose obviously, but imo this sends out the wrong message.)

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
CreditAttribution: greggles commented

I'm not happy but I also think we have to have limits about the kinds of things we demand from module maintainers. It is very frustrating to me to see this, but that doesn't mean I want to require issue queues to be enabled.

It does mean that when I'm making a choice of which module to use I will choose a different module (or write a new one and contribute that) if the maintainer is doing something I don't agree with.

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented

I understand that the module maintainer prefers github and can sympathise with that preference. However, when the only code available on d.o appears to be broken, and the code maintainer makes statements such as "I care for developers, not users. Users give me little in return (other then high-usage rates and self-esteem)." then this is only going to discourage the use of Tagadelic and the many other modules that depend on it.

A good developer wants to hand their clients a site that doesn't need the developer's involvement every time something needs to be updated. Sadly, a project moving code away to github and leaving broken 7.x dev versions on d.o. doesn't do anything to help achieve that aim.

lizzjoy’s picture

lizzjoy
she/her
Primary language English
Location Ann Arbor
CreditAttribution: lizzjoy at Drupal Association commented
Component: Project problem » Broken link
Issue summary: View changes
Status: Active » Closed (won't fix)

Thanks for posting this issue @arski and for everyone giving feedback. It isn't possible at this time to stop people from moving to GitHub. What we can do is continue working on improving the experience on Drupal.org. Here are the priorities right now: https://www.drupal.org/roadmap. If you feel your issue has been closed in error, please do comment on the issue and let us know. If we know something is critical, we may reconsider the closure of a feature request or bug report.
Thank you for your understanding while we work to clean up the Drupal.org queues.

lizzjoy’s picture

lizzjoy
she/her
Primary language English
Location Ann Arbor
CreditAttribution: lizzjoy at Drupal Association commented
Component: Broken link » Project/Git problem