BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VEVENT DTSTART:20180423T123000Z DTEND:20180423T132000Z DTSTAMP:20180420T104809Z ORGANIZER;CN=atumball@xxxxxxxxxx:mailto:atumball@xxxxxxxxxx UID:0lg6ib7qjkumf6ftr90lh337ap@xxxxxxxxxx ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=jeff@xxxxxxxxxx;X-NUM-GUESTS=0:mailto:jeff@xxxxxxxxxx ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=nbabu@xxxxxxxxxx;X-NUM-GUESTS=0:mailto:nigelb@xxxxxxxxxx ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=srangana@xxxxxxxxxx;X-NUM-GUESTS=0:mailto:srangana@xxxxxxxxxx ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=gluster-devel@xxxxxxxxxxx;X-NUM-GUESTS=0:mailto:gluster-devel@glust er.org ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE ;CN=atumball@xxxxxxxxxx;X-NUM-GUESTS=0:mailto:atumball@xxxxxxxxxx ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=jahernan@xxxxxxxxxx;X-NUM-GUESTS=0:mailto:jahernan@xxxxxxxxxx CREATED:20180420T104809Z DESCRIPTION:BJ: \;https://bluejeans.com/205933580<br><br>We will talk a nd come to agreement on \;https://bugzilla.redhat.com/show_bug.cgi?id=1 564149<br><br>It was agreed that we will go ahead with format change automa tion\, so\, goal of this meeting is to pick the right options.<br><br>Goal is to get gluster's own `.clang-format` file. Once that file is agreed upon \, we will go ahead and create a job for fixing the patches for format\, an d also fix the codebase to get the formats.<br><br>Pre-work if you are inte rested\, read about : https://clang.llvm.org/docs/ClangFormatStyleOptions.h tml<br><br>Also pick a gluster file which would pass through agreed format\ , so you can validate how it looks after formatting. Instead of waiting for this to happen\, we can see is this good enough?<br><br>Few things we most ly agree:<br><br><pre class="bz_comment_text bz_wrap_commen t_text" id="comment_text_11" style="font-size: small\; white-space: pre-wra p\; word-wrap: break-word\; width: 50em\; color: rgb(0\, 0\, 0)\;"> !AllowS hortIfStatementsOnASingleLine !AllowShortLoopsOnASingleLine BraceWrapping(! AfterControlStatement) BraceWrapping(AfterFunction) BraceWrapping(!BeforeEl se) ColumnLimit(80) IndentWidth(4) PointerAlignment(PAS_Right) SpaceBeforeP arens(SBPO_Always) TabWidth(8) UseTab(UT_Never)</pre><br><pre class="bz_com ment_text bz_wrap_comment_text" id="comment_text_12" style= "font-size: small\; white-space: pre-wrap\; word-wrap: break-word\; width: 50em\; color: rgb(0\, 0\, 0)\;"><span style="font-family: Roboto\, Helvetic a\, Arial\, sans-serif\;"> BinPackParameters=true</span></pre><pre class=" bz_comment_text bz_wrap_comment_text" id="comment_text_12" style="font-size: small\; white-space: pre-wrap\; word-wrap: break-word\; w idth: 50em\; color: rgb(0\, 0\, 0)\;"><font face="Roboto\, Helvetica\, Aria l\, sans-serif"> </font>AlignEscapedNewLinesLeft=false</pre><pre class="bz _comment_text bz_wrap_comment_text" id="comment_text_12" st yle="font-size: small\; white-space: pre-wrap\; word-wrap: break-word\; wid th: 50em\; color: rgb(0\, 0\, 0)\;"> AlignConsecutiveDeclarations=true</pre ><pre class="bz_comment_text bz_wrap_comment_text" id="comm ent_text_12" style="font-size: small\; white-space: pre-wrap\; word-wrap: b reak-word\; width: 50em\; color: rgb(0\, 0\, 0)\;"><span style="font-family : Roboto\, Helvetica\, Arial\, sans-serif\;"> AlignConsecutiveAssignments= true</span></pre><pre class="bz_comment_text bz_wrap_commen t_text" id="comment_text_12" style="font-size: small\; white-space: pre-wra p\; word-wrap: break-word\; width: 50em\; color: rgb(0\, 0\, 0)\;"> AlwaysB reakAfterReturnType = true</pre><br><br>More options which we can discuss:< br><pre class="bz_comment_text bz_wrap_comment_text" id="co mment_text_11" style="font-size: small\; white-space: pre-wrap\; word-wrap: break-word\; width: 50em\; color: rgb(0\, 0\, 0)\;">!IndentCaseLabels<span style="font-family: Roboto\, Helvetica\, Arial\, sans-serif\;">SpaceBefore Parens = ControlStatements</span> </pre><pre class="bz_comment_text bz_wrap_comment_text" id="comment_text_11" style="font-size: small \; white-space: pre-wrap\; word-wrap: break-word\; width: 50em\; color: rgb (0\, 0\, 0)\;"><br></pre><br>I propose two steps as preventing history:<br> <br>* The commit before the mass-format-change commit will maintained as a separate branch. (No cost of space\, but everyone clearly knows where to go for history\, when git blame pointing to the commit of mass changes).<br>* Similarly\, to get history of pre-2009 (currently 'historic' repo)\, I per sonally feel moving \; https://github.com/amarts/glusterfs/commits/git- based-history-from-historic\, as a separate branch in gluster/glusterfs wou ld help. Again\, today people has to switch repositories for this.\n\n-::~: ~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~: :~:~::-\nPlease do not edit this section of the description.\n\nView your e vent at https://www.google.com/calendar/event?action=VIEW&eid=MGxnNmliN3Fqa 3VtZjZmdHI5MGxoMzM3YXAgZ2x1c3Rlci1kZXZlbEBnbHVzdGVyLm9yZw&tok=MTkjYXR1bWJhb GxAcmVkaGF0LmNvbWU5MjY1N2M0N2YzNGJiZWViZjY3MTI1ODk1MmQ5YmU5YmI3ZDg3MjA&ctz= Asia%2FCalcutta&hl=en&es=1.\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~: ~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::- LAST-MODIFIED:20180420T104809Z LOCATION: SEQUENCE:0 STATUS:CONFIRMED SUMMARY:Coding Standard: Automation TRANSP:OPAQUE END:VEVENT END:VCALENDAR
Attachment:
invite.ics
Description: application/ics
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-devel
