join with flickrripper or document differences
greggles - September 15, 2008 - 03:38
| Project: | Flickr Sync |
| Version: | 5.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
This module seems really similar in purpose to http://drupal.org/project/flickrrippr
Perhaps you can join forces with that module and together build one much better module?
Otherwise, it's worth documenting why it is necessary to build this separate module and what makes it different so that people deciding between them know why your module exists.
#1
Exactly what I was wondering when I saw this module show up.
#2
I re-read the project description and see
If that's the case, then the changes to make this module work should be created as a patch file and submitted to the flickrrippr queue. If the module maintainer for flickrrippr has stopped maintaining it, then you should follow the abandoned project process to take it over.
#3
Absolutely... you guys are too fast and I haven't gotten a chance to do these things yet! The full story is that I wrote and released three new modules for a talk I did at DrupalCamp LA yesterday. The changes to FlickrRippr are extensive, so I felt it was beyond the scope of a patch, plus I needed to get this out there ASAP so attendees could try it. I will contact the FlickrRippr maintainer and see if we can work something out.
#4
FlickrRippr module is active now and it even has D6 beta version. However, this module has only dev. version and it is already 7 months old. Is this module still under development? Maybe it is better to switch to FlickrRippr, if it is abandoned. These two modules overlap in functionality.