Page History

...

1. (Ongoing Topic) DSpace 7 Status Updates for this week. 

   1. DSpace 7 Working Group is where the work is taking place
   2. DSpace 7 Dev Status spreadsheet: https://docs.google.com/spreadsheets/d/18brPF7cZy_UKyj97Ta44UJg5Z8OwJGi7PLoPJVz-g3g/edit#gid=0

2. (Ongoing Topic) DSpace 6.x Status Updates for this week

   1. Master ports from 6.3. A number of PRs merged into 6.3 release have not yet been ported to `master` branch.  These PRs are closed but still have the "port to master" label. 
      1. https://docs.google.com/spreadsheets/d/1X-Zk56gz-wg6p7JaiuBzzUquqOvwwx_-o_ZDDvGPSQU/edit?usp=sharing 
      2. As we're working through this list, we should remove the 'port to master' label from the dspace-6.x PR and if possible, edit the JIRA comment to remove the "63_PORT_TO_MASTER" text.
   2. 6.4 will surely happen at some point, but no definitive plan or schedule at this time.  Please continue to help move forward / merge PRs into the dspace-6.x branch, and we can continue to monitor when a 6.4 release makes sense.
3. NOTE: IRC logging bot has been blocked from Freenode 
   1. Stopped logging in IRC on Friday, July 27.  Logs are now filled with SASL-related error messages: http://irclogs.duraspace.org/index.php?date=2018-07-27
   2. Tim has not found a way around this as of yet.  Indications elsewhere are that Freenode has begun blocking AWS-based IPs, and requiring SASL authentication. Our currently used logbot doesn't support SASL authentication.
   3. Also reached out to https://botbot.me/ to see if they could log our #duraspace IRC channel.
4. DSpace and Docker
   1. Tutorial: https://dspace-labs.github.io/DSpace-Docker-Images/
   2. PRs for DSpace 4, 5, 6, 7 -  see DSpace and Docker link above
5. Discussion topics / half-baked ideas (Anything more to touch on with these?)
   
   1. Bulk Operations Support Enhancements (from Mark H. Wood)
      1. Better support for bulk operations (in database layer), so that business logic doesn't need to know so much about the database layer. Specifically, perhaps a way to pass a callback into the database layer, to be applied iteratively to the results of a query.
      2. Then, the database layer can handle batching, transaction boundaries, and other things that it should know about, and the business logic won't have to deal with them.
      3. This is the result of thinking about a recent -tech posting from a site with half a million objects that needed checksum processing.
      4. (This is almost an extension of the tabled topic below regarding DSpace Database Access, but a bit more specific in trying to simplify/improve upon how bulk operations are handled)
   2. Curation System Needs (from Terrence W Brady )
6. How to encourage / credit folks who do Code Reviews? (Tim Donohue)
   1. We have a lot of open PRs.  As we know, the process for reviewing is very ad-hoc, sometimes encounters delays.  If we can find ways to encourage/empower folks (even non-Committers if they know Java / Angular well) to do code reviews & be credited publicly...maybe we can speed up this process?
   2. Other brainstorms welcome!
7. Tickets, Pull Requests or Email threads/discussions requiring more attention? (Please feel free to add any you wish to discuss under this topic)
   
   
   

...