Issues that needs to be fixed before releasing 7.x-1.6

Here is a start: please update this list.

Original issue

It's great that 98k sites are using the D7 version of this module. It's really been an important part of the SEO strategy for a lot of organizations.

It's been a long time since the last release (2012-Jun-15) and really, modules with this type of development activity & usage really need to have a release at least once a year. There are still 48 open bugs in the D7 version, quite a few of those bugs are over a year old. This can really be discouraging for folks who are new to drupal.org.

I do think that there should be incentives to ensure that people who are contributing to it are recognized. There should be some motivation to go through the issue queue and see that reports that people have made are acknowledged, repeatable, fixable and eventually closed. This is a lot of work, but there should be some acknowledgement done for those who are tending the issue queue, but I don't think that's enough.

I've blogged about the use of Flattr & Gittip. The latter brought up some great discussions about initiatives like Top Shelf Modules and DrupalFund.us.

Adoption of any of those platforms seems to be pretty slow though. Gittip has the greatest acceptance on d.o because there is at least a form on each users Profile page to add it in, and yet, there has been marginal increase in the adoption or donation rates https://www.gittip.com/for/drupal/

I tried to highlight how Gittip could be incorporated into d.o's issue queue in order to provide incentives to individual contributors. From feedback there, I decided to look at how Corporate logos could be incorporated into the issue queues (even for anonymous users).

None of these solutions is without it's problems. Some of these solutions will work better to support some projects than others. I think there are probably hundreds of other ways to help shape participation in the Drupal community such that end users, developers, designers and Drupal shops are able to find easier ways to contribute back. But I think we need to get the conversation moving about how to see that important projects like this get the support that they need to see that they are properly resourced.

There's a place to discuss Drupal.org improvements in GDO but there isn't a lot of active participation there.

Ultimately, what kinds of functionality/UI changes would help make this module better maintained? For folks who are active contributors, what would help you? Each project may have it's own ideas about how to best motivate the community that uses it's code. It might be that folks are confident that there's no need to change anything, and perhaps they are right.

I would like to know when we can expect to see the next stable release of this module and think it is great when there is a meta issue queue to gather the issues that should go into that next release. I couldn't find this, but if it doesn't already exist it can be started here.

Comments

mgifford’s picture

Just wanted to add that this module is listed as seeking a co-maintainer. Info on becoming involved is available https://drupal.org/node/251466

frob’s picture

So is this project abandoned then?

miro_dietiker’s picture

Note that there is an issue about merging globalredirect into the redirect modules
#905914: Merge global redirect functions into Redirect module
This seems to be one of the next steps to happen in 7.x-2.x.

Also note that MD Systems pushed the Drupal 8 Redirect port and also is working on a branch to complete merging globalredirect into it.
https://github.com/md-systems/redirect/tree/globalredirectmerge
The Redirect module will try to cover all relevant aspects for proper 360 degree redirect handling with nice SEO behavior. Once completed, one module less.

For D7 though, i don't know about the current status.

BarisW’s picture

Title: ETA of Next Release - 7.x-1.6 » META: Release blockers for 7.x-1.6
Related issues: +#2810595: Tag a 7.x-1.6-beta1 release

I'm happy to release a 7.x-1.6 as soon as possible. Please have a look at the issue queue and list issues here that have to be fixed before we can release 7.x-1.6.

BarisW’s picture

Issue summary: View changes

I'd start by looking at this list: https://www.drupal.org/project/issues/globalredirect?status=14&categories=1. My feeling: we only fix bugs, we won't add new features anymore in 7.x-1.6.

BarisW’s picture

Issue summary: View changes
ajayg’s picture

The first 3 issues have been RTBC for quite a while. In fact there are 12 issues RTBC and not just 3. Why not get those committed to dev and release a beta 1.6 release? So it will get tested while we review the last one?

BarisW’s picture

Good point. I will commit all RTBC issues today and release a 1.6-beta.

BarisW’s picture

Committed 4 more patches and put the rest back on Needs work or Needs review for various reasons. All RBTC bugs have been committed now.

#2596939: Add README.txt
#1411704: Conflict with Domain Access as domain_url_outbound_alter() returns alias
#2385415: Use of undefined constant LOCALE_LANGUAGE_NEGOTIATION_URL_PREFIX
#2013785: Redirect loop occurs when visiting a directory with deslash enabled.

Doing some last tests and will then tag/release the 1.6-beta.

BarisW’s picture

Status: Active » Fixed

Ladies and gentleman, we have a release: https://www.drupal.org/project/globalredirect/releases/7.x-1.6-beta1
Please test. If no new bugs are reported in the next few weeks, I'll add a 7.x-1.6 release.

ajayg’s picture

Following important patch went after the previous beta. So shouldn't this be included in the release notes?

https://www.drupal.org/node/1680978

BarisW’s picture

Added that one too. Thanks @ajayg!

Status: Fixed » Closed (fixed)

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

Chris Matthews’s picture

@BarisW - It does not look like any new bugs have been reported since the 7.x-1.6-beta1 release. Would it be possible to add a 7.x-1.6 release?

BarisW’s picture

fgjohnson@lojoh.ca’s picture

Hi,
I realize that this may be too late but ...

The patch found here is really great.
https://www.drupal.org/project/globalredirect/issues/1438584#comment-121...

Chris Matthews’s picture

fgjohnson@lojoh.ca - I opened Issue #3018118: Plan Global Redirect 7.x-1.7 release so maybe the patch from Issue #1438584: Disable Global Redirect on certain paths that currently needs work can get in the next release