Re: Berlin Consensus document posted to toolchain-site
[email protected] ("Philippe Bruhat (BooK)")
| Newsgroups | perl.cpan.workers |
|---|---|
| Message-ID | <[email protected]> |
On Sat, May 09, 2015 at 02:38:02PM -0700, John SJ Anderson wrote: > On Sat, May 9, 2015 at 10:57 AM, David Golden <[email protected]> wrote: > > > > > https://github.com/Perl-Toolchain-Gang/toolchain-site/blob/master/berlin-consensus.md > > > > I've posted the Berlin Consensus document. > > > > Perhaps this will come in the "color commentary" version, but I wonder if > there was any discussion of how to best handle the situation where a module > starts "way downstream" but ends up "way upstream" because of popular > adoption, *if the module author doesn't agree to the "way upstream" > recommended policies*. The answer was "fork nicely". -- Philippe Bruhat (BooK) To flaunt your strength is to make it your weakness. (Moral from Groo The Wanderer #25 (Epic))