GNU MediaGoblin Wiki - User contributions [en]

20170304 Log

2017-03-04T19:23:51Z

Ayleph: missed the last line

<pre>
09:02:40 breton #startmeeting
09:02:48 breton where is the bot?
09:03:03 breton #startmeeting mediagoblin
09:03:11 breton oh well
09:03:18 ayleph i haven't seen chaosgoblin in quite a while :
09:03:24 paroneayea womp womp
09:03:33 paroneayea well, we could record the log and just post it to the list ourselves
09:03:53 breton hi everyone, welcome to our monthly meeting
09:03:59 breton todays agenda
09:03:59 paroneayea \o/
09:04:03 breton - GSoC
09:04:16 breton what else?
09:04:35 paroneayea - Federation and ActivityPub progress
09:04:43 paroneayea it ties in with at least one GSoC option
09:05:40 paroneayea maybe we should do the federation / activitypub update first since it impacts the gsoc
discussion? breton, wdyt?
09:06:26 breton paroneayea: sounds good, go for it :)
09:06:29 paroneayea ok :)
09:06:37 paroneayea so let's open up with some Good News
09:07:29 paroneayea ActivityPub relies on ActivityStreams, and ActivityStreams just got signed off to "go to PR",
ie "Proposed Recommendation"
09:07:51 paroneayea ActivityStreams is our whole vocabulary, etc in ActivityPub, so this is good
09:07:58 paroneayea PR means the group has spent a lonnnnnng time vetting the spec
09:08:13 paroneayea and it's now ready to be sent to the w3c advisory committee to review
09:08:23 paroneayea and hopefully make it an official spec
09:08:27 paroneayea so that's good news \o/
09:09:29 paroneayea in helping to make sure that we didn't have any important vocabulary dropped from the spec, we
had to prove implementation of all the terms, which means I've done a TON of implementation of
ActivityStreams terms in Pubstrate, the ActivityPub testbed server I've been working on
09:09:34 paroneayea http://dustycloud.org/gfx/goodies/video-in-pubstrate.png look, video! :)
09:09:46 paroneayea Pubstrate isn't doing anything like MediaGoblin's processing tooling
09:10:05 paroneayea but it can read the metadata that MediaGoblin will publish once MediaGoblin supports ActivityPUb
09:10:32 paroneayea so I already have a good idea of what that'll be "shaped" like once we switch MediaGoblin's
federation code over to ActivityPub
09:11:18 paroneayea in the meanwhile, as for ActivityPub itself, it's still at Candidate Recommendation stage,
pre-CR. The group got a 6 month extension for ActivityPub, but in order to meet that
09:12:00 paroneayea we need implementation reports (the template for which I'm just now about to merge
https://github.com/w3c/activitypub/pull/174#issuecomment-284131233 )
09:12:13 paroneayea and we need a test suite implementations can test against
09:12:19 paroneayea my whole next month will mostly be spent on that test suite.
09:12:42 paroneayea after that's done, I'll be helping with MediaGoblin's switch over to ActivityPub, but the test
suite needs to happen first
09:12:50 paroneayea so that's the update.
09:12:54 paroneayea questions? :)
09:13:01 ayleph when do you sleep?
09:13:36 ayleph sounds like you've been extremely busy, and very productive.
09:13:44 paroneayea thanks ayleph :) I appreciate that
09:13:49 breton there should be more docs for dumb people like me
09:14:01 breton or blogposts
09:14:14 paroneayea breton: have you read the AP spec? https://www.w3.org/TR/activitypub/
09:14:24 paroneayea we've tried to make it fairly readable
09:14:54 paroneayea breton: and yes I'd like to do more blogposts, I haven't gotten to it yet
09:15:06 ayleph i'm really excite about that pubstrate screen shot with video
09:15:07 breton paroneayea: yes. But it's 40 pages :(
09:15:38 paroneayea though! If you want a fun distraction
https://archive.org/details/feb_2017-live_network_coding_8sync
09:15:41 paroneayea watch this after the meeting :)
09:15:52 paroneayea it'll tie together the federation work with some other things ;)
09:15:56 paroneayea that's not important though. Okay!
09:16:03 paroneayea any other questions, or on to GSoC?
09:16:18 paroneayea ayleph: glad you're excited to see it... I was excited to get it working :)
09:16:53 paroneayea ayleph: btw if you want a rendering of what that AS2 object is before it's rendered in fancy
HTML, I could pull it up...
09:17:22 paroneayea no questions? maybe we should move on to GSoC
09:17:35 breton yes, lets move on
09:17:38 paroneayea #topic GSoC
09:17:41 paroneayea breton: why don't you lead this one
09:17:48 breton GNU was accepted to GSoC
09:17:58 breton we participate under GNU umbrella
09:18:36 breton https://wiki.mediagoblin.org/GSOC_2017 -- is our GSoC page, please fix it if you see something
wrong there
09:19:26 breton we have several students who contacted us early!
09:19:33 paroneayea breton: cool :)
09:20:10 breton so if some of them are here, we could talk about the projects
09:20:31 paroneayea let's do it!
09:20:51 breton one thing i wanted to discuss is access control project
09:21:04 breton paroneayea: how do you see it tied with activitypub one?
09:21:22 paroneayea breton: let's look at an example ActivityStreams object to see how!
09:21:26 paroneayea let me pull it up, one sec
09:22:57 paroneayea http://dpaste.com/1PDDHR3
09:23:00 paroneayea here are two examples
09:23:14 paroneayea taken from the ActivityPub document
09:23:41 paroneayea you can see a couple of things: a) objects are nested, the first one shows that we are
Create'ing a Note
09:24:09 paroneayea usually a stream will consist of Activity related to an Object (by an Actor)
09:24:46 paroneayea b) you'll notice that there's these fields for "to" or "cc" (and also "bcc" and "bto" in case
you don't want to disclose those recipients)
09:24:54 paroneayea so we're sending things to those specific users
09:25:02 paroneayea or even possibly to collections of users!
09:25:16 paroneayea "to": ["https://example.org/~john/"],
09:25:16 paroneayea "cc": ["https://example.com/~erik/followers",
09:25:17 paroneayea "https://www.w3.org/ns/activitystreams#Public"]
09:25:37 paroneayea in this example, "example.org/~john" is an actor on the network
09:25:53 paroneayea whereas "https://example.com/~erik/followers" is a collection of all the followers
09:26:10 paroneayea "https://www.w3.org/ns/activitystreams#Public" is kind of a special meta-collection that says
"actually anyone can see this"
09:26:16 paroneayea if we pretend the Public wasn't there
09:26:27 paroneayea we'd only want the original author, john, and erik's followers to read this
09:26:43 paroneayea that implies some fine-grained access control on an object level
09:27:10 paroneayea and indeed, for the Like by Mallory in Example 2, sarah and john presumably are the only people
who read it
09:27:21 breton so like email
09:27:24 paroneayea yes exactly.
09:27:35 paroneayea so to and cc and etc are *primarily* used for delivery
09:27:40 paroneayea but they also *imply* access control.
09:28:07 paroneayea so, let's say we had two GSoC students at once, one working on access control and one working on
ActivityPub federation! How could we get them to work together?
09:28:37 paroneayea well I think it isn't so terrrrrribly hard actually, but it will require they are willing to
work together a bit. they don't have to work from the same branch.
09:29:16 ayleph paroneayea: do you think that ActivityPub implied access control should be *the* access control
method for MediaGoblin? Or do you see it as just one possible implementation?
09:29:18 paroneayea we'd have to make sure the access control branch was set up with the *intent* of doing this kind
of fine grained access control: things are either public (anyone can see them), or they're
restricted to individuals and collections
09:29:29 breton i am opposed to students working together then
09:29:30 paroneayea ayleph: I think it should be *the* basis, and maybe there can be some hooks.
09:29:46 ayleph I'm wondering if some people just want to make an instance they can share with family member
without having to figure out ActivityPub stuff
09:29:51 breton ayleph: so mg switches to activitypub
09:30:05 breton ayleph: i think we shall mask all activitypub stuff
09:30:12 breton ayleph: hide it behind web-interface
09:30:14 paroneayea ayleph: I think it'll be possible
09:30:26 paroneayea you could add extra access checks
09:30:29 paroneayea via plugin hooks
09:30:44 paroneayea but it's just, the primary "how do I say this person has access" *starts with* the AP side of
things.
09:30:46 paroneayea make sense?
09:31:14 paroneayea so AP access control ideas start as foundation, and if you want to add some plugin hook that
gives broad sweeping access via some other authenticated mechanism, go for it
09:31:40 ayleph okay, i think i get it. (it's still a little early for me on a saturday morning...)
09:31:46 breton ok, that's actually nice
09:32:07 breton here is what we need to do
09:32:10 paroneayea so, what I imagine the person working on the ActivityPub implementation for the summer focusing
primarily on delivery
09:32:21 paroneayea so it's possible for them to focus on delivery, and not access control
09:32:39 paroneayea but we need the actor and actor collections stuff put in place before GSoC for that to work
09:32:47 paroneayea or else it's going to be a gnarly merge.
09:32:47 breton 1. drop access control project for now
09:33:00 paroneayea breton: or we can do that :)
09:33:08 breton 2. add more description about activitypub stuff to the project
09:33:20 breton activitypub looks scary
09:33:25 paroneayea here's the other thing about activitypub
09:33:30 breton i know it isn't, but it is.
09:33:33 paroneayea I think this is going to be an unusual GSoC
09:33:37 breton *but it looks
09:33:42 paroneayea the person working on GSoC this year will in some ways be my "assistant"
09:33:47 paroneayea I will be actively working with them
09:34:31 paroneayea I think that could reduce the scariness a bit
09:34:48 paroneayea so whoever is working on it this year will have to be willing to do a lot of collaboration, more
than most GSoC
09:34:58 paroneayea breton: does that make sense to you?
09:35:01 breton paroneayea: yes
09:35:11 paroneayea I figure I've been doing this ActivityPub stuff and getting it to a stable state for a couple of
years
09:35:27 paroneayea so it's time to land it, and I can certainly use help, but I think it'll go smoothest with
direct guidance
09:35:33 paroneayea tsyesika also said she'd be willing to help mentor
09:36:46 paroneayea ok
09:36:52 paroneayea so I guess one question is
09:37:44 paroneayea since this is kind of an unusual GSoC, do we need to do anything to help students prepare or
help check before GSoC stuff even starts?
09:38:03 paroneayea breton: do you have ideas?
09:38:16 paroneayea one tricky thing is I'm doing this test suite all month so that's going to be a bit overwhelming
already :)
09:38:17 breton the first thing i will do is update description of the task
09:39:04 breton the worst thing about the whole federation stuff is lack of description readable in 5-10 minutes
09:39:41 paroneayea ha
09:39:43 paroneayea yeah
09:39:56 paroneayea breton: maybe we should link to the part of the mediagoblin 2nd campaign video where federation
is explained ;)
09:40:22 breton the second worst is ambiguity of word "federation"
09:41:57 paroneayea http://mediagoblin.org/pages/campaign.html 1:45-2:20 on the video for talking about federation :)
09:42:10 paroneayea then it goes into some outdated stuff about the Pump API. but that was all pre-standardization!
09:42:20 ayleph the description mentions that there's a federation branch...is the idea to first try to merge
that branch, and then to convert it to activitypub?
09:42:37 paroneayea ayleph: hauuuuugh, I need to review it.
09:42:38 ayleph i imagine merging the branch alone may be a big task
09:42:44 paroneayea yes that's true
09:42:54 paroneayea maybe I need to devote weekends to getting up-to-date on that this month
09:43:18 paroneayea so we have two other gsoc tasks also
09:43:19 breton isn't it merged yet?
09:43:25 paroneayea breton: no :)
09:43:30 breton but
09:43:34 paroneayea it's been sitting there, burning on the back burner :)
09:43:48 breton why did the switch from user to actor happened?
09:44:34 paroneayea breton: *part of* the federation stuff landed
09:44:37 paroneayea but there's still more
09:44:40 ayleph there were certainly a lot of changes to the API code a year or two ago, but it was a pretty
basic implementation
09:44:50 ayleph images only, most clients couldn't successfully connect
09:44:53 paroneayea the complete federation branch is still sitting in tsyesika's branch
09:44:56 breton oh well.
09:45:00 paroneayea so
09:45:03 paroneayea I guess that's a task for me.
09:45:08 paroneayea assess the state of federation stuff
09:45:14 * paroneayea piles it on a towering heap
09:45:17 ayleph hehe
09:45:32 ayleph is that branch on savannah?
09:46:05 ayleph yeah, appears to be
09:46:06 paroneayea nope, notabug https://notabug.org/tsyesika/federated-mediagoblin.git
09:46:07 paroneayea oh
09:46:10 paroneayea maybe there too
09:46:33 ayleph oh, i probably shouldn't assume the one on savannah is the same one
09:46:34 paroneayea we might have pushed it to sannah
09:46:43 paroneayea another thing to look into!
09:47:03 paroneayea ayleph: breton: ok, so I'm going to be crazy busy for the next 1.5 weeks on this test suite
09:47:13 adfeno Savannah is the most respectful of the two repository hosts so far.
09:47:18 paroneayea in 2 weeks, can I ask one of you to pester me, "hey how's reviewing that federation code going"?
;)
09:47:35 ayleph hmm, it looks like the one on notabug is many commits behind the one on savannah
09:47:58 paroneayea ok, savannah is most up to date then. noted!
09:48:15 ayleph oh, but then i noticed the "federation" branch on notabug
09:48:31 ayleph they look about the same?
09:49:00 paroneayea meh, I'll look :)
09:49:08 breton ok, other GSoC projects
09:49:11 paroneayea yes
09:49:15 paroneayea there are 2 others!
09:49:25 breton Multiple qualities of video
09:49:48 breton i think it is pretty clear what to do there
09:50:11 breton this is the one i would love to mentor
09:50:13 ayleph maybe we could tack on some advanced user upload limit stuff to that one?
09:50:15 paroneayea great :)
09:50:25 paroneayea ayleph: don't we have a user upload limit thing?
09:50:33 paroneayea maybe it's not advanced :)
09:50:33 ayleph i think the current user upload limit code only looks at the size of the uploaded video (which
may or may not stick around), not the size of the transcoded video
09:50:46 ayleph and if we have multiple transcoded video sizes, that's a lot more disk space
09:50:59 paroneayea ahhh
09:51:03 paroneayea yes ayleph, good point.
09:51:15 paroneayea I think that's a reasonable thing to add to it
09:51:15 breton ayleph: lets just make a list of possible video qualities configurable
09:51:47 breton ayleph: also, if original video is 480p, there is definitely no reason to transcode it to 720p
09:53:42 breton ok, anything else aout multiple video qualities?
09:54:04 paroneayea breton: seems pretty good
09:54:19 breton cool. Our next project is "Chunked uploads / multi-upload UI"
09:54:41 paroneayea I think we have like, three branches that have attempted this and I've failed to review any of
them, like the terrible maintainer I am
09:54:47 paroneayea well wait
09:54:51 paroneayea I did review one once I think!
09:54:52 breton this one looks like an easy one actually
09:55:56 ayleph looking at the comments on the wiki, this may already be working code
09:56:15 ayleph i didn't realize that someone had updated the VenKamikaze multi-upload code to work with 0.9
09:58:31 breton so... there is no project?
09:59:04 ayleph i'm not sure, but at a quick glance, it seems that most of the work is already done
09:59:10 breton the code also doesn't look too complex for GSoC project
09:59:17 ayleph unless we want someone to create a new method
09:59:43 ayleph this code may need some adjustments; i'm not sure what happens if a browser doesn't support html5
09:59:50 ayleph but i don't think that's worthy of GSoC
10:00:31 breton i agree
10:00:34 paroneayea ok :)
10:00:40 breton lets drop the project
10:00:53 paroneayea also, one more thing
10:01:06 paroneayea is there any reason not to generalize multiple quality types?
10:01:18 paroneayea eg, multiple image quality, multiple audio quality
10:01:20 paroneayea all seems related.
10:01:27 paroneayea just thinkin' out loud here.
10:01:45 breton weeeell
10:01:55 breton multiple audio qualities -- meh
10:02:10 breton maybe just 2 -- high-quality and low-quality
10:02:26 breton well actually yes
10:02:30 breton this could be a thing
10:03:23 breton i am now thinking how i would do this project
10:05:36 ayleph totally different subject just popped into my head, but isn't there some issue with celery
moving forward? is this something that we could turn into a project?
10:05:56 paroneayea ayleph: yes... so our Celery stuff is kind of a mess
10:05:59 ayleph i seem to recall celery 4 dropped support for something that we need
10:06:19 paroneayea it dropped our crappy default solution that used an sqlite database as a message queue ;)
10:06:24 paroneayea I think we agreed to move to RabbitMQ
10:06:28 ayleph oh okay
10:06:45 paroneayea this might not be that big of a project, not sure if it's a whole summer's worth, but it needs
to be done
10:08:23 breton ++
10:09:17 breton maybe it will be done as part of multiple audio qualities
10:09:19 paroneayea (also, if the chunked upload stuff really is ready, why haven't we merged it? :) probably my
fault...)
10:09:32 paroneayea too bad "odds and ends" style GSoC's never seem to work out
10:09:59 breton because the project requires priorities in video transcoding
10:10:19 breton paroneayea: i will think about generalizing the qualities
10:10:42 breton we are 10 minutes out of our time and i need to go :)
10:11:18 breton thanks everyone for coming
10:11:25 paroneayea yes, time to wrap up
10:11:43 paroneayea #endmeeting ;)
10:11:44 breton #endmeeting
</pre>

Meeting

2017-03-04T19:19:55Z

Ayleph: link to Mar 4 2017 meeting log

== MediaGoblin Monthly Meeting ==

'''When:''' 9:00 am Pacific Time first Saturday of the month. [http://www.timeanddate.com/worldclock/converter.html Convert time to your timezone]. Print current UTC time: <code>date -u +"It's %F %T UTC"</code>. [https://en.wikipedia.org/wiki/Daylight_saving_time_in_the_United_States#2005_revision_to_dates_of_observance Pacific Time in 2014 has DST between March 9th and November 2nd].

'''Where:''' IRC #mediagoblin on irc.freenode.net

Always announced several days in advance on the [http://lists.mediagoblin.org/pipermail/devel/ mailing list] as is date adjustments, agenda discussion and other meeting preparation.

'''Purpose:''' The idea is to discuss the past month, what happened, what was good, what should be done better. And to create roadmap for the upcoming month and assign tasks to people willing to handle them.

Typical Agenda topics:

* What happened in the last month, what was good, what could be better next time?
* What should be done next month?

Meetings are logged. See below for logs of each meeting.

== Next Meeting ==

Every first Saturday of the month with JIT-compiled agenda.

=== April 1, 2017 ===

== Past Meetings ==

=== March 4, 2017, 9:00AM Pacific Time, 17:00 UTC ===
* Federation and ActivityPub progress
* GSoC

[[20170304_Log]]

=== Oct 1, 2016 ===

=== Sept 4, 2016, 17:00 UTC ===

[[20160904_Log]]

=== May 7, 2016 ===

=== April 2, 2016, 17:00 UTC ===
* 0.9.0 release (done!)
* GSoC
* 1.0

[[20160402_Log]]

=== March 5, 2016, 9:00AM Pacific Time, 17:00 UTC ===
* 0.9.0 release (imminent!)
* GSoC
** Project ideas
** Interested mentors?
* Federation mini-update

[[20160305_Log]]

=== February 6, 2016, 9:00AM Pacific Time, 17:00 UTC ===

* Continuous integration / Commit Notifications
* Move sqlite to development-only? (no more migrations)
* Upcoming 0.9.0 release
* Path to 1.0
* Stripe retreat update
* ActivityPub update (related!)
* GSOC ideas, and volunteers?

[[20160206_Log]]

=== January 2, 2016, 9:00AM Pacific Time, 17:00 UTC ===

* 0.9.0
* FOSDEM
* 0.8.2
[[20160102_Log]]

=== November 7, 2015, 9:00AM Pacific Time, 17:00 UTC ===

* 0.8.1 and 0.9.0
* Activipy and W3C Social WG stuff
* Help squash bugs!
* Revisiting the code / issue hosting situation??

=== March 7, 2015, 09:00AM Pacific Time, 17:00 UTC ===

* Moving off of gitorious, to?
* 0.8.0 upcoming release
* LibrePlanet and W3C meeting
* GSoC 2015
* Heads up: UserOps list
* Federation status
* Chris to take a temporary break?

=== December 6, 2014, 09:00AM Pacific Time, 17:00 UTC ===

* 0.8.0 upcoming release
** Current state (including looking at issue list)
** How to help!
*** Help us [https://issues.mediagoblin.org/query?status=new&status=in_progress&status=accepted&status=review&group=status&milestone=0.8.0 fix issues!]
*** Documentation (check it! improve it!)
*** Gstreamer 1.0 merge?
*** Help test!
*** Translate? (Maybe, but maybe not yet?)
* Translation talk, if breton is around
* Update on federation
* Update on W3C group

=== November 1, 2014, 09:00AM Pacific Time, 16:00 UTC ===

Loose meeting structure :)

=== October 4, 2014, 09:00AM Pacific Time, 16:00 UTC ===

* 0.8.0 progress
** Python 3 is in!
** Cleanup happening
** What's next
*** Gstreamer 1.0 merge
*** Search merge
*** [https://issues.mediagoblin.org/query?status=new&status=in_progress&status=accepted&status=review&group=status&milestone=0.8.0 Tickets!]
* Autoconf update
* Breton's translation update
* Federation update
* Deployment research update
* Add your things!

=== September 6, 2014, 09:00AM Pacific Time, 16:00 UTC ===

* Things happened! Horray!
** 0.7.0 is out!
** GSoC is done!
* Transifex move... help!
* 0.8.0 planning
* Updates on federation
* Updates on campaign-todo-items
* Premium hosting and deployment
* Documentation updates ( j1mc )
* Triage day! And the [https://etherpad.mozilla.org/gmg-triage new setup]!
* Help on reviewing?
* Epicanis' feature questions

=== August 2, 2014, 09:00AM Pacific Time, 16:00 UTC ===

* GSoC updates
* State of 0.7.0
* State of Federation
* State of post-campaign stuff (rewards, etc)
* General community updates
* Feedback: how are things going?

=== June 7, 2014, 09:00AM Pacific Time, 16:00 UTC ===

* GSoC updates
* Researchcation brief summary
* Campaign-related updates
* Upcoming release
* Code reviews

=== May 3, 2014, 09:00AM Pacific Time, 16:00 UTC ===

* GSoC starts!
* Post campaign updates!
** Horray, we did it!
** Unlocked features
** The rewards
** Premium hosting brainstorm
** Extra features brainstorm
* [http://lists.mediagoblin.org/pipermail/devel/2014-May/000867.html Metadata] discussion
* Chris' researchcation
** Federation stuff
** Deployment stuff
** Other stuff?
* Help review!
* Add your items HERE!

=== March 1st, 2014, 09:00AM Pacific Time, 17:00 UTC ===

* GSoC
* The [http://mediagoblin.org/pages/campaign.html crowdfunding campaign!]
** State of things / Q & A
** You can help!
* MediaGoblin in the meanwhile

=== November 2nd, 2013, 09:00AM Pacific Time, 16:00 UTC ===

Pretty loose on the schedule this month? :)

* Post-conference wrapup stuff?
* What's ahead in the next year for MediaGoblin?

=== October 5th, 2013, 09:00AM Pacific Time, 16:00 UTC ===

* Post-OPW/GSoC wrapup discussion
* Huge pile of code to review
* Planning out 0.6.0
* Road to 1.0
* mediagoblin.org changes
* GNU 30th recap, upcoming conferences
* MediaGoblin's graphic design?

=== September 7th, 2013 ===

* 0.5.0 release recap!
* Next release: 0.6.0!
* GSoC/OPW updates
* Review queue that needs attention
* GNU 30th! (and traveling)
* Other things???

=== August 3rd, 2013 9:00 am Pacific Time (2013-08-03 16:00 UTC) ===

* Configure && make merge
* 0.5.0 plans
* GSoC / OPW updates
* GNU 30th birthday party / GoblinCon? :)
* Documentation overhaul
* Reprocessing
* Bonus topics
** Mumble server
** XUDD

=== July 6th, 2013 9:00 am Pacific Time (2013-07-06 16:00 UTC) ===

* 0.4.0 is out! On to 0.4.1!
* OPW/GSoC update
* Federation status
* Module owners (and reducing the "Chris Webber bottleneck")?
** Projects like Blender, the Linux Kernel, and qemu have "module owners", people responsible for a domain of the code
** Could/should MediaGoblin do the same?
** How would that be broken up?

=== Jun 1st, 2013 9:00 am Pacific Time (2013-06-01 16:00 UTC) ===

* Welcoming our GSoC and OPW interns
* The coming 0.4.0
* What's after 0.4.0?
* RTL

=== May 4th, 2013, 9:00 am Pacific Time (2013-05-04 16:00 UTC) ===

[[meeting-2013-05-04|May 4th, 2013, 9:00 am Pacific Time (2013-05-04 16:00 UTC)]]

* GSOC and Gnome Outreach for Women participation update
* Mention the bug triage meeting
* Improving our unit tests?
* 0.4.0 release coming soon
* Help review code?
* Thanking simonft for sysadmin help!

=== April 6, 2013, 9:00 am Pacific Time (2013-03-30 16:00 UTC) ===

* Plugins update
* Post-libreplanet sprint merging
* Gstreamer 1.0 stuff (if Joar is here!)
* GSOC and Gnome Outreach for Women participation
* ???

=== March 2nd, 2013, 9:00 am Pacific Time (2013-03-02 16:00 UTC) ===

* Bug triage day discussion
* Upgrading Trac to 1.0
* Next release: 0.3.3
* Consider have release dates?
* Plugin stystem
* Consider moving to GStreamer 1.0
** Debian - 1.0 in sid
** Ubuntu - 1.0 in 12.10
*** Possibly backports for 12.04
** Fedora - 1.0 in 18
* Upcoming conferences and hackathons

=== February 9th, 2013, 9:00 am Pacific Time (2013-02-09 16:00 UTC) ===

* 0.3.3 milestone! What about our next release? :)
* Where to put Developer docs?
*: Our Documentation for developers is currently a bit split. Some are on the wiki, some in the main docs. There are pros and cons for both. We should consider where to put things. One place? Which? Or decide on an individual basis?
*: Good about main docs: Easy to integrate source code doc strings. That way internal api docs can be kept mostly up to date.
*: Good about wiki: Doesn't feel so "set in stone".
* wiki spam: Do we want to change something?
* [http://lists.mediagoblin.org/pipermail/devel/2012-November/000307.html Designing features!]
* Plugins, and architecting for plugins
* Chris Webber gives updates on how he's settling into his role ;)

=== October 13th, 2012, 9:00 am Pacific Time (2012-10-13 16:00 UTC) ===

* 0.3.2 release
** What existing features need to be wrapped up?
*** Werkzeug switch
** What time might we do the release?
* Fundraising campaign
** Keeping things going mid-campaign
** You have questions? I have answers, kinda :)
* Getting new contributors involved
* Plugins? New features?

==== Etherpad ====
<pre>
AGENDA

0.3.2 release

What existing features need to be wrapped up?

Werkzeug switch

What time might we do the release?

Congrats to Deb from the mediagoblin team! Congrats de Deb!

Fundraising campaign

Keeping things going mid-campaign

You have questions? I have answers, kinda :)

Getting new contributors involved

Plugins? New features?

-- http://wiki.mediagoblin.org/Meeting#Next_Meeting
Fundraising stuff
Things are going great mostly when people check it out!
But how to spread the word?

should contact more podcasts, etc

currently working with FSF on this

need community to spread the word!

List of places already spreaded list and contacted

VideoThumbnailerMarkII
New video thumbnailer, rewritten to try to eliminate a bug in the old one where processing would stall.
New bugs introduce (of course ;)
Collections
Merged - Thanks aaronw!
WebOb => Werkzeug switch
Made some things break. Need help with testing + bugfixes
borked stuffs:

Accessing paths without trailing slashes, e.g. /submit (instead of /submit/)

Still a lot of legacy WebOb responses (such as webob.exc.HTTPFound() HTTPForbidden() left)

API
Delivered to mrn.is, tryggvib will test it and get back with feedback.
Working, still a lot of room for improvements.
Mostly done, usable, still room for improvements. Example applications:

https://github.com/jwandborg/automgtic

https://github.com/jwandborg/omgmg
</pre>

=== September 1st, 2012, 9:00 am Pacific Time (2012-09-01 16:00 UTC) ===

[http://mediagoblin.org/irclogs/irc_meeting_2012-09-01.txt IRC log]

* FIXME - can someone type in summary here?

=== August 4th, 2012, 9:00 am Pacific Time (2012-08-04 16:00 UTC) ===

[http://mediagoblin.org/irclogs/irc_meeting_2012-08-04.txt IRC log]

* Release schedule
* Plugins and themes! Who's working on one? What problems are you having? -- Please write up issues for problems so they can get fixed!
* Should we namespace plugins? If so, how should we namespace plugins?
** Python 3.3 will have support for namespace plugins. [http://www.python.org/dev/peps/pep-0420/#namespace-packages-today]
** In Python >=2.3, <3.3 it's a hack [http://www.python.org/dev/peps/pep-0402/#the-problem][http://www.python.org/dev/peps/pep-0420/#namespace-packages-today]
** Flask has a workaround[https://github.com/mitsuhiko/flask/blob/master/flask/ext/__init__.py]

=== July 7th, 2012, 9:00 am Pacific Time (2012-07-07 16:00 UTC) ===

[http://mediagoblin.org/irclogs/irc_meeting_2012-07-07.txt IRC log]

Announcements:

* Anyone who wants to edit the wiki needs to be in the goblin army group. Ask Will or Chris to get added.
* Plugin infrastructure landed. If you're interested in writing plugins, talk to Will. Some documentation at http://docs.mediagoblin.org/#part-2-plugin-writer-s-guide

Agenda:

* Keyboard shortcuts ([http://issues.mediagoblin.org/ticket/346 #346])
* Ticket triaging?
* Base plugin stuff!
* Theming
* Conference: OSCON
* Chris Webber's new "office hours"

=== June 2nd, 2012, 9:00 am Pacific Time ===

[http://mediagoblin.org/irclogs/irc_meeting_2012-06-02.txt IRC log]

* docs changes
** Will split the docs/ guide into a Site Administrator's Guide and a Plugin Writer's Guide
** Has anyone looked at the Plugin Writer's Guide, yet?
** Will wants to add a "Contributor's Guide" to docs/ which he'd update from the wiki before every release
* Is there a way to improve our unit tests and motivation to write them?
** Simulating a browser by the way of [http://phantomjs.org/ PhantomJS], [http://seleniumhq.org/ Selenium] instead of having code simulating other code against itself might be more natural to write and even more testing the actual application. I have a good feeling about this, please prove me wrong if I'd be. --[[User:Joar|Joar]] 08:53, 28 May 2012 (EDT)
* Administrative panel/tools and user uploads panel
* Git and tickets
* Plugins
** What's the state of things?
** Documentation
** What plugins might we want to build for this upcoming release?
** What things do we currently have that we might want to pluginify?
* State of kuneco/federation mini-update (Chris)

=== May 5th, 2012, 9:00 am Pacific Time ===

[http://mediagoblin.org/irclogs/irc_meeting_2012-05-05.txt IRC log]

* Post-release reflections
** Woohoo, release!
** How did this release process go?
*** We should talk about that conference.
** What's left to clean up?
*** Mongokit->SQL "style" query conversion?
*** Other cruft code?
* What are our next goals?
** Plugins
** Federation
** Favoriting
*** Take that, Pinterest! ;)
** Galleries
** Theming
*** Using sass would be neat
** Access restrictions
*** User management, or having a "secret url" that is not in the photo index that you can share with friends and generate as needed for any media type
** What about traffic? Some of us will host GMG on limited plans.
** Some kind of coding guidelines? Do we have a philosophy like "Keep it Simple, Stupid"
*** This concerns things like: Should plugins land in core eventually, do we want to support ALL THE MEDIA TYPES, ...
** Podcasting support?
** Things that have been hanging???
** Bugtrackers and milestone?
** More??? We should organize things!
* jancborchardt and his team of UX wizard-students
* Website redesign
* OpenShift?

=== April 7th, 2012, 4:00 pm UTC ===

[http://mediagoblin.org/irclogs/irc_meeting_2012-04-07.txt IRC log]

* Post-SQL stuff
* Pending 0.0.3 release!
* Are there stray patches/branches to be merged?
* Our glorious upcoming plugin future! (Update from Will)

=== March 3rd, 2012, 9:00 am Pacific Time ===

[http://mediagoblin.org/irclogs/irc_meeting_2012-03-03.txt IRC log]

* [[GSOC 2012]]
* State of the SQL transition (preview: it's super close, but we need help!)
* Plugin discussion (Will can't make this, but we should talk about use cases)
* MediaGoblin at upcoming conferences
* PageKite accounts

=== 2012-02 (held on 2012-02-04) ===

[http://mediagoblin.org/irclogs/irc_meeting_2012-02-04.txt IRC log]

* Code style guide? See also: http://issues.mediagoblin.org/ticket/197
* Kuneco/federation
* API
* More testing discussion?
* Theming?
* Preliminary plugin discussion
* Status update from the "SQL Team".

Some of the decisions:

* file an issue about proper <audio> support.
* some TODOs recorded

=== 2011-12 (held on 2011-12-03) ===

[http://mediagoblin.org/irclogs/irc_meeting_2011-12-03.txt IRC log]

* We plan to create a plugin system. Do we want to create that soon or push it off until things settle a bit more? ([[User:Willkg|Willkg]] 08:54, 10 November 2011 (EST))
* [[Feature Ideas]]: What should we do about the wiki page? Keep it and have it as a monthly topic for "what next"? Convert everything to long waiting bugs?
* Possibility of an [[SQL Database Backend]]?
*: 'executive summary' (well, you should read the long docs): "We could move to sql. It's probably replacing one type of pain by another type of pain, but those are somewhat comparable. Leaving the main question: Do we want to occupy our main devs for some long time with this task and loose momentum?"
* Schendje's [http://wiki.mediagoblin.org/Feature_Ideas/Activities activities proposal]
* "Coming up next" blogpost draft by Deb Nicholson
* Jef's requests:
** Ticket #466 "Use of "Submit" in site copy is sterile and not as friendly and welcoming as it could be". I'd really like to change this soon to something more suitable. How can we improve the wording here? Some alternatives have been mentioned in the bug report, but which one should we pick? Link: http://bugs.foocorp.net/issues/466
** The concept and naming of "favourites". We'll (hopefully) be able to "favourite" media soon, which I *think* means that 1) it'll work like a "I like this" comment, a quick token of appreciation, 2) it'll be added to your list of favourites so you can save and promote it, and 3) we could maybe use the number of favourites as a ranking. What I'd like to know is: is that the intended purpose? If so, should we name them favo(u)rites or something else? "Like", "love", "save", "appreciate", "heart", "high five" and many more could all be contenders. And the name should be consistent with the action and purpose, of course. So I'd like to clear up how and why we will use favourites and what we should call them.

=== 2011-11 (held on 2011-11-05) ===

[http://mediagoblin.org/irclogs/irc_meeting_2011-11-05.txt IRC log]

* What happened in the last month, what was good, what could be better next time?
** Release:
*** Good: 0.1.0 released!
*** Bad: postponing vs not postponing
** Sites and deployment documentation:
*** Good: new mediagoblin.org
*** Good: deployment documentation
*** Bad: py-bcrypt’s site was down just after the release, so the virtualenv deployment didn’t work, and it wasn’t clear how to fix it.
** Live instances:
*** Joar has a live instance!
*** But what does it mean? Should ordinary users start using it?
**** Details at [[User:Joar/mg.wandborg.se]] -- [[User:Joar|Joar]] 17:01, 6 November 2011 (EST)
*** nyergler added a note about "heartbeat"/status to API notes
* What should be done next month?
* Starting real work on federation (via OStatus)... and do we split any of this work out into its own library?
* An API
* Creative Commons licensing tools
* Merging in the multimedia/video branch
*: (this is *very close* already actually thanks to the hard work of Joar Wandborg! But we need some help on the gstreamer front to fix a few issues... if you or someone you know is an expert in this area we could really use their help to make the videos that come out smoother!)
* Rollover items from 0.1.0
* Multiple file upload interface
* Drag and drop uploads interface (probably related!)

=== 2011-10 (held on 2011-10-01) ===

[http://mediagoblin.org/irclogs/irc_meeting_2011-10-01.txt IRC log]

This month's meeting was a quickly announced short meeting. The project is getting back on track and next month's meeting will be scheduled more properly. A bunch of people were around.

The most important decisions:
* The project will keep monthly releases. They're the heartbeat of the project.
* Release 0.1.0 this sunday/monday.
* New website will hopefully be deployed in the next few days.
* And the following things are planned to happen during this month: Most importantly federation. The developers have decided to make up their minds on what federation aactually should mean for MediaGoblin. Concerning code, probably "activity streams" are the first goal. If there is no (good) python library for this, a new stand alone library may be created. If so, a name for it has to be found. It should have something about communication in it. And the other thing to happen during this month is an ongoing discussion about "bus factor".

=== 2011-09 (held on 2011-09-03) ===

[http://mediagoblin.org/irclogs/irc_meeting_2011-09-03.txt IRC log]

=== 2011-08 (held on 2011-08-06) ===

[http://mediagoblin.org/irclogs/irc_meeting_2011-08-06.txt IRC log]

20170304 Log

2017-03-04T19:19:15Z

Ayleph: Created page with "<pre> 09:02:40 breton #startmeeting 09:02:48 breton where is the bot? 09:03:03 breton #startmeeting mediagoblin 09:03:11 breton oh well 09:03:18 ..."

Meeting

2017-03-04T18:59:43Z

Ayleph:

== MediaGoblin Monthly Meeting ==

'''When:''' 9:00 am Pacific Time first Saturday of the month. [http://www.timeanddate.com/worldclock/converter.html Convert time to your timezone]. Print current UTC time: <code>date -u +"It's %F %T UTC"</code>. [https://en.wikipedia.org/wiki/Daylight_saving_time_in_the_United_States#2005_revision_to_dates_of_observance Pacific Time in 2014 has DST between March 9th and November 2nd].

'''Where:''' IRC #mediagoblin on irc.freenode.net

Always announced several days in advance on the [http://lists.mediagoblin.org/pipermail/devel/ mailing list] as is date adjustments, agenda discussion and other meeting preparation.

'''Purpose:''' The idea is to discuss the past month, what happened, what was good, what should be done better. And to create roadmap for the upcoming month and assign tasks to people willing to handle them.

Typical Agenda topics:

* What happened in the last month, what was good, what could be better next time?
* What should be done next month?

Meetings are logged. See below for logs of each meeting.

== Next Meeting ==

Every first Saturday of the month with JIT-compiled agenda.

=== April 1, 2017 ===

== Past Meetings ==

=== March 4, 2017, 9:00AM Pacific Time, 17:00 UTC ===
* Federation and ActivityPub progress
* GSoC

=== Oct 1, 2016 ===

=== Sept 4, 2016, 17:00 UTC ===

[[20160904_Log]]

=== May 7, 2016 ===

=== April 2, 2016, 17:00 UTC ===
* 0.9.0 release (done!)
* GSoC
* 1.0

[[20160402_Log]]

=== March 5, 2016, 9:00AM Pacific Time, 17:00 UTC ===
* 0.9.0 release (imminent!)
* GSoC
** Project ideas
** Interested mentors?
* Federation mini-update

[[20160305_Log]]

=== February 6, 2016, 9:00AM Pacific Time, 17:00 UTC ===

* Continuous integration / Commit Notifications
* Move sqlite to development-only? (no more migrations)
* Upcoming 0.9.0 release
* Path to 1.0
* Stripe retreat update
* ActivityPub update (related!)
* GSOC ideas, and volunteers?

[[20160206_Log]]

=== January 2, 2016, 9:00AM Pacific Time, 17:00 UTC ===

* 0.9.0
* FOSDEM
* 0.8.2
[[20160102_Log]]

=== November 7, 2015, 9:00AM Pacific Time, 17:00 UTC ===

* 0.8.1 and 0.9.0
* Activipy and W3C Social WG stuff
* Help squash bugs!
* Revisiting the code / issue hosting situation??

=== March 7, 2015, 09:00AM Pacific Time, 17:00 UTC ===

* Moving off of gitorious, to?
* 0.8.0 upcoming release
* LibrePlanet and W3C meeting
* GSoC 2015
* Heads up: UserOps list
* Federation status
* Chris to take a temporary break?

=== December 6, 2014, 09:00AM Pacific Time, 17:00 UTC ===

* 0.8.0 upcoming release
** Current state (including looking at issue list)
** How to help!
*** Help us [https://issues.mediagoblin.org/query?status=new&status=in_progress&status=accepted&status=review&group=status&milestone=0.8.0 fix issues!]
*** Documentation (check it! improve it!)
*** Gstreamer 1.0 merge?
*** Help test!
*** Translate? (Maybe, but maybe not yet?)
* Translation talk, if breton is around
* Update on federation
* Update on W3C group

=== November 1, 2014, 09:00AM Pacific Time, 16:00 UTC ===

Loose meeting structure :)

=== October 4, 2014, 09:00AM Pacific Time, 16:00 UTC ===

* 0.8.0 progress
** Python 3 is in!
** Cleanup happening
** What's next
*** Gstreamer 1.0 merge
*** Search merge
*** [https://issues.mediagoblin.org/query?status=new&status=in_progress&status=accepted&status=review&group=status&milestone=0.8.0 Tickets!]
* Autoconf update
* Breton's translation update
* Federation update
* Deployment research update
* Add your things!

=== September 6, 2014, 09:00AM Pacific Time, 16:00 UTC ===

* Things happened! Horray!
** 0.7.0 is out!
** GSoC is done!
* Transifex move... help!
* 0.8.0 planning
* Updates on federation
* Updates on campaign-todo-items
* Premium hosting and deployment
* Documentation updates ( j1mc )
* Triage day! And the [https://etherpad.mozilla.org/gmg-triage new setup]!
* Help on reviewing?
* Epicanis' feature questions

=== August 2, 2014, 09:00AM Pacific Time, 16:00 UTC ===

* GSoC updates
* State of 0.7.0
* State of Federation
* State of post-campaign stuff (rewards, etc)
* General community updates
* Feedback: how are things going?

=== June 7, 2014, 09:00AM Pacific Time, 16:00 UTC ===

* GSoC updates
* Researchcation brief summary
* Campaign-related updates
* Upcoming release
* Code reviews

=== May 3, 2014, 09:00AM Pacific Time, 16:00 UTC ===

* GSoC starts!
* Post campaign updates!
** Horray, we did it!
** Unlocked features
** The rewards
** Premium hosting brainstorm
** Extra features brainstorm
* [http://lists.mediagoblin.org/pipermail/devel/2014-May/000867.html Metadata] discussion
* Chris' researchcation
** Federation stuff
** Deployment stuff
** Other stuff?
* Help review!
* Add your items HERE!

=== March 1st, 2014, 09:00AM Pacific Time, 17:00 UTC ===

* GSoC
* The [http://mediagoblin.org/pages/campaign.html crowdfunding campaign!]
** State of things / Q & A
** You can help!
* MediaGoblin in the meanwhile

=== November 2nd, 2013, 09:00AM Pacific Time, 16:00 UTC ===

Pretty loose on the schedule this month? :)

* Post-conference wrapup stuff?
* What's ahead in the next year for MediaGoblin?

=== October 5th, 2013, 09:00AM Pacific Time, 16:00 UTC ===

* Post-OPW/GSoC wrapup discussion
* Huge pile of code to review
* Planning out 0.6.0
* Road to 1.0
* mediagoblin.org changes
* GNU 30th recap, upcoming conferences
* MediaGoblin's graphic design?

=== September 7th, 2013 ===

* 0.5.0 release recap!
* Next release: 0.6.0!
* GSoC/OPW updates
* Review queue that needs attention
* GNU 30th! (and traveling)
* Other things???

=== August 3rd, 2013 9:00 am Pacific Time (2013-08-03 16:00 UTC) ===

* Configure && make merge
* 0.5.0 plans
* GSoC / OPW updates
* GNU 30th birthday party / GoblinCon? :)
* Documentation overhaul
* Reprocessing
* Bonus topics
** Mumble server
** XUDD

=== July 6th, 2013 9:00 am Pacific Time (2013-07-06 16:00 UTC) ===

* 0.4.0 is out! On to 0.4.1!
* OPW/GSoC update
* Federation status
* Module owners (and reducing the "Chris Webber bottleneck")?
** Projects like Blender, the Linux Kernel, and qemu have "module owners", people responsible for a domain of the code
** Could/should MediaGoblin do the same?
** How would that be broken up?

=== Jun 1st, 2013 9:00 am Pacific Time (2013-06-01 16:00 UTC) ===

* Welcoming our GSoC and OPW interns
* The coming 0.4.0
* What's after 0.4.0?
* RTL

=== May 4th, 2013, 9:00 am Pacific Time (2013-05-04 16:00 UTC) ===

[[meeting-2013-05-04|May 4th, 2013, 9:00 am Pacific Time (2013-05-04 16:00 UTC)]]

* GSOC and Gnome Outreach for Women participation update
* Mention the bug triage meeting
* Improving our unit tests?
* 0.4.0 release coming soon
* Help review code?
* Thanking simonft for sysadmin help!

=== April 6, 2013, 9:00 am Pacific Time (2013-03-30 16:00 UTC) ===

* Plugins update
* Post-libreplanet sprint merging
* Gstreamer 1.0 stuff (if Joar is here!)
* GSOC and Gnome Outreach for Women participation
* ???

=== March 2nd, 2013, 9:00 am Pacific Time (2013-03-02 16:00 UTC) ===

* Bug triage day discussion
* Upgrading Trac to 1.0
* Next release: 0.3.3
* Consider have release dates?
* Plugin stystem
* Consider moving to GStreamer 1.0
** Debian - 1.0 in sid
** Ubuntu - 1.0 in 12.10
*** Possibly backports for 12.04
** Fedora - 1.0 in 18
* Upcoming conferences and hackathons

=== February 9th, 2013, 9:00 am Pacific Time (2013-02-09 16:00 UTC) ===

* 0.3.3 milestone! What about our next release? :)
* Where to put Developer docs?
*: Our Documentation for developers is currently a bit split. Some are on the wiki, some in the main docs. There are pros and cons for both. We should consider where to put things. One place? Which? Or decide on an individual basis?
*: Good about main docs: Easy to integrate source code doc strings. That way internal api docs can be kept mostly up to date.
*: Good about wiki: Doesn't feel so "set in stone".
* wiki spam: Do we want to change something?
* [http://lists.mediagoblin.org/pipermail/devel/2012-November/000307.html Designing features!]
* Plugins, and architecting for plugins
* Chris Webber gives updates on how he's settling into his role ;)

=== October 13th, 2012, 9:00 am Pacific Time (2012-10-13 16:00 UTC) ===

* 0.3.2 release
** What existing features need to be wrapped up?
*** Werkzeug switch
** What time might we do the release?
* Fundraising campaign
** Keeping things going mid-campaign
** You have questions? I have answers, kinda :)
* Getting new contributors involved
* Plugins? New features?

==== Etherpad ====
<pre>
AGENDA

0.3.2 release

What existing features need to be wrapped up?

Werkzeug switch

What time might we do the release?

Congrats to Deb from the mediagoblin team! Congrats de Deb!

Fundraising campaign

Keeping things going mid-campaign

You have questions? I have answers, kinda :)

Getting new contributors involved

Plugins? New features?

-- http://wiki.mediagoblin.org/Meeting#Next_Meeting
Fundraising stuff
Things are going great mostly when people check it out!
But how to spread the word?

should contact more podcasts, etc

currently working with FSF on this

need community to spread the word!

List of places already spreaded list and contacted

VideoThumbnailerMarkII
New video thumbnailer, rewritten to try to eliminate a bug in the old one where processing would stall.
New bugs introduce (of course ;)
Collections
Merged - Thanks aaronw!
WebOb => Werkzeug switch
Made some things break. Need help with testing + bugfixes
borked stuffs:

Accessing paths without trailing slashes, e.g. /submit (instead of /submit/)

Still a lot of legacy WebOb responses (such as webob.exc.HTTPFound() HTTPForbidden() left)

API
Delivered to mrn.is, tryggvib will test it and get back with feedback.
Working, still a lot of room for improvements.
Mostly done, usable, still room for improvements. Example applications:

https://github.com/jwandborg/automgtic

https://github.com/jwandborg/omgmg
</pre>

=== September 1st, 2012, 9:00 am Pacific Time (2012-09-01 16:00 UTC) ===

[http://mediagoblin.org/irclogs/irc_meeting_2012-09-01.txt IRC log]

* FIXME - can someone type in summary here?

=== August 4th, 2012, 9:00 am Pacific Time (2012-08-04 16:00 UTC) ===

[http://mediagoblin.org/irclogs/irc_meeting_2012-08-04.txt IRC log]

* Release schedule
* Plugins and themes! Who's working on one? What problems are you having? -- Please write up issues for problems so they can get fixed!
* Should we namespace plugins? If so, how should we namespace plugins?
** Python 3.3 will have support for namespace plugins. [http://www.python.org/dev/peps/pep-0420/#namespace-packages-today]
** In Python >=2.3, <3.3 it's a hack [http://www.python.org/dev/peps/pep-0402/#the-problem][http://www.python.org/dev/peps/pep-0420/#namespace-packages-today]
** Flask has a workaround[https://github.com/mitsuhiko/flask/blob/master/flask/ext/__init__.py]

=== July 7th, 2012, 9:00 am Pacific Time (2012-07-07 16:00 UTC) ===

[http://mediagoblin.org/irclogs/irc_meeting_2012-07-07.txt IRC log]

Announcements:

* Anyone who wants to edit the wiki needs to be in the goblin army group. Ask Will or Chris to get added.
* Plugin infrastructure landed. If you're interested in writing plugins, talk to Will. Some documentation at http://docs.mediagoblin.org/#part-2-plugin-writer-s-guide

Agenda:

* Keyboard shortcuts ([http://issues.mediagoblin.org/ticket/346 #346])
* Ticket triaging?
* Base plugin stuff!
* Theming
* Conference: OSCON
* Chris Webber's new "office hours"

=== June 2nd, 2012, 9:00 am Pacific Time ===

[http://mediagoblin.org/irclogs/irc_meeting_2012-06-02.txt IRC log]

* docs changes
** Will split the docs/ guide into a Site Administrator's Guide and a Plugin Writer's Guide
** Has anyone looked at the Plugin Writer's Guide, yet?
** Will wants to add a "Contributor's Guide" to docs/ which he'd update from the wiki before every release
* Is there a way to improve our unit tests and motivation to write them?
** Simulating a browser by the way of [http://phantomjs.org/ PhantomJS], [http://seleniumhq.org/ Selenium] instead of having code simulating other code against itself might be more natural to write and even more testing the actual application. I have a good feeling about this, please prove me wrong if I'd be. --[[User:Joar|Joar]] 08:53, 28 May 2012 (EDT)
* Administrative panel/tools and user uploads panel
* Git and tickets
* Plugins
** What's the state of things?
** Documentation
** What plugins might we want to build for this upcoming release?
** What things do we currently have that we might want to pluginify?
* State of kuneco/federation mini-update (Chris)

=== May 5th, 2012, 9:00 am Pacific Time ===

[http://mediagoblin.org/irclogs/irc_meeting_2012-05-05.txt IRC log]

* Post-release reflections
** Woohoo, release!
** How did this release process go?
*** We should talk about that conference.
** What's left to clean up?
*** Mongokit->SQL "style" query conversion?
*** Other cruft code?
* What are our next goals?
** Plugins
** Federation
** Favoriting
*** Take that, Pinterest! ;)
** Galleries
** Theming
*** Using sass would be neat
** Access restrictions
*** User management, or having a "secret url" that is not in the photo index that you can share with friends and generate as needed for any media type
** What about traffic? Some of us will host GMG on limited plans.
** Some kind of coding guidelines? Do we have a philosophy like "Keep it Simple, Stupid"
*** This concerns things like: Should plugins land in core eventually, do we want to support ALL THE MEDIA TYPES, ...
** Podcasting support?
** Things that have been hanging???
** Bugtrackers and milestone?
** More??? We should organize things!
* jancborchardt and his team of UX wizard-students
* Website redesign
* OpenShift?

=== April 7th, 2012, 4:00 pm UTC ===

[http://mediagoblin.org/irclogs/irc_meeting_2012-04-07.txt IRC log]

* Post-SQL stuff
* Pending 0.0.3 release!
* Are there stray patches/branches to be merged?
* Our glorious upcoming plugin future! (Update from Will)

=== March 3rd, 2012, 9:00 am Pacific Time ===

[http://mediagoblin.org/irclogs/irc_meeting_2012-03-03.txt IRC log]

* [[GSOC 2012]]
* State of the SQL transition (preview: it's super close, but we need help!)
* Plugin discussion (Will can't make this, but we should talk about use cases)
* MediaGoblin at upcoming conferences
* PageKite accounts

=== 2012-02 (held on 2012-02-04) ===

[http://mediagoblin.org/irclogs/irc_meeting_2012-02-04.txt IRC log]

* Code style guide? See also: http://issues.mediagoblin.org/ticket/197
* Kuneco/federation
* API
* More testing discussion?
* Theming?
* Preliminary plugin discussion
* Status update from the "SQL Team".

Some of the decisions:

* file an issue about proper <audio> support.
* some TODOs recorded

=== 2011-12 (held on 2011-12-03) ===

[http://mediagoblin.org/irclogs/irc_meeting_2011-12-03.txt IRC log]

* We plan to create a plugin system. Do we want to create that soon or push it off until things settle a bit more? ([[User:Willkg|Willkg]] 08:54, 10 November 2011 (EST))
* [[Feature Ideas]]: What should we do about the wiki page? Keep it and have it as a monthly topic for "what next"? Convert everything to long waiting bugs?
* Possibility of an [[SQL Database Backend]]?
*: 'executive summary' (well, you should read the long docs): "We could move to sql. It's probably replacing one type of pain by another type of pain, but those are somewhat comparable. Leaving the main question: Do we want to occupy our main devs for some long time with this task and loose momentum?"
* Schendje's [http://wiki.mediagoblin.org/Feature_Ideas/Activities activities proposal]
* "Coming up next" blogpost draft by Deb Nicholson
* Jef's requests:
** Ticket #466 "Use of "Submit" in site copy is sterile and not as friendly and welcoming as it could be". I'd really like to change this soon to something more suitable. How can we improve the wording here? Some alternatives have been mentioned in the bug report, but which one should we pick? Link: http://bugs.foocorp.net/issues/466
** The concept and naming of "favourites". We'll (hopefully) be able to "favourite" media soon, which I *think* means that 1) it'll work like a "I like this" comment, a quick token of appreciation, 2) it'll be added to your list of favourites so you can save and promote it, and 3) we could maybe use the number of favourites as a ranking. What I'd like to know is: is that the intended purpose? If so, should we name them favo(u)rites or something else? "Like", "love", "save", "appreciate", "heart", "high five" and many more could all be contenders. And the name should be consistent with the action and purpose, of course. So I'd like to clear up how and why we will use favourites and what we should call them.

=== 2011-11 (held on 2011-11-05) ===

[http://mediagoblin.org/irclogs/irc_meeting_2011-11-05.txt IRC log]

* What happened in the last month, what was good, what could be better next time?
** Release:
*** Good: 0.1.0 released!
*** Bad: postponing vs not postponing
** Sites and deployment documentation:
*** Good: new mediagoblin.org
*** Good: deployment documentation
*** Bad: py-bcrypt’s site was down just after the release, so the virtualenv deployment didn’t work, and it wasn’t clear how to fix it.
** Live instances:
*** Joar has a live instance!
*** But what does it mean? Should ordinary users start using it?
**** Details at [[User:Joar/mg.wandborg.se]] -- [[User:Joar|Joar]] 17:01, 6 November 2011 (EST)
*** nyergler added a note about "heartbeat"/status to API notes
* What should be done next month?
* Starting real work on federation (via OStatus)... and do we split any of this work out into its own library?
* An API
* Creative Commons licensing tools
* Merging in the multimedia/video branch
*: (this is *very close* already actually thanks to the hard work of Joar Wandborg! But we need some help on the gstreamer front to fix a few issues... if you or someone you know is an expert in this area we could really use their help to make the videos that come out smoother!)
* Rollover items from 0.1.0
* Multiple file upload interface
* Drag and drop uploads interface (probably related!)

=== 2011-10 (held on 2011-10-01) ===

[http://mediagoblin.org/irclogs/irc_meeting_2011-10-01.txt IRC log]

This month's meeting was a quickly announced short meeting. The project is getting back on track and next month's meeting will be scheduled more properly. A bunch of people were around.

The most important decisions:
* The project will keep monthly releases. They're the heartbeat of the project.
* Release 0.1.0 this sunday/monday.
* New website will hopefully be deployed in the next few days.
* And the following things are planned to happen during this month: Most importantly federation. The developers have decided to make up their minds on what federation aactually should mean for MediaGoblin. Concerning code, probably "activity streams" are the first goal. If there is no (good) python library for this, a new stand alone library may be created. If so, a name for it has to be found. It should have something about communication in it. And the other thing to happen during this month is an ongoing discussion about "bus factor".

=== 2011-09 (held on 2011-09-03) ===

[http://mediagoblin.org/irclogs/irc_meeting_2011-09-03.txt IRC log]

=== 2011-08 (held on 2011-08-06) ===

[http://mediagoblin.org/irclogs/irc_meeting_2011-08-06.txt IRC log]

HackingHowto

2016-10-18T05:39:24Z

Ayleph: Add section about py2 vs py3 and issues with py3

= Hacking HOWTO =

== So you want to hack on GNU MediaGoblin? ==

First thing to do is check out the [http://mediagoblin.org/join/ web site] where we list all the project
infrastructure including:

* the IRC channel
* the mailing list
* the issue tracker

Additionally, we have information on how to get involved, who to talk
to, what needs to be worked on, and other things besides!

Second thing to do is take a look at [http://docs.mediagoblin.org/devel/codebase.html codebase chapter] where
we've started documenting how GNU MediaGoblin is built and how to add
new things. If you're planning on contributing in python, you should be aware
of [http://www.python.org/dev/peps/pep-0008/ PEP-8], the official Python style guide,
which we follow.

Third you'll need to get the requirements.

Fourth, you'll need to build a development environment. We use an
in-package checkout of virtualenv. This isn't the convenional way to
install virtualenv (normally you don't install virtualenv inside the
package itself) but we've found that it's significantly easier for
newcomers who aren't already familiar with virtualenv. If you *are*
already familiar with virtualenv, feel free to just install
mediagoblin in your own virtualenv setup... the necessary adjustments
should be obvious.

== Python 2 vs Python 3 ==

GNU MediaGoblin was originally written for Python 2, and much of the documentation on the wiki reflects that. However, since release v0.9.0, GNU MediaGoblin has attempted to provide support for Python 3. Unfortunately, not everything is working for Python 3 environments yet. Below is a non-exhaustive list of things that might not work if you set up GNU MediaGoblin a Python 3 environment.

=== Python 3 Issues ===

* fcgi - none of the flup packages ([https://pypi.python.org/pypi/flup flup], [https://pypi.python.org/pypi/flup-py3 flup-py3], [https://pypi.python.org/pypi/flup6 flup6]) appear to have proper support for Python 3.5.
* audio file spectrographs - [https://pypi.python.org/pypi/scikits.audiolab scikits.audiolab] [https://issues.mediagoblin.org/ticket/5467 appears to not work] in Python 3.
* Rackspace storage - the [https://pypi.python.org/pypi/python-cloudfiles cloudfiles] plugin may not work with Python 3.

== Getting requirements ==

First, you need to have the following installed before you can build
an environment for hacking on GNU MediaGoblin:

* Python 2.7 - http://www.python.org/ (You'll need Python as well as the dev files for building modules.)
* python-lxml - http://lxml.de/
* git - http://git-scm.com/
* SQLAlchemy 0.7.0 or higher - http://www.sqlalchemy.org/
* Pillow - http://python-pillow.org/
* virtualenv - http://www.virtualenv.org/
* Python GStreamer Bindings - http://gstreamer.freedesktop.org/modules/gst-python.html
* Node.js

=== GNU/Linux ===

==== Debian and derivatives ====

If you're running Debian GNU/Linux or a Debian-derived distribution
such as Debian, Mint, or [http://bugs.foocorp.net/issues/478 Ubuntu 10.10+], running the following should install these
requirements:

{{Cmd|sudo apt-get install git-core python python-dev python-lxml python-imaging python-virtualenv python-gst-1.0 libjpeg8-dev autoconf nodejs npm nodejs-legacy}}

==== Debian GNU/Linux jessie ====

{{Cmd|sudo apt-get install -y git-core python python-dev python-lxml python-imaging python-virtualenv libjpeg-dev autoconf nodejs npm nodejs-legacy python-gst-1.0 gstreamer1.0-plugins-base gstreamer1.0-plugins-bad gstreamer1.0-plugins-good gstreamer1.0-plugins-ugly gstreamer1.0-libav python-numpy python-scipy libsndfile1-dev libasound2-dev libgstreamer-plugins-base1.0-dev}}

==== Fedora / RedHat(?) / CentOS ====

===== On Fedora: =====

{{Cmd|yum install python-paste-deploy python-paste-script git-core python python-devel python-lxml python-imaging python-virtualenv gstreamer-python nodejs}}

===== On CentOS7: =====

'''epel-release''' is the prerequisite for most of the below listed packages

{{Cmd|sudo yum install epel-release}}

{{Cmd|sudo yum update}}

{{Cmd|sudo yum install python-paste-deploy python-paste-script \ git-core python python-devel python-lxml python-imaging \ python-virtualenv npm automake nginx gcc}}

for video to work correctly (as per [https://mediagoblin.readthedocs.io/en/stable/siteadmin/media-types.html?highlight=video#video Enabling Media-Types Video]) you may choose to install AWEL 3rd party repo which provides with the latest gstreamer bindings and more:

* [http://awel.domblogger.net/7/media/x86_64/repoview/awel-media-release.html AWEL Repo],[https://media.librelamp.com/gst AWEL Gstreamer]

once installed:

{{Cmd|sudo yum install gstreamer1 gstreamer1-libav gstreamer1-plugins-base gstreamer1-plugins-base-tools gstreamer1-plugins-good gstreamer1-plugins-ugly gstreamer1-plugins-bad gstreamer1-python ffmpeg }}

==== openSUSE ====

This instructions might be incomplete.
Try on openSUSE 13.2 or 13.1:

{{Cmd|zypper install python-devel python-gstreamer-0_10 git-core python python-lxml python-Pillow python-virtualenv npm}}

==== ArchLinux / Parabola ====

The following command should work (<del>not tested on a new ArchLinux / Parabola install</del>. tested, it works):

{{Cmd|pacman -S git python2 python2-lxml python2-pillow python2-virtualenv gstreamer0.10-python}}

=== Mac OS X ===

==== Mac OS X Lion ====

Download the Newest Python.

Git is already installed.

* Note for Pillow and lxml, you can: pip install Pillow lxml

Python-lxml: http://muffinresearch.co.uk/archives/2009/03/05/install-lxml-on-osx/ with sudo

Pillow: http://pillow.readthedocs.org/en/3.0.x/installation.html#os-x-installation

Libjpeg & Libpng: http://ethan.tira-thompson.com/Mac_OS_X_Ports.html Combo Installer

==== Mac OS X Snow Leopard ====

# You will probably want to install MacPorts this will give you access to many free software packages in the same manner to apt-get and yum: https://www.macports.org/install.php
# Ensure you install Git and the command line tools: https://help.github.com/articles/set-up-git#platform-mac
# Once both of those are installed type this in your terminal and enter your password when prompted for it {{Cmd|sudo port install python27 py27-lxml py27-sqlalchemy py27-Pillow py27-virtualenv py27-gst-python py27-pastescript}}

=== Microsoft Windows ===

''Thanks wctype!''

==== Getting requirements ====

* Python 2.7 - [http://www.python.org/download/ Download] 
* git - [https://github.com/msysgit/git/downloads Download] 
* python-lxml - [http://pypi.python.org/pypi/lxml/2.3.5#downloads Tarball] [http://www.lfd.uci.edu/~gohlke/pythonlibs/#pil Binaries] 
* Pillow - [http://pillow.readthedocs.org/en/3.0.x/installation.html#windows-installation Download] 
* virtualenv - [http://pypi.python.org/pypi/virtualenvwrapper-win/1.0.8#downloads Download] 
* OSSBuild project provides reasonably up-to-date binaries of GStreamer - [https://code.google.com/p/ossbuild/downloads/list Download] 
* py-bcrypt - [https://bitbucket.org/alexandrul/py-bcrypt/downloads/ Download] 
* Node JS

----

'''You can help:'''

If you have instructions for other GNU/Linux distributions, Windows, or Mac OS X to set
up requirements, [http://mediagoblin.org/join/ let us know]!

== How to set up and maintain an environment for hacking with virtualenv ==

'''Requirements'''

No additional requirements.

'''Create a development environment'''

After installing the requirements, follow these steps:

* Clone the repository: {{Cmd|git clone <nowiki>git://git.savannah.gnu.org/mediagoblin.git</nowiki>}}
* Make the environment: {{Cmd|./bootstrap.sh && ./configure && make}}
* Init the database:
{{Cmd|./bin/gmg dbupdate}}

That's it!

If you want to make sure things are working, consider running the test suite:
{{Cmd|./runtests.sh}}

(If you have troubles in the remaining steps, consider try installing
virtualenv with one of the flags --setuptools, --distribute or possibly --no-site-packages. Additionally, if your system has python3.X as the default, you might need to do virtualenv --python=python2.7 or --python=python2.6)

If you have problems, please [http://mediagoblin.org/join/ let us know]!

== Updating an existing environment ==

'''Updating for dependency changes'''

While hacking on GNU MediaGoblin over time, you'll eventually have to
update your development environment because the dependencies have
changed.

To do that, run:

{{Cmd|./bin/python setup.py develop --upgrade && ./bin/gmg dbupdate}}

'''Updating for code changes'''

{{Cmd|git pull -u}}
{{Cmd|git submodule update}}

'''NOTE:''' MediaGoblin used to be hosted on gitorious.org, but that is moving to read-only mode, so we're now on Savannah. If you have an old checkout, please update it by running the following:

{{Cmd|git remote set-url origin git://git.savannah.gnu.org/mediagoblin.git}}

== Running the server ==

If you want to get things running quickly and without hassle, just
run:

{{Cmd|./lazyserver.sh}}

This will start up a python server where you can begin playing with
mediagoblin, listening on 127.0.0.1:6543. It will also run celery in "always eager" mode so you
don't have to start a separate process for it.

By default, the instance is not sending out confirmation mails. Instead they are redirected to the standard output (the console) of lazyserver.sh.

You can change this behavior setting <code>email_debug_mode</code> to <code>false</code> in mediagoblin.ini

This is fine in development, but if you want to actually run celery
separately for testing (or deployment purposes), you'll want to run
the server independently:

{{Cmd|./bin/paster serve paste.ini --reload}}

== Running celeryd ==

If you aren't using <tt>./lazyserver.sh</tt> or otherwise aren't running celery
in always eager mode, you'll need to do this if you want your media to
process and actually show up. It's probably a good idea in
development to have the web server (above) running in one terminal and
celeryd in another window.

Run:

{{Cmd|<nowiki>CELERY_CONFIG_MODULE=mediagoblin.init.celery.from_celery ./bin/celeryd</nowiki>}}

== Running the test suite ==

Run:

{{Cmd|./runtests.sh}}

== Running a shell ==

If you want a shell with your database pre-setup and an instantiated
application ready and at your fingertips....

Run:

{{Cmd|./bin/gmg shell}}

== Troubleshooting ==

== Wiping your user data ==

You can completely wipe all data from the instance by doing:

{{Cmd|rm -rf mediagoblin.db kombu.db celery.db user_dev; ./bin/gmg dbupdate}}

'''Note:'''

Unless you're doing development and working on and testing creating
a new instance, you will probably never have to do this.

== Quickstart for Django programmers ==

We're not using Django, but the codebase is very Django-like in its
structure.

* <tt>routing.py</tt> is like <tt>urls.py</tt> in Django
* <tt>models.py</tt> has SQLAlchemy ORM definitions
* <tt>views.py</tt> is where the views go

We're using SQLAlchemy, which is semi-similar to the Django ORM, but
not really because you can get a lot more fine-grained. The
[http://docs.sqlalchemy.org/en/latest/orm/tutorial.html SQLAlchemy ORM tutorial] is a great place to start.

'''YouCanHelp'''

If there are other things that you think would help orient someone
new to GNU MediaGoblin but coming from Django, let us know!

== Showing off your work with PageKite ==

If you're doing development with MediaGoblin, it's sometimes helpful to show off your work to gather feedback from other contributors. A number of the MediaGoblin developers use something called [http://pagekite.net PageKite], which is a fellow free software web service which makes temporarily showing off work on your machine easy. There's a [http://pagekite.net/wiki/Howto/UsePageKiteWithMediaGoblin/ tutorial on how to use PageKite and MediaGoblin together] available on the PageKite wiki.

If you are doing a lot of MediaGoblin development, the PageKite people have graciously offered us a good amount of bandwidth at no cost in an effort to help out fellow free software projects. If you've been making significant contributions, PM Chris Webber on freenode (who is paroneayea there) and ask if you can be added to our group plan.

== Bite-sized bugs to start with ==

Now you should visit our latest list of [http://issues.mediagoblin.org/query?status=!closed&keywords=~bitesized bite-sized issues] because squishing bugs is messy fun. If you're interested in other things to work on, or need help getting started on a bug, let us know on [http://mediagoblin.org/join/ the mailing list] or on the [http://mediagoblin.org/join/ IRC channel].

Deployment

2016-06-08T22:31:37Z

Ayleph: Fixing script name per https://issues.mediagoblin.org/ticket/5459

This page could use a lot of work. For now, a few smaller deployment tips!

See also: http://docs.mediagoblin.org/deploying.html (some of which may belong here)

= uwsgi =

Possibly a cleaner way to do nginx configuration than the official nginx + fastcgi suggestions!

http://nathanielca.se/fossrit/deploying-mediagoblin-1-fastcgi-vs-uwsgi.html

= uwsgi with configs =

Below there are 3 configs: for nginx, for uwsgi version 1.2.3-debian and for supervisord, used to run celery.

In future, when newer versions of uwsgi appear in debian, supervisor can be removed.

All instructions below are for Debian 7. They should also work with rpm-based systems, but with other paths.

<pre>apt-get install uwsgi uwsgi-plugin-python nginx-full supervisor;</pre>

/etc/nginx/sites-available/mediagoblin:
<pre>
server {
server_name <domain>;

access_log /var/log/nginx/mg.access.log;
error_log /var/log/nginx/mg.error.log error;

#include global/common.conf;

client_max_body_size 100m;
add_header X-Content-Type-Options nosniff;

root /path/to/mediagoblin//user_dev/;

location /mgoblin_static/ {
alias /path/to/mediagoblin/mediagoblin/static/;
}
location /mgoblin_media/ {
alias /path/to/mediagoblin/user_dev/media/public/;
}
location /theme_static/ {
}
location /plugin_static/ {
}
location / {
uwsgi_pass unix:///tmp/mg.uwsgi.sock;
uwsgi_param SCRIPT_NAME "";
include uwsgi_params;
}
}
</pre>

/etc/uwsgi/apps-available/mg.yaml:
<pre>
uwsgi:
uid: mediagoblin
gid: mediagoblin
socket: /tmp/mg.uwsgi.sock
chown-socket: www-data:www-data
plugins: python
home: /path/to/mediagoblin/
chdir: /path/to/mediagoblin/
ini-paste: /path/to/mediagoblin/paste_local.ini
</pre>

/etc/supervisor/conf.d/mediagoblin.conf:
<pre>
[program:celery]
command=/path/to/mediagoblin/bin/celery worker -l debug

; Set PYTHONPATH to the directory containing celeryconfig.py
environment=PYTHONPATH="/path/to/mediagoblin",MEDIAGOBLIN_CONFIG="/path/to/mediagoblin/mediagoblin_local.ini",CELERY_CONFIG_MODULE="mediagoblin.init.celery.from_celery"

directory=/path/to/mediagoblin/
user=mediagoblin
numprocs=1
; uncomment below to enable logs saving
;stdout_logfile=/some/logs/path/celeryd_stdout.log
;stderr_logfile=/some/logs/path/celeryd_stderr.log
autostart=true
autorestart=false
startsecs=10

; Need to wait for currently executing tasks to finish at shutdown.
; Increase this if you have very long running tasks.
stopwaitsecs = 600
</pre>

After setting all configs do:
<pre>
ln -s /etc/nginx/sites-available/mediagoblin /etc/nginx/sites-enabled/
ln -s /etc/uwsgi/apps-available/mg.yaml /etc/uwsgi/apps-enabled/
</pre>

And don't forget to restart all your daemons:
<pre>
service uwsgi restart;
service nginx restart;
service supervisor stop; sleep 1; service supervisor start # sleep 1 might be needed here because supervisor really stops not at once
</pre>

= FCGI script =

This works great with the apache FCGID config example in the next section :) in which case you should name it "mg.fcgi".

Before use, make sure you replace '/path/to/mediagoblin/bin/python' with a real path on your server, e.g. '/srv/www/myhomepage.com/mediagoblin/bin/python'. Also replace '/path/to/mediagoblin/paste.ini'.

If you encounter problems, try executing executing the script manually, e.g. <pre>./mg.fcgi</pre>

Script:

<pre>#!/path/to/mediagoblin/bin/python

# Written in 2011 by Christopher Allan Webber
#
# To the extent possible under law, the author(s) have dedicated all
# copyright and related and neighboring rights to this software to the
# public domain worldwide. This software is distributed without any
# warranty.
#
# You should have received a copy of the CC0 Public Domain Dedication along
# with this software. If not, see
# <http://creativecommons.org/publicdomain/zero/1.0/>.

from paste.deploy import loadapp
from flup.server.fcgi import WSGIServer

CONFIG_PATH = '/path/to/mediagoblin/paste.ini'

## Uncomment this to run celery in "always eager" mode... ie, you don't have
## to run a separate process, but submissions wait till processing finishes
# import os
# os.environ['CELERY_ALWAYS_EAGER'] = 'true'

def launch_fcgi():
ccengine_wsgi_app = loadapp('config:' + CONFIG_PATH)
WSGIServer(ccengine_wsgi_app).run()

if __name__ == '__main__':
launch_fcgi()</pre>

= Apache 2 Config With fcgid =

Note that the libapache2-mod-fcgi in Debian is in the main section. libapache2-mod-fcgid can be used, but requires a slightly different configuration. For yum-based distributions, you may need to install mod_fcgid.

<VirtualHost *:80>
Options +ExecCGI

# Accept up to 16MB requests
FcgidMaxRequestLen 16777216

ServerName mediagoblin.example.org

Alias /mgoblin_static/ /path/to/mediagoblin/mediagoblin/static/
Alias /mgoblin_media/ /path/to/mediagoblin/user_dev/media/public/

ScriptAlias / /path/to/mediagoblin/mg.fcgi/
</VirtualHost>

= Apache 2 Config With mod_wsgi =

Apache can manage the MediaGoblin application itself with mod_wsgi. It requires slightly more configuration on the Apache side, but cuts out the FastCGI middleware. See their [http://code.google.com/p/modwsgi/wiki/ConfigurationGuidelines configuration guidelines] for advanced configuration.

<VirtualHost *:80>
ServerName mediagoblin.example.org

Alias /mgoblin_static/ /path/to/mediagoblin/mediagoblin/static/
Alias /mgoblin_media/ /path/to/mediagoblin/user_dev/media/public/

WSGIScriptAlias / /path/to/mediagoblin/wsgi.py
# Set user and group to whatever user you used to install mediagoblin (if you used a system account,
# it may have the group 'nogroup' assigned, in that case you can remove the group parameter)
# Remember to change python-path too!
# Replace the python version in the 'python-path' below with the correct one (eg 2.x -> 2.7)
WSGIPassAuthorization On
WSGIDaemonProcess gmg user=mediagoblin group=mediagoblin processes=2 threads=10 \
umask=0007 inactivity-timeout=900 maximum-requests=1000 \
python-path=/path/to/mediagoblin/:/path/to/mediagoblin/lib/python-2.x/site-packages/
WSGIProcessGroup gmg
WSGIApplicationGroup %{GLOBAL}

<Directory "/path/to/mediagoblin/mediagoblin/static/">
Order allow,deny
Allow from all
</Directory>
<Directory "/path/to/mediagoblin/user_dev/media/public">
Order allow,deny
Allow from all
</Directory>
</VirtualHost>

You'll also need to copy this into /path/to/mediagoblin/wsgi.py:

#!/path/to/mediagoblin/bin/python

# Written in 2011 by Christopher Allan Webber
#
# To the extent possible under law, the author(s) have dedicated all
# copyright and related and neighboring rights to this software to the
# public domain worldwide. This software is distributed without any
# warranty.
#
# You should have received a copy of the CC0 Public Domain Dedication along
# with this software. If not, see
# <http://creativecommons.org/publicdomain/zero/1.0/>.

import site
# Replace the python version with the correct one in the line below (eg 2.x -> 2.7)
site.addsitedir('/path/to/mediagoblin/lib/python-2.x/site-packages')

from paste.deploy import loadapp

CONFIG_PATH = '/path/to/mediagoblin/paste.ini'

## Uncomment this to run celery in "always eager" mode... ie, you don't have
## to run a separate process, but submissions wait till processing finishes
#import os
#os.environ['CELERY_ALWAYS_EAGER'] = 'true'

application = loadapp('config:' + CONFIG_PATH)

If you're getting strange errors when trying to upload something, your WSGI setup is probably not starting Celery. You should start it yourself, perhaps with your preferred init system or service supervisor.

= Apache Config Example =
This configuration example uses mod_fastcgi.

To install and enable mod_fastcgi on a Debian/Ubuntu based system:
<pre># apt-get install libapache2-mod-suexec libapache2-mod-fastcgi
# a2enmod suexec
# a2enmod fastcgi</pre>

Sample configuration:
<pre>
<VirtualHost *:80>
ServerName mediagoblin.yourdomain.tld
ServerAdmin webmaster@yourdoimain.tld
DocumentRoot /var/www/
# Custom log files
CustomLog /var/log/apache2/mediagobling_access.log combined
ErrorLog /var/log/apache2/mediagoblin_error.log

# Serve static and media files via alias
Alias /mgoblin_static/ /path/to/mediagoblin/mediagoblin/static/
Alias /mgoblin_media/ /path/to/mediagoblin/user_dev/media/public/

# Rewrite all URLs to fcgi, except for static and media urls
RewriteEngine On
RewriteRule ^(mgoblin_static|mgoblin_media)($|/) - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^/(.*)$ /mg.fcgi/$1 [QSA,L]

# Allow access to static and media directories
<Directory /path/to/mediagoblin/mediagoblin/static>
Order allow,deny
Allow from all
</Directory>
<Directory /path/to/mediagoblin/mediagoblin/user_dev/media/public>
Order allow,deny
Allow from all
</Directory>

# Connect to fcgi server
FastCGIExternalServer /var/www/mg.fcgi -host 127.0.0.1:26543
</VirtualHost>
</pre>
Then, you need to make sure mediagoblin is running in fcgi mode:
<pre>cd /path/to/mediagoblin
./lazyserver.sh --server-name=fcgi fcgi_host=127.0.0.1 fcgi_port=26543</pre>

Note: there may be several ways to improve this configuration

If it is too slow and you use the deflate module, you could try to use the following option : SetOutputFilter INFLATE

= Lighttpd =

This configuration example uses mod_fastcgi.
Make a symbolic link from <pre>/etc/lighttpd/conf-available/10-fastcgi.conf</pre> to <pre>/etc/lighttpd/conf-enabled/10-fastcgi.conf</pre>

<pre>
ln -s /etc/lighttpd/conf-available/10-fastcgi.conf /etc/lighttpd/conf-enabled/10-fastcgi.conf
</pre>

then edit your /etc/lighttpd/conf-enabled/10-fastcgi.conf file modifying it as below to serve mediagoblin on the /tube/ path of your webserver.

<pre>
## FastCGI programs have the same functionality as CGI programs,
## but are considerably faster through lower interpreter startup
## time and socketed communication
##
## Documentation: /usr/share/doc/lighttpd-doc/fastcgi.txt.gz
## http://www.lighttpd.net/documentation/fastcgi.html

server.modules += ( "mod_fastcgi" )

## Start an FastCGI server for mediagoblin (lazyserver.sh or other deployments scripts should be up and running)
fastcgi.server = (
# url at which the app should be accessible on the server
"/tube" =>
# mnemonical name of the backend
( "mg-local" => (
"host" => "127.0.0.1",
"port" => 6543,
"docroot" => "/path/to/mediagoblin-git-folder/mediagoblin",
"check-local" => "disable"
)
)

)
</pre>

Then open your /etc/lighttpd/lighttpd.conf and add the configuration to serve directly the static/public folders

<pre>
alias.url += (
"/mgoblin_static/" => "/path/to/mediagoblin-git-folder/mediagoblin/static/",
"/mgoblin_media/" => "/path/to/mediagoblin-git-folder/user_dev/media/public/",
"/theme_static/" => "/path/to/mediagoblin-git-folder/user_dev/theme_static/",
"/plugin_static/" => "/path/to/mediagoblin-git-folder/user_dev/plugin_static/"
)

</pre>

Done!

= OpenShift =

Thers's a blogpost saying how to [http://www.sud0.com/gnu-media-goblin-on-openshift.html install mediagoblin on openshift].

= Juju =

There is a juju [https://juju.ubuntu.com/Charms charm] available for deploying mediagoblin into EC2 or on your local box. [https://juju.ubuntu.com/ juju] is available in Ubuntu 11.10 and later, though it is recommended that you pull it from [https://launchpad.net/~juju/+archive/pkgs the juju PPA], which includes backported packages going back to Ubuntu 11.10. To use the juju charm, install juju and configure either the [https://juju.ubuntu.com/docs/provider-configuration-local.html local provider] or one of the cloud API providers, currently the [https://juju.ubuntu.com/docs/provider-configuration-ec2.html EC2 provider] is the best supported and works not only with Amazon Web Services but also OpenStack clouds. There is also a newer native OpenStack API provider which is known to support HP Cloud.
<pre>
# if you have not bootstrapped
juju bootstrap
mkdir ~/charms
bzr init-repo ~/charms/precise
bzr branch lp:~clint-fewbar/charms/precise/mediagoblin/trunk ~/charms/precise/mediagoblin
juju deploy --repository ~/charms local:mediagoblin
juju expose mediagoblin
</pre>

Currently the charm is volatile, deploying from trunk, and deploys a single-server version of MediaGoblin only. It will eventually relate to the existing juju charms for other supported data stores to allow one to scale out their MediaGoblin instance.

= Init scripts =

== Debian init scripts ==

Joar has some scripts for running celery and mediagoblin separately that are designed for Debian.

https://github.com/joar/mediagoblin-init-scripts

== Arch Linux init scripts ==

[http://whird.jpope.org/2012/04/14/mediagoblin-archlinux-rcd-scripts Jeremy Pope has written a nice blogpost] on how to add init scripts to deploy MediaGoblin with both the python paste http server and the celery deployments separated.

If you want a simpler setup and don't want to deploy celery separately, consider either turning CELERY_ALWAYS_EAGER to true in the paste init script described above, or check out [http://chimo.chromic.org/2012/03/01/mediagoblin-init-script-on-archlinux/ Chimo's guide].

== Generic, simple init script ==

This is a super stupidly simple init script that was used for mediagoblin.com... note that this has Celery running in always eager mode.

You will need to adjust the paths appropriately. This could probably be better written!

#! /bin/sh

## Stupidly simple mediagoblin init script.
#
# Written in 2012 by Christopher Allan Webber
#
# To the extent possible under law, the author(s) have dedicated all
# copyright and related and neighboring rights to this software to the
# public domain worldwide. This software is distributed without any
# warranty.
#
# You should have received a copy of the CC0 Public Domain Dedication along
# with this software. If not, see
# <http://creativecommons.org/publicdomain/zero/1.0/>.

PASTER=/srv/mediagoblin.com/bin/paster
PASTE_CONFIG=/srv/mediagoblin.com/paste.ini
OPTIONS="--pid-file=/tmp/mediagoblin.pid \
--log-file=/srv/mediagoblin.com/paster.log \
--server-name=fcgi fcgi_host=127.0.0.1 fcgi_port=26543"

CELERY_ALWAYS_EAGER=true su -pc "$PASTER serve $PASTE_CONFIG $1 $OPTIONS" webadmin

== systemd init scripts ==

The following systemd scripts provide separate Paste and Celery instances. Replace <code>/path/to/mediagoblin</code> to match your install path. The directories <code>/var/log/mediagoblin</code> and <code>/var/run/mediagoblin</code> are not created by default; you may create them yourself or change the location of the pid and log files. You may omit the log file if you choose. The init scripts provided below assume customized versions of mediagoblin.ini and paste.ini have been created as mediagoblin_local.ini and paste_local.ini, respectively; you should change those lines to point back to the original mediagoblin.ini or paste.ini files if you haven't made customizations.

If you prefer not to run separate Celery, uncomment <code>Environment=CELERY_ALWAYS_EAGER=true</code> and comment <code>Environment=CELERY_ALWAYS_EAGER=false</code>. You won't need the file <code>/etc/systemd/system/gmg-celery.service</code>.

<code>/etc/systemd/system/gmg.service</code>:

[Unit]
Description=Mediagoblin

[Service]
Type=forking
User=mediagoblin
Group=mediagoblin
#Environment=CELERY_ALWAYS_EAGER=true
Environment=CELERY_ALWAYS_EAGER=false
WorkingDirectory=/path/to/mediagoblin
ExecStart=/path/to/mediagoblin/bin/paster serve \
/path/to/mediagoblin/paste_local.ini \
--pid-file=/var/run/mediagoblin/paster.pid \
--log-file=/var/log/mediagoblin/paster.log \
--daemon \
--server-name=fcgi fcgi_host=127.0.0.1 fcgi_port=26543
ExecStop=/path/to/mediagoblin/bin/paster serve \
--pid-file=/var/run/mediagoblin/paster.pid \
/path/to/mediagoblin/paste_local.ini stop
PIDFile=/var/run/mediagoblin/paster.pid

[Install]
WantedBy=multi-user.target

<code>/etc/systemd/system/gmg-celeryd.service</code>:

[Unit]
Description=Mediagoblin Celeryd

[Service]
User=mediagoblin
Group=mediagoblin
Type=simple
WorkingDirectory=/path/to/mediagoblin
Environment="MEDIAGOBLIN_CONFIG=/path/to/mediagoblin/mediagoblin_local.ini" \
CELERY_CONFIG_MODULE=mediagoblin.init.celery.from_celery
ExecStart=/path/to/mediagoblin/bin/celeryd
PIDFile=/var/run/mediagoblin/mediagoblin-celeryd.pid

[Install]
WantedBy=multi-user.target

<code>/usr/lib/tmpfiles.d/gmg.conf</code>:
d /var/run/mediagoblin 0755 mediagoblin mediagoblin

Invoke the Paste or Celery processes using systemctl. Eg,

$ sudo systemctl start|stop|restart gmg.service

$ sudo systemctl start|stop|restart gmg-celeryd.service

= Running on Dreamhost.com =

===Set up your python virtualenv===

dreamhost.com servers come with python 2.4 and 2.5 installed which is too old for mediagoblin. This means you need to compile and install a newer python (don't worry this is really not difficult on dreamhost servers). In order to be able to install python packages for a local user without touching system files, we need to setup a python ''virtualenv''. Fortunately, this is not too tricky either. If your server has python 2.6 or 2.7 installed already, you can skip the [[#Install a local python|python installation stuff]] and you'll only need to [[#Setup virtualenv to install local python packages|install virtualenv]].

====Install a local python====
# Download the latest python: http://python.org/ftp/python/XXX/Python-XXX.tar.bz2
# Unpack with <pre>tar xvjf Python-XXX.tar.bz2</pre>
# ''cd'' into the directory and compile and install python locally:
<blockquote><pre>./configure --prefix=$HOME/local
make
make install</pre></blockquote>
:This will install python (I used 2.7.3) into /home/<USERNAME>/local/bin/python. You might get warnings about some modules not being able to compile. :It was tcl/tk and bzip2 mainly, but things still worked out overall.
:
:You should now be able to invoke <tt>~/local/bin/python</tt> and fall into a shell of your new python (exit with ctrl-d). Congrats, you have now a new python 2.7 that you can use. However, you will need to be able to install additional packages as a user and this is what virtualenv allows.

====Setup virtualenv to install local python packages====
# Download the latest virtualenv: http://pypi.python.org/packages/source/v/virtualenv/XXX
# Install the virtualenv: <blockquote><pre>~/local/bin/python ~/virtualenv-1.8/virtualenv.py $HOME/local/virtenv</pre></blockquote>
:: You will now have: ~/local/virtenv/bin/python
# In ~/.bash_profile add: <blockquote><pre>PATH=~/local/virtenv/bin:~/local/bin:${PATH}</pre></blockquote>
:: so that your local python will be preferred.
:: Log out, log in again and test python" to see which version will be invoked. It should be the new python. Check "which easy_install" to see if the one in local/virtenv would be executed.
::
:: You have now 1) a local ''python'' installation that you can use, and 2) ''easy_install'' will also work with your local user installation. From now on you can e.g. locally install the nose testing framework (''easy_install nose'') and use it (''python -c "import nose"'').

===Install mediagoblin as a site package===

# Check out mediagoblin from git to e.g. ~/mediagoblin
# Install MediaGoblin and all dependencies for MediaGoblin with easy_install.
:* In the mediagoblin directory issue:
:<blockquote><pre>python setup.py</pre></blockquote>
:* You will also need to: easy_install lxml
:* Python-image was trickier to install: <pre>easy_install --find-links http://www.pythonware.com/products/pil/ Imaging</pre>
::Test by leaving the mediagoblin directory and see if you can import it: <pre>python -c "import mediagoblin"</pre> looking for error messages.

===Set up an WSGI environment on Dreamhost===

# Enable the mod_passenger setting for ruby/python in the domains web panel
# ''cd'' into the domain directory (e.g. ~/media.sspaeth.de for me)
# Copy mediagoblin.ini and paste.ini from the ~/mediagoblin directory here
# Create passenger_wsgi.py in your domain directory (e.g. ~/media.sspaeth.de for me):
<blockquote><pre>import sys, os
INTERP = "/home/<username>/local/virtenv/bin/python"
#INTERP is present twice so that the new python interpreter knows the actual executable path
if sys.executable != INTERP: os.execl(INTERP, INTERP, *sys.argv)

from paste.deploy import loadapp
application = loadapp('config:/home/mediagoblin/media.sspaeth.de/paste.ini')

#If in case of errors, all you get are mysterious error 500, you can set debug=true in paste.ini to see stack traces
# Otherwise, add this:
#from paste.exceptions.errormiddleware import ErrorMiddleware
#application = ErrorMiddleware(application, debug=True)</pre></blockquote>
# Set up the database by issueing: <pre>gmg dbupdate</pre>
# (optional but recommended) Serve the static files directly from the webserver.
:In paste.ini in this section: [composite:routing] comment out the static files:
#/mgoblin_static/ = mediagoblin_static
#/theme_static/ = theme_static
:and symlink the mediagobin/mediagoblin/static directoy to public/mgoblin_static
: and mediagoblin/mediagoblin/themes to public/theme_static
:
:so it is displayed directly. This step might be different depending on your web server configuration. There is no reason that static
:files need to go through all the python indirection when they can be served directly by nginx/apache/...
:
:In case you want to delete your git checkout after the installation (you don't need it, since you installed the mediagoblin package to ~/local/virtenv/lib/python2.7/mediagoblin... you should do the symlinking from there.
===Open Issues===
Please fill in the blanks if you find them out:
* How to enable logging to a file or standard html logs? Console output just disappears.
* How to set up things not using sqlite. What's wrong with mySQL?

===Troubleshooting===
* First of all: invoke <pre>python passenger_wsgi.py</pre> directly from the shell. This will tell you if there are import errors etc. If this command exits without any output on the console, you have already achieved a lot.
* In ''paste.ini'' set debug=true. This will show you python backtraces directly in the web page
* You will need to configure an smtp user/passwd/server in mediagoblin.ini, so you actually get the account creation token mailed out. Hint, the relevant settings are: <blockquote><pre>email_debug_mode = false
email_sender_address = postmaster@sspaeth.de
email_smtp_host = SMTP.DOMAIN.TLD
email_smtp_user = USERNAME
email_smtp_pass = WEIRDPASSWORD</pre></blockquote>
* In case you can upload media, but it does not appear. You don't have the celery server running. Add <pre>CELERY_ALWAYS_EAGER = true</pre> to the ''[celery]'' section in mediagoblin.ini

=Miscellaneous Hacks=
==Force translation==
There might some conditions under which you would prefer that MediaGoblin always return the same translation. If you are deploying with nginx and fastcgi, you can force MediaGoblin to return a specific translation regardless of browser preferences by passing a specific HTTP_ACCEPT_LANGUAGE fastcgi parameter in your location block. Example last line in location block:
<nowiki>
fastcgi_param HTTP_ACCEPT_LANGUAGE es; #force spanish translation
</nowiki>

==Create an admin user==

To create an admin user, first create the user you need either via the website or the command
<pre>
./bin/gmg adduser
</pre>

Then to turn it into an admin account use

<pre>
./bin/gmg makeadmin your_username
</pre>

CommunityGovernance

2015-08-24T16:56:19Z

Ayleph: who admins the issue tracker box?

MediaGoblin is a community project and we everybody try to help each other. Chris Webber is our lead developer, but the project should be able to self govern so he can take a break if he needs it or when he or other contributors take deserved holidays :)

In general, you can ask anything in the mailing list or the IRC channel and hopefully somebody will answer soon. Topics are discussed in the mailing list, IRC channel or monthly meetings (in the IRC channel).

In this page we list several tasks or areas along with the names or nicks of MediaGoblin community members that may help on them (for example, because they have permissions to perform certain operations). Please be kind when asking for help, most of us are volunteering for MediaGoblin in our free time, so answers or problems resolution can take a while.

Feel free to edit this page to list more tasks or sign the ones you self-assign.

More information about this in this mailing list thread: http://lists.mediagoblin.org/pipermail/devel/XXXXX

== MediaGoblin codebase ==

* People with permissions to commit/merge and handle the main codebase

* General stuff: breton, Elrond (via PM on IRC)
* Python 3 support: berkerpeksag (berker on IRC), breton
* Audio/Video: breton
* Documentation: jcampbell / j1mc

== MediaGoblin website ==

* People with permissions to handle website outages

* Publish pages (for example new releases)

== MediaGoblin wiki ==

* Some Wiki administration: Elrond (via PM on IRC)

== MediaGoblin issue tracker ==

* Issue tracker server administration: ???
* Help triaging bugs: R13ose
* People with permissions to create accounts in trac: Elrond
* People with permissions to delete users/issues/comments in trac: Elrond
* Volunteers for spam cleaning: LArjona, ayleph
* Talk to trac people about spam: R13ose
* Would like more access to be able to help/fix things:

== MediaGoblin translation platform ==

* If there is need of manual import/export files between Pootle and the MediaGoblin codebase, who can help on that
* LArjona (Spanish translator) can guide new translators, reproduce problems in the translation platform, test changes, and help with Pootle quality checks. Available in the mailing list and IRC channel.
* breton knows how and why translations are downloaded/compiled

== MediaGoblin IRC channel and mailing list ==

* Change IRC topic, channel operators
* Running the monthly meetings: breton
* Administrate the mailing list: larjona

CommunityGovernance

2015-06-25T17:52:12Z

Ayleph: /* MediaGoblin issue tracker */ I have spam admin access

MediaGoblin is a community project and we everybody try to help each other. Chris Webber is our lead developer, but the project should be able to self govern so he can take a break if he needs it or when he or other contributors take deserved holidays :)

In general, you can ask anything in the mailing list or the IRC channel and hopefully somebody will answer soon. Topics are discussed in the mailing list, IRC channel or monthly meetings (in the IRC channel).

In this page we list several tasks or areas along with the names or nicks of MediaGoblin community members that may help on them (for example, because they have permissions to perform certain operations). Please be kind when asking for help, most of us are volunteering for MediaGoblin in our free time, so answers or problems resolution can take a while.

Feel free to edit this page to list more tasks or sign the ones you self-assign.

More information about this in this mailing list thread: http://lists.mediagoblin.org/pipermail/devel/XXXXX

== MediaGoblin codebase ==

* People with permissions to commit/merge and handle the main codebase

* General stuff: breton, Elrond (via PM on IRC)
* Python 3 support: berkerpeksag (berker on IRC), breton
* Audio/Video: breton
* Documentation: jcampbell / j1mc

== MediaGoblin website ==

* People with permissions to handle website outages

* Publish pages (for example new releases)

== MediaGoblin wiki ==

* Some Wiki administration: Elrond (via PM on IRC)

== MediaGoblin issue tracker ==

* Help triaging bugs: R13ose
* People with permissions to create accounts in trac: Elrond
* People with permissions to delete users/issues/comments in trac: Elrond
* Volunteers for spam cleaning: LArjona, ayleph
* Talk to trac people about spam: R13ose
* Would like more access to be able to help/fix things:

== MediaGoblin translation platform ==

* If there is need of manual import/export files between Pootle and the MediaGoblin codebase, who can help on that
* LArjona (Spanish translator) can guide new translators, reproduce problems in the translation platform, test changes, and help with Pootle quality checks. Available in the mailing list and IRC channel.
* breton knows how and why translations are downloaded/compiled

== MediaGoblin IRC channel and mailing list ==

* Change IRC topic, channel operators

Main Page

2015-01-15T01:04:26Z

Ayleph: Undo revision 1634 by MonikaQDCU (talk)

= Want to Join the MediaGoblin Community? =

We’re really glad that you want to join the MediaGoblin community!

There are a variety of ways to help and support MediaGoblin and to join the team. If you want to code, great, if not, even better! MediaGoblin interested contributors in many different roles: users, system administrators, technical writers, testers, evangelists, UI/UX and graphics designers, cheerleaders, and dreamers.

We observe the [https://www.djangoproject.com/conduct/ Django code of conduct]. Be welcoming, friendly, and patient!

This wiki covers a variety of ways that you can get involved with MediaGoblin as well as instructions on how to get started.

== Hang out with the MediaGoblin folk ==

MediaGoblin has a mailing list and an IRC channel where we hang out. See [http://mediagoblin.org/pages/join.html our join page] for links.

Please drop by and say “Hi!” And, if you’re looking for something to do, just ask---there’s always work to be done.

== Take Part in the Monthly Meetings ==

Each month is a [[:Meeting|Meeting]]. You can take part and help decide on the future of MediaGoblin. Or just be around and see what's happening live!

=How Can you help ?=

First and foremost, for many (but not all) types of contributions you may want to set up a local instance. To learn how to do this, see the [[HackingHowto]] page. (If you're not familiar with command line level things, there are still ways you can help below!)

== File Bugs / Triage Bugs ==

Issue reports are critical for all projects. Identified bugs give developers a basis for beginning work, and providing an idea of what features and issues are most important to users and the overall usability of the software. If you identify errors, flaws, unexpected behaviors, or deficits that impede use, file a bug.

* [[File Bugs]] -- notes on filing new bugs/issues/feature requests
* [[Feature Ideas]] -- notes on possible features
* [[Triage Bugs]] -- notes on triaging
* [[BugTriageDay]] -- every other Thursday is bug triage day where anyone can help out triaging bugs

== Send Encouragement / Spread the Word ==

Sometimes, a nice word, simple encouragement, and interest in the work we’re doing is enough to inspire a tizzy of productive work. Just a bit more interest and encouragement can even make the difference between a complete feature and limited functionality; between a completed milestone and lost momentum.

Similarly, MediaGoblin, and the movement for free network services, is always in need of encouragement. Use free network services, understand the principals behind the movement, be able to articulate the benefits of free network services and the problems with psudo-free applications that don’t respect the users’ freedom.

Write a blog post, post a status update, drop by the listserv or join #mediagoblin on freenode.net and let us know. See [http://mediagoblin.org/join/ our join page] for links.

== Write Documentation / Edit Documentation ==

* [[Documentation quick start]] - How to contribute to the documentation effort.
* [[ManualStandards]] - covers the standards for writing the user manual (forthcoming.)

== Test MediaGoblin ==

Do you have access to the web? Do you like sharing your opinions? If so, we need your help to test MediaGoblin! Testers play around with the current test instance, note what operating system and browser they use (notes on multiple set-ups are also helpful) and take some notes. That's it! It's a very important task that doesn't require any special knowledge and you're done in under an hour. Ready to help?

* [[User Experience]] - user experience testing. Includes link to an instance you can try!
* [[UnitTests|Unit Tests]] - all about the unit tests
* [[Manual_Functional_Testing|Manual Functional Testing]] - a great way to get to know MediaGoblin.

== Translate MediaGoblin ==

If you know English and another language and feel comfortable translating elements of the interface or even the documentation, we’d love to have help translating the software and resources.
Translating MediaGoblin is very easy with a web interface, so there is no programming knowledge required at all.

* [[Translations]] - How to translate stuff or update the translations

== Become a User ==

Coming soon!

We’re building MediaGoblin for us and for you but really you’re one of us and I am you and we are we and MediaGoblin is the walrus.

We're planning to launch our own public instance of MediaGoblin in the near future--probably in the September/October 2011 time frame. When we do, sign up for an account, use the service and relish in the thought that this service comes with a heaping side of Freedom and you can salt and pepper it to your liking.

== Help Others ==

Have you spent time with MediaGoblin? If so, your experience and wisdom are invaluable and you’re the best person we can think of to help other users with their questions.

Hang out on the IRC channel and help answer new peoples' questions. See [http://mediagoblin.org/join/ our join page] for links.

== Run your own MediaGoblin Instance ==

Are there things about our instance you want to change? Are there things about other instances you wish were different? Want to test upcoming changes? Want to create patches to implement things you need? That’s great—you can run your own instance!

The primary documentation for this is at [http://docs.mediagoblin.org http://docs.mediagoblin.org] but here are some additional tips:

* [[Configure_MediaGoblin|Configuration]] - Learn about MediaGoblin configuration files and file options.
* [[Deployment]] - General deployment advice
* [[Scaling Down]] - Minimizing MediaGoblin's resource requirements
* [[Virtual Machine Hosting]] - Deploy your own publicly available MediaGoblin server using [http://aws.amazon.com/free/?utm_source=adwords&utm_medium=cpc&utm_campaign=CPC_Google_AWS_ec2&utm_content=TextV01_PP_V01_EC2&trk=CPC_Google_AWS_ec2 Amazon's free EC2 tier].

= Technical project documentation =

The technical docs, that are more finished and the ones that are better maintained near the code (so they stay up to date) are in the more technical chapters of the [http://docs.mediagoblin.org/ main documentation].
* [[Storage]] - How MediaGoblin's internal storage system works.
* [[Processing]] - What happens after you submit your image/video/etc? Processing! More about that.
* [https://gitorious.org/mediagoblin/mediagoblin/blobs/master/extlib/README External Library Policy] - covers use of external libraries
* [[User:Cwebber/braindumps]] - Chris Webber's braindumps (you can help refactoring these into real sections of the site!)
* [[Multiple media support]] - Design plan for multiple media support

== Write Code / Fix Code ==

MediaGoblin development is premised on the idea that the entire interface for the platform be completely theme-able. If you have a design or theming background, consider developing themes for MediaGoblin. New themes help test the theming system, provide attractive and appealing interfaces for prospective users. If you want to start a new theme but don’t know where to start, touch base with the development community on the list or in the IRC channel for more information.

If you are a coder and you would like to write code, the repository is hosted on gitorious. Clone or fork the repository and start poking around. Become familiar with this manual for an overview of how the software works and is used. Consider the contributor wiki for more information about the project, our preferred methods, and guides for developing MediaGoblin. We even have tips on becoming a coder and we’re willing to help!

* [[HackingHowto|Hacking]] - notes on making and sending in code contributions
** [[BeginnersCorner|Beginner's Corner]] - resources for those who are new to Python or Git.
** ''Started from an older version of the Hacking Howto? We switched from buildout->virtualenv, so look at [[Moving from buildout to virtualenv]] for information on how to move over.''
* [[Git workflow]] - How to go about submitting patches via git.
* [[Code review tips]] - Tips on how to go about doing local code review
* [[Templating]] - How our templating structure is set up
* [[Code overview]] - Overview of the structure of the codebase

== Create a Theme ==

See [http://docs.mediagoblin.org/siteadmin/theming.html the theming docs]

== Write a plugin ==

If you start, you'll find some basic documentation [http://docs.mediagoblin.org/#part-4-developer-s-zone| in the docs site]

You've made a plugin ? List it here :

[[Available_Plugins|Available plugins]]

You've written a plugin ? You got some tips to share ? A tutorial idea ? Please do :

[[PluginsTips|Plugins Tips]]

= Misc =

== Android client ==

See [[Android Client]]

= Inner workings of the secret sanctum =

* [[IRCBot]] - covers our irc bot
* [[ReleaseProcess|Release Process]] - covers the release process
* [[Update the website]] - Learn how to update mediagoblin.org!

=FAQ=

[[GMG FAQ]]

Main Page

2015-01-15T01:04:04Z

Ayleph: Undo revision 1635 by TarenSlowik (talk)

To learn more info on [http://madlyfatherland08.sosblogs.com/The-first-blog-b1/baby-shop-b1-p2353.htm онлайн магазин за бебето] check out the [http://Www.Answers.com/topic/internet+site internet site].

Main Page

2015-01-15T01:03:49Z

Ayleph: Undo revision 1636 by SungGirardi (talk)

If you loved this report and you would like to get more facts regarding [https://Www.Gov.uk/search?q=%D0%B1%D0%B5%D0%B1%D0%B5%D1%88%D0%BA%D0%B8 бебешки] продукти NUK - [http://worthlesslid413.deviantart.com/status/ deviantart.com], kindly visit the [http://Www.europeana.eu/portal/search.html?query=web-site web-site].

Search

2014-11-01T01:07:08Z

Ayleph: added search plugin

Currently MG does not have any built-in search engine, but Praveen Kumar has developed a proposal during his [[GSOC_2013#Search_interface|GSOC 2013]] project. Some links:

* [http://mediagoblin.org/news/summer-of-awesome-wrapup.html Summer of Awesome Wrap-up blog post]
* [https://github.com/praveen97uma/GSoC-Docs/wiki/Search-Interface-for-MediaGoblin Documentation related to the project]
* [https://www.gitorious.org/mediagoblin/alons-mediagoblin/commits/74f0f0943305ab85dbc1a6c6495db92148ac716e Gitorious branch (being reviewed and polished)]

A basic search [[Available Plugins|plugin]] is also available from [https://github.com/ayleph/mediagoblin-search github]. The plugin is not as full-featured or as polished as the search function described above, but it does provide a quick and easy way to perform basic searches on an instance.

Main Page

2014-09-21T17:36:06Z

Ayleph: Undo revision 1585 by RethaLimavkh (talk)

= Want to Join the MediaGoblin Community? =

We’re really glad that you want to join the MediaGoblin community!

There are a variety of ways to help and support MediaGoblin and to join the team. If you want to code, great, if not, even better! MediaGoblin interested contributors in many different roles: users, system administrators, technical writers, testers, evangelists, UI/UX and graphics designers, cheerleaders, and dreamers.

We observe the [https://www.djangoproject.com/conduct/ Django code of conduct]. Be welcoming, friendly, and patient!

This wiki covers a variety of ways that you can get involved with MediaGoblin as well as instructions on how to get started.

== Hang out with the MediaGoblin folk ==

MediaGoblin has a mailing list and an IRC channel where we hang out. See [http://mediagoblin.org/pages/join.html our join page] for links.

Please drop by and say “Hi!” And, if you’re looking for something to do, just ask---there’s always work to be done.

== Take Part in the Monthly Meetings ==

Each month is a [[:Meeting|Meeting]]. You can take part and help decide on the future of MediaGoblin. Or just be around and see what's happening live!

=How Can you help ?=

First and foremost, for many (but not all) types of contributions you may want to set up a local instance. To learn how to do this, see the [[HackingHowto]] page. (If you're not familiar with command line level things, there are still ways you can help below!)

== File Bugs / Triage Bugs ==

Issue reports are critical for all projects. Identified bugs give developers a basis for beginning work, and providing an idea of what features and issues are most important to users and the overall usability of the software. If you identify errors, flaws, unexpected behaviors, or deficits that impede use, file a bug.

* [[File Bugs]] -- notes on filing new bugs/issues/feature requests
* [[Feature Ideas]] -- notes on possible features
* [[Triage Bugs]] -- notes on triaging
* [[BugTriageDay]] -- every other Thursday is bug triage day where anyone can help out triaging bugs

== Send Encouragement / Spread the Word ==

Sometimes, a nice word, simple encouragement, and interest in the work we’re doing is enough to inspire a tizzy of productive work. Just a bit more interest and encouragement can even make the difference between a complete feature and limited functionality; between a completed milestone and lost momentum.

Similarly, MediaGoblin, and the movement for free network services, is always in need of encouragement. Use free network services, understand the principals behind the movement, be able to articulate the benefits of free network services and the problems with psudo-free applications that don’t respect the users’ freedom.

Write a blog post, post a status update, drop by the listserv or join #mediagoblin on freenode.net and let us know. See [http://mediagoblin.org/join/ our join page] for links.

== Write Documentation / Edit Documentation ==

* [[Documentation quick start]] - How to contribute to the documentation effort.
* [[ManualStandards]] - covers the standards for writing the user manual (forthcoming.)

== Test MediaGoblin ==

Do you have access to the web? Do you like sharing your opinions? If so, we need your help to test MediaGoblin! Testers play around with the current test instance, note what operating system and browser they use (notes on multiple set-ups are also helpful) and take some notes. That's it! It's a very important task that doesn't require any special knowledge and you're done in under an hour. Ready to help?

* [[User Experience]] - user experience testing. Includes link to an instance you can try!
* [[UnitTests|Unit Tests]] - all about the unit tests
* [[Manual_Functional_Testing|Manual Functional Testing]] - a great way to get to know MediaGoblin.

== Translate MediaGoblin ==

If you know English and another language and feel comfortable translating elements of the interface or even the documentation, we’d love to have help translating the software and resources.
Translating MediaGoblin is very easy with a web interface, so there is no programming knowledge required at all.

* [[Translations]] - How to translate stuff or update the translations

== Become a User ==

Coming soon!

We’re building MediaGoblin for us and for you but really you’re one of us and I am you and we are we and MediaGoblin is the walrus.

We're planning to launch our own public instance of MediaGoblin in the near future--probably in the September/October 2011 time frame. When we do, sign up for an account, use the service and relish in the thought that this service comes with a heaping side of Freedom and you can salt and pepper it to your liking.

== Help Others ==

Have you spent time with MediaGoblin? If so, your experience and wisdom are invaluable and you’re the best person we can think of to help other users with their questions.

Hang out on the IRC channel and help answer new peoples' questions. See [http://mediagoblin.org/join/ our join page] for links.

== Run your own MediaGoblin Instance ==

Are there things about our instance you want to change? Are there things about other instances you wish were different? Want to test upcoming changes? Want to create patches to implement things you need? That’s great—you can run your own instance!

The primary documentation for this is at [http://docs.mediagoblin.org http://docs.mediagoblin.org] but here are some additional tips:

* [[Configure_MediaGoblin|Configuration]] - Learn about MediaGoblin configuration files and file options.
* [[Deployment]] - General deployment advice
* [[Scaling Down]] - Minimizing MediaGoblin's resource requirements
* [[Virtual Machine Hosting]] - Deploy your own publicly available MediaGoblin server using [http://aws.amazon.com/free/?utm_source=adwords&utm_medium=cpc&utm_campaign=CPC_Google_AWS_ec2&utm_content=TextV01_PP_V01_EC2&trk=CPC_Google_AWS_ec2 Amazon's free EC2 tier].

= Technical project documentation =

The technical docs, that are more finished and the ones that are better maintained near the code (so they stay up to date) are in the more technical chapters of the [http://docs.mediagoblin.org/ main documentation].
* [[Storage]] - How MediaGoblin's internal storage system works.
* [[Processing]] - What happens after you submit your image/video/etc? Processing! More about that.
* [https://gitorious.org/mediagoblin/mediagoblin/blobs/master/extlib/README External Library Policy] - covers use of external libraries
* [[User:Cwebber/braindumps]] - Chris Webber's braindumps (you can help refactoring these into real sections of the site!)
* [[Multiple media support]] - Design plan for multiple media support

== Write Code / Fix Code ==

MedaGoblin development is premised on the idea that the entire interface for the platform be completely theme-able. If you have a design or theming background, consider developing themes for MediaGoblin. New themes help test the theming system, provide attractive and appealing interfaces for prospective users. If you want to start a new theme but don’t know where to start, touch base with the development community on the list or in the IRC channel for more information.

If you are a coder and you would like to write code, the repository is hosted on gitorious. Clone or fork the repository and start poking around. Become familiar with this manual for an overview of how the software works and is used. Consider the contributor wiki for more information about the project, our preferred methods, and guides for developing MediaGoblin. We even have tips on becoming a coder and we’re willing to help!

* [[HackingHowto|Hacking]] - notes on making and sending in code contributions
** [[BeginnersCorner|Beginner's Corner]] - resources for those who are new to Python or Git.
** ''Started from an older version of the Hacking Howto? We switched from buildout->virtualenv, so look at [[Moving from buildout to virtualenv]] for information on how to move over.''
* [[Git workflow]] - How to go about submitting patches via git.
* [[Code review tips]] - Tips on how to go about doing local code review
* [[Templating]] - How our templating structure is set up
* [[Code overview]] - Overview of the structure of the codebase

== Create a Theme ==

See [http://docs.mediagoblin.org/siteadmin/theming.html the theming docs]

== Write a plugin ==

If you start, you'll find some basic documentation [http://docs.mediagoblin.org/#part-4-developer-s-zone| in the docs site]

You've made a plugin ? List it here :

[[Available_Plugins|Available plugins]]

You've written a plugin ? You got some tips to share ? A tutorial idea ? Please do :

[[PluginsTips|Plugins Tips]]

= Misc =

== Android client ==

See [[Android Client]]

= Inner workings of the secret sanctum =

* [[IRCBot]] - covers our irc bot
* [[ReleaseProcess|Release Process]] - covers the release process
* [[Update the website]] - Learn how to update mediagoblin.org!

=FAQ=

[[GMG FAQ]]

Main Page

2014-09-21T17:35:51Z

Ayleph: Undo revision 1586 by Anitra2502 (talk)

คอบอลลีกต่างๆพากันดู [http://www.bestballwin.com สายบอล] ที่เว็บนี้และติดตามข่าว ดัชนีนิกเกอิปรับตัวลดลงปิดในแดนลบเป็นวันที่ 5 ติดต่อกัน และปิดที่ระดับต่ำสุดในรอบประมาณ 1 เดือนครึ่ง ในวันนี้ หลังจากตัวเลขจ้างงานสหรัฐที่มีการเปิดเผยเมื่อวันศุกร์ที่ผ่านมาได้จุดชนวนความวิตกกังวลเกี่ยวกับการฟื้นตัวของเศรษฐกิจสหรัฐ สำนักข่าวเกียวโดรายงานว่า ดัชนีนิกเกอิตลาดหุ้นโตเกียวร่วงลง 142.19 จุด หรือ 1.47% ปิดที่ 9,546.26 จุด ซึ่งเป็นระดับปิดต่ำสุดนับตั้งแต่วันที่ 21 ก.พ.เป็นต้นมา โดยหุ้นทั้ง 33 กลุ่มปรับตัวลง นำโดยหุ้นกลุ่มประกัน ตามด้วยกลุ่มเหมืองแร่และโลหะนอกกลุ่มเหล็ก โบรกเกอร์กล่าวว่า ดัชนีนิกเกอิร่วงลงสู่ระดับ 9,500 จุดเป็นครั้งแรกในรอบกว่าหนึ่งเดือน หลังจากที่กระทรวงแรงงานสหรัฐเปิดเผยเมื่อวันศุก[http://Www.Bing.com/search?q=%E0%B8%A3%E0%B9%8C%E0%B8%A7%E0%B9%88%E0%B8%B2&form=MSNNWS&mkt=en-us&pq=%E0%B8%A3%E0%B9%8C%E0%B8%A7%E0%B9%88%E0%B8%B2 ร์ว่า] ตัวเลขจ้างงานนอกภาคเกษตรเพิ่มขึ้น 120,000 ตำแหน่งในเดือนมี.ค. ซึ่งน้อยกว่าคาดการณ์ของนักเศรษฐศาสตร์ส่วนใหญ่ที่ว่าจะเพิ่มขึ้น 203,000 ตำแหน่ง และต่ำกว่าค่าเฉลี่ยในช่วง 3 เดือนก่อนที่ 246,000 ตำแหน่ง นอกจากนี้ ตลาดหุ้นโตเกียวยังได้รับแรงกดดันจากเงินเยนที่แข็งค่าขึ้นหลังจากที่มีการเปิดเผยข้อมูลดังกล่าว โดยเงินดอลลาร์สหรัฐมีการซื้อขายอยู่ใน[http://Search.Un.org/search?ie=utf8&site=un_org&output=xml_no_dtd&client=UN_Website_en&num=10&lr=lang_en&proxystylesheet=UN_Website_en&oe=utf8&q=%E0%B8%8A%E0%B9%88%E0%B8%A7%E0%B8%87&Submit=Go ช่วง] 81 เยนกลางๆ เมื่อเทียบกับระดับ 82 เยนกลางๆ ในการซื้อขายเมื่อวันศุกร์ที่แล้ว ขณะที่ยูโรเคลื่อนไหวในช่วง 106 เยนกลางๆ เทียบกับ 107 เยนปลายๆ ในสัปดาห์ก่อน

Deployment

2014-09-09T07:11:19Z

Ayleph: /* Init scripts */ added systemd scripts

This page could use a lot of work. For now, a few smaller deployment tips!

See also: http://docs.mediagoblin.org/deploying.html (some of which may belong here)

= uwsgi =

Possibly a cleaner way to do nginx configuration than the official nginx + fastcgi suggestions!

http://qalthos.github.io/blog/FOSS@RIT/deploying-mediagoblin-1-fastcgi-vs-uwsgi.html

= uwsgi with configs =

Below there are 3 configs: for nginx, for uwsgi version 1.2.3-debian and for supervisord, used to run celery.

In future, when newer versions of uwsgi appear in debian, supervisor can be removed.

All instructions below are for Debian 7. They should also work with rpm-based systems, but with other paths.

<pre>apt-get install uwsgi uwsgi-plugin-python nginx-full supervisor;</pre>

/etc/nginx/sites-available/mediagoblin:
<pre>
server {
server_name <domain>;

access_log /var/log/nginx/mg.access.log;
error_log /var/log/nginx/mg.error.log error;

#include global/common.conf;

client_max_body_size 100m;
add_header X-Content-Type-Options nosniff;

root /path/to/mediagoblin//user_dev/;

location /mgoblin_static/ {
alias /path/to/mediagoblin/mediagoblin/static/;
}
location /mgoblin_media/ {
alias /path/to/mediagoblin/user_dev/media/public/;
}
location /theme_static/ {
}
location /plugin_static/ {
}
location / {
uwsgi_pass unix:///tmp/mg.uwsgi.sock;
uwsgi_param SCRIPT_NAME "/";
include uwsgi_params;
}
}
</pre>

/etc/uwsgi/apps-available/mg.yaml:
<pre>
uwsgi:
uid: mediagoblin
gid: mediagoblin
socket: /tmp/mg.uwsgi.sock
chown-socket: www-data:www-data
plugins: python
home: /path/to/mediagoblin/
chdir: /path/to/mediagoblin/
ini-paste: /path/to/mediagoblin/paste_local.ini
</pre>

/etc/supervisor/conf.d/mediagoblin.conf:
<pre>
[program:celery]
command=/path/to/mediagoblin/bin/celery worker -l debug

; Set PYTHONPATH to the directory containing celeryconfig.py
environment=PYTHONPATH="/path/to/mediagoblin",MEDIAGOBLIN_CONFIG="/path/to/mediagoblin/mediagoblin_local.ini",CELERY_CONFIG_MODULE="mediagoblin.init.celery.from_celery"

directory=/path/to/mediagoblin/
user=mediagoblin
numprocs=1
; uncomment below to enable logs saving
;stdout_logfile=/some/logs/path/celeryd_stdout.log
;stderr_logfile=/some/logs/path/celeryd_stderr.log
autostart=true
autorestart=false
startsecs=10

; Need to wait for currently executing tasks to finish at shutdown.
; Increase this if you have very long running tasks.
stopwaitsecs = 600
</pre>

After setting all configs do:
<pre>
ln -s /etc/nginx/sites-available/mediagoblin /etc/nginx/sites-enabled/
ln -s /etc/uwsgi/apps-available/mg.yaml /etc/uwsgi/apps-enabled/
</pre>

= FCGI script =

This works great with the apache FCGID config example in the next section :) in which case you should name it "mg.fcgi".

Before use, make sure you replace '/path/to/mediagoblin/bin/python' with a real path on your server, e.g. '/srv/www/myhomepage.com/mediagoblin/bin/python'. Also replace '/path/to/mediagoblin/paste.ini'.

If you encounter problems, try executing executing the script manually, e.g. <pre>./mg.fcgi</pre>

Script:

<pre>#!/path/to/mediagoblin/bin/python

# Written in 2011 by Christopher Allan Webber
#
# To the extent possible under law, the author(s) have dedicated all
# copyright and related and neighboring rights to this software to the
# public domain worldwide. This software is distributed without any
# warranty.
#
# You should have received a copy of the CC0 Public Domain Dedication along
# with this software. If not, see
# <http://creativecommons.org/publicdomain/zero/1.0/>.

from paste.deploy import loadapp
from flup.server.fcgi import WSGIServer

CONFIG_PATH = '/path/to/mediagoblin/paste.ini'

## Uncomment this to run celery in "always eager" mode... ie, you don't have
## to run a separate process, but submissions wait till processing finishes
# import os
# os.environ['CELERY_ALWAYS_EAGER'] = 'true'

def launch_fcgi():
ccengine_wsgi_app = loadapp('config:' + CONFIG_PATH)
WSGIServer(ccengine_wsgi_app).run()

if __name__ == '__main__':
launch_fcgi()</pre>

= Apache 2 Config With fcgid =

Note that the libapache2-mod-fcgi in Debian is in the main section. libapache2-mod-fcgid can be used, but requires a slightly different configuration. For yum-based distributions, you may need to install mod_fcgid.

<VirtualHost *:80>
Options +ExecCGI

# Accept up to 16MB requests
FcgidMaxRequestLen 16777216

ServerName mediagoblin.example.org

Alias /mgoblin_static/ /path/to/mediagoblin/mediagoblin/static/
Alias /mgoblin_media/ /path/to/mediagoblin/user_dev/media/public/

ScriptAlias / /path/to/mediagoblin/mg.fcgi/
</VirtualHost>

= Apache 2 Config With mod_wsgi =

Apache can manage the MediaGoblin application itself with mod_wsgi. It requires slightly more configuration on the Apache side, but cuts out the FastCGI middleware. See their [http://code.google.com/p/modwsgi/wiki/ConfigurationGuidelines configuration guidelines] for advanced configuration.

<VirtualHost *:80>
ServerName mediagoblin.example.org

Alias /mgoblin_static/ /path/to/mediagoblin/mediagoblin/static/
Alias /mgoblin_media/ /path/to/mediagoblin/user_dev/media/public/

WSGIScriptAlias / /path/to/mediagoblin/wsgi.py
# Set user and group to whatever user you used to install mediagoblin (if you used a system account,
# it may have the group 'nogroup' assigned, in that case you can remove the group parameter)
# Remember to change python-path too!
# Replace the python version in the 'python-path' below with the correct one (eg 2.x -> 2.7)
WSGIDaemonProcess gmg user=mediagoblin group=mediagoblin processes=2 threads=10 \
umask=0007 inactivity-timeout=900 maximum-requests=1000 \
python-path=/path/to/mediagoblin/:/path/to/mediagoblin/lib/python-2.x/site-packages/
WSGIProcessGroup gmg
WSGIApplicationGroup %{GLOBAL}

<Directory "/path/to/mediagoblin/mediagoblin/static/">
Order allow,deny
Allow from all
</Directory>
<Directory "/path/to/mediagoblin/user_dev/media/public">
Order allow,deny
Allow from all
</Directory>
</VirtualHost>

You'll also need to copy this into /path/to/mediagoblin/wsgi.py:

#!/path/to/mediagoblin/bin/python

# Written in 2011 by Christopher Allan Webber
#
# To the extent possible under law, the author(s) have dedicated all
# copyright and related and neighboring rights to this software to the
# public domain worldwide. This software is distributed without any
# warranty.
#
# You should have received a copy of the CC0 Public Domain Dedication along
# with this software. If not, see
# <http://creativecommons.org/publicdomain/zero/1.0/>.

import site
# Replace the python version with the correct one in the line below (eg 2.x -> 2.7)
site.addsitedir('/path/to/mediagoblin/lib/python-2.x/site-packages')

from paste.deploy import loadapp

CONFIG_PATH = '/path/to/mediagoblin/paste.ini'

## Uncomment this to run celery in "always eager" mode... ie, you don't have
## to run a separate process, but submissions wait till processing finishes
#import os
#os.environ['CELERY_ALWAYS_EAGER'] = 'true'

application = loadapp('config:' + CONFIG_PATH)

= Apache Config Example =
This configuration example uses mod_fastcgi.

To install and enable mod_fastcgi on a Debian/Ubuntu based system:
<pre># apt-get install libapache2-mod-suexec libapache2-mod-fastcgi
# a2enmod suexec
# a2enmod fastcgi</pre>

Sample configuration:
<pre>
<VirtualHost *:80>
ServerName mediagoblin.yourdomain.tld
ServerAdmin webmaster@yourdoimain.tld
DocumentRoot /var/www/
# Custom log files
CustomLog /var/log/apache2/mediagobling_access.log combined
ErrorLog /var/log/apache2/mediagoblin_error.log

# Serve static and media files via alias
Alias /mgoblin_static/ /path/to/mediagoblin/mediagoblin/static/
Alias /mgoblin_media/ /path/to/mediagoblin/user_dev/media/public/

# Rewrite all URLs to fcgi, except for static and media urls
RewriteEngine On
RewriteRule ^(mgoblin_static|mgoblin_media)($|/) - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^/(.*)$ /mg.fcgi/$1 [QSA,L]

# Allow access to static and media directories
<Directory /path/to/mediagoblin/mediagoblin/static>
Order allow,deny
Allow from all
</Directory>
<Directory /path/to/mediagoblin/mediagoblin/user_dev/media/public>
Order allow,deny
Allow from all
</Directory>

# Connect to fcgi server
FastCGIExternalServer /var/www/mg.fcgi -host 127.0.0.1:26543
</VirtualHost>
</pre>
Then, you need to make sure mediagoblin is running in fcgi mode:
<pre>cd /path/to/mediagoblin
./lazyserver.sh --server-name=fcgi fcgi_host=127.0.0.1 fcgi_port=26543</pre>

Note: there may be several ways to improve this configuration

If it is too slow and you use the deflate module, you could try to use the following option : SetOutputFilter INFLATE

= Lighttpd =

This configuration example uses mod_fastcgi.
Make a symbolic link from <pre>/etc/lighttpd/conf-available/10-fastcgi.conf</pre> to <pre>/etc/lighttpd/conf-enabled/10-fastcgi.conf</pre>

<pre>
ln -s /etc/lighttpd/conf-available/10-fastcgi.conf /etc/lighttpd/conf-enabled/10-fastcgi.conf
</pre>

then edit your /etc/lighttpd/conf-enabled/10-fastcgi.conf file modifying it as below to serve mediagoblin on the /tube/ path of your webserver.

<pre>
## FastCGI programs have the same functionality as CGI programs,
## but are considerably faster through lower interpreter startup
## time and socketed communication
##
## Documentation: /usr/share/doc/lighttpd-doc/fastcgi.txt.gz
## http://www.lighttpd.net/documentation/fastcgi.html

server.modules += ( "mod_fastcgi" )

## Start an FastCGI server for mediagoblin (lazyserver.sh or other deployments scripts should be up and running)
fastcgi.server = (
# url at which the app should be accessible on the server
"/tube" =>
# mnemonical name of the backend
( "mg-local" => (
"host" => "127.0.0.1",
"port" => 6543,
"docroot" => "/path/to/mediagoblin-git-folder/mediagoblin",
"check-local" => "disable"
)
)

)
</pre>

Then open your /etc/lighttpd/lighttpd.conf and add the configuration to serve directly the static/public folders

<pre>
alias.url += (
"/mgoblin_static/" => "/path/to/mediagoblin-git-folder/mediagoblin/static/",
"/mgoblin_media/" => "/path/to/mediagoblin-git-folder/user_dev/media/public/",
"/theme_static/" => "/path/to/mediagoblin-git-folder/user_dev/theme_static/",
"/plugin_static/" => "/path/to/mediagoblin-git-folder/user_dev/plugin_static/"
)

</pre>

Done!

= OpenShift =

Thers's a blogpost saying how to [http://www.sud0.com/gnu-media-goblin-on-openshift.html install mediagoblin on openshift].

= Juju =

There is a juju [https://juju.ubuntu.com/Charms charm] available for deploying mediagoblin into EC2 or on your local box. [https://juju.ubuntu.com/ juju] is available in Ubuntu 11.10 and later, though it is recommended that you pull it from [https://launchpad.net/~juju/+archive/pkgs the juju PPA], which includes backported packages going back to Ubuntu 11.10. To use the juju charm, install juju and configure either the [https://juju.ubuntu.com/docs/provider-configuration-local.html local provider] or one of the cloud API providers, currently the [https://juju.ubuntu.com/docs/provider-configuration-ec2.html EC2 provider] is the best supported and works not only with Amazon Web Services but also OpenStack clouds. There is also a newer native OpenStack API provider which is known to support HP Cloud.
<pre>
# if you have not bootstrapped
juju bootstrap
mkdir ~/charms
bzr init-repo ~/charms/precise
bzr branch lp:~clint-fewbar/charms/precise/mediagoblin/trunk ~/charms/precise/mediagoblin
juju deploy --repository ~/charms local:mediagoblin
juju expose mediagoblin
</pre>

Currently the charm is volatile, deploying from trunk, and deploys a single-server version of MediaGoblin only. It will eventually relate to the existing juju charms for other supported data stores to allow one to scale out their MediaGoblin instance.

= Init scripts =

== Debian init scripts ==

Joar has some scripts for running celery and mediagoblin separately that are designed for Debian.

https://github.com/joar/mediagoblin-init-scripts

== Arch Linux init scripts ==

[http://whird.jpope.org/2012/04/14/mediagoblin-archlinux-rcd-scripts Jeremy Pope has written a nice blogpost] on how to add init scripts to deploy MediaGoblin with both the python paste http server and the celery deployments separated.

If you want a simpler setup and don't want to deploy celery separately, consider either turning CELERY_ALWAYS_EAGER to true in the paste init script described above, or check out [http://chimo.chromic.org/2012/03/01/mediagoblin-init-script-on-archlinux/ Chimo's guide].

== Generic, simple init script ==

This is a super stupidly simple init script that was used for mediagoblin.com... note that this has Celery running in always eager mode.

You will need to adjust the paths appropriately. This could probably be better written!

#! /bin/sh

## Stupidly simple mediagoblin init script.
#
# Written in 2012 by Christopher Allan Webber
#
# To the extent possible under law, the author(s) have dedicated all
# copyright and related and neighboring rights to this software to the
# public domain worldwide. This software is distributed without any
# warranty.
#
# You should have received a copy of the CC0 Public Domain Dedication along
# with this software. If not, see
# <http://creativecommons.org/publicdomain/zero/1.0/>.

PASTER=/srv/mediagoblin.com/bin/paster
PASTE_CONFIG=/srv/mediagoblin.com/paste.ini
OPTIONS="--pid-file=/tmp/mediagoblin.pid \
--log-file=/srv/mediagoblin.com/paster.log \
--server-name=fcgi fcgi_host=127.0.0.1 fcgi_port=26543"

CELERY_ALWAYS_EAGER=true su -pc "$PASTER serve $PASTE_CONFIG $1 $OPTIONS" webadmin

== systemd init scripts ==

The following systemd scripts provide separate Paste and Celery instances. Replace <code>/path/to/mediagoblin</code> to match your install path. The directories <code>/var/log/mediagoblin</code> and <code>/var/run/mediagoblin</code> are not created by default; you may create them yourself or change the location of the pid and log files. You may omit the log file if you choose. The init scripts provided below assume customized versions of mediagoblin.ini and paste.ini have been created as mediagoblin_local.ini and paste_local.ini, respectively; you should change those lines to point back to the original mediagoblin.ini or paste.ini files if you haven't made customizations.

If you prefer not to run separate Celery, uncomment <code>Environment=CELERY_ALWAYS_EAGER=true</code> and comment <code>Environment=CELERY_ALWAYS_EAGER=false</code>. You won't need the file <code>/etc/systemd/system/gmg-celery.service</code>.

<code>/etc/systemd/system/gmg.service</code>:

[Unit]
Description=Mediagoblin

[Service]
Type=forking
User=mediagoblin
Group=mediagoblin
#Environment=CELERY_ALWAYS_EAGER=true
Environment=CELERY_ALWAYS_EAGER=false
WorkingDirectory=/path/to/mediagoblin
ExecStart=/path/to/mediagoblin/bin/paster serve \
/path/to/mediagoblin/paste_local.ini \
--pid-file=/var/run/mediagoblin/paster.pid \
--log-file=/var/log/mediagoblin/paster.log \
--daemon \
--server-name=fcgi fcgi_host=127.0.0.1 fcgi_port=26543
ExecStop=/path/to/mediagoblin/bin/paster serve \
--pid-file=/var/run/mediagoblin/paster.pid \
/path/to/mediagoblin/paste_local.ini stop
PIDFile=/var/run/mediagoblin/mediagoblin.pid

[Install]
WantedBy=multi-user.target

<code>/etc/systemd/system/gmg-celeryd.service</code>:

[Unit]
Description=Mediagoblin Celeryd

[Service]
User=mediagoblin
Group=mediagoblin
Type=simple
WorkingDirectory=/path/to/mediagoblin
Environment="MEDIAGOBLIN_CONFIG=/path/to/mediagoblin/mediagoblin_local.ini" \
CELERY_CONFIG_MODULE=mediagoblin.init.celery.from_celery
ExecStart=/path/to/mediagoblin/bin/celeryd
PIDFile=/var/run/mediagoblin/mediagoblin-celeryd.pid

[Install]
WantedBy=multi-user.target

Invoke the Paste or Celery processes using systemctl. Eg,

$ sudo systemctl start|stop|restart gmg.service

$ sudo systemctl start|stop|restart gmg-celeryd.service

= Running on Dreamhost.com =

===Set up your python virtualenv===

dreamhost.com servers come with python 2.4 and 2.5 installed which is too old for mediagoblin. This means you need to compile and install a newer python (don't worry this is really not difficult on dreamhost servers). In order to be able to install python packages for a local user without touching system files, we need to setup a python ''virtualenv''. Fortunately, this is not too tricky either. If your server has python 2.6 or 2.7 installed already, you can skip the [[#Install a local python|python installation stuff]] and you'll only need to [[#Setup virtualenv to install local python packages|install virtualenv]].

====Install a local python====
# Download the latest python: http://python.org/ftp/python/XXX/Python-XXX.tar.bz2
# Unpack with <pre>tar xvjf Python-XXX.tar.bz2</pre>
# ''cd'' into the directory and compile and install python locally:
<blockquote><pre>./configure --prefix=$HOME/local
make
make install</pre></blockquote>
:This will install python (I used 2.7.3) into /home/<USERNAME>/local/bin/python. You might get warnings about some modules not being able to compile. :It was tcl/tk and bzip2 mainly, but things still worked out overall.
:
:You should now be able to invoke <tt>~/local/bin/python</tt> and fall into a shell of your new python (exit with ctrl-d). Congrats, you have now a new python 2.7 that you can use. However, you will need to be able to install additional packages as a user and this is what virtualenv allows.

====Setup virtualenv to install local python packages====
# Download the latest virtualenv: http://pypi.python.org/packages/source/v/virtualenv/XXX
# Install the virtualenv: <blockquote><pre>~/local/bin/python ~/virtualenv-1.8/virtualenv.py $HOME/local/virtenv</pre></blockquote>
:: You will now have: ~/local/virtenv/bin/python
# In ~/.bash_profile add: <blockquote><pre>PATH=~/local/virtenv/bin:~/local/bin:${PATH}</pre></blockquote>
:: so that your local python will be preferred.
:: Log out, log in again and test python" to see which version will be invoked. It should be the new python. Check "which easy_install" to see if the one in local/virtenv would be executed.
::
:: You have now 1) a local ''python'' installation that you can use, and 2) ''easy_install'' will also work with your local user installation. From now on you can e.g. locally install the nose testing framework (''easy_install nose'') and use it (''python -c "import nose"'').

===Install mediagoblin as a site package===

# Check out mediagoblin from git to e.g. ~/mediagoblin
# Install MediaGoblin and all dependencies for MediaGoblin with easy_install.
:* In the mediagoblin directory issue:
:<blockquote><pre>python setup.py</pre></blockquote>
:* You will also need to: easy_install lxml
:* Python-image was trickier to install: <pre>easy_install --find-links http://www.pythonware.com/products/pil/ Imaging</pre>
::Test by leaving the mediagoblin directory and see if you can import it: <pre>python -c "import mediagoblin"</pre> looking for error messages.

===Set up an WSGI environment on Dreamhost===

# Enable the mod_passenger setting for ruby/python in the domains web panel
# ''cd'' into the domain directory (e.g. ~/media.sspaeth.de for me)
# Copy mediagoblin.ini and paste.ini from the ~/mediagoblin directory here
# Create passenger_wsgi.py in your domain directory (e.g. ~/media.sspaeth.de for me):
<blockquote><pre>import sys, os
INTERP = "/home/<username>/local/virtenv/bin/python"
#INTERP is present twice so that the new python interpreter knows the actual executable path
if sys.executable != INTERP: os.execl(INTERP, INTERP, *sys.argv)

from paste.deploy import loadapp
application = loadapp('config:/home/mediagoblin/media.sspaeth.de/paste.ini')

#If in case of errors, all you get are mysterious error 500, you can set debug=true in paste.ini to see stack traces
# Otherwise, add this:
#from paste.exceptions.errormiddleware import ErrorMiddleware
#application = ErrorMiddleware(application, debug=True)</pre></blockquote>
# Set up the database by issueing: <pre>gmg dbupdate</pre>
# (optional but recommended) Serve the static files directly from the webserver.
:In paste.ini in this section: [composite:routing] comment out the static files:
#/mgoblin_static/ = mediagoblin_static
#/theme_static/ = theme_static
:and symlink the mediagobin/mediagoblin/static directoy to public/mgoblin_static
: and mediagoblin/mediagoblin/themes to public/theme_static
:
:so it is displayed directly. This step might be different depending on your web server configuration. There is no reason that static
:files need to go through all the python indirection when they can be served directly by nginx/apache/...
:
:In case you want to delete your git checkout after the installation (you don't need it, since you installed the mediagoblin package to ~/local/virtenv/lib/python2.7/mediagoblin... you should do the symlinking from there.
===Open Issues===
Please fill in the blanks if you find them out:
* How to enable logging to a file or standard html logs? Console output just disappears.
* How to set up things not using sqlite. What's wrong with mySQL?

===Troubleshooting===
* First of all: invoke <pre>python passenger_wsgi.py</pre> directly from the shell. This will tell you if there are import errors etc. If this command exits without any output on the console, you have already achieved a lot.
* In ''paste.ini'' set debug=true. This will show you python backtraces directly in the web page
* You will need to configure an smtp user/passwd/server in mediagoblin.ini, so you actually get the account creation token mailed out. Hint, the relevant settings are: <blockquote><pre>email_debug_mode = false
email_sender_address = postmaster@sspaeth.de
email_smtp_host = SMTP.DOMAIN.TLD
email_smtp_user = USERNAME
email_smtp_pass = WEIRDPASSWORD</pre></blockquote>
* In case you can upload media, but it does not appear. You don't have the celery server running. Add <pre>CELERY_ALWAYS_EAGER = true</pre> to the ''[celery]'' section in mediagoblin.ini

=Miscellaneous Hacks=
==Force translation==
There might some conditions under which you would prefer that MediaGoblin always return the same translation. If you are deploying with nginx and fastcgi, you can force MediaGoblin to return a specific translation regardless of browser preferences by passing a specific HTTP_ACCEPT_LANGUAGE fastcgi parameter in your location block. Example last line in location block:
<nowiki>
fastcgi_param HTTP_ACCEPT_LANGUAGE es; #force spanish translation
</nowiki>

==Create an admin user==

To create an admin user, first create the user you need either via the website or the command
<pre>
./bin/gmg adduser
</pre>

Then to turn it into an admin account use

<pre>
./bin/gmg makeadmin your_username
</pre>

Main Page

2014-05-21T22:36:24Z

Ayleph: Undo revision 1531 by Jenifferhomes (talk) Undo spam edit

= Want to Join the MediaGoblin Community? =

We’re really glad that you want to join the MediaGoblin community!

There are a variety of ways to help and support MediaGoblin and to join the team. If you want to code, great, if not, even better! MediaGoblin interested contributors in many different roles: users, system administrators, technical writers, testers, evangelists, UI/UX and graphics designers, cheerleaders, and dreamers.

We observe the [https://www.djangoproject.com/conduct/ Django code of conduct]. Be welcoming, friendly, and patient!

This wiki covers a variety of ways that you can get involved with MediaGoblin as well as instructions on how to get started.

== Hang out with the MediaGoblin folk ==

MediaGoblin has a mailing list and an IRC channel where we hang out. See [http://mediagoblin.org/pages/join.html our join page] for links.

Please drop by and say “Hi!” And, if you’re looking for something to do, just ask---there’s always work to be done.

== Take Part in the Monthly Meetings ==

Each month is a [[:Category:Meeting|Meeting]]. You can take part and help decide on the future of MediaGoblin. Or just be around and see what's happening live!

=How Can you help ?=

First and foremost, for many (but not all) types of contributions you may want to set up a local instance. To learn how to do this, see the [[HackingHowto]] page. (If you're not familiar with command line level things, there are still ways you can help below!)

== File Bugs / Triage Bugs ==

Issue reports are critical for all projects. Identified bugs give developers a basis for beginning work, and providing an idea of what features and issues are most important to users and the overall usability of the software. If you identify errors, flaws, unexpected behaviors, or deficits that impede use, file a bug.

* [[File Bugs]] -- notes on filing new bugs/issues/feature requests
* [[Feature Ideas]] -- notes on possible features
* [[Triage Bugs]] -- notes on triaging
* [[BugTriageDay]] -- every other Thursday is bug triage day where anyone can help out triaging bugs

== Send Encouragement / Spread the Word ==

Sometimes, a nice word, simple encouragement, and interest in the work we’re doing is enough to inspire a tizzy of productive work. Just a bit more interest and encouragement can even make the difference between a complete feature and limited functionality; between a completed milestone and lost momentum.

Similarly, MediaGoblin, and the movement for free network services, is always in need of encouragement. Use free network services, understand the principals behind the movement, be able to articulate the benefits of free network services and the problems with psudo-free applications that don’t respect the users’ freedom.

Write a blog post, post a status update, drop by the listserv or join #mediagoblin on freenode.net and let us know. See [http://mediagoblin.org/join/ our join page] for links.

== Write Documentation / Edit Documentation ==

* [[Documentation quick start]] - How to contribute to the documentation effort.
* [[ManualStandards]] - covers the standards for writing the user manual (forthcoming.)

== Test MediaGoblin ==

Do you have access to the web? Do you like sharing your opinions? If so, we need your help to test MediaGoblin! Testers play around with the current test instance, note what operating system and browser they use (notes on multiple set-ups are also helpful) and take some notes. That's it! It's a very important task that doesn't require any special knowledge and you're done in under an hour. Ready to help?

* [[User Experience]] - user experience testing. Includes link to an instance you can try!
* [[UnitTests|Unit Tests]] - all about the unit tests
* [[Manual_Functional_Testing|Manual Functional Testing]] - a great way to get to know MediaGoblin.

== Translate MediaGoblin ==

If you know English and another language and feel comfortable translating elements of the interface or even the documentation, we’d love to have help translating the software and resources.
Translating MediaGoblin is very easy with a web interface, so there is no programming knowledge required at all.

* [[Translations]] - How to translate stuff or update the translations

== Become a User ==

Coming soon!

We’re building MediaGoblin for us and for you but really you’re one of us and I am you and we are we and MediaGoblin is the walrus.

We're planning to launch our own public instance of MediaGoblin in the near future--probably in the September/October 2011 time frame. When we do, sign up for an account, use the service and relish in the thought that this service comes with a heaping side of Freedom and you can salt and pepper it to your liking.

== Help Others ==

Have you spent time with MediaGoblin? If so, your experience and wisdom are invaluable and you’re the best person we can think of to help other users with their questions.

Hang out on the IRC channel and help answer new peoples' questions. See [http://mediagoblin.org/join/ our join page] for links.

== Run your own MediaGoblin Instance ==

Are there things about our instance you want to change? Are there things about other instances you wish were different? Want to test upcoming changes? Want to create patches to implement things you need? That’s great—you can run your own instance!

The primary documentation for this is at [http://docs.mediagoblin.org http://docs.mediagoblin.org] but here are some additional tips:

* [[Configure_MediaGoblin|Configuration]] - Learn about MediaGoblin configuration files and file options.
* [[Deployment]] - General deployment advice
* [[Scaling Down]] - Minimizing MediaGoblin's resource requirements
* [[Virtual Machine Hosting]] - Deploy your own publicly available MediaGoblin server using [http://aws.amazon.com/free/?utm_source=adwords&utm_medium=cpc&utm_campaign=CPC_Google_AWS_ec2&utm_content=TextV01_PP_V01_EC2&trk=CPC_Google_AWS_ec2 Amazon's free EC2 tier].

= Technical project documentation =

The technical docs, that are more finished and the ones that are better maintained near the code (so they stay up to date) are in the more technical chapters of the [http://docs.mediagoblin.org/ main documentation].
* [[Storage]] - How MediaGoblin's internal storage system works.
* [[Processing]] - What happens after you submit your image/video/etc? Processing! More about that.
* [https://gitorious.org/mediagoblin/mediagoblin/blobs/master/extlib/README External Library Policy] - covers use of external libraries
* [[User:Cwebber/braindumps]] - Chris Webber's braindumps (you can help refactoring these into real sections of the site!)
* [[Multiple media support]] - Design plan for multiple media support

== Write Code / Fix Code ==

MedaGoblin development is premised on the idea that the entire interface for the platform be completely theme-able. If you have a design or theming background, consider developing themes for MediaGoblin. New themes help test the theming system, provide attractive and appealing interfaces for prospective users. If you want to start a new theme but don’t know where to start, touch base with the development community on the list or in the IRC channel for more information.

If you are a coder and you would like to write code, the repository is hosted on gitorious. Clone or fork the repository and start poking around. Become familiar with this manual for an overview of how the software works and is used. Consider the contributor wiki for more information about the project, our preferred methods, and guides for developing MediaGoblin. We even have tips on becoming a coder and we’re willing to help!

* [[HackingHowto|Hacking]] - notes on making and sending in code contributions
** [[BeginnersCorner|Beginner's Corner]] - resources for those who are new to Python or Git.
** ''Started from an older version of the Hacking Howto? We switched from buildout->virtualenv, so look at [[Moving from buildout to virtualenv]] for information on how to move over.''
* [[Git workflow]] - How to go about submitting patches via git.
* [[Code review tips]] - Tips on how to go about doing local code review
* [[Templating]] - How our templating structure is set up
* [[Code overview]] - Overview of the structure of the codebase

== Create a Theme ==

See [http://docs.mediagoblin.org/siteadmin/theming.html the theming docs]

== Write a plugin ==

If you start, you'll find some basic documentation [http://docs.mediagoblin.org/#part-4-developer-s-zone| in the docs site]

You've made a plugin ? List it here :

[[Available_Plugins|Available plugins]]

You've written a plugin ? You got some tips to share ? A tutorial idea ? Please do :

[[PluginsTips|Plugins Tips]]

= Misc =

== Android client ==

See [[Android Client]]

= Inner workings of the secret sanctum =

* [[IRCBot]] - covers our irc bot
* [[ReleaseProcess|Release Process]] - covers the release process
* [[Update the website]] - Learn how to update mediagoblin.org!

=FAQ=

[[GMG FAQ]]