Well, "merge it into core" is sort of code for "get it released with the rest of DSpace". So, how shall we get this work to release status and be distributed alongside the rest of DSpace? We've not done as well as we might, historically, in bringing good GSOC work into the product when GSOC ends, and I think the desire to do better is causing the sense of urgency about merging these projects into core. If the work is to be released another way, we need to plan and schedule doing so.
This opens up another question: how, now, do we define "the rest of
DSpace"? When a monolithic product becomes a collection of modules,
there is still a need to draw a boundary around the modules and say
"these constitute the product". Since it's still an *evolving* and
*open* product, there will be several sets of code:
o the core and the modules which constitute "DSpace proper". These
are maintained together by the community, though they may release
on different schedules. All have production-quality code drops
from time to time and can be used with confidence. Not all are
required to assemble a functional DSpace instance.
o development, experimental, beta, etc. modules which will probably
move into "DSpace proper" when they mature. Early adopters are
welcome, with the understanding that this code is unstable.
o third-party modules "out there somewhere", maintained and released
by others. Any one may or may not offer production-quality code
drops. DSpace-the-project may provide a distribution point and
other services for some, while others will simply be well-known
add-ons that you get elsewhere. Some of these will be commercial
products.
We need to help people answer the question: "so, what bits do I need
to get DSpace up and running, and how do I get them, and how do I put
them together?" And that answer should be as simple as we can
reasonably make it.
--
Mark H. Wood, Lead System Programmer mw...@iupui.edu
Balance your desire for bells and whistles with the reality that only a
little more than 2 percent of world population has broadband.
-- Ledford and Tyler, _Google Analytics 2.0_
pgpJDaLCr4z7i.pgp
Description: PGP signature
------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
