Craig Russell wrote on 4/4/17 7:20 PM: > >> On Apr 2, 2017, at 5:42 PM, Shane Curcuru <[email protected]> >> wrote: >> >> Craig Russell wrote on 4/2/17 7:54 PM: ...snip...
>> The larger question: is there any standard structure that we can >> use to create/display/manage documentation for Whimsy bits? >> >> We have a lot of different corporate and infra processes that >> whimsy helps with, but is not necessarily the canonical command >> line way to do things. Is there some way we can write once, read >> everywhere the bits of help docs for our processes? 8-) > > I've tried to at least capture what the secretary role does in > https://svn.apache.org/repos/private/foundation/officers/personnel-duties/secretary.txt Excellent! > Even though that does not include the mechanical process of doing > things. > > For the board processes, we formerly had agenda.txt which would be > mechanically edited by each pmc chair, officer, and director. > Indentation did not matter. But, indentation does matter, but it is > automatic if using whimsy. If not using whimsy, the entire process > can be upset by a bad commit. Remember Sally's complaints about not > being able to grok svn and vi? Do we really need to go back to that > era? > > Stepping back a bit, it's not clear that there is a command line way > of doing everything that secretary does. Without Whimsy, the job > would be a mid-level part time paid position, not a volunteer > position, at least by me. No kidding. I think I was unclear: my point is: is there some standard way/place we can write documentation fro the various little bits of processes that can be re-used both in high-level docs like /governance/, but also in specific whimsy processes for the individual steps of a process. I'm not suggesting any tool changes with that - just pondering ways to document all these little steps in a way that could *also* be put together into documentation that explains the larger process. I agree - we need Whimsy's automation of individual process steps, and I welcome the day we store formal corporate records in some self-validating structured way... 8-) - Shane -- - Shane https://www.apache.org/foundation/marks/resources
