[development] re CVS requirements
pinglaura at gmail.com
Wed Oct 28 18:26:02 UTC 2009
It seems the actionable solution is to allow people to contribute what
they're doing, and let the consolidation happen in the community,
rather than what some people might feel is a "bow down to Zod" kind of
An overabundance of modules with overlapping functionalities is not a
CVS problem, it's a module/project parsing and rating problem,
something that DrupalModules.com helps address and what the D.o
redesign is also intended to address.
A friendly policy would be to first make it easy peasy to get people
involved and excited about contributing their own itch they scratched,
and then get them involved in collaborations and consolidations. After
all, much of what ends up being overlapping functionality is because
the developer had a project that needed X and did not have the time or
resources to try to get Y to change to solve his/her use case. I feel
we should let that developer serve his/her client and contribute what
was done, and let improvements and consolidations happen within the
On Oct 28, 2009, at Wed 10/28/09 11:53am, Dave Reid wrote:
> For reference, the application was http://drupal.org/node/578596.
> And the point that could have been better made is that should we
> allow each tiny module to add SimpleNews subscription forms to a
> single module's code? Or should there maybe be a sub-module of
> SimpleNews that allows users to add subscription checkboxes to any
> form or page and would be infinately more useful to the community?
> Also the module provided for review was sloppy, and limited to only
> one newsletter, and as someone pointed out, didn't even work. But
> again, that never made it into the review.
> Also please see my earlier points about community needing to get
> involved with reviews. You can point out things that went wrong all
> day, but until you provide reasonable and actionable solutions,
> nothing is going to help.
> Dave Reid
> dave at davereid.net
> On Wed, Oct 28, 2009 at 12:29 PM, Jeff Greenberg
> <jeff at ayendesigns.com> wrote:
> So, here's another example (I think) of what I would consider CVS
> censorship. I've spent a couple hours already today trying to get a
> simplenews subscription checkbox onto the Ubercart checkout. Found
> the function in simplenews, but it has a parm that I can't find the
> source of, etc. Busy work that I don't need.
> I find an entry at Ubercart after much searching, for a module that
> was developed -just for this- requirement. It adds a simplenews
> newsletter subscription pane to the checkout process.
> Here is the author's explanation of why it's listed there and not at drupal.org
> "I think the module was a bit too simple to put on the main Drupal
> site (my application for a CVS account was rejected <smile.png> so
> I'll put it here instead."
More information about the development