Community Sync Notes

[Greg Mann <gr...@mesosphere.io>]

Hello all!
We had some great discussion yesterday during the Mesos community sync, you
can find the notes below.

Cheers,
Greg


Mesos Developer Community Sync

http://mesos.apache.org/community/

May 19, 2016

Time: 3pm PST

Location: Mesosphere HQ

Attendees:

Mesosphere: Greg M., Gilbert, Artem, Vinod, MPark, Joris, Joseph, Anand,
Kapil

Apple: James, Yan, Anindya

Intel: Connor, Nik

       Shopee: Haosdent

José Vanz

Agenda/Note:

   -

   How to improve the review process? [Vinod]
   -

      Survey of the group: are there issues with the current review process?
      -

         Feeling is that without direct contact with a committer, it can be
         hard to get feedback on tickets/patches
         -

         Have been concerns about the lack of transparency with respect to
         priorities. Roadmap has been created to help address this:
         https://cwiki.apache.org/confluence/display/MESOS/Roadmap
         -

      Picking up small patches from outside contributors is manageable, but
      whole features which sit outside the roadmap are difficult
      -

      Currently ~650 outstanding review requests
      -

         Most of these come from a small number of contributors
         -

         Encouraging contributors to discard RRs could solve this
         -

         ReviewBoard grooming will be done after MesosCon
         -

      Could solicit direct feedback from folks who have expressed concern
      -

      How do other projects manage a high volume of incoming patches?
      -

         Kubernetes has labels for the size of PRs: small, med., large, etc.
         -

         Other types of labels: “style”, “architectural”, “bug”, “feature”,
         “doc”
         -

      To improve efficiency and ship more patches, we can get better at
      identifying low-hanging fruit that is quickly committed
      -

      Small patches may not strictly need a shepherd before the RR is posted
      -

      The difficulty in some review processes may be due to issues in the
      code, rather than the review process itself
      -

      Could have a more hierarchical review process, with a “chain of
      trust” fanning out to larger numbers of people
      -

      More automation may be able to catch mistakes before the review stage
      -

      “Newbie” label in JIRA is meant to help new contributors find tasks -
      however, this currently needs grooming in JIRA
      -

      Having an actively-curated list of tickets which active committers
      are interested in for newbies could help
      -

   Mesos website work group [Vinod]
   -

      Solicited website assistance on the mailing list, received good
      interest
      -

      JIRA tickets have been tagged with the “project website” component
      -

   Update from performance isolation working group [Niklas/Connor]
   https://docs.google.com/document/d/1peagt7dNgU78hQbjOz1fwPTs-ftYFP9DXAyetCM7XcY/edit
   -

   Roadmap <https://cwiki.apache.org/confluence/display/MESOS/Roadmap>!
   [Everyone]
   -

      Regarding MESOS-3094: if a contributor makes a contribution that
      needs a Windows implementation but they can’t implement it themselves,
      reach out to Joris/Alex Clemmer and they can assist in the implementation
      or find folks who can.
      -

      Should send out an email to the dev/user lists about cutting the v1 RC
      -

   MesosCon Hackathon [Greg]
   -

      Should we plan any possible projects for the hackathon? Nope, calls
      will go out during the conference for folks to organize.