[development] Code duplication, collaboration, and sandboxes. Oh my! (was: Custom Theme Settings)
drupal.user at albin.net
Sun May 13 01:54:23 UTC 2007
On May 12, 2007, at 8:06 AM, Earnie Boyd wrote:
> How can this be controlled? What methods could be put into place
> to help reduce the duplication? Self policing doesn't work well
> for these situations. We need some stronger methods to control the
> desire to create YA module of the same function.
Actually, Frederic and I exchanged about 4 emails on April 8
regarding the 2 themesettings modules. But it seems he has
forgotten. So self policing actually did work in this situation; we
were both aware of each other's code and I invited him to
collaborate. I agree with Earnie that 2 YA-solution _projects_ are
indeed a problem, but 1 project and 1 sandbox module... not so much.
Collaboration & the sandbox:
What are the uses of the CVS sandbox? If the sandbox is supposed to
be a place where people can collaborate before a project is created,
perhaps a CVS repository associated with the groups.d.o website would
be more useful.
Perhaps it needs to be a requirement that module developer's announce
their project on this list BEFORE any code becomes public on the d.o
website. I'm not sure how we could enforce that requirement, but
perhaps just documenting it in the appropriate places in the handbook
would be enough.
Any other suggestions?
More information about the development