[178940] in North American Network Operators' Group
Re: BCOP appeals numbering scheme -- feedback requested
daemon@ATHENA.MIT.EDU (Rob Seastrom)
Sun Mar 15 12:15:25 2015
X-Original-To: nanog@nanog.org
To: Charles N Wyble <charles@thefnf.org>
From: Rob Seastrom <rs@seastrom.com>
Date: Sun, 15 Mar 2015 12:15:22 -0400
In-Reply-To: <1EED65CF-0861-4F60-97D1-CB3CF471C65A@thefnf.org> (Charles N.
Wyble's message of "Sun, 15 Mar 2015 10:17:38 -0500")
Cc: "bcop-support@nanog.org" <bcop-support@nanog.org>,
"nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
Charles N Wyble <charles@thefnf.org> writes:
> Use a git repository.
> Make tagged releases.
> This enables far easier distributed editing, translating, mirroring etc. And
A fine idea in theory, but not quite as much traction in reality as bcp38.
Creating a need for a BCP for retrieving BCPs so that you get the
right version rather than typing "git clone" and erroneously referring
to whatever is tagged "-develop" seems like a Bad Plan.
It's also not a really reasonable method for distributing
point-in-time documents once people are done with collaborating on
creating them. Most end consumers will not care about the change
history.
> you can still do whatever release engineering you want.
Sure.
> A wiki is a horrible solution for something like this.
Agree 100%
-r
