November OpenZFS Leadership Meeting

[Matthew Ahrens]

Meeting recording available here: https://youtu.be/WKfS3lAmLGc

At this month's meeting we discussed: new ZoL minimum kernel version; ZoL
repo move/rename; issue tracker curatioon

Meeting notes (thanks Serapheim):

   -

   Rescheduled OpenZFS DevSummit talk: Securing the Cloud with ZFS
   Encryption (Jason King)
   -

   New ZoL minimum kernel version (Brian)
   -

      Change: Increase the minimum version to 3.10 kernel (from 2.6)
      -

      Practical implication:
      1.

         Dropping some support for very old enterprise releases of Linux
         2.

         Net removal of around 2,000 lines of code
         -

      Timeline: will not roll out until OpenZFS 2.0 version
      -

   ZoL repo move/rename (Matt)
   -

      From ZFSonLinux to OpenZFS (mentioned at the conference during Matt’s
      Talk)
      -

      Transfer ownership feature on Github is to be used (all PRs, issues,
      even URLs should be moved/redirected to the new home)
      1.

         If anyone has had a bad experience with this feature, please let
         us now
         -

      Should be a non-event for people doing development
      -

      Currently targeting to do this by the end of the year
      -

      Notes: We will keep all the existing ZoL resources like email list
      and IRC channel under the same name (ZFSonLinux, not OpenZFS) - OpenZFS
      mailing list will remain the canonical place for developer
discussions for
      new features. Leave user-centered questions or platform-specific
issues to
      per-platform mailing lists
      -

   Issue tracker curation (Matt)
   -

      Request for input from folks: Several issues that have been filed
      against ZoL end up being open for a long time and contain a lot of
      off-topic discussion (some getting close to an actual flamewar). What
      should we do about this?
      -

      Consequences of this issue:
      1.

         Discourages new members from getting involved with the community
         2.

         It is counter-productive for existing members- especially the ones
         who can fix the actual issue
         -

      Potential ways forward:
      1.

         Ignore these messages (status quo)
         2.

         Try to respond to every message (re-iterate the current status,
         explain the situation or dependencies on other issues, etc..)
- showing
         that we understand the situation - diffusing the situation a bit
         3.

         Hide the off-topic comments - this could backfire a bit and cause
         more impolite messages.
         4.

         A combination of 2 & 3 - where they do get a reply and then we
         hide the messages.
         -

      Idea for dealing with incoming bugs:
      1.

         After initial triaging or skimming through the issue, assign a
         specific tag or component and have a certain group of folks
responsible for
         each component.
         2.

         Have more folks help with labeling incoming issues
         -

            Unfortunately (and incredibly) github permissions
            <https://help.github.com/en/github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests>
            only allow people with write access to the repo to do this.
            -

      Discussion
      1.

         The most popular “potential ways forward” were i (status quo) and
         ii (try to respond to every comment)
         -

      Action Item: Brian and Matt will draft a proposal for this and
      present it in the next meeting and the mailing list.


On Tue, Nov 12, 2019 at 12:44 PM Matthew Ahrens <mahrens at delphix.com> wrote:

> The next OpenZFS Leadership meeting will be held today, November 12th,
> 1pm-2pm Pacific time.
>
> Today Jason King will give his postponed talk from the OpenZFS Developer
> Summit, titled "Securing the Cloud with ZFS Encryption"
>
> Everyone is welcome to attend and participate, and we will try to keep the
> meeting on agenda and on time.  The meetings will be held online via Zoom,
> and recorded and posted to the website and YouTube after the meeting.
>
> The agenda for the meeting will be a discussion of the projects listed in
> the agenda doc.
>
> For more information and details on how to attend, as well as notes and
> video from the previous meeting, please see the agenda document:
>
>
> https://docs.google.com/document/d/1w2jv2XVYFmBVvG1EGf-9A5HBVsjAYoLIFZAnWHhV-BM/edit
>
> --matt
>