Hello everyone I maintain a set of modules called Vote Up/Down Package - http://drupal.org/project/vote_up_down It's essentially 2 modules (which is why its 'package'). One module provides the voting interface. The other module is called Storylink, and it provides a Digg-submission-like content type that has a title, some small info and a link to the actual story. It also has other stuff like a JS bookmarklet. Since this module has been in existence, these both modules were packaged together. I feel now that it would be beneficial for people to have these as separate modules since they perform 2 separate tasks. Initially, these were together to give a Digg-like package. I don't really see people using the package for that purpose now. I'd like to know what other developers think about this issue. Should I separate Storylink and develop it as a separate module? cheers pratul -- Incoming! - OSScamp Pantnagar, 30 Jan - 1 Feb, 2009 - Freed.in, 20 - 21 February, 2009 dum vivimus, vivamus. http://pratul.in
Why not separate storylink and make it use updown instead of vote_up_down, and deprecate vote_up_down in favor of updown, and of course provide an upgrade path? I'd be able to help with this later this month or next month (or at least the upgrade path) Dmitri On Jan 14, 2009, at 12:02 AM, Pratul Kalia wrote:
Hello everyone
I maintain a set of modules called Vote Up/Down Package - http://drupal.org/project/vote_up_down It's essentially 2 modules (which is why its 'package'). One module provides the voting interface. The other module is called Storylink, and it provides a Digg-submission-like content type that has a title, some small info and a link to the actual story. It also has other stuff like a JS bookmarklet.
Since this module has been in existence, these both modules were packaged together. I feel now that it would be beneficial for people to have these as separate modules since they perform 2 separate tasks. Initially, these were together to give a Digg-like package. I don't really see people using the package for that purpose now. I'd like to know what other developers think about this issue. Should I separate Storylink and develop it as a separate module?
cheers pratul
-- Incoming! - OSScamp Pantnagar, 30 Jan - 1 Feb, 2009 - Freed.in, 20 - 21 February, 2009 dum vivimus, vivamus. http://pratul.in
On Wed, Jan 14, 2009 at 6:57 PM, Dmitri Gaskin <dmitrig01@gmail.com> wrote:
Why not separate storylink and make it use updown instead of vote_up_down, and deprecate vote_up_down in favor of updown, and of course provide an upgrade path? I'd be able to help with this later this month or next month (or at least the upgrade path)
If anything I'd say the other way would be better. Not to start a flame war over modules but vote_up_down seemed much more useful when I was evaluating voting modules last month. I'd say split storylink out into it's own project if it turns out it's useful outside of the module that spawned it. I just did that with the audio module's audio_itunes sub-module. It's now the iTunes module (http://drupal.org/project/itunes) and will hopefully prevent other media modules from having to re-implement iTunes feed support. andrew
participants (3)
-
andrew morton -
Dmitri Gaskin -
Pratul Kalia