[Monotone-devel] Contributed scripts and how to handle them...

[Richard Levitte]

Sparked by a (somewhat heated ;-)) discussion I had on IRC with Thomas
in late december (*), I've started thinking that the contrib directory, 
while having served us well for a while, might not serve everyone who
wishes to contribute their little nuggets, or have them maintained
separately without having to have write permissions on n.v.m.

Looking at the contents of contrib/, there are things that are aged or
completely superceded by newer monotone commands, or other scripts and
so on.

So, following what Thomas was thinking, we probably should clean out
the contrib directory and put the contents somewhere else, except for
scripts that we really want to ship as part of monotone (and that we
test).  Maybe a place on the wiki would be a start, with a page for
each contributed thing, either refering to a repo somewhere or with
the source directly in the page (similar to plugin contributions that
you can see with other projects).

I'd like to, however, keep the stuff that we use on code.monotone.ca
and the bash completion scripts (I'm about to write a test for it),
and perhaps a few others that are regularly used.  If you have a pet
script in there, please yell, and possibly provide a kind of test for
it.

Ideas are welcome for how the tests should be structured.  For fairly
obvious reasons, lua will not be enough (bash completion testing
requires the use of expect, there's not much lua in there ;-)).

Cheers,
Richard

(*) starting here:
http://colabti.org/irclogger/irclogger_log/monotone?date=2011-01-01#l54

-- 
Richard Levitte                         address@hidden
                                        http://richard.levitte.org/

"Life is a tremendous celebration - and I'm invited!"
-- from a friend's blog, translated from Swedish