[dev] Weekly Technical Meeting 4/18 11 am EDT

[Donald Sharp]

On Sun, Apr 16, 2017 at 7:03 PM, Donald Sharp
<sharpd at cumulusnetworks.com> wrote:
> https://bluejeans.com/9192742159
>
> Agenda
>
> 1) TSC Voting by maintainers ( Nominations have been under separate email )
>

Vote via survey monkey?  Totals public but who voted for what private

Maintainers is the list of people on the team 'Maintainers' at the
github website

Alistair -> Confirm with all nominee's that they are actually interested

Nominations are closed as of right before this meeting.

1 week voting period.

> 2) Criteria for inclusion on the FRR Website ( Alistair )

How do we include company logo's on the frrouting.org website.

This is a TSC decision.

Desire a reasonable explanation for inclusion?

Over time we will probably order based upon which organizations are
helping out more than others?

Who owns the website -> JR currently owns the keys.  He is on vacation
and once he gets back I will make sure that he interacts with the TSC
for key handover.

>
> 3) Branch names to prevent cornfusion ( Martin )

stable/3.0 is causing confusion because it implies 3.0 is actually released.

-> Update README to tell current version.
-> Get rid of stable and have dev and release?
stable/3.0 -> becomes dev/3.0
stable/2.0 -> becomes rel/2.0

Donald to do figure out how renames work and report back

>
> 4) Issue #335 discussion, split lib/vty.c into separate library ( osmoc )

<see issue #335 for update>

>
> 5) Stable/3.0 Issues
>

New Features go against -> master
Submit PR's against the appropriate stable/XX branch if it is a bug fix.

Lou and Martin would like an Auto-merge of stable/XX down to master as
things go in.  Martin has volunteered to look into an auto-merge tool
and how to make it work for us.

> 6) New Issues

<discussed and issues updated as appropriate>

>
> 7) PR's

<discussed and issues updated as appropriate>

>
> 8) Anything else?


snap packages are in for 2.0 and for 3.0 they need to probably be fixed.

we still need debian packages to be fixed up.

>
> This looks like a heavy week of issues that will be discussed.  Let's
> extend the meeting an additional 1/2 hour to 12:30 EDT?
>
> donald