Date: Fri, 29 Mar 2024 10:36:56 -0400 (EDT) Message-ID: <1703388511.167.1711723016789@lyrasis1-roc-mp1> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_166_1562646345.1711723016788" ------=_Part_166_1562646345.1711723016788 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Time: 11:00 am, Eastern Daylight Time (New York, GMT-04:00)
To join the online meeting:
Indicating note-taker
Mike: had two pull requests m= erged. Yahoo! Thank you all for reviews and merging and everything el= se. Comments I got were really good and really improved the pull requ= ests.
Andrew: Glad to hear th= at was a positive experience.
Tickets discussed last wee= k.
Andrew: 1409 and 1459 were reviewed and merged.=
Review of process: &nb= sp;two committers; one should be a committer. Committer would be in a= position to commit the change.
In these two pull requ= ests, did two reviews and at least one was from a committer. But for = whatever reason those pull requests were not merged after crossing the thre= shold of two reviewer thumbs up. Wasn=E2=80=99t clear why; I ended up= doing the merge in both of those cases.
Was there a reason for= not merging?
Mike: Wasn=E2=80= =99t clear to me that if the committer was the second reviewer that the com= mitter could go ahead and commit.
Andrew: I would sugges= t that that be the case. I don=E2=80=99t see a reason not to go ahead= and move it forward.
For 1459, Brian hadn= =E2=80=99t seen that the second approval had occurred before Andrew=E2=80= =99s merge happened.
Kitio still has one pu= ll request awaiting further changes.
Benjamin: Huda b= rought up that there were some changes made that weren=E2=80=99t directly a= ddressing the issue. Agree that they should be separated out and addr= essed via a separate pull request.
With some of these cha= nges, you have to know that the language translations repository exists and= needs to be updated as well. Can=E2=80=99t leave their various strin= g fields blank.
Christian: not a fan o= f using Google Translate to fill in new fields. English would probabl= y be better than Google Translate.
Mike. The es-GO is pro= bably Google Translate, but I believe the Portuguese is actually done by na= tive speaker collaborators.
Andrew: Something we c= an do to make it more clear that the language translations repository exist= s? A README addition?
Mike: README is = good, but reviewers of language properties are probably also likely to noti= ce.
2. Exp= erience with steps involved in closing JIRA tickets / squashed commitBy default, commit message is a concatenation of the individual commit mes= sages. Cleaned up the messages a bit.
Added a link to the JIRA tick= et to the commit comment so there is traceability between the commit and th= e JIRA ticket.
After committed in Github, we= nt over to JIRA ticket to close issue -- changed to =E2=80=98fixed=E2=80=99= and added a link to the commit in the JIRA comment.
Release field: what release t= his will end up in. For Jena tools, simply created a new 0.1 release.=
Don=E2=80=99t need to be the = committer who did the review of a pull request; any committer can move it f= orward if there are two thumbs up.
3. waiting for Jim
4. Andrew: Strategy meeting las= t week.
One outcome was creation of f= ive task forces. All clearly relevant to everyone here, but 4a - Product Ev= olution Taskforce - Google doc is probably of most interest. <= a class=3D"external-link" href=3D"https://drive.google.com/drive/folders/1y= 0Rbgi1t3RpcGdpnkYKIABABprhfUQfl?usp=3Dsharing" rel=3D"nofollow">Produ= ct Evolution task force
Number of ideas floating arou= nd
Can revisit this document and= its implications
Initial musings plus existing= are sources for what we want to be focusing on for the sprints that = are coming up.
Benjamin: I was there and Ale= x Viggio was there as well in person. Had 1-=C2=BD hour discussion on= things that were our priorities and things that we though the community as= a whole would be interested in. Doc created by Paul summarizes some = of the discussion we had during this time. Wanted to create an action plan:= still blank. Don=E2=80=99t think that document should have been created wi= th just five of us in the room anyway. People on this call can contri= bute to that.
Document should be open to co= mments from everyone. Feel free to make comments.
Mike: I was at the meet= ing. Not at the product evolution breakout. The highest-level i= dea here is, perhaps, that the project wants to make progress and had signi= ficant concern about the progress that had been made over the last several = years. These five topics emerged as things that needed to be addresse= d. Five volunteers stepped forward to organized events related to these are= as.
Goal is to create action plan= s that can be executed over the next twelve months. Will be various r= eport-back opportunities over the year to see the progress made in these fi= ve areas.
Other general direction is th= ink creatively. Absolutely an opportunity to do what needs to be done= , to start doing what needs to be done to put us in a better place. T= hat is certainly the general direction for all the groups including Product= Evolution.
Javed: in Google doc, lists o= f nominees.
Mike: only from the people in= the meeting, just for facilitating the breakout session. Will be cal= ls for participation in all of these groups.
Huda: Do you want to ta= lk about the difference between vision and product evolution?
Mike: You=E2=80=99re right: v= ision is broader. Product is about building a piece of software. &nbs= p;Vision people are on a short timeline (6-8 weeks) and have plenty to work= from. Not sure how much vision tweaking they=E2=80=99re going to do.=
Dovetails into a product conc= ept, which is that the world has changed a lot since VIVO was first conceiv= ed in 2003, since the grant began in 2009. What can we give away? I.e= ., are there things in the world that we should use. New and exciting data = sources and related efforts. E.g., ORCID did not exist when we started; ope= n APIs didn=E2=80=99t exist. Vision people will be doing some of that= along with the product people. Vision people will be broader and finish fi= rst.
Don: Will linked data a= nd semantic technology still be pillars of the technical product?
Mike: Yes. An interest = in VIVO=E2=80=99s being a semantic product. Absolutely. Semantics is = a central principle. Need not be the method by which data are presented or = analyzed.
Don: Driving for having= it be the interface. Delivering JSON to other consumers. Is the goal= of VIVO=E2=80=99s product to be able to deliver that semantic representati= on of the data so we can leverage linked open data?
Mike: Two issues. 1. De= livering data to the world: semantics are fundamental. 2. Within an o= rganization, want to deliver data in whatever context makes sense. Te= chnology should be optimized for the use cases. Semantics as the foundation= and local delivery methods to optimize delivery in various contexts.
A lot to be done to optimize = the presentation layer.
Ralph: I=E2=80=99m work= ing on and have gotten quite far with a Bootstrap version of a VIVO theme t= hat works seamlessly on 1.9 and beta 1.10 snapshot version. Got a thu= mbs-up from our communications department. Responds correctly on mobile dev= ices. Includes all the front-end visual parts of VIVO; still working on the= backend. Looks and works correctly. Still cleaning up the libraries = and some weirdness that had been in there previously. Posting it on Github = for everyone to start looking at. Purpose to be a generic Bootstrap templat= e that anyone can take and run with. Out-of-the-box replacement for W= ilma. Would be a quick way to get a quick win for us.
Mike: Is there a ticket= for this? I would like to follow the work and make comments. =
Ralph: Was related to t= he JIRA ticket to take the Symplectic template and create a generic templat= e from that. Think is got closed and some point.
Some screenshots and links on= Slack channel
Andrew: Reopen ticket o= r create a new one.
Any comments you put on Slack= will eventually go away until we have a paid version. Free version o= nly retains last 10,000 messages.
Ralph: I will fix it la= ter today.
Benjamin: Ticket for responsi= ve template here: https://jira.duraspace.org/browse/VIVO-114
Christian: Presentation= is also reporting to research administration.
Mike: I think you=E2=80= =99ll find a lot of comments in the Google doc and would encourage everyone= to read through and make more comments.
Andrew: Task forces tha= t came out of strategy meeting. Thinking about communication. Mike do= es a great job putting out a weekly blurb, but it=E2=80=99s vitally importa= nt that whoever is interested here be involved -- specifically in the Produ= ct Evolution Task Force -- or get a flow of information so that we all move= in the same direction. Don=E2=80=99t want task force and developers = to move in different directions.
Mike: First approach is to pa= rticipate. Product Evolution Task Force should be everyone on this ca= ll.
Action plan group will be pro= ducing notes and process. Calls this week; will share as soon as ther= e is something I can share.
Fixing lack of notes from 1 M= arch meeting as soon as I can.
Andrew: Sprints
Please add your name to the p= articipants list on the development sprints link in Slack https:= //wiki.duraspace.org/display/VIVO/Development+Sprints
Starting to decide on the top= ics and focus of sprints. Will be a bit of a challenge
If it would be helpful for me= or Mike to talk to someone at your institution to advocate for your partic= ipation, we can do that.
Not crystal clear what needs = to be focused on.
Would suggest that just getti= ng a release out and starting from a clean slate would be useful: doi= ng what we need for 1.10.
But clearly there are other t= hings that would be beneficial.
Don: chicken and egg position= : can=E2=80=99t commit to sprint until I know what will be in the sprint. &= nbsp;
Incorporating Elastic might b= e compelling for our business case, for example, but other things might be = harder to justify
Mike: Would like to wor= k on the build process: may be difficult to justify at an individual instit= ution, but have gotten a lot of feedback that it could be done a different = way.
Andrew: Get additional topics= on the table so they=E2=80=99re available as topics of conversation.
Benjamin: I can definit= ely participate in one of the sprints, but agree with Don that the time com= mitment would be dependent on the topic addressed. Elasticsearch woul= d also be of interest to us here.
Authentication system is anot= her possible topic.
Christian: A bit shy ab= out dedicating time to the sprint, because the developers are not yet hired= .
Ralph: The password thi= ng might be a good one to start with. Good view into the system but n= ot overly complex.
I would work on the sprint; a= lso generally advocating the topic.
Don: can share a slide I did = with Jim Blake on the benefits of Elastic. When you incorporate it yo= u get pretty deep into the VIVO code. Would be a great opportunity to get n= ot only another index but also to help us create documentation and to allow= the rest of us to get under the hood into the layer that=E2=80=99s not tha= t accessible.
Andrew: Yes, ideally th= ese sprints would help expand capacity.
Andrew: Please do whatever yo= u can to slice off time and indicate that time on the wiki.
Don: Andrew, is there a= document out there where we can get ideas for sprints?
Under agenda item 5, relative= ly comprehensive document Mike put together: https://docs.google.com/document/d/1dddA9sPsJMAvfd6vS7tx5= dsVYzBKWIqU8MUkRbIMClk/edit?usp=3Dsharing . Commenti= ng on the document is one relatively effective way to indicate interest. &n= bsp;Could also translate it into a poll.
Huda: would suggest that we h= ave a separate document for the sprint topics. Technical initiatives = doc is probably too broad: in a sprint we will only do a portion of what is= listed in that doc. As long as we link back to the technical initiat= ives document and say what initiative this is further breaking out, should = be clear. But otherwise, the granularity won=E2=80=99t match up.
https://docs.google.com/document/d/1zgIt_VdFMxUNokrdFyvFwUKgrU95NoBtq= _JkkU3oOgU/edit?usp=3Dsharing
Andrew: Were a bunch of= unmerged pull requests stuck in review. Reopened tickets and put the= m in the In Review state. Maybe there are others. Please do a review = of tickets you are associated with to make sure they aren=E2=80=99t inappro= priately closed or to do the review if in review.
6. Cloning / backing up / restoring a= VIVO instance
Wiki pages lacking sufficient= detail to do it successfully. Can take it to Slack: would be great t= o flesh out the details so someone can actually do this.
Tick= ets created in the last 30 days:
Tick= ets resolved in the last 30 days:
Bugs=
<= br>