[Gluster-devel] Invitation: Coding Standard: Automation @ Mon Apr 23, 2018 6pm - 6:50pm (IST) (gluster-devel at gluster.org)

[atumball at redhat.com]

You have been invited to the following event.

Title: Coding Standard: Automation
BJ: https://bluejeans.com/205933580We will talk and come to agreement  
on https://bugzilla.redhat.com/show_bug.cgi?id=1564149It was agreed  
that we will go ahead with format change automation, so, goal of this  
meeting is to pick the right options.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, and also fix the codebase  
to get the formats.Pre-work if you are interested, read about :  
https://clang.llvm.org/docs/ClangFormatStyleOptions.htmlAlso 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?Few things we mostly  
agree: !AllowShortIfStatementsOnASingleLine !AllowShortLoopsOnASingleLine  
BraceWrapping(!AfterControlStatement) BraceWrapping(AfterFunction)  
BraceWrapping(!BeforeElse) ColumnLimit(80) IndentWidth(4)  
PointerAlignment(PAS_Right) SpaceBeforeParens(SBPO_Always) TabWidth(8)  
UseTab(UT_Never)  BinPackParameters=true  AlignEscapedNewLinesLeft=false  
AlignConsecutiveDeclarations=true  AlignConsecutiveAssignments=true  
AlwaysBreakAfterReturnType = trueMore options which we can  
discuss:!IndentCaseLabelsSpaceBeforeParens = ControlStatements I propose  
two steps as preventing history:* 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).* Similarly, to get history of pre-2009  
(currently 'historic' repo), I personally feel moving   
https://github.com/amarts/glusterfs/commits/git-based-history-from-historic,  
as a separate branch in gluster/glusterfs would help. Again, today people  
has to switch repositories for this.
When: Mon Apr 23, 2018 6pm – 6:50pm India Standard Time
Calendar: gluster-devel at gluster.org
Who:
     * atumball at redhat.com - organizer
     * jeff at pl.atyp.us
     * nbabu at redhat.com
     * srangana at redhat.com
     * gluster-devel at gluster.org
     * jahernan at redhat.com

Event details:  
https://www.google.com/calendar/event?action=VIEW&eid=MGxnNmliN3Fqa3VtZjZmdHI5MGxoMzM3YXAgZ2x1c3Rlci1kZXZlbEBnbHVzdGVyLm9yZw&tok=MTkjYXR1bWJhbGxAcmVkaGF0LmNvbWU5MjY1N2M0N2YzNGJiZWViZjY3MTI1ODk1MmQ5YmU5YmI3ZDg3MjA&ctz=Asia%2FCalcutta&hl=en&es=0

Invitation from Google Calendar: https://www.google.com/calendar/

You are receiving this courtesy email at the account  
gluster-devel at gluster.org because you are an attendee of this event.

To stop receiving future updates for this event, decline this event.  
Alternatively you can sign up for a Google account at  
https://www.google.com/calendar/ and control your notification settings for  
your entire calendar.

Forwarding this invitation could allow any recipient to modify your RSVP  
response. Learn more at  
https://support.google.com/calendar/answer/37135#forwarding
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-devel/attachments/20180420/caf37823/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 5856 bytes
Desc: not available
URL: <http://lists.gluster.org/pipermail/gluster-devel/attachments/20180420/caf37823/attachment-0001.ics>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: invite.ics
Type: application/ics
Size: 5947 bytes
Desc: not available
URL: <http://lists.gluster.org/pipermail/gluster-devel/attachments/20180420/caf37823/attachment-0001.bin>