On Mon, 2007-22-01 at 14:00 -0500, Guy Hulbert wrote:
> I will create a separate plugin links page and add everything I can
> find
> for tomorrow.
I have started work on this and I will start the wiki page in a few
minutes. The first and easiest thing to do was to checkout the
'contrib' tree from subversion and try my auto-doc script.
[ I will follow-up to the wiki and post the notes below. That will
simplify correcting my mistakes and cut down on offtopic threads :-) ]
Unfortunately each of the two contributors has chosen a different layout
and neither layout is compatible with the script that I wrote.
It would be convenient if each contrib directory had the following
structure, which mirrors the trunk, branches, and tags:
plugins/ plugins only
t/plugins/ plugin tests
lib/ core changes
config/ plugin configs
where any of these might not exists (presumably there would usually be
at least one file under 'plugins/'. This would simplify moving
contributions into the core as well ... or not.
In the case of hjp, who has provided all the code required to build .rpm
files for each plugin, I would put the existing content under
rpm-source
(or something like that). In the case of vetinari it is sufficient to
move everything down one level.
I am going to make a local structure as described above for the purposes
of generating documentation. I will make it available from a web server
(possibly under subversion or svk, if I have time) but not until next
week.
However, I will also provide links (in documentation) back to the
originals and on the wiki I will provide links ONLY to the original
code. I think uploading copies from subversion repositories to the wiki
should be discouraged as it will lead to confusion when the repository
copy is updated and the two sources then disagree.
I think the best solution, long-term, is to provide each wiki user
'USER' a tree: contrib/USER in subversion but I realize that it would be
a bit of work to set up and coordinate. I will look at the details of
how to do that (it is on my todo list anyway) but that may take a bit
longer.
--
--gh
