[Bf-committers] 2.71 Call for Docs
Gavin Howard
gavin.d.howard at gmail.com
Mon Jun 16 19:56:52 CEST 2014
All,
Ton has graciously allowed me to take on the role of documentation support.
What this means, as I understand it, is that I get the job of gathering all
raw documentation from developers and artists ahead of a release and
turning it into something useful on the wiki. I believe that this means
that I will also be putting together the release log.
So this is what I need:
Developers:
I need anything you can give me, including, but not limited to: notes of
any kind (implementation, user interface, scratch notes, etc), videos,
screenshots, commit lists (though I can go over the git history if needed),
git username (so I can find your commits), and any other useful
information. It does NOT need to be organized (that's my job), but any
effort would be greatly appreciated.
Artists/users:
If you worked with a developer on a feature and/or you tested it, I can
also use any information from you.
Again, the information doesn't need to be organized; I'll do that. Above
all, I don't want any of you to stress about sending stuff to me. If
necessary, I will go over the commit history.
One last thing: to prevent spamming this mailing list, don't send to the
list; send everything to me personally at
gavin(dot)d(dot)howard(at)gmail(dot)com. Thanks!
Gavin Howard
More information about the Bf-committers
mailing list