Clearly organize text to pre-approval required if Per-Diem Lodging rates exceeded.

Based on discussion with Conservancy's Treasurer, I reworked this section
to clearly state that Conservancy can approve higher rates for hotels, but
that such approval should be done before travel begins. I also cut down
some of the extra detail in this section that I think is obvious (i.e.,
how to use the GSA website).

Fixed URL changes.

Many changes.

Format converstion to asciidoc.

- edited "competitive bids" language to broaden scope from software developers to all "technical service contractors."
- made a few grammatical and wording changes to the section re: Community Members' (lack of) influence over a Project's technical direction

s/some/substantial/g because the real concern is a serious substantial
interest rather than a de minimus.

Fixed m-dash typo.

Be clear about what state and federal laws we mean.

cjl asked:
I believe it is important to be very specific about reimbursement for
travel as this is probably one of the moret common forms of financial
transactions in many projects. It would be unfortunate if PLC members
were made ineligible (or unduly burdened) in requesting travel funding
on an equal footing with other project members.

We've explicitly stated now that legitimate reimbursements are not
compensation.

Typo fix.

cjl raised this issue:

As a practical matter, this one is difficult may be difficult for
Sugar Labs to achieve (particularly, "permitted to hear") as our PLC
discussions are held in an open IRC forum and openness is a
philosophical position within our project. Can we narrow this
restriction for PLC members to "participate" while allowing
"hearing" on an equal footing with all project members?

This change reworks that section to allow for after-the-fact reading of
logs and/or minutes by the conflicted Person, but does not allow them to
attend the meeting except to disclose facts, etc.

cjl suggests that:
While "available bandwidth" is common enough jargon in our community,
perhaps this should be changed to "interest and availability".
We accepted the change since "bandwidth" is indeed jargon.

cjl from the Sugar Labs committee raised the following concern:

In theory, engagement in the proposal drafting process might allow a
conflicted person to "tip the scales", thereby justifying their
exclusion. However; in practice, it may be that the conflicted
person is the only PLC member with the requisite technical expertise
or situational awareness to draft a suitably detailed proposal. Is
it possible to acknowledge that the rest of the PLC should generally
be capable of taking advantage of the conflicted persons special
knowledge and contributions to the drafting without allowing the
creation of "an uneven playing field".

This change allows the conflicted PLC Person to "disclose material facts
and to respond to questions" to the drafting process, but does not allow
them to do the drafting themselves.

After discussion with Denver and Tony, we narrowed these sections to
"for-profit", since we decided that non-profit "competition" wasn't an
issue of direct concern in these scenarios.

Converted format from LaTeX to asciidoc

typo fixes.

mostly typo fixes. Added supporting material to board records.

A few formatting fixes.