Opened 12 years ago
Last modified 12 years ago
#13 closed defect (FIXED)
flesh out hacking howto in docs
|Reported by:||Will Kahn-Greene||Owned by:||Will Kahn-Greene|
This is kind of a hand-wavy issue in that it's hard to discern when it's "completed". I vote we can use a gut feeling to decide one way or the other. Thus this bug is for helping to figure out what goes into the Hacking HOWTO and making sure it gets there. For April 30th, we want a Hacking HOWTO chapter in the documentation that covers the following: 1. how to build a working development environment for GNU MediaGoblin 2. how to run GNU MediaGoblin in a development environment (the deployment howto covers how to run it in a production environment) 3. how to contribute patches 4. where to look for things to work on 5. where to look for help when you're stuck The document is in the mediagoblin repository in docs/hackinghowto.rst .
Change History (6)
comment:1 by , 12 years ago
comment:2 by , 12 years ago
I pushed some changes to the hacking howto: 1. how to build a working development environment for GNU MediaGoblin 2. how to run GNU MediaGoblin in a development environment (the deployment howto covers how to run it in a production environment) This is covered in the contributing howto, so it seems weird to cover it again in the hacking howto, but maybe that's a good idea anyhow: 1. where to look for help when you're stuck Things that are outstanding: 1. how to contribute patches 2. where to look for things to work on
comment:3 by , 12 years ago
Assigning this to myself.
comment:4 by , 12 years ago
|Status:||New → Resolved|
Wrote up and checked in the last two bits. Closing this out now!
comment:5 by , 12 years ago
|Status:||Resolved → Closed|
comment:5 by , 11 years ago
The original url for this bug was http://bugs.foocorp.net/issues/272 .
Note: See TracTickets for help on using tickets.