I've only skimmed this but a quick thought related to #2 is that parallel
to new documentation efforts it would be good for someone(s) to go through
a lot of that existing 'dev' and 'technical' content and mark pages with
banners that say things like "may be out of date", "use at your own risk",
"
Hello all,
A bit later than hoped, here are an assortment of small proposals for
(re-)organizing the developer documentation on the Evergreen wiki. The
overall goal is to develop what we have and what will come into a useful
and cohesive corpus.
1. Use the wiki
As mentioned in our talk, after c
Hi all,
I'm just catching up to this email thread now. I also saw that there was
a similar request for a circulation list that was briefly discussed in
IRC last week.
There seems to be two schools of thought in the community about mailing
lists. There are a lot of people who would like to se
