If you would like to take over this module, please make your request in a follow up post.

Thanks, Paul

Comments

Anonymous’s picture

Title: New maintainer needed. » Co-maintainer needed.

If you would like help out as a Co-maintainer of this module, please make your request in a follow up post.

seanr’s picture

I'd like to help, but I don't have enough spare time to be the only maintainer.

ksenzee’s picture

I actually have commit access to this module, and didn't realize it was in need of attention. I'll get on the stick. Paul, do you want to stay on as primary maintainer, or do you want me to just wade in?

Anonymous’s picture

Thanks for the reply Katherine

I'll stay on as maintainer at least until someone gives me
some good reasons to hand it over to them.

If you could help out with the issue queue that would be brilliant.

It would be great if we could reach a point where we could agree
that the flickr module is implemented and then work on a generic
picture service module ..
http://drupal.org/project/ps_wapi

It would be great to here you thoughts.

Best Paul

BarisW’s picture

Hi Paul,

if you give me access I can help with co-maintaining the module.
The last commit is 44 weeks ago...

My issue #778628: Migration to Drupal 7 is almost finished!

Anonymous’s picture

Assigned: Unassigned »

@CVS contributors

I shall add BarisW to the list of CVS commiters at my discretion If there are no objections given here by the end of the month of May

Respectfully,
Paul Booker
Appcoast

Anonymous’s picture

Status: Active » Closed (fixed)
lolandese’s picture

Version: 6.x-1.x-dev » 7.x-1.x-dev
Status: Closed (fixed) » Active

I would be happy to commit some of the RTBC patches posted in the issue queue and give the D7 version some love.

Thanks.

lolandese’s picture

Status: Active » Fixed

I have been added as a maintainer. Thanks.

The short term battle plan:

  1. Indicate the default repository branch (7.x-1.x instead of master). DONE.
  2. Remove the patch file still present in the D7 dev version.
  3. Release a stable D7 version before committing patches with new features to the dev. This way users of the current dev have a version to turn to if they don't need the new features. The current dev has been released and is unchanged for over a year now, so it can be presumed pretty stable.
  4. Commit RTBC patches to the dev and describe them on the project page in a section "What's new in the dev?".
  5. Fix most of the open issues to get the status of the project back to "Actively maintained".

Status: Fixed » Closed (fixed)

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