Nothing like making the same changes to two similar
but different apps, eh? I've been through that hell..
3 different version of the same app, use by three
different groups and different levels of complexity
(read different tasks) that was duct-taped to gether
over 1.5 years because management said, Ohh this is
neet, add it! Gotta love dot com clueless managers...
--- Matt Seitz <mseitz@xxxxxxxxx> wrote:
> --- Shawn Hamzee <shamzee@xxxxxxxxxxxxxxx> wrote:
> > Let's concentrate on functionality first and
> foremost. Once functionality is
> > where we want it to be, we then can concentrate on
> look and feel, if need
> > be.
>
> This doesn't have to be an "either/or" choice.
> There may be developers who
> would be willing to work on adding skins, but would
> not be interested in
> working on other tasks. Telling them "don't work on
> skins" gains nothing.
>
> If there is concern about hurting the main product,
> put the "skins" version on
> a branch or separate tree. Let those who want to
> develop or use a skin version
> work on it, and those who don't use the current
> trunk. That way, skins can be
> developed and tested without risking the trunk. If
> skins prove worthy, they
> can be merged back into the trunk. If not, they can
> continue to develop on a
> branch, or wither as a failed experiment.
>
> Part of the whole appeal of open source software is
> to allow experimentation
> and choice. Let people use their freedom to try new
> things.
>
> =====
> Sincerely,
> Matt Seitz
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! - Official partner of 2002 FIFA World Cup
> http://fifaworldcup.yahoo.com
>
>
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
|
