| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
| |
Chris correctly pointed out that you can't quite run your own instance,
yet. But that's the goal!
|
|
|
|
|
|
| |
I chatted with Asheesh on IRC today and asked him to look over the
contributer howto. He had a lot of thoughts and I factored most/all
of them in. It's much better now.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
* Nixed codedocs and software stack chapters in favor of a chapter on
Beardomatic!
* Switched workflow to vision and added an additional caveat at the top
|
| |
|
|
|
|
|
|
| |
* adds "what's where" section which isn't wildly interesting right now
but it's somewhat interesting
* adds "wiping environment" section
|
|
|
|
|
| |
CC0 is a waiver and not a license, so this fixes all the language
accordingly.
|
|
|
|
|
|
|
| |
* lots of changes to the contributing howto from Matt, Greg, Will, and
Chris
* adds references between the contributing howto and other chapters
* adds a design decision regarding copyright assignment
|
|
|
|
|
|
|
|
| |
* changes COPYING to explain licensing for all of GNU MediaGoblin
* adds design decision regarding why we picked the licensing we did
* adds CC0 and AGPLv3 texts
* removes licensing bits from hacking howto--we should put that somewhere
else
|
|
|
|
|
| |
* adjusts some whitespace and formatting
* tweaks language and section breakdown
|
| |
|
|
|
|
| |
stuff.
|
|
|
|
|
|
|
| |
This work is based on discussion and etherpadding (is that a verb) on
April 14th between Deb, Greg, Karen, Will, and Chris.
It was an epic collaborative sprint.
|
| |
|
|
|
|
|
| |
* wrote up some basic bits of a hacking howto
* added a better deployment howto stub
|
|
|
|
|
|
|
| |
* fixes some typos
* tweaks some language issues that occured because I took Chris'
stuff out of the context of the original READMEish structure
* ditches installation for deploymenthowto and hackinghowto
|
| |
|
|
|
|
|
|
|
|
|
| |
use, what their function is, and urls for library documentation
* adds a forward chapter which talks about the documentation
* adds an installation stub
* adds a software stack chapter that covers what libraries are in
* adds a design decisions chapter which covers why we chose the
libraries and architecture
|
|
|