Please note that This meeting involves 2 big topics related to developers/community, please try to attend the meeting.
1. Coding style (which can be very personal for many developers, great to agree and move forward on this).
2. GPL cure discussions
- The link given explains most of it. But if people need further help understanding the benefits/impact of this, we can arrange for a legal presence to explain things out (Best effort, as it depends on their availability)
On Tue, Apr 17, 2018 at 3:29 PM, Amar Tumballi <atumball@xxxxxxxxxx> wrote:
Meeting date: 14/18/2018 (April 18th, 2018), 19:30 IST, 14:00 UTC, 10:00 EDT
BJ Link
- Bridge: https://bluejeans.com/
205933580 - Download:
Attendance
Agenda
Format change proposal:
- Check the bug
- Provide feedbacks
- We want to do a big bang format change with clang-format.
- Which format should we start with as base? Google/LLVM/Mozilla/Webkit/
Chromium
- Samples present in repo. NOTE: Samples generated with indent as 4 spaces.
- Google Style Guide
- LLVM Style Guide
- Mozilla Style Guide
- WebKit style guide
- Chromium style guide
- When do we want to make this change? Before the 4.1 branching seems like a good time to make vast changes.
Gluster’s Adoption of GPL cure period enforcement
- What is it?
- How to go about implementing it?
Automation Update:
- Run regressions with brick multiplex directly from Gerrit now with a keyword rather than hacky temporary review requests. Keyword is ‘run brick-mux regression’. Example: https://review.
gluster.org/#/c/19734/ - More automation moving to Python so we have the ability to write unit tests. If you are going to write a complicated shell script as a test runner, please get approval from CI component maintainers.
- We’ve been testing Facebook’s distributed test runner and have managed to get it working. Time for regression drops with every new machine added to the pool. Targetting a few weeks to bring it to production.
- Github Label check is now enforced:
- Need help from others to identify the needs for going to give the flag.
- As ‘ndevos’ asked, we need to highlight this in Developer Guide and other places in documentation.
- Can we fix the ‘gluter spec’ format and ask people to fill the github issues in that format? So that it becomes easier to give the flags.
Regression failures
trash.tandnfs-mount-auth.tare failing frequently. - git bisect shows https://review.gluster.
org/19837 as possible suspect.- Need to resolve soon as some critical patches are failing regression.
Release timelines:
- Can we extend branching out by a week or two? to compansate for github flag enforcement?
- Target GA date should remain same.
Round Table:
- [Name] Note
-----Feel free to add more topics before meeting @ https://hackmd.io/yTC-un5XT6KUB9V37LG6OQ?both
Amar Tumballi (amarts)
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-devel
