New code and bus factors
jones.chris.g at gmail.com
Tue Aug 13 08:53:28 PDT 2013
Agreed. I think the only way anything like that would work is making a
policy that code changes on a scale that would affect the high-level design
overview would have to be proposed as a change to that design-overview doc
(and committed along with the code changes).
On Tue, Aug 13, 2013 at 3:38 AM, Robert O'Callahan <robert at ocallahan.org>wrote:
> On Tue, Aug 6, 2013 at 12:34 PM, Chris Jones <jones.chris.g at gmail.com>wrote:
>> rr is accumulating some new code that I'd like to document at a higher
>> level, since the code itself is somewhat obscure. Code comments and
>> permanently semi-out-of-date wiki pages work OK, but I'm wondering if
>> anyone has better ideas or strong feelings. I've thought of trying these
>> in the past
>> - keep a slide deck source (S5 or LaTeX type thing) checked into the
>> repo and keep as up to date as possible. "Design ideas" can be patches
>> that add new slides to the deck. And the revision history of the deck is
>> inline with the code's.
>> - similar to above, but with a "tech report" style document in the repo.
> They sound like good ideas but I don't have a strong feeling about what
> would work. Keeping anything up to date that's not the code is hard.
> Jtehsauts tshaei dS,o n" Wohfy Mdaon yhoaus eanuttehrotraiitny eovni
> le atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?o Whhei csha iids teoa
> stiheer :p atroa lsyazye,d 'mYaonu,r "sGients uapr,e tfaokreg iyvoeunr,
> 'm aotr atnod sgaoy ,h o'mGee.t" uTph eann dt hwea lmka'n? gBoutt uIp
> waanndt wyeonut thoo mken.o w *
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rr-dev