Opened 11 years ago

Last modified 11 years ago

#237 closed task (FIXED)

Move Hacking How To Guides into Documentation

Reported by: Sam Kleinman Owned by: Sam Kleinman
Priority: minor Milestone: 0.1.0
Component: documentation Keywords:
Cc: Parent Tickets:


I'm working to update and revise a few documents from existing
resources into our documentation (i.e. docs/).

` <>`_

` <>`_

` <>`_

` <>`_

The goal here is to provide an introduction to hacking on
MediaGoblin that outlines both "how to get all of the necessary
components working," in order to begin hacking on GMG.

As part of this, I want to include sections that answer the
questions, "what/where are the (popular) components that one might
be interested in working on," (i.e. templates, db schema,
configuration files, urlmapping.) and "why are things the way they
are," (drawing from existing design documents.)


Change History (4)

comment:1 Changed 11 years ago by Will Kahn-Greene

I think there's some confusion about what the docs/ documentation
is all about. It's the manual for site administrators.

The wiki is where we're putting all the contributor-related

Given that, documentation related to how to contribute should all
be in the wiki. Documentation related to configuring and deploying
a production instance should be in the docs/ .

Does that make sense?

comment:2 Changed 11 years ago by Christopher Allan Webber


comment:2 Changed 11 years ago by Christopher Allan Webber

Status: NewClosed
Marking as closed; superseded by
` <>`_
` <>`_

comment:3 Changed 11 years ago by Will Kahn-Greene

The original url for this bug was .
#238: related, #40: related

Note: See TracTickets for help on using tickets.