[Gluster-Maintainers] Meeting date: 10/17/2017 (Oct 17th, 19:30IST, 10:00EST)

[Amar Tumballi]

<https://hackmd.io/MYTgzADARgplCGBaA7DArMxAWAZvATIiFhJgCYarBQCMCYIQA===?both#bj-link>BJ
Link

   - Bridge: https://bluejeans.com/205933580
   - Download: <To be updated after the meeting>

<https://hackmd.io/MYTgzADARgplCGBaA7DArMxAWAZvATIiFhJgCYarBQCMCYIQA===?both#attendance>
Attendance

   - [Sorry Note]
   - <comma separated value>

<https://hackmd.io/MYTgzADARgplCGBaA7DArMxAWAZvATIiFhJgCYarBQCMCYIQA===?both#agenda>
Agenda

   -

   AI from previous week
   -

      Coding standard (if time permits)
      https://review.gluster.org/#/c/17651/
      - AI: Maintainers please review, add all maintainers as reviewers
         [Mostly Done, Good to merge]
         - Possibly add Go coding standards [Kaushal - Not Done yet]
            - Would be good to have it by the time of merging of GD2 to
            mainstream
         -

      3.13 -> 4.0 Additional quality tracking [Pending Votes]
      - Reduce overall coverity defects/issues
         - Improve on code coverage across each component
         - Glusto runs should pass
         - All components not meeting above guidelines will block the
         release, and hence need attention
         - The base line will be compared to 3.12 and announced just post
         branching for 3.13, giving teams 6 weeks to meet the required targets
         - Future releases, may track an actual %age increase/decrease in
         the metrics
         - Thoughts?
            - Get more tests into Glusto, mandate this in 4.0
               - AI: Check back with Nigel and see if Glusto code coverage
               metrics can also be gathered [Shyam]
            - Accept: Shyam, Amar, Nigel,
            - Reject: <names>
         -

   Gluster Summit
   - Any specific off-hour meetings?
         - Error code finalizing (issue #280
         <https://github.com/gluster/glusterfs/issues/280>)
         - Protocol changes
         <http://lists.gluster.org/pipermail/gluster-devel/2017-August/053462.html>.
         Email has some responses, but need a list made and agreement on
         implementation.
         - Should we have Technical Leadership committee ?
            - It was proposed in one of the earlier maintainers meetings.
            Do we need it to pursue it further?
         - gfproxy? GD2?
         - Experimental Demos? : RIO / cgroups effort / etc etc…
      -

   Gluster 4.0
   - Review backlog piling up. Need help
      -
   -

   Round Table

----

Feel free to add your points @
https://hackmd.io/MYTgzADARgplCGBaA7DArMxAWAZvATIiFhJgCYarBQCMCYIQA===?both
-- 
Amar Tumballi (amarts)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/maintainers/attachments/20171017/d7d50985/attachment.html>