to the Marpa Team. At the moment, this is simply me.
Other projects of the size and complexity of Marpa are managed by multi-person
teams, and I hope that will become the case with Marpa.
Thanks, jeffrey kegler
The consensus in this forum seems be against the uploading of PDF's,
or at least of ones of the size I am asking about. So I won't do it.
-- jeffrey kegler
On Mon, Jul 18, 2011 at 2:07 PM, Andreas J. Koenig
andreas.koenig.7os6v...@franz.ak.mind.de wrote:
On Sun, 17 Jul 2011 09:43:01 -0700
, jeffrey kegler
I'd like feedback on a question. My feeling is that internals documentation
is important, that disk is relatively cheap, and that I should include the
PDF file that contains Marpa's internal documentation with the CPAN
distribution. But I'd like to know if others agree.
Marpa::XS, my XS version
, with the assurance that they do not
have to depend on any response from me.
By way of justifying my reserving the name Marpa: Marpa predates
PAUSE, and Marpa is a name unlikely to be of use to anyone
else.
Thanks, Jeffrey Kegler
On Mar 31, 2:51 am, tim.bu...@pobox.com (Tim Bunce) wrote:
It would be handy if there was a way for authors to indicate that
new maintainers are sought. Perhaps via the META.yaml/(.json) file.
It would also be handy if that (or another) mechanism would also
indicate orphaned modules -- modules
with the
following:
Modules listed in this section are necessary to build and install the
given module. If a listed module is necessary for regular usage as
well as the build and install, the listed module also needs to be
specified using the 'requires' argument.
Thanks, jeffrey
On Mar 18, 5:23 am, pagalt
? META.yml, which is created by
Module::build has a Marpa: 0.100 line, which I hoped would suffice.
3.) Is this a problem with some of the cpantesters setups.
thanks, jeffrey kegler
