Timestamps are in GMT/BST.
[6:28] -verne.freenode.net- *** Looking up your hostname...
[6:28] -verne.freenode.net- *** Checking Ident
[6:28] -verne.freenode.net- *** Found your hostname
[6:29] -verne.freenode.net- *** No Ident response
[6:29] * DuraLogBot (~PircBot@webster.duraspace.org) has joined #duraspace
[6:29] * Topic is 'Welcome to DuraSpace IRC. This channel is used for formal meetings and is logged - http://irclogs.duraspace.org/'
[6:29] * Set by tdonohue on Thu Sep 15 17:49:38 UTC 2016
[11:20] * tdonohue (~tdonohue@dspace/tdonohue) has joined #duraspace
[12:05] * misilot (~misilot@p-body.lib.fit.edu) Quit (Read error: Connection reset by peer)
[12:07] * mhwood (~mhwood@mhw.ulib.iupui.edu) has joined #duraspace
[14:48] <DSpaceSlackBot> <tdonohue> <here>: I know it's a very late agenda & reminder, but our weekly DSpace DevMtg is scheduled for the top of the hour (~13mins) here. It may be a brief meeting, but would like to do a post-6.3 wrapup, etc. https://wiki.duraspace.org/display/DSPACE/DevMtg+2018-07-11
[14:48] <kompewter> [ DevMtg 2018-07-11 - DSpace - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSPACE/DevMtg+2018-07-11
[15:01] <DSpaceSlackBot> <tdonohue> <here>: It's DevMtg time. I realize that the reminder and agenda were a bit late, but hopefully a few of you are still available today. Let's do a quick roll call to see who is joining us
[15:02] <DSpaceSlackBot> <terrywbrady> Joining in 2 min n
[15:02] <DSpaceSlackBot> <jcreel256> hello
[15:02] <DSpaceSlackBot> <mwood> Hi
[15:04] <DSpaceSlackBot> <tdonohue> Looks like we got a few of the usual suspects, which is good. It's been several weeks since we last talked (cause of recent travel / holidays), so welcome!
[15:05] <DSpaceSlackBot> <tdonohue> As we haven't talked in several weeks, most of today may be a bit of a 6.3 Release wrap-up (what we felt went well, what still needs doing, what could have been improved, etc).
[15:05] <DSpaceSlackBot> <tdonohue> But, before we get to that, a few brief updates/reminders
[15:06] <DSpaceSlackBot> <tdonohue> First the second DSpace 7 Sprint is going on this week (started on Monday, and goes through July 20). https://wiki.duraspace.org/display/DSPACE/DSpace+7+Community+Sprint+2
[15:06] <kompewter> [ DSpace 7 Community Sprint 2 - DSpace - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSPACE/DSpace+7+Community+Sprint+2
[15:06] <DSpaceSlackBot> <tdonohue> We still welcome others to get involved (mostly we are catching up on backlogs of PRs that need review/testing, and also getting code that was demoed at OR2018 actually merged/finalized).
[15:07] <DSpaceSlackBot> <tdonohue> If you are interested in getting involved or following along, join us in the dev-sprint channel.
[15:08] <DSpaceSlackBot> <tdonohue> Also The next Dev Show & Tell meeting will be at the end of this month. It will feature tools for working with the new DSpace 7 REST API (so, it's a good opportunity to learn more about that part of DSpace 7) https://wiki.duraspace.org/display/DSPACE/Dev+Show+and+Tell+-+July+31%2C+2018+-+1500UTC+-+REST+API+Tools
[15:08] <kompewter> [ Dev Show and Tell - July 31, 2018 - 1500UTC - REST API Tools - DSpace - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSPACE/Dev+Show+and+Tell+-+July+31%2C+2018+-+1500UTC+-+REST+API+Tools
[15:09] <DSpaceSlackBot> <terrywbrady> Just a reminder... for any new Sprint participants, the following resource is available: https://dspace-labs.github.io/DSpace7RestTutorial/walkthrough/intro
[15:09] <kompewter> [ DSpace 7 REST Code Walkthrough | DSpace 7 REST API Tutorial ] - https://dspace-labs.github.io/DSpace7RestTutorial/walkthrough/intro
[15:09] <DSpaceSlackBot> <tdonohue> And the DSpace Entities Working Group is still yet to be re-established....it has been delayed from vacations, etc. So, expect more on a new iteration of this working group (and a call for new participants) in coming week or so.
[15:09] <DSpaceSlackBot> <terrywbrady> If any of you have an additional API tool to share at the Dev Show and Tell meeting, let me know.
[15:09] <DSpaceSlackBot> <tdonohue> That's it for the DSpace 7 related updates & updates from other Working Groups/efforts.
[15:10] <DSpaceSlackBot> <tdonohue> Any questions/comments though before I move forward? Or any other quick announcements/reminders that anyone wants to share?
[15:11] <DSpaceSlackBot> <terrywbrady> I have been doing some work on our Docker Images: https://github.com/DSpace-Labs/DSpace-Docker-Images/blob/master/README.md
[15:11] <kompewter> [ DSpace-Docker-Images/README.md at master · DSpace-Labs/DSpace-Docker-Images · GitHub ] - https://github.com/DSpace-Labs/DSpace-Docker-Images/blob/master/README.md
[15:11] <DSpaceSlackBot> <jcreel256> @terrywbrady is that show and tell supposed to have a focus on the 7 REST API or is the 5/6 just as relevant?
[15:11] <DSpaceSlackBot> <terrywbrady> Thanks to @mohideen for submitting a PR. I am eager to get more feedback on these images and their proposed usage
[15:12] <DSpaceSlackBot> <terrywbrady> @jcreel256, the tools should apply to any version.
[15:12] <DSpaceSlackBot> <terrywbrady> @art-lowel will show how he uses Postman to query the solr service.
[15:12] <DSpaceSlackBot> <tdonohue> @terrywbrady: maybe it'd be worth having you walk us through this DSpace Docker proposal at some point in more detail -- either in this meeting in a future week, or in a Dev Show & Tell. It looks interesting, but might deserve a walkthough/discussion
[15:13] <DSpaceSlackBot> <tdonohue> In any case, thanks for moving DSpace Docker stuff forward! Glad to see this going on. I just need to catch up on the work/discussion ;)
[15:14] <DSpaceSlackBot> <terrywbrady> @tdonohue that sounds like a good plan. I will likely make that the focus of the Aug Show and Tell. I would be glad to do an update here as well if folks are interested.
[15:14] <DSpaceSlackBot> <tdonohue> A regular update might be nice here, if there's anything to say in a given week. But, yes, a Show & tell to talk through it, ask questions, etc would be wonderful! Looking forward to it
[15:15] <DSpaceSlackBot> <tdonohue> And obviously anyone interested in this should join the dspace-docker channel in Slack ;)
[15:15] <DSpaceSlackBot> <terrywbrady> @jcreel256 let me know if you can think of additional api tools that would be good to show at the July Show and Tell.
[15:15] <DSpaceSlackBot> <jcreel256> Yes, we have something in mind.
[15:16] <DSpaceSlackBot> <jcreel256> https://github.com/TAMULib/MetadataAssignmentToolService
[15:16] <kompewter> [ GitHub - TAMULib/MetadataAssignmentToolService ] - https://github.com/TAMULib/MetadataAssignmentToolService
[15:16] <DSpaceSlackBot> <tdonohue> Moving back to the agenda now... 6.3 wrap-up!
[15:16] <DSpaceSlackBot> <jcreel256> https://github.com/TAMULib/MetadataAssignmentToolService/blob/master/src/main/java/edu/tamu/app/service/repository/DSpaceRepository.java
[15:16] <kompewter> [ MetadataAssignmentToolService/DSpaceRepository.java at master · TAMULib/MetadataAssignmentToolService · GitHub ] - https://github.com/TAMULib/MetadataAssignmentToolService/blob/master/src/main/java/edu/tamu/app/service/repository/DSpaceRepository.java
[15:18] <DSpaceSlackBot> <tdonohue> First, as this is the first meeting we've had since 6.3 went out the door, I'd like to again say thanks to everyone who chipped in here! It was a pretty large bug fix release with a lot of contributors!
[15:18] <DSpaceSlackBot> <tdonohue> I won't call out everyone here, but thanks especially to @kshepherd (who is asleep right now, or should be). The full list of contributors though is in the Release Notes: https://wiki.duraspace.org/display/DSDOC6x/Release+Notes
[15:18] <kompewter> [ Release Notes - DSpace 6.x Documentation - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSDOC6x/Release+Notes
[15:18] <DSpaceSlackBot> <terrywbrady> @tdonohue did you send a release announcement to the dist lists?
[15:19] <DSpaceSlackBot> <tdonohue> @kshepherd sent out the release announcement, yes.
[15:20] <DSpaceSlackBot> <tdonohue> As I said though, this happened a few weeks back (we haven't met in some time). Here was the announcement from Kim: https://groups.google.com/d/msg/dspace-community/xM2-R_ELNg8/TsHLbtqqCAAJ
[15:20] <kompewter> [ Google Groups ] - https://groups.google.com/d/msg/dspace-community/xM2-R_ELNg8/TsHLbtqqCAAJ
[15:20] <DSpaceSlackBot> <tdonohue> And as he noted there, we had 37 contributors to 6.3 alone! That's massive for a bug fix release...most bug-fix releases tend to have 10 or less.
[15:21] <DSpaceSlackBot> <tdonohue> In any case, job well done. But, the work is never complete ;)
[15:22] <DSpaceSlackBot> <tdonohue> As a reminder, we still have several bug fixes that were applied in 6.3 that need to be adapted/ported to our `master` branch. Kim created a useful spreadsheet for our reference:
[15:22] <DSpaceSlackBot> <tdonohue> https://docs.google.com/spreadsheets/d/1X-Zk56gz-wg6p7JaiuBzzUquqOvwwx_-o_ZDDvGPSQU/edit?usp=sharing
[15:22] <kompewter> [ Closed for 6.3 but still need port to master (search JIRA for 63_PORT_TO_MASTER) - Google Sheets ] - https://docs.google.com/spreadsheets/d/1X-Zk56gz-wg6p7JaiuBzzUquqOvwwx_-o_ZDDvGPSQU/edit?usp=sharing
[15:23] <DSpaceSlackBot> <tdonohue> So, Kim & I could use help in taking these (already merged/released) 6.3 PRs and porting them over to the `master` branch, quickly reviewing & merging.
[15:23] <DSpaceSlackBot> <tdonohue> I'm not concerned too much with heavy testing of these ported PRs (as they were tested for 6.3, and the 6.3 and master APIs are rather similar).
[15:24] <DSpaceSlackBot> <tdonohue> So, the job is more to port them...have someone else compare the 6.3 PR with the new `master` PR, ensure it passes unit tests, etc...and then get it merged
[15:24] <DSpaceSlackBot> <tdonohue> As a reminder, the biggest challenge in porting these PRs is our new code style requirements on `master`: https://wiki.duraspace.org/display/DSPACE/Code+Style+Guide
[15:24] <kompewter> [ Code Style Guide - DSpace - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSPACE/Code+Style+Guide
[15:25] <DSpaceSlackBot> <tdonohue> Unfortunately, as these code style requirements *don't exist* in 6.x, many of these PRs cannot be simply cherry-picked to `master`. There's often (minor) code realignment / style fixes that need to occur. Travis CI will keep you honest though, as it will validate style in all `master` PRs
[15:27] <DSpaceSlackBot> <mwood> Your IDE may be adjustable to catch these when porting to master, and 'mvn clean verify' should also show any problems.
[15:28] <DSpaceSlackBot> <tdonohue> So, if others are willing to chip in here, I could use the help. This would go much much faster if a few people are working on it, than if it falls down to 1-2 people.
[15:28] <DSpaceSlackBot> <tdonohue> To that end, I just added a new "Volunteer" column to that spreadsheet: https://docs.google.com/spreadsheets/d/1X-Zk56gz-wg6p7JaiuBzzUquqOvwwx_-o_ZDDvGPSQU/edit?usp=sharing
[15:28] <kompewter> [ Closed for 6.3 but still need port to master (search JIRA for 63_PORT_TO_MASTER) - Google Sheets ] - https://docs.google.com/spreadsheets/d/1X-Zk56gz-wg6p7JaiuBzzUquqOvwwx_-o_ZDDvGPSQU/edit?usp=sharing
[15:29] <DSpaceSlackBot> <tdonohue> I think this task will likely be ongoing for several weeks...but obviously, we should get this done as soon as possible. Definitely let me know if there are questions on how to chip in!
[15:31] <DSpaceSlackBot> <tdonohue> To wrap up the 6.x topic here..as noted in the agenda, I suspect we will have a 6.4 at some point. But, currently there's no definitive schedule. (And we should clean up these `master` ports before we move on to 6.4 anyhow)
[15:31] <DSpaceSlackBot> <tdonohue> Any questions / comments / thoughts about 6.x or 6.3? Anything I missed?
[15:32] <DSpaceSlackBot> <mwood> Nope
[15:33] <DSpaceSlackBot> <tdonohue> Not hearing any ;) We'll move along
[15:33] <DSpaceSlackBot> <tdonohue> As noted in topic #3 in the agenda.... now that 6.3 is out the door, we may have a bit more time available in these weekly DevMtgs.
[15:34] <DSpaceSlackBot> <tdonohue> Obviously, we'll still have certain ongoing topics...updates on DSpace 7 (and other efforts), and ensuring we get these 6.3 PRs ported to master
[15:34] <DSpaceSlackBot> <tdonohue> But, it seems to me like we'll have more and more opportunity for *new topics* / new areas of discussion / brainstorms / proposals
[15:35] <DSpaceSlackBot> <tdonohue> (As an example, we are only about 1/2 way through today's meeting, and we've essentially covered the agenda)
[15:35] <DSpaceSlackBot> <tdonohue> So, I'd like to offer to all of you the opportunity to bring new topics / discussions / brainstorms to this meeting as agenda items.
[15:36] <DSpaceSlackBot> <tdonohue> While I gladly facilitate this meeting, I think the agenda should be more of a team effort here...so, suggesting topics for the agenda is more than welcome
[15:37] <DSpaceSlackBot> <mwood> Okay: better support for bulk operations, so that business logic doesn't need to know so much about the storage layer. Specifically, perhaps a way to pass a callback into the storage layer, to be applied iteratively to the results of a query.
[15:38] <DSpaceSlackBot> <mwood> Then, the storage 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.
[15:39] <DSpaceSlackBot> <mwood> This is the result of thinking about a recent -tech posting from a site with half a million objects that needed checksum processing.
[15:40] <DSpaceSlackBot> <tdonohue> @mwood: the general idea sounds reasonable. I'm not sure myself how to implement, but it seems like something that someone could investigate and come back with a proposal of "this is one way we could better support bulk operations"
[15:40] <DSpaceSlackBot> <tdonohue> Is this something you are suggesting you'd like to work on? Or are you just looking for fellow brainstormers / others to collaborate on a proposal?
[15:41] <DSpaceSlackBot> <mwood> I was hoping someone else, with more ORM experience, would venture an opinion before I dive into coding. I'm rather unlike an expert on that.
[15:41] <DSpaceSlackBot> <tdonohue> But, yes, this is exactly the sort of topics we could bring to these meetings...either as proposals...or as early brainstorms which ideally get volunteers to turn into a proposal / test implemenation
[15:43] <DSpaceSlackBot> <tdonohue> I suspect the challenge here is that we can come up with all sorts of "good ideas". But, good ideas don't turn into code without someone finding time to dig in -- and finding that someone isn't always easy (as we all know)
[15:43] <DSpaceSlackBot> <tdonohue> (And that's a general challenge, not specific to this one idea)
[15:44] <DSpaceSlackBot> <mwood> I'm interested in contributing to this one, as I find the current approach bothersome. We have similar problems all over the admin. tools.
[15:44] <DSpaceSlackBot> <mwood> A different approach might also help to contain some of the caching issues we've fought (and may have to fight again).
[15:47] <DSpaceSlackBot> <terrywbrady> Regarding Admin tooling, I wish that we could turn admin tasks and curation tasks into a simple set of modules that could be invoked in a consistent manner. (And the new REST API could invoke any admin/curation task).
[15:47] <DSpaceSlackBot> <mwood> Yes, there are a lot of random admin. tools that should have been tasks, if tasks had existed when they were first written.
[15:48] <DSpaceSlackBot> <terrywbrady> At one time, I captured some thoughts here: https://wiki.duraspace.org/display/~terrywbrady/Curation+System+Needs
[15:48] <kompewter> [ Curation System Needs - Terry Brady - DuraSpace Wiki ] - https://wiki.duraspace.org/display/~terrywbrady/Curation+System+Needs
[15:48] <DSpaceSlackBot> <tdonohue> These are good discussions. I'm trying (in my head) to figure out the best way to support this sort of brainstorming / idea gathering in our virtual environment (either in these DevMtgs or elsewhere)
[15:49] <DSpaceSlackBot> <terrywbrady> It might be good to tackle this when the Admin features are addressed in REST 7
[15:49] <DSpaceSlackBot> <tdonohue> Obviously, ideally, we get the "right people" (with right expertise) to show up and hash it out...and then volunteers show up to implement. But, as we all know, that's hard to do virtually.
[15:50] <DSpaceSlackBot> <mwood> @terrywbrady those are some good thoughts.
[15:50] <DSpaceSlackBot> <terrywbrady> Will CLI tasks access the DSpace API directly, or will they be run through REST.
[15:50] <DSpaceSlackBot> <tdonohue> We could however schedule out discussions on topics of interest in these meetings just to gather rough ideas/brainstorms (and hope others or one of us) can steward those into proposals/implementations.
[15:52] <DSpaceSlackBot> <tdonohue> My suspicion is saying "let's leave this to DSpace 7" won't really work. As the DSpace 7 team is really concentrating on moving quickly & mostly just porting DSpace 6 stuff into this new environment.
[15:52] <DSpaceSlackBot> <mwood> Sounds well. I often want to start by just airing an idea to find out: is this daft? does anyone else care?
[15:52] <DSpaceSlackBot> <mwood> Maybe we need a "DSpace 7 Plumbing" WG.
[15:53] <DSpaceSlackBot> <tdonohue> But, if we can use these meetings to brainstorm & start to move towards proposals, we could perhaps "inject" small improvements into DSpace 7 at times....or at the worst, make proposals for how to improve in DSpace 8
[15:53] <DSpaceSlackBot> <tdonohue> DSpace 7 won't be the last release ;) We should not try and stuff everything into it.
[15:54] <DSpaceSlackBot> <terrywbrady> It will be worthwhile to hear the plan for Admin, Curation, and CLI tasks in DSpace 7.
[15:54] <DSpaceSlackBot> <mwood> Personally, I've just been putting the DSpace 7 milestone onto anything I come up with that isn't a bugfix.
[15:55] <DSpaceSlackBot> <mwood> At some point, there'll be a decision: this is the stuff we can get done without unduly delaying the release. The rest will get swept onward to v8.
[15:55] <DSpaceSlackBot> <tdonohue> @terrywbrady: DSpace 7 is trying to tighten scope (to avoid scope creep & get a release ready by early 2019). Admin features that are at the UI level will need to be enabled in the REST API (which includes triggering curation tasks). But, thinks like CLI I expect to be unchanged/untouched
[15:56] <DSpaceSlackBot> <tdonohue> *things* like CLI, I expect to be unchanged/untouched (from 6.x)
[15:56] <DSpaceSlackBot> <terrywbrady> Thanks for filling me in on that.
[15:58] <DSpaceSlackBot> <tdonohue> I think that shouldn't limit our ability to create proposals & code improvements. If there is more work/features that are *ready in time* for DSpace 7, we obviously would include them.
[15:58] <DSpaceSlackBot> <tdonohue> But, the current team on DSpace 7 is concentrating on a tightened scope...so, that current time won't address "plumbing" issues unless those issues are required to enable something in the REST API layer.
[15:58] <DSpaceSlackBot> <tdonohue> that current *team*
[15:59] <DSpaceSlackBot> <tdonohue> Nonetheless, it seems like we can use these meetings to start to discuss specific topics we see as beneficial to resolving in DSpace (no matter whether it is fixed in v7, v8 or v9).
[16:00] <DSpaceSlackBot> <terrywbrady> My comments were not a proposal to change scope. Porting some of this functionality to a REST API is already a type of plumbing change. I am not always current with the latest decisions.
[16:01] <DSpaceSlackBot> <mwood> Before we go, I wanted to draw attention to a bug fix: DS-3895. It's a minor thing, apparently not causing trouble with stock code, but I tripped over it in local code. The fix is conceptually small but it touches a variety of classes since it renames a method.
[16:01] <kompewter> [ https://jira.duraspace.org/browse/DS-3895 ] - [DS-3895] Bitstream size can't be referenced in HQL queries - DuraSpace JIRA
[16:01] <DSpaceSlackBot> <tdonohue> @terrywbrady: to be honest, no "decisions" have been made other than...we cannot delay DSpace 7 further, so we have to tighten scope. Obviously that tightened scope will still including porting all functionality (in either XMLUI or JSPUI) into the REST API layer. It's just we likely won't go beyond that ;)
[16:02] <DSpaceSlackBot> <terrywbrady> @tdonohue That makes sense to me
[16:02] <DSpaceSlackBot> <mwood> So, it sounds like any revamping of CLI tools is scheduled for DSpace 8.
[16:02] <DSpaceSlackBot> <mwood> Or later.
[16:03] <DSpaceSlackBot> <tdonohue> @mwood: correct, unless some other developer resources step forward and take it on (and then, only if it can be done without throwing our DSpace 7 schedule out of wack). The likelihood of that is low though, so my expectation is that would be done in DSpace 8
[16:04] <DSpaceSlackBot> <tdonohue> (I never can say something *won't* happen....resources sometimes arise out of the blue...but it's pretty unlikely at this point)
[16:04] <DSpaceSlackBot> <tdonohue> In any case, we are at the top of the hour (over by 4 mins). So, we should wrap this up!
[16:05] <DSpaceSlackBot> <tdonohue> For next week, I'll add a brief summary of some of these topics to the agenda to see if we want to discuss them further. Other discussion topics are also welcome (forward my way or add to agenda)
[16:05] <DSpaceSlackBot> <mwood> Thanks!
[16:06] <DSpaceSlackBot> <terrywbrady> The Dev Show and Tell Agendas have been updated: https://wiki.duraspace.org/display/DSPACE/DSpace+Developer+Show+and+Tell+Meetings @tdonohue, thanks for posting the last recording.
[16:06] <kompewter> [ DSpace Developer Show and Tell Meetings - DSpace - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSPACE/DSpace+Developer+Show+and+Tell+Meetings
[17:45] * misilot (~misilot@p-body.lib.fit.edu) has joined #duraspace
[21:07] * mhwood (~mhwood@mhw.ulib.iupui.edu) Quit (Remote host closed the connection)
[21:54] * tdonohue (~tdonohue@dspace/tdonohue) has left #duraspace
These logs were automatically created by DuraLogBot on irc.freenode.net using the Java IRC LogBot.