[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#545548: debian-policy package should include a pointer to http://wiki.debian.org/PolicyChangesProcess



On Tue, Sep 15 2009, Russ Allbery wrote:

> Manoj Srivastava <srivasta@debian.org> writes:
>
>>      These series of patches add easy to edit sources for a README file,
>>  for documenting the Policy change process, and finally, the upgrading
>>  checklist. The source format is designed to be easy to read and edit,
>>  and is rendered into a pretty text format, as well as HTML, as long
>>  as a recent versionof Emacs is found. The rendered files are shipped
>>  in the package to avoid a build dependency on Emacs; the idea is that
>>  policy editors have emacs isntalled and pre-create the rendered files
>>  before release, kind of like the bad old days of autotools.
>
> I'm okay with that, personally.  It'll give me something new in Emacs
> to play with.  It's not entirely ideal, but if it's expedient, I have
> no problems.

> In the long run, using something like Markdown or reStructured Text for
> documents like this that aren't full manuals might be a good idea.

        Well,I can't live without the getting things done stuff in org
 mode, and I do find  raw org-mode more readable than markdown or ReST,
 but I have no objections if someone converts these docs to the  formats
 you mentioned.

On Tue, Sep 15 2009, Bill Allombert wrote:

> Well I do not have emacs installed...

        That could be an issue. Well, I would be willing to take over
 the burden of maintaining these documents; and for the README and
 Process documents this is not much of an issue (we hardly ever change
 them), but it could be a problem with the upgrading-checklist.org, if
 you think emacs23 is too big a beast for you.

> Did you by any chance numbered your patches 0/3, 1/3 and 3/3 ?
> Did that count as one 'Manoj Wonderful Typo' (MWT) ?

        The mails were generated by git send-email, so I don't think
 that was the case. Perhaps it got eaten by a spam filter?

        So, I am pushing out the branch bug545548-srivasta out, y'all
 can do the diff yourself. I rebased it against latest master before
 pushing. 

        manoj
-- 
The second best policy is dishonesty.
Manoj Srivastava <srivasta@debian.org> <http://www.debian.org/~srivasta/>  
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C



Reply to: