::Builder is
actually just fine.
So yeah, Test2. Or, if the new architecture does not have the same
limitation, some entirely new top-level namespace, like Check::,
Trial::, etc.
[1] That might also be a data point for saying that a plan ending a
TAP stream should not be required to produce
roblem I still have to resolve is what name we put
> non-article-oriented things like "The Lancaster Consensus" info under.
>
That probably fits under Policy::Org::Toolchain::Consensus::Lancaster.
--
Philippe Bruhat (BooK)
Solve a problem before you become part of it.
cludes in
most of his distributions fit under Policy::Author::DAGOLDEN?
--
Philippe Bruhat (BooK)
Just because you believe it does not make it so.
(Moral from Groo The Wanderer #54 (Epic))
On Wed, May 06, 2015 at 08:48:18PM +1200, Kent Fredric wrote:
> On 6 May 2015 at 20:44, Philippe Bruhat (BooK)
> wrote:
>
> > Just thinking that the "Org" intermediate bit is not really needed
> > (and ugly). The said organizations are big/important enough that the
al location
- static site, easy to generate locally
- easy to add/remove repositories (and documents)
- any source format can be used, so long as it can be turned to HTML
--
Philippe Bruhat (BooK)
Honesty is its own reward. Dishonesty is its own punishment.
(Moral from Groo The Wanderer #30 (Epic))
ng
> contribution systems" thing )
Hey, this is exactly what I was proposing in my other email: aggregating
documents that live on specific branches of specific directories.
I'll try to quickly produce a proof-of-concept.
--
Philippe Bruhat (BooK)
When you create a climate of pea
On Thu, May 07, 2015 at 09:30:59AM +0200, Philippe Bruhat (BooK) wrote:
> On Thu, May 07, 2015 at 06:14:57PM +1200, Kent Fredric wrote:
> >
> > Even some git based workflow that published to github pages with some
> > atrocity of jekyll would be better for this task IMH
On Thu, May 07, 2015 at 01:37:55PM +0200, Philippe Bruhat (BooK) wrote:
>
> The current reference documents are obtained from these repositories:
> - https://github.com/neilbowers/history-of-cpan.git
>
> Unless someone objects, I'll put this live in a day or two.
>
Becau
nto a static website via my own
Wallflower (https://metacpan.org/pod/wallflower). Of course, everyone
has to build his own! ;-)
--
Philippe Bruhat (BooK)
None suffer so much in a war as those who strive to end it.
(Moral from Groo The Wanderer #51 (Epic))
> - associates policies with tags
> - define desired policy presentation order
> - define visibility of policies at the top level ( ie: so that deprecated
> policies don't list on the main lists )
>
> etc.
Good idea! This special config file should be optional, though.
--
Philippe Bruhat (BooK)
Sometimes only by losing the battle can you win the war.
(Moral from Groo The Wanderer #117 (Epic))
tion, *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))
t to judge water quality is that it only
> considers the most recent version of every dependency. That is, it
> samples the water quality once, ignoring the factory upstream that shits
> its pants a coupla times a year.
Well, it tells you if there's *currently* shit in the water.
ernet Archive has some old copies:
https://web.archive.org/web/20041010044220/http://www.astray.com/cpanstats/
> Then, if you're planning on making a controversial change to module Y,
> you have a list of users whom you can warn or poll for advice.
Preventing anonymous posts would also prevent some popularity contest
and ballot stuffing.
--
Philippe Bruhat (BooK)
Just because you do not see it does not mean it is not there.
(Moral from Groo The Wanderer #85 (Epic))
ve been thinking about proposing to hold it in Lyon
again in 2017.
I look forward to seeing the summary of all the feedback Neil has been
gathering from the participants, as I'm quite certain it will give the
next organisers many useful clue for organising a very successful event.
--
Philipp
e distribution"
would basically mean "apply the patch that creates the whole tree". This
does not work if the tree does not contain files that haven't changed
between versions.
Depending on what you meant, that could be an issue for you too.
--
Philippe Bruhat
system for the packlist files.
>
Or the distribution -> packlist index can be store in a well known location
(top of the install directory I suppose).
> Might seem slow, but on SSDs scanning the filesystem like that is super
> super fast.
--
Philippe Bruhat (BooK)
When you wander
16 matches
Mail list logo
