Date: Thu, 28 Mar 2024 20:19:39 -0400 (EDT)
Message-ID: <1671717968.29264.1711671579409@lyrasis1-roc-mp1>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_29263_1681632901.1711671579409"
------=_Part_29263_1681632901.1711671579409
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
DevMtg 2010-09-01
DevMtg 2010-09-01
<=
a href=3D"/display/DSPACE/DevMtg+2010-09-01">Developers Meeting on Weds, Se=
ptember 1, 2010
Agenda
- JIRA Catch-Up (fo=
r first 20 mins or so of meeting) =E2=80=93 starting with issue DS-588=20
- DSpace 1.7 F=
eatures/Updates=20
- Unclaimed 1.7 Issues/Potential Features in JIRA
- Documentation now on Wiki at: DSpace Documentation
- Jeff Trimble is cleaning up with help from Bill Anderson of Georgia Tec=
h. If you'd like to volunteer to help, contact Jeff.
- Only Committers & Official Doc Gardeners can edit this area. Anyone=
else can only add Comments to pages.
- General Plan for 1.7: Official Documentation will be these Wiki Docs, a=
nd we'll generate PDF from Wiki (rather than old DocBook).
- Potential Asynchronous Release Processes (for DSpace Discovery and possibly REST API)=20
- Proposal is to find an easy way to install DSpace addons (where 'addons=
' are separate Maven Projects, like REST or Discovery) after you've already installed out-of-the-box DSpace. This could allow DSpace =
to move into more of a "plugin" architecture =E2=80=93 where initially you'=
d just install the base DSpace, and later you can install only the addons/p=
lugins that you want.
- One Option for Async Releases via Maven:
- Mark Diggory had suggested potentially creating Maven Archetypes (templ=
ates) which can be used to assist in installation of these 'addons'. We cou=
ld also create our own Maven Plugin for DSpace to allow us to easily call t=
hese archetypes.
- E.g. In the end, you could run
mvn dspace:install-discovery
to auto-create the [dspace]/dspace/modules/discovery/
direct=
ory and add its dependency the [dspace]/dspace/modules/pom.xml
=
(thus Maven would install 'Discovery' the next time you ran mvn pack=
age
).
- The Maven "dspace:xxxxxxx" namespace would be reserved for only "offici=
al" addons which you could install on demand. (e.g. 'dspace:install-rest', =
'dspace:install-discovery', 'dspace:install-lni', etc.).
- Background Information (for Async Release Process proposal)=20
- More info on Maven Archetypes:=20
- More info on Maven Plugins (like the "dspace:xxxxxx" example):=20
Meeting Notes
JIRA catchup, 1.7 updates (need volunteers!), Async Release Process Disc=
ussion
- JIRA catchup =E2=80=93 last item reviewed was DS-605
- DSpace 1.7 updates=20
- Many unclaimed issues scheduled for 1.7. We need vol=
unteers! If you are interested in one of these issues, please clai=
m it in JIRA. If you are a committer & haven't volunteered to help with=
any issues yet, we'd appreciate it if you could help out (even with just a=
1-2 issues).
- DSpace Documentation now on Wiki at: DSpace Documentation =E2=80=93 Still being cleaned up, =
but all new Doc changes should be made on Wiki.
- Discussion of Async Release Processes=20
- Two main goals:=20
- Goal 1: to be able to depend on dspace-api independent of official rele=
ase distro=20
- So that dspace-api-1.0.0 <--- addon-1.0.1 <--- dspace-release-1.7=
.0
- We are most interested in "deploy time" integration (although compile-t=
ime & assembly-time integration could also be nice)
- Goal 2: needs to avoid extra complexity =E2=80=93 must simplify install=
/upgrades and NOT make them more difficult than they already are.
- Mark D's suggested approach=20
- Mark has started prototyping this idea in SVN Sandbox at: http://scm.dspace.org/svn/repo/sandbox/dspace-a=
sync-prototype/
Meeting Transcript
------=_Part_29263_1681632901.1711671579409--