(Nov 29th, 19:30IST, 14:00UTC, 09:00EST)
BJ Link
- Bridge: https://bluejeans.com/205933580
- Download:
Attendance
- [Sorry Note] amye,
- <Add your name here>
Agenda
Action Items from last meeting (if any)?:
4.0 email from Shyam:
- Is your feature/issue updated with proper milestone?
- What is your preferred date for branch out?
- Dec 15th?
- Jan 15th?
- Quality/Testing focus?
Getting more contribution from outside (non-RH/non-FB):
- Are we right in expecting people to follow our guidelines?
- As a maintainer what would you do if someone posts a PR in github, and is not willing to follow the gerrit workflow?
- [Amar] I prefer to treat it same as how we agreed to proceed with continuing to rebase and send with
--authorintact to the contributor. - [Amar] At the moment, we should be more willing to accept any type of contribution, and respect author decision on how much they want to contribute.
- [Amar] Pointing them the gerrit workflow and asking to use our dev workflow is the right first step, but within a week if nothing happens, maintainers / peers taking the patch up and sending it on
--authors behalf is ideal.
- [Amar] I prefer to treat it same as how we agreed to proceed with continuing to rebase and send with
[Nigel?] Should the maintainers’s (or peer’s) +2 mandatory for merging a patch? Can other maintainers from different component merge the patches too?
- What is ideal time of wait?
Round Table?
Decisions
- Add if any
-----------------
Amar Tumballi (amarts)
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-devel
