<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font face="Ubuntu">Hi <font face="Ubuntu">D</font>onald, all,</font></p>
<p>Since I can't access to google doc from my office due to internal
proxy rules, and perhaps other persons are in the same situation,
why not create a new 'Meetings' channel in Slack for that purpose
? <br>
</p>
<p>We could post meeting announcement, not only regular but also
extra meetings, with agenda and bluejeans info. Minutes will
follow that could be commented. Files could be also shared if
needed.<br>
</p>
<p>Regards</p>
<p>Olivier<br>
</p>
<br>
<div class="moz-cite-prefix">Le 22/02/2018 à 14:55, Donald Sharp a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:CAK989yfOtNKy1xcjE22k6KGuqj7VBL-zeEO-bDn7baDLPPHzAg@mail.gmail.com">
<pre wrap="">I've created the PR that adds to our documentation our release
schedule information:
<a class="moz-txt-link-freetext" href="https://github.com/FRRouting/frr/pull/1784">https://github.com/FRRouting/frr/pull/1784</a>
donald
ps - And thanks Olivier for pushing the issue on note taking!
On Tue, Feb 20, 2018 at 12:32 PM, Olivier Dugeon
<a class="moz-txt-link-rfc2396E" href="mailto:olivier.dugeon@orange.com"><olivier.dugeon@orange.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi all,
Here it is the minutes of the today's meeting. Don't hesitate to modify
them.
Regards
Olivier
------------ FRRouting Metting Minutes - 20th of February 2018
---------------
1. Discuss and Finalize the Release Schedule
Donald has presented the new release schedule (see
<a class="moz-txt-link-freetext" href="https://docs.google.com/presentation/d/1GdqVFn7s7kkOV_wDz7oJ1IYr_EVONuPX9t4TMHeGCMs/edit?usp=sharing">https://docs.google.com/presentation/d/1GdqVFn7s7kkOV_wDz7oJ1IYr_EVONuPX9t4TMHeGCMs/edit?usp=sharing</a>).
Some questions has been raised:
Master branch still remains open after pull a dev branch
Bug fix Pull Request must be submitted on dev branch as well as master
separately to avoid cherry-pick. CI run on both.
Security fix duration has been precise on the document.
2. Discuss meeting notes
The team ran into memory leak several times about decision taken during
meeting but not write nor registered. Transcript minutes from a registered
meeting seems a too huge task and leave them as raw files is not easy to
use. Olivier suggest to take minutes in turn. As we are at least 15
attendees per meeting, this means take notes once every 3/4 months. Not too
much even if it is a drudgery.
Participant approve. Olivier volunteers to start and Lou suggest to put the
minutes in a sharing tools like Google Doc. Donald will setup appropriate
sharing space and Olivier mention that a link to this place must be added in
the Wiki. For the first time, minutes will be circulate on the mailing list
and then upload on the sharing space once setup.
3. Issue review
Not too many issue to review. Donald live update the Issue (see GitHub).
Just to mention 2 mains decisions:
#1763: Donald will create a new Pull Request to backport the feature in 3.0
release
#1769: Philipp has presented a scheam from Cisco on how BGP FlowSpec could
work. Cumulus will provide some base code to progress on that part and
Donald will schedule a meeting to discuss the architecture. Olivier mention
that OpenDayLight is a good candidate as controller to make tests.
4. Pull Request review
Donald live update the different PR (See GitHub). Just to mention few of
them:
#1689: Martin will propose an update to this Pull Request to solve the issue
with 'systemctl relaod frr' when the frr-reload.py is not present or
python-ipaddr not install.
#1711: Renato needs one more day for a final review
#1739: Donald will schedule a dedicated meeting (Friday noon) to discuss
this PR
#69 (topotest): Lou suggest to rebase this PR to avoid the problem of MPLS
detection in armv7 platform
Le 20/02/2018 à 16:09, Donald Sharp a écrit :
Today's Technical meeting is at the same bat time and place. If you
would like to attend please let me know, I'll get you an invite.
1) Discuss and finalize release schedule:
<a class="moz-txt-link-freetext" href="https://docs.google.com/presentation/d/1GdqVFn7s7kkOV_wDz7oJ1IYr_EVONuPX9t4TMHeGCMs/edit?usp=sharing">https://docs.google.com/presentation/d/1GdqVFn7s7kkOV_wDz7oJ1IYr_EVONuPX9t4TMHeGCMs/edit?usp=sharing</a>
2) Discuss meeting notes
3) Discuss New Issues
4) Discuss PR's in progress.
donald
_______________________________________________
dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:dev@lists.frrouting.org">dev@lists.frrouting.org</a>
<a class="moz-txt-link-freetext" href="https://lists.frrouting.org/listinfo/dev">https://lists.frrouting.org/listinfo/dev</a>
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<br>
</body>
</html>