Time/Place

This meeting is a hybrid teleconference and slack chat. Anyone is welcome to join...here's the info:

• Time: 11:00am Eastern Daylight Time US (UTC-4)
• Audio/Video Conference Link: https://duraspace.zoom.us/my/fedora
  

  • Dial-in:
    +1 408 638 0968
    +1 646 876 9923
    +1 669 900 6833
    Meeting ID:
    812 835 3771

• Join fedora-project.slack.com on the "tech" channel
  
  

Attendees

• Danny Bernstein
• Andrew Woods
• Bethany Seeger 
• Jared Whiklo 
• Peter Eichman  
• Doron Shalvi 
• Kevin Ford 
• Ben Pennell
• James Silas Creel
• David Wilcox

Agenda

1. Sign up for the upcoming Alignment Sprint
2. Sprint planning
   1. Update on  Ben Pennell's work on mementos of binaries and their descriptions.
      
      1. Outstanding questions:
         1. Should we have LDP responses for mementos?
         2. Does a memento object act as a full LDP object, particularly with respect to headers?
         3. Are the edge things (such as headers) important for our users' workflows?  Should we handle these?
         4. Is versioning for items only currently in the repo, or all items that have ever been in repo?
         5. Should Fedora keep versions of items that have been deleted?
      2. feedback from leadership?
   2. WEB ACLs
      1. Peter Eichman's assessment of moving WebACLs from modeshape.
      2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
         
         1. Do we still want to support the current scheme for the sake of backward compatibility?
      3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
         
         1. Discuss Aaron Birkland's questions in the issue comments section
         2. Should we consider abandoning Section 5.4 Specify ACL on resource creation in light of this issue as well as  Unable to locate Jira server for this macro. It may be due to Application Link configuration.  and  Unable to locate Jira server for this macro. It may be due to Application Link configuration. ?
   3. "Pre-sprint" work that can be done
   4. Reading work? 
   5. Low-hanging JIRA tickets:
      1. ?
3. Shall we consider using Duraspace checkstyle rules?
   
   1. Checkstyle Analysis
   2. Repo
   3. There are three rules in the fedora checkstyle rules that are not in the Duraspace checkstyle rules: 
      
      1. requiring @author in javadoc
      2. "final" required for parameter variables
      3. "final" required for local variables
   4. There are 40-odd lines in fcrepo4  that would need to be corrected to roll this out.
4. Documenting Breaking Changes Between Fedora 4.7.x and 5.0.0

Sprint tickets 

Ticket Summaries

1. Please squash a bug!

   Click here to expand...

   key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

2. Tickets resolved this week:

   Click here to expand...

   key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

3. Tickets created this week:

   Click here to expand...

   key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Minutes

Actions

• Danny Bernstein: to create list of breaking changes in Fedora5
• Danny Bernstein: to send message to community wrt whether webac breaking change is tolerable in Fedora5 (or should continue to be supported, and deprecated)