Hi Folks,
Over the past year or so I've been working on an enhanced SWORDv2
implementation for DSpace, and would like to contribute it back to the main
DSpace release.
I have published the code as a separate module from DSpace, here:
https://github.com/swordapp/DSpaceSWORDv2
Because of the way that I extracted it from the project where it was
developed, there is no version history, which is quite unhelpful. The
original fork of DSpace where this was developed is here:
https://github.com/nye-duo/DSpace/tree/duo
In that module, the commits to the SWORDv2 module are mixed in with commits
to other aspects of the enhancements we were developing.
Is it possible to incorporate this into the release cycle for DSpace 4.0,
and what can I do to help the process? I haven't added anything yet to the
4.0 release notes page (
https://wiki.duraspace.org/display/DSPACE/DSpace+Release+4.0+Notes) but can
do that.
Cheers,
Richard
------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
