On Sat, May 9, 2015 at 8:28 PM, Aristotle Pagaltzis
wrote:
> It was also brought up that if you are way upstream yourself with one of
> your modules, you shouldn’t take dependencies on things willy nilly – as
> that puts maintainers in an upstream position they may not want to be
> in. Rather bef
* John SJ Anderson [2015-05-09 23:40]:
> 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*.
Y
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 wrote:
>
> >
> > https://github.com/Perl-Toolchain-Gang/toolchain-site/blob/master/berlin-consensus.md
> >
> > I've posted the Berlin Consensus document.
> >
>
> Perhaps this will co
On Sat, May 9, 2015 at 10:57 AM, David Golden 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 ho
https://github.com/Perl-Toolchain-Gang/toolchain-site/blob/master/berlin-consensus.md
I've posted the Berlin Consensus document.
I'll be working on my "annotated" version with color commentary for my blog
over the next week or so.
Regards,
David
--
David Golden Twitter/IRC: @xdg
On 9 May 2015 at 09:54, Philippe Bruhat (BooK)
wrote:
>
> Simple template with basic HTML around.
>
> For now, only markdown format is supported, but I intend to support
> additional formats as needed.
I think some of this question I was looking for information as to how the
document hierarchy
6 matches
Mail list logo
