Re: Device tree binding documentation

[Matt Sealey <matt-sEEEE4iEDtaXzmuOJsdVMQ@public.gmane.org>]

Grant Likely wrote:
> On Tue, Oct 28, 2008 at 10:58 AM, Matt Sealey <matt-sEEEE4iEDtaXzmuOJsdVMQ@public.gmane.org> wrote:
>>
>> Yoder Stuart wrote:
>>>  So my vote is to maintain bindings as plain text files.
>> Just like the real elections I don't actually have a vote here,
> 
> If that were true you wouldn't have been in the 'to:' list.

I got an Obama campaign leaflet through the door the other day, too :)

>> but can I put my oar in that after a certain review process and
>> time has passed and the binding stabilizes, these get published
>> as PDF
> 
> I think that is reasonable if it is something people find useful or
> more accessible.

I guess we would need to decide how those documents are published
without using proprietary software, then, and easily committed to
another git repository (or the same one just in a published form).
I don't suppose office xml is a good choice? It should be flexible
enough and similar enough that sections and layout do not change a
great deal, and git can easily produce diffs?

For another time maybe. Continue on the discussion. I really like
the git repo/wiki idea. But I do not agree that a web browser is
inefficient; a wiki for editing changes (for registered users
assigned to a "project") in a collaborative way is probably far
better in some respects than using Kate and xdiff (certainly
less difficult in some other respects), if you want to quickly
look at changes or so, or make an update to a section.

If we didn't like web browsers that much then we wouldn't have
patchwork, for example, which is an insanely useful tool..
although the same care must be taken not to do what patchwork
just did and go through a lovely rewrite or software update
and suddenly lose years of patch reference URLs :D

I understand not wanting to have to keep a browser open to read
a forum instead of a mailing list, but this is something a
little different. Wouldn't collaboratively editing a wiki allow
multiple users to submit changes to a page (in "private"), yet
ultimately have a Responsible Person collect those changes into
a bundle and submit that as a patch to devicetree-discuss when
development is complete? Branching and checkouts in git would
work the same way but you wouldn't have to be sitting at your
desk (with git) to make a tiny update or collaborate with your
colleagues while out in the field or at a customer site.

-- 
Matt Sealey <matt-sEEEE4iEDtaXzmuOJsdVMQ@public.gmane.org>
Genesi, Manager, Developer Relations