official written documentation for DMB policies/rules/process/etc

[Robie Basak]

On Mon, Apr 04, 2022 at 05:05:40PM -0400, Dan Streetman wrote:
> Those are only a representative sample of questions to try to
> illustrate that the DMB operates mainly on 'institutional knowledge'
> (or 'tribal knowledge') instead of clear, documented policies and
> rules. I personally think this impacts the DMB when administrative
> issues cause the DMB to be unable to meet its Mission Statement, at
> least partially because I don't think the DMB actually has a Mission
> Statement.

No documentation is ever complete for any project really. There are
always gaps, and it's a continuous job to fix up the docs when gaps are
found.

I suggest that you (and all others) ask questions when you find gaps or
ambiguity, and seek to document the answers when you understand them.
Then we slowly reduce the gaps.

Please do a little bit at a time though. I don't think it's practical to
do it all at once.

For example, recently you asked where the election process was
documented, and where the private IRC channel was documented. In fact
these were already documented. These are both things that I took on at
some point, found them to be undocumented, and I documented them. If you
think the documentation is inadequate for these somehow, please could
you explain?

How about you start by describing the single most important thing you'd
like documented better, and we'll work on that?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/devel-permissions/attachments/20220516/4b618fff/attachment.sig>