GNU MediaGoblin Wiki - User contributions [en]

20160904 Log

2016-09-03T17:15:04Z

Larjona:

<nowiki>

[18:02:41] <paroneayea> #startmeeting

[18:02:49] <paroneayea> oh, there's no chaosgoblin :)

[18:02:58] <paroneayea> well, consider that line to be the "meeting strated" line :)

[18:03:11] <larjona> Hi

[18:03:17] <paroneayea> hey, larjona too!

[18:03:24] <paroneayea> that makes three of us. a good start! :)

[18:03:55] <paroneayea> how about we Just-In-Time some meeting topics :)

[18:04:02] <paroneayea> * Pubstrate / ActivityPub updates

[18:04:14] <paroneayea> * When's paroneayea working on MediaGoblin again????

[18:04:42] <paroneayea> * GSoC wrapup

[18:04:52] <paroneayea> anything else? :)

[18:05:01] <larjona> 1.0?

[18:05:09] <paroneayea> * 1.0 !

[18:05:12] <breton> o/

[18:05:21] <paroneayea> hey breton ! yay, we're at 4

[18:05:24] <breton> yeeey, i am almost not late

[18:05:28] <paroneayea> :D

[18:05:42] <paroneayea> breton: want to add any topics?

[18:05:56] <breton> paroneayea: nope

[18:06:07] <paroneayea> cool, ok

[18:06:21] <paroneayea> #topic Pubstrate / ActivityPub updates

[18:06:51] <paroneayea> as I think everyone here knows, I've been focused on getting the federation spec work tsyesika and I are editors on for the W3C, which is ActivityPub

[18:07:10] <paroneayea> we basically want to get to Candidate Recommendation state by the end of TPAC, if not before

[18:07:24] <paroneayea> maybe not everyone knows what tpac is :)

[18:07:33] -*- breton doesn't know

[18:07:57] <paroneayea> https://www.w3.org/2016/09/TPAC/

[18:08:05] <paroneayea> so TPAC is the big w3c technical conference thing

[18:08:12] <paroneayea> I'm going to be attending in-person

[18:08:20] <paroneayea> it's in Lisbon

[18:08:51] <paroneayea> so, the good news is that AcitvityPub is moving well along. We just put out a new Working Draft a week ago: https://www.w3.org/TR/activitypub/

[18:08:58] <paroneayea> earlier in the month, my friend Amy Guy stayed with us for a week

[18:09:10] <paroneayea> she's also part of the w3c group (currently works at the w3c part time even)

[18:09:15] <paroneayea> we knocked out a ton of updates

[18:09:27] <paroneayea> including more cleanly separating the client-to-server from the server-to-server stuff

[18:09:36] <paroneayea> anyway, the good news is: the spec is in very good shape

[18:09:47] <paroneayea> the bad news is: the deadline is tight, and *serious*.

[18:10:00] <paroneayea> the group only is chartered to be around till end of this year

[18:10:22] <paroneayea> if we want the spec to go through and not just be a "note", we have to get everything to that point by year's end, and that's a lot of process

[18:10:23] <paroneayea> and... we need implementations

[18:10:42] <paroneayea> luckily, there are two implementations in progress: Amy's site runs one, and I'm writing Pubstrate.

[18:11:12] <paroneayea> http://dustycloud.org/tmp/pubstrate_2016-08-17.png

[18:11:22] <paroneayea> I can now log in and post notes

[18:11:29] <paroneayea> it's very similar in design to pump.io

[18:11:41] <paroneayea> but written in guile scheme, and a bit more demo'y

[18:11:55] <breton> so, no integration with mg yet?

[18:12:03] <paroneayea> not yet. so

[18:12:09] <paroneayea> I think porting GMG's federation code to this

[18:12:11] <paroneayea> will not be hard.

[18:12:23] <paroneayea> I'd like to have that done by end of 2016.

[18:12:52] <paroneayea> that's a good tie in to the next topic, but maybe there are questions :)

[18:13:21] <paroneayea> (I'm hoping to release a Pubstrate 0.1 release in the next few weeks so people can try it)

[18:13:55] <paroneayea> https://github.com/cwebber/pubstrate it's currently (unfortunately) hosted on github. I'll move it to gitlab before release.

[18:14:12] <paroneayea> that was originally for perceived-synchronization-with-group reasons, but I no longer believe that matters.

[18:14:26] <paroneayea> any questions? or should we move on

[18:14:30] <paroneayea> sorry for textwall :)

[18:14:48] -*- breton has none

[18:14:51] <paroneayea> ok :)

[18:15:46] <paroneayea> #topic When's paroneayea working on MediaGoblin again????

[18:15:57] <paroneayea> good question/topic! :)

[18:16:06] <paroneayea> I've been noticably absent, because of all the above, and tight deadlines

[18:16:30] <paroneayea> I'm hoping that by late october I'm back on GMG to a reasonable degree.

[18:16:59] <paroneayea> which is maybe also related to 1.0

[18:17:11] <paroneayea> maybe we should switch to that topic since what else is there to say on this one ;)

[18:17:23] <paroneayea> and we'll do gsoc after

[18:17:33] <paroneayea> #topic 1.0

[18:17:52] <paroneayea> 1.0! Right around the corner, several months ago, I thought, but then this happened...

[18:18:24] <paroneayea> the main thing that needs to happen next is that we need to review, make sure it's stable, and merge tsyesika's federation code.

[18:18:36] <breton> isn't it merged yet?

[18:18:36] <paroneayea> tsyesika: maybe you might have comments on what you remember the current state of that is?

[18:18:42] <paroneayea> is it?

[18:18:46] <breton> i thought that all federation stuff is in

[18:19:04] <paroneayea> nope :)

[18:19:23] <paroneayea> it's still unmerged.

[18:19:31] <tsyesika> nupe it's not merged yet, there are a few little tasks that need finished and then a full review

[18:19:33] <breton> is the branch with federation in the main repo?

[18:19:42] <tsyesika> nope, it's on my notabug

[18:19:50] -*- tsyesika finds the link

[18:19:58] <tsyesika> https://notabug.org/Tsyesika/federated-mediagoblin

[18:21:07] <paroneayea> so

[18:21:16] <paroneayea> if someone wants to do review and help this move along towards merge

[18:21:22] <paroneayea> that *can* be done without me, I think

[18:21:31] <paroneayea> though it would be helpful if there's a list of "things that need to be done"

[18:21:33] <paroneayea> do we have that tsyesika ?

[18:21:37] <breton> tsyesika: which branch?

[18:21:54] <breton> i'd love to do review

[18:21:58] <tsyesika> paroneayea: i can make one up and post it to the dev mailing list later :)

[18:22:18] <breton> in fact i'd do one if i knew that it needs reviewing a lot of time ago

[18:22:20] <tsyesika> breton: "federation" i believe

[18:22:33] <paroneayea> tsyesika: that would be great

[18:22:40] <paroneayea> breton: that would also be great! :)

[18:22:56] <tsyesika> before a review those little tasks need fixing, some a serious but quick to do but they definitely definitely need doing

[18:24:52] <paroneayea> I want to add one more topic

[18:25:20] <paroneayea> * Making breton co-maintainer (at least while SocialWG stuff is wrapping up)?

[18:25:31] <paroneayea> not to switch topics now

[18:25:34] <paroneayea> just queue it :)

[18:26:12] <breton> i have a question about 1.0. What about deployment stuff?

[18:26:21] <paroneayea> breton: it's a good question...

[18:26:27] <breton> we had that as a target during that campaign

[18:26:29] <paroneayea> breton: we need packages for distros.

[18:26:52] <paroneayea> breton: we never hit that goal

[18:26:56] <paroneayea> http://mediagoblin.org/pages/campaign.html

[18:27:01] <paroneayea> but nonetheless

[18:27:05] <paroneayea> it's still important to me

[18:27:11] <paroneayea> that was going to be at the $100k

[18:27:12] <paroneayea> level

[18:27:15] <paroneayea> well

[18:27:27] <paroneayea> we have another target

[18:27:30] <paroneayea> which is premium hosting

[18:27:37] <paroneayea> ironically, deployment has been a pre-requisite for launching that!

[18:27:42] <breton> oh, yeah, that one too

[18:27:51] <paroneayea> so we never officially hit "deployment".

[18:27:57] <paroneayea> but

[18:28:02] <paroneayea> so I can't give details

[18:28:21] <paroneayea> there's some vague possibility of funding debian packaging but I think it's low chance.

[18:28:28] <paroneayea> but regardless

[18:28:31] <paroneayea> I think it needs to happen.

[18:28:40] <paroneayea> simonft got debian packaging pretty close already

[18:28:52] <paroneayea> I have a guix package near-done

[18:28:54] <larjona> Debian freezes 5 november

[18:29:01] <paroneayea> I was working on making things more easily packaged before I got caught up in all this stuff

[18:29:15] <paroneayea> larjona: it's unlikely we'll hit that freeze by my own work, but maybe if someone else can help

[18:29:31] <paroneayea> I feel like our build system, in trying to make things easier, has also made things a lot harder

[18:30:07] <paroneayea> probably the autotools part, but definitely the npm/bower part

[18:30:25] <paroneayea> though, I hear jquery 2.0 is packaged in debian now

[18:30:29] <breton> actually i never figured that part out

[18:30:37] <breton> because i haven't done js in ages

[18:31:16] <paroneayea> I think it should be torn out and replaced with something simpler: a directory where either distros can put javascript files, or we can pull them down and unpack the prebuilt ones

[18:31:22] <paroneayea> via a script

[18:31:52] <paroneayea> I think every javascript dependency we use already has prebuilt versions anyway

[18:32:09] <paroneayea> so if we let distros provide the full version, or for developers let them run some script to get something

[18:32:14] <paroneayea> or at the very least

[18:32:15] <breton> what do others do?

[18:32:19] <breton> for example, wordpress

[18:32:21] <paroneayea> not make the bower stuff a core part

[18:32:27] <paroneayea> breton: I don't know about wordpress, it's a good question

[18:32:52] <paroneayea> breton: it's hard to answer, because what examples of web applications aside from wordpress do you see successfully packaged with distros anyway :\

[18:33:42] <breton> i also wonder about, say, django-cms

[18:33:47] <paroneayea> even the php things are getting just as complex to deploy now

[18:33:54] <paroneayea> breton: yeah a good question

[18:34:01] <paroneayea> we should probably research before we make decisions

[18:34:12] <paroneayea> probably we should try to package, and see how hard our stuff currently is, and figure out how to change things around that.

[18:34:31] <paroneayea> I'll be interested in working on this once I'm done with my socialwg focus-mode madness

[18:34:44] <paroneayea> even php is hard now with Composer

[18:34:50] <paroneayea> https://lwn.net/Articles/670752/

[18:34:59] <paroneayea> see the owncloud / debian rift

[18:35:36] <breton> what about guix package?

[18:35:42] <paroneayea> breton: that one's already almost done :)

[18:35:45] <paroneayea> I packaged all our deps

[18:35:53] <paroneayea> and I was using it

[18:35:59] <paroneayea> I just wasn't doing the final mediagoblin package

[18:36:00] <paroneayea> excepting the javascript stuff

[18:36:05] <paroneayea> heh!

[18:36:23] <paroneayea> I have no idea how the js stuff will be done. we might need to provide another repo that does "evil" things and pulls in the pre-minified js pakcages

[18:36:28] <paroneayea> though!

[18:36:30] <paroneayea> oh, good news

[18:36:40] <paroneayea> we had a "packaging npm for guix stuff" gsoc student

[18:36:50] <paroneayea> I was technically a mentor, though the student did quite well without my help

[18:37:07] <paroneayea> so, it turns out packaging jquery is insane, but hey, some things can be packaged using their tools now :)

[18:37:15] <paroneayea> so there's hope? maybe? :)

[18:37:32] <breton> to meet the "premium hosting" target, we don't really need debian packages, we might provide the hosting with guix, right?

[18:37:41] <paroneayea> I have high hopes and optimism for anything that doesn't need npm (and maybe even npm can eventually happen in guix)

[18:37:43] <paroneayea> breton: yup

[18:37:57] <paroneayea> no need to use debian, and I can do guix easily, even if it means mediagoblin's js deps won't go into guix proper

[18:38:10] <paroneayea> we could get mediagoblin in guix proper, and provide a supplementary package that provides the js stuff

[18:38:25] <paroneayea> maybe we should tear out all this js stuff. Who needs javascript libraries anyway! :)

[18:38:28] <larjona> There is a sandstorm package but outdated (0.7?) If anybody can have a look at it, maybe it's easy to update it

[18:39:16] <paroneayea> larjona: sandstorm support would be good... I wouldn't be using it for premium hosting I would myself run, but I would want us to be up-to-date in sandstorm-land

[18:39:33] <paroneayea> breton: ugh, one more item not even on the agenda, what to do about this kombu / celery stuff :(

[18:39:46] <paroneayea> breton: I have a client that paid me to do some consulting on their GMG deployment (which was nice!)

[18:39:52] <paroneayea> and they got bit by it :(

[18:40:09] <breton> paroneayea: yep, lets get to it in the end

[18:40:12] <paroneayea> ok cool

[18:40:21] <paroneayea> * kombu / celery

[18:40:28] <paroneayea> one more topic to queue for later :)

[18:40:52] <paroneayea> so it sounds like tsyesika will post stuff to list, breton will review, and paroneayea will come back in late october to help? :)

[18:41:02] <paroneayea> and larjona will look at sandstorm state? :)

[18:41:13] <tsyesika> sounds good

[18:41:22] --> neiljp joined #mediagoblin

[18:41:29] <paroneayea> (you don't have to do anything larjona , but maybe just nice to see what the state is !)

[18:41:38] <paroneayea> though if you want to, you're more than welcome to :)

[18:41:47] <breton> yep

[18:41:56] <paroneayea> cool, is it next topic time?

[18:42:07] <paroneayea> (I'll probably just dump these minutes on the mailing list btw)

[18:42:27] <paroneayea> #topic GSoC wrapup

[18:42:36] <larjona> Yes, I'll report to the list

[18:42:40] <paroneayea> larjona: great!

[18:43:20] <paroneayea> so saksham1115 got their video subtitling stuff in

[18:43:20] <-- afuentes left (Ping timeout: 258 seconds)

[18:43:43] <paroneayea> looks like results are announced

[18:43:53] <paroneayea> we passed saksham1115 :)

[18:44:11] <paroneayea> thanks to saksham1115, and to breton for co-mentoring (and doing bulk of mentoring, TBH!)

[18:44:45] <paroneayea> saksham1115 wrote an update to the mailing list...

[18:44:52] <paroneayea> maybe I should pull it up

[18:45:09] <paroneayea> http://lists.mediagoblin.org/pipermail/devel/2016-August/001465.html

[18:45:10] <paroneayea> there we go

[18:45:40] <paroneayea> breton: do you think we could/should maybe get this merged in for 1.0 also?

[18:46:24] <breton> paroneayea: i'll review more thoroughly and tell after that

[18:46:46] <paroneayea> breton: cool, if you think it's close

[18:46:54] <paroneayea> tag for 1.0 on the tracker please!

[18:47:06] <paroneayea> cool, any questions?

[18:47:10] <paroneayea> should we move on?

[18:47:26] <paroneayea> congrats again to saksham1115, and thank you, from GMG land! :)

[18:47:26] <breton> yep

[18:47:44] <paroneayea> #topic Making breton co-maintainer (at least while SocialWG stuff is wrapping up)?

[18:48:12] <paroneayea> so, breton has already been doing a lot of work keeping things moving smoothly in mediagoblin land... more than me while I've been in focus on the socialwg!

[18:48:17] <paroneayea> and long-term, I'm not going anywhere

[18:48:31] <paroneayea> but I think it would be a good idea to officially appoint breton co-maintainer, at least for now

[18:48:46] <larjona> +1

[18:48:46] <paroneayea> we'd have to make it official with GNU too, but how do people feel?

[18:48:54] <paroneayea> +1 here too :)

[18:49:03] <tsyesika> +1

[18:49:12] <breton> yay!

[18:49:14] <paroneayea> let's make sure breton +1's ;)

[18:49:23] <breton> +1 :)

[18:49:24] <paroneayea> whew that was the most important vote :)

[18:49:30] <paroneayea> ok, so I'll start that process :)

[18:49:34] <paroneayea> thank you breton !

[18:49:45] <larjona> Thanks breton

[18:50:22] <paroneayea> whee!

[18:50:28] <paroneayea> ok, next topic

[18:50:29] <breton> that's a good present for my todays birthday :p

[18:50:35] <paroneayea> :D

[18:50:38] <tsyesika> happy birthday breton :)

[18:50:39] <paroneayea> happy birthday breton!

[18:50:52] <larjona> happy birthday!

[18:50:52] <paroneayea> . o O (I have just the ascii art to close today's meeting...)

[18:51:07] <paroneayea> #topic kombu / celery

[18:51:21] <paroneayea> breton: want to explain the state of affairs?

[18:51:45] <breton> yep

[18:52:01] <breton> celery dropped sqlalchemy as a broker

[18:52:07] <breton> with a bunch of other brokers

[18:52:20] <breton> and they support only 4 brokers: http://celery.readthedocs.io/en/master/getting-started/brokers/index.html

[18:52:35] <paroneayea> I mean, to be fair, sqlalchemy was never a "great" broker, but it made it easy for people to get started

[18:52:41] <paroneayea> esp for small installs

[18:52:47] <breton> the reason is that it was hard to maintain and had some issues

[18:52:51] <paroneayea> yes

[18:53:03] <paroneayea> we could do a few things:

[18:53:21] <paroneayea> - maintain the broker ourselves? (yuck, maybe temporarily?)

[18:53:40] <paroneayea> - switch from celery to an actor model system... hm, that's maybe too long term :)

[18:53:52] <paroneayea> - write a broker that uses unix named pipes?

[18:54:00] <breton> https://github.com/celery/celery/issues/3274#issuecomment-228324848 if someone's interested

[18:54:31] <paroneayea> one more

[18:54:43] <paroneayea> - we could switch to recommending one of the official brokers

[18:54:53] <paroneayea> like rabbit/redis/etc

[18:55:06] <breton> i'd chose the last one as the simpliest one.

[18:55:40] <breton> the only thing that bugs me is uncertanty around redis

[18:55:59] <paroneayea> breton: what's the uncertainty?

[18:56:21] <breton> paroneayea: the bug ^ initially was about issues with redis broker

[18:56:29] <breton> paroneayea: and they wanted to remove it too

[18:56:38] <paroneayea> oh right

[18:56:45] <breton> but people from redis came and said that they are willing to work on the issues

[18:56:50] <paroneayea> breton: maybe we should choose rabbitmq then

[18:57:05] <paroneayea> breton: it's something to research, for now, I think

[18:57:24] <breton> paroneayea: yes. I don't thing that it's going to be hard, because it's well packaged everywhere

[18:58:00] <paroneayea> breton: rabbitmq you mean?

[18:58:20] <breton> paroneayea: yes

[18:58:50] <paroneayea> breton: ok, I'm ok with going rabbitmq

[18:58:54] <paroneayea> it will take work

[18:59:29] <paroneayea> here is our ticket https://issues.mediagoblin.org/ticket/5464

[18:59:42] <paroneayea> I'll add a comment summarizing our thoughts from the meeting

[19:00:23] <paroneayea> and... I think that's it from the meeting right?

[19:00:34] <larjona> Yes

[19:00:52] <paroneayea> ok, in that case :)

[19:00:58] <paroneayea> HAPPY BIRTHDAY

[19:01:02] <paroneayea> ()

[19:01:02] <paroneayea> .-----||-----.

[19:01:05] <paroneayea> |'---______---'|

[19:01:08] <paroneayea> |. .|

[19:01:11] <paroneayea> _| '----__----' |_

[19:01:14] <paroneayea> ( '--__________--' )

[19:01:17] <paroneayea> '---__________---'

[19:01:20] <paroneayea> BRETON!

[19:01:24] <paroneayea> thanks for coming, breton, larjona, tsyesika :)

[19:01:40] <paroneayea> #endmeeting

</nowiki>

20160904 Log

2016-09-03T17:13:48Z

Larjona:

20160904 Log

2016-09-03T17:12:42Z

Larjona: add log

<nowiki>

[18:02:41] <paroneayea> #startmeeting
[18:02:49] <paroneayea> oh, there's no chaosgoblin :)
[18:02:58] <paroneayea> well, consider that line to be the "meeting strated" line :)
[18:03:11] <larjona> Hi
[18:03:17] <paroneayea> hey, larjona too!
[18:03:24] <paroneayea> that makes three of us. a good start! :)
[18:03:55] <paroneayea> how about we Just-In-Time some meeting topics :)
[18:04:02] <paroneayea> * Pubstrate / ActivityPub updates
[18:04:14] <paroneayea> * When's paroneayea working on MediaGoblin again????
[18:04:42] <paroneayea> * GSoC wrapup
[18:04:52] <paroneayea> anything else? :)
[18:05:01] <larjona> 1.0?
[18:05:09] <paroneayea> * 1.0 !
[18:05:12] <breton> o/
[18:05:21] <paroneayea> hey breton ! yay, we're at 4
[18:05:24] <breton> yeeey, i am almost not late
[18:05:28] <paroneayea> :D
[18:05:42] <paroneayea> breton: want to add any topics?
[18:05:56] <breton> paroneayea: nope
[18:06:07] <paroneayea> cool, ok
[18:06:21] <paroneayea> #topic Pubstrate / ActivityPub updates
[18:06:51] <paroneayea> as I think everyone here knows, I've been focused on getting the federation spec work tsyesika and I are editors on for the W3C, which is ActivityPub
[18:07:10] <paroneayea> we basically want to get to Candidate Recommendation state by the end of TPAC, if not before
[18:07:24] <paroneayea> maybe not everyone knows what tpac is :)
[18:07:33] -*- breton doesn't know
[18:07:57] <paroneayea> https://www.w3.org/2016/09/TPAC/
[18:08:05] <paroneayea> so TPAC is the big w3c technical conference thing
[18:08:12] <paroneayea> I'm going to be attending in-person
[18:08:20] <paroneayea> it's in Lisbon
[18:08:51] <paroneayea> so, the good news is that AcitvityPub is moving well along. We just put out a new Working Draft a week ago: https://www.w3.org/TR/activitypub/
[18:08:58] <paroneayea> earlier in the month, my friend Amy Guy stayed with us for a week
[18:09:10] <paroneayea> she's also part of the w3c group (currently works at the w3c part time even)
[18:09:15] <paroneayea> we knocked out a ton of updates
[18:09:27] <paroneayea> including more cleanly separating the client-to-server from the server-to-server stuff
[18:09:36] <paroneayea> anyway, the good news is: the spec is in very good shape
[18:09:47] <paroneayea> the bad news is: the deadline is tight, and *serious*.
[18:10:00] <paroneayea> the group only is chartered to be around till end of this year
[18:10:22] <paroneayea> if we want the spec to go through and not just be a "note", we have to get everything to that point by year's end, and that's a lot of process
[18:10:23] <paroneayea> and... we need implementations
[18:10:42] <paroneayea> luckily, there are two implementations in progress: Amy's site runs one, and I'm writing Pubstrate.
[18:11:12] <paroneayea> http://dustycloud.org/tmp/pubstrate_2016-08-17.png
[18:11:22] <paroneayea> I can now log in and post notes
[18:11:29] <paroneayea> it's very similar in design to pump.io
[18:11:41] <paroneayea> but written in guile scheme, and a bit more demo'y
[18:11:55] <breton> so, no integration with mg yet?
[18:12:03] <paroneayea> not yet. so
[18:12:09] <paroneayea> I think porting GMG's federation code to this
[18:12:11] <paroneayea> will not be hard.
[18:12:23] <paroneayea> I'd like to have that done by end of 2016.
[18:12:52] <paroneayea> that's a good tie in to the next topic, but maybe there are questions :)
[18:13:21] <paroneayea> (I'm hoping to release a Pubstrate 0.1 release in the next few weeks so people can try it)
[18:13:55] <paroneayea> https://github.com/cwebber/pubstrate it's currently (unfortunately) hosted on github. I'll move it to gitlab before release.
[18:14:12] <paroneayea> that was originally for perceived-synchronization-with-group reasons, but I no longer believe that matters.
[18:14:26] <paroneayea> any questions? or should we move on
[18:14:30] <paroneayea> sorry for textwall :)
[18:14:48] -*- breton has none
[18:14:51] <paroneayea> ok :)
[18:15:46] <paroneayea> #topic When's paroneayea working on MediaGoblin again????
[18:15:57] <paroneayea> good question/topic! :)
[18:16:06] <paroneayea> I've been noticably absent, because of all the above, and tight deadlines
[18:16:30] <paroneayea> I'm hoping that by late october I'm back on GMG to a reasonable degree.
[18:16:59] <paroneayea> which is maybe also related to 1.0
[18:17:11] <paroneayea> maybe we should switch to that topic since what else is there to say on this one ;)
[18:17:23] <paroneayea> and we'll do gsoc after
[18:17:33] <paroneayea> #topic 1.0
[18:17:52] <paroneayea> 1.0! Right around the corner, several months ago, I thought, but then this happened...
[18:18:24] <paroneayea> the main thing that needs to happen next is that we need to review, make sure it's stable, and merge tsyesika's federation code.
[18:18:36] <breton> isn't it merged yet?
[18:18:36] <paroneayea> tsyesika: maybe you might have comments on what you remember the current state of that is?
[18:18:42] <paroneayea> is it?
[18:18:46] <breton> i thought that all federation stuff is in
[18:19:04] <paroneayea> nope :)
[18:19:23] <paroneayea> it's still unmerged.
[18:19:31] <tsyesika> nupe it's not merged yet, there are a few little tasks that need finished and then a full review
[18:19:33] <breton> is the branch with federation in the main repo?
[18:19:42] <tsyesika> nope, it's on my notabug
[18:19:50] -*- tsyesika finds the link
[18:19:58] <tsyesika> https://notabug.org/Tsyesika/federated-mediagoblin
[18:21:07] <paroneayea> so
[18:21:16] <paroneayea> if someone wants to do review and help this move along towards merge
[18:21:22] <paroneayea> that *can* be done without me, I think
[18:21:31] <paroneayea> though it would be helpful if there's a list of "things that need to be done"
[18:21:33] <paroneayea> do we have that tsyesika ?
[18:21:37] <breton> tsyesika: which branch?
[18:21:54] <breton> i'd love to do review
[18:21:58] <tsyesika> paroneayea: i can make one up and post it to the dev mailing list later :)
[18:22:18] <breton> in fact i'd do one if i knew that it needs reviewing a lot of time ago
[18:22:20] <tsyesika> breton: "federation" i believe
[18:22:33] <paroneayea> tsyesika: that would be great
[18:22:40] <paroneayea> breton: that would also be great! :)
[18:22:56] <tsyesika> before a review those little tasks need fixing, some a serious but quick to do but they definitely definitely need doing
[18:24:52] <paroneayea> I want to add one more topic
[18:25:20] <paroneayea> * Making breton co-maintainer (at least while SocialWG stuff is wrapping up)?
[18:25:31] <paroneayea> not to switch topics now
[18:25:34] <paroneayea> just queue it :)
[18:26:12] <breton> i have a question about 1.0. What about deployment stuff?
[18:26:21] <paroneayea> breton: it's a good question...
[18:26:27] <breton> we had that as a target during that campaign
[18:26:29] <paroneayea> breton: we need packages for distros.
[18:26:52] <paroneayea> breton: we never hit that goal
[18:26:56] <paroneayea> http://mediagoblin.org/pages/campaign.html
[18:27:01] <paroneayea> but nonetheless
[18:27:05] <paroneayea> it's still important to me
[18:27:11] <paroneayea> that was going to be at the $100k
[18:27:12] <paroneayea> level
[18:27:15] <paroneayea> well
[18:27:27] <paroneayea> we have another target
[18:27:30] <paroneayea> which is premium hosting
[18:27:37] <paroneayea> ironically, deployment has been a pre-requisite for launching that!
[18:27:42] <breton> oh, yeah, that one too
[18:27:51] <paroneayea> so we never officially hit "deployment".
[18:27:57] <paroneayea> but
[18:28:02] <paroneayea> so I can't give details
[18:28:21] <paroneayea> there's some vague possibility of funding debian packaging but I think it's low chance.
[18:28:28] <paroneayea> but regardless
[18:28:31] <paroneayea> I think it needs to happen.
[18:28:40] <paroneayea> simonft got debian packaging pretty close already
[18:28:52] <paroneayea> I have a guix package near-done
[18:28:54] <larjona> Debian freezes 5 november
[18:29:01] <paroneayea> I was working on making things more easily packaged before I got caught up in all this stuff
[18:29:15] <paroneayea> larjona: it's unlikely we'll hit that freeze by my own work, but maybe if someone else can help
[18:29:31] <paroneayea> I feel like our build system, in trying to make things easier, has also made things a lot harder
[18:30:07] <paroneayea> probably the autotools part, but definitely the npm/bower part
[18:30:25] <paroneayea> though, I hear jquery 2.0 is packaged in debian now
[18:30:29] <breton> actually i never figured that part out
[18:30:37] <breton> because i haven't done js in ages
[18:31:16] <paroneayea> I think it should be torn out and replaced with something simpler: a directory where either distros can put javascript files, or we can pull them down and unpack the prebuilt ones
[18:31:22] <paroneayea> via a script
[18:31:52] <paroneayea> I think every javascript dependency we use already has prebuilt versions anyway
[18:32:09] <paroneayea> so if we let distros provide the full version, or for developers let them run some script to get something
[18:32:14] <paroneayea> or at the very least
[18:32:15] <breton> what do others do?
[18:32:19] <breton> for example, wordpress
[18:32:21] <paroneayea> not make the bower stuff a core part
[18:32:27] <paroneayea> breton: I don't know about wordpress, it's a good question
[18:32:52] <paroneayea> breton: it's hard to answer, because what examples of web applications aside from wordpress do you see successfully packaged with distros anyway :\
[18:33:42] <breton> i also wonder about, say, django-cms
[18:33:47] <paroneayea> even the php things are getting just as complex to deploy now
[18:33:54] <paroneayea> breton: yeah a good question
[18:34:01] <paroneayea> we should probably research before we make decisions
[18:34:12] <paroneayea> probably we should try to package, and see how hard our stuff currently is, and figure out how to change things around that.
[18:34:31] <paroneayea> I'll be interested in working on this once I'm done with my socialwg focus-mode madness
[18:34:44] <paroneayea> even php is hard now with Composer
[18:34:50] <paroneayea> https://lwn.net/Articles/670752/
[18:34:59] <paroneayea> see the owncloud / debian rift
[18:35:36] <breton> what about guix package?
[18:35:42] <paroneayea> breton: that one's already almost done :)
[18:35:45] <paroneayea> I packaged all our deps
[18:35:53] <paroneayea> and I was using it
[18:35:59] <paroneayea> I just wasn't doing the final mediagoblin package
[18:36:00] <paroneayea> excepting the javascript stuff
[18:36:05] <paroneayea> heh!
[18:36:23] <paroneayea> I have no idea how the js stuff will be done. we might need to provide another repo that does "evil" things and pulls in the pre-minified js pakcages
[18:36:28] <paroneayea> though!
[18:36:30] <paroneayea> oh, good news
[18:36:40] <paroneayea> we had a "packaging npm for guix stuff" gsoc student
[18:36:50] <paroneayea> I was technically a mentor, though the student did quite well without my help
[18:37:07] <paroneayea> so, it turns out packaging jquery is insane, but hey, some things can be packaged using their tools now :)
[18:37:15] <paroneayea> so there's hope? maybe? :)
[18:37:32] <breton> to meet the "premium hosting" target, we don't really need debian packages, we might provide the hosting with guix, right?
[18:37:41] <paroneayea> I have high hopes and optimism for anything that doesn't need npm (and maybe even npm can eventually happen in guix)
[18:37:43] <paroneayea> breton: yup
[18:37:57] <paroneayea> no need to use debian, and I can do guix easily, even if it means mediagoblin's js deps won't go into guix proper
[18:38:10] <paroneayea> we could get mediagoblin in guix proper, and provide a supplementary package that provides the js stuff
[18:38:25] <paroneayea> maybe we should tear out all this js stuff. Who needs javascript libraries anyway! :)
[18:38:28] <larjona> There is a sandstorm package but outdated (0.7?) If anybody can have a look at it, maybe it's easy to update it
[18:39:16] <paroneayea> larjona: sandstorm support would be good... I wouldn't be using it for premium hosting I would myself run, but I would want us to be up-to-date in sandstorm-land
[18:39:33] <paroneayea> breton: ugh, one more item not even on the agenda, what to do about this kombu / celery stuff :(
[18:39:46] <paroneayea> breton: I have a client that paid me to do some consulting on their GMG deployment (which was nice!)
[18:39:52] <paroneayea> and they got bit by it :(
[18:40:09] <breton> paroneayea: yep, lets get to it in the end
[18:40:12] <paroneayea> ok cool
[18:40:21] <paroneayea> * kombu / celery
[18:40:28] <paroneayea> one more topic to queue for later :)
[18:40:52] <paroneayea> so it sounds like tsyesika will post stuff to list, breton will review, and paroneayea will come back in late october to help? :)
[18:41:02] <paroneayea> and larjona will look at sandstorm state? :)
[18:41:13] <tsyesika> sounds good
[18:41:22] --> neiljp joined #mediagoblin
[18:41:29] <paroneayea> (you don't have to do anything larjona , but maybe just nice to see what the state is !)
[18:41:38] <paroneayea> though if you want to, you're more than welcome to :)
[18:41:47] <breton> yep
[18:41:56] <paroneayea> cool, is it next topic time?
[18:42:07] <paroneayea> (I'll probably just dump these minutes on the mailing list btw)
[18:42:27] <paroneayea> #topic GSoC wrapup
[18:42:36] <larjona> Yes, I'll report to the list
[18:42:40] <paroneayea> larjona: great!
[18:43:20] <paroneayea> so saksham1115 got their video subtitling stuff in
[18:43:20] <-- afuentes left (Ping timeout: 258 seconds)
[18:43:43] <paroneayea> looks like results are announced
[18:43:53] <paroneayea> we passed saksham1115 :)
[18:44:11] <paroneayea> thanks to saksham1115, and to breton for co-mentoring (and doing bulk of mentoring, TBH!)
[18:44:45] <paroneayea> saksham1115 wrote an update to the mailing list...
[18:44:52] <paroneayea> maybe I should pull it up
[18:45:09] <paroneayea> http://lists.mediagoblin.org/pipermail/devel/2016-August/001465.html
[18:45:10] <paroneayea> there we go
[18:45:40] <paroneayea> breton: do you think we could/should maybe get this merged in for 1.0 also?
[18:46:24] <breton> paroneayea: i'll review more thoroughly and tell after that
[18:46:46] <paroneayea> breton: cool, if you think it's close
[18:46:54] <paroneayea> tag for 1.0 on the tracker please!
[18:47:06] <paroneayea> cool, any questions?
[18:47:10] <paroneayea> should we move on?
[18:47:26] <paroneayea> congrats again to saksham1115, and thank you, from GMG land! :)
[18:47:26] <breton> yep
[18:47:44] <paroneayea> #topic Making breton co-maintainer (at least while SocialWG stuff is wrapping up)?
[18:48:12] <paroneayea> so, breton has already been doing a lot of work keeping things moving smoothly in mediagoblin land... more than me while I've been in focus on the socialwg!
[18:48:17] <paroneayea> and long-term, I'm not going anywhere
[18:48:31] <paroneayea> but I think it would be a good idea to officially appoint breton co-maintainer, at least for now
[18:48:46] <larjona> +1
[18:48:46] <paroneayea> we'd have to make it official with GNU too, but how do people feel?
[18:48:54] <paroneayea> +1 here too :)
[18:49:03] <tsyesika> +1
[18:49:12] <breton> yay!
[18:49:14] <paroneayea> let's make sure breton +1's ;)
[18:49:23] <breton> +1 :)
[18:49:24] <paroneayea> whew that was the most important vote :)
[18:49:30] <paroneayea> ok, so I'll start that process :)
[18:49:34] <paroneayea> thank you breton !
[18:49:45] <larjona> Thanks breton
[18:50:22] <paroneayea> whee!
[18:50:28] <paroneayea> ok, next topic
[18:50:29] <breton> that's a good present for my todays birthday :p
[18:50:35] <paroneayea> :D
[18:50:38] <tsyesika> happy birthday breton :)
[18:50:39] <paroneayea> happy birthday breton!
[18:50:52] <larjona> happy birthday!
[18:50:52] <paroneayea> . o O (I have just the ascii art to close today's meeting...)
[18:51:07] <paroneayea> #topic kombu / celery
[18:51:21] <paroneayea> breton: want to explain the state of affairs?
[18:51:45] <breton> yep
[18:52:01] <breton> celery dropped sqlalchemy as a broker
[18:52:07] <breton> with a bunch of other brokers
[18:52:20] <breton> and they support only 4 brokers: http://celery.readthedocs.io/en/master/getting-started/brokers/index.html
[18:52:35] <paroneayea> I mean, to be fair, sqlalchemy was never a "great" broker, but it made it easy for people to get started
[18:52:41] <paroneayea> esp for small installs
[18:52:47] <breton> the reason is that it was hard to maintain and had some issues
[18:52:51] <paroneayea> yes
[18:53:03] <paroneayea> we could do a few things:
[18:53:21] <paroneayea> - maintain the broker ourselves? (yuck, maybe temporarily?)
[18:53:40] <paroneayea> - switch from celery to an actor model system... hm, that's maybe too long term :)
[18:53:52] <paroneayea> - write a broker that uses unix named pipes?
[18:54:00] <breton> https://github.com/celery/celery/issues/3274#issuecomment-228324848 if someone's interested
[18:54:31] <paroneayea> one more
[18:54:43] <paroneayea> - we could switch to recommending one of the official brokers
[18:54:53] <paroneayea> like rabbit/redis/etc
[18:55:06] <breton> i'd chose the last one as the simpliest one.
[18:55:40] <breton> the only thing that bugs me is uncertanty around redis
[18:55:59] <paroneayea> breton: what's the uncertainty?
[18:56:21] <breton> paroneayea: the bug ^ initially was about issues with redis broker
[18:56:29] <breton> paroneayea: and they wanted to remove it too
[18:56:38] <paroneayea> oh right
[18:56:45] <breton> but people from redis came and said that they are willing to work on the issues
[18:56:50] <paroneayea> breton: maybe we should choose rabbitmq then
[18:57:05] <paroneayea> breton: it's something to research, for now, I think
[18:57:24] <breton> paroneayea: yes. I don't thing that it's going to be hard, because it's well packaged everywhere
[18:58:00] <paroneayea> breton: rabbitmq you mean?
[18:58:20] <breton> paroneayea: yes
[18:58:50] <paroneayea> breton: ok, I'm ok with going rabbitmq
[18:58:54] <paroneayea> it will take work
[18:59:29] <paroneayea> here is our ticket https://issues.mediagoblin.org/ticket/5464
[18:59:42] <paroneayea> I'll add a comment summarizing our thoughts from the meeting
[19:00:23] <paroneayea> and... I think that's it from the meeting right?
[19:00:34] <larjona> Yes
[19:00:52] <paroneayea> ok, in that case :)
[19:00:58] <paroneayea> HAPPY BIRTHDAY
[19:01:02] <paroneayea> ()
[19:01:02] <paroneayea> .-----||-----.
[19:01:05] <paroneayea> |'---______---'|
[19:01:08] <paroneayea> |. .|
[19:01:11] <paroneayea> _| '----__----' |_
[19:01:14] <paroneayea> ( '--__________--' )
[19:01:17] <paroneayea> '---__________---'
[19:01:20] <paroneayea> BRETON!
[19:01:24] <paroneayea> thanks for coming, breton, larjona, tsyesika :)
[19:01:40] <paroneayea> #endmeeting

</nowiki>

Meeting

2016-09-03T17:11:11Z

Larjona: /* Past Meetings */

== 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. [http://mediagoblin.org/irclogs/ Logs for past meetings]. (Temporarily not working), see below for logs of each meeting.

== Next Meeting ==

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

=== Oct 1, 2016 ===

== Past Meetings ==

=== 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]

Meeting

2016-09-03T17:09:15Z

Larjona: /* May 7, 2016 */

== 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. [http://mediagoblin.org/irclogs/ Logs for past meetings]. (Temporarily not working), see below for logs of each meeting.

== Next Meeting ==

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

=== Oct 1, 2016 ===

== Past Meetings ==

=== 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]

Meeting

2016-09-03T17:08:20Z

Larjona: /* MediaGoblin Monthly Meeting */ note about http://mediagoblin.org/irclogs/ not working

== 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. [http://mediagoblin.org/irclogs/ Logs for past meetings]. (Temporarily not working), see below for logs of each meeting.

== Next Meeting ==

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

=== May 7, 2016 ===

== Past Meetings ==

=== 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]

Meeting

2016-04-02T20:27:08Z

Larjona: /* Past Meetings */

== 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. [http://mediagoblin.org/irclogs/ Logs for past meetings.]

== Next Meeting ==

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

=== May 7, 2016 ===

== Past Meetings ==

=== 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]

20160305 Log

2016-04-02T20:26:25Z

Larjona: Created page with " <nowiki> [18:02] <chaosgoblin> ###################### [18:02] <chaosgoblin> Meeting started Sat Mar 5 17:02:14 2016 UTC. The chair is paroneayea. Information about the ..."

<nowiki>

[18:02] <chaosgoblin> ######################

[18:02] <chaosgoblin> Meeting started Sat Mar 5 17:02:14 2016 UTC.
The chair is paroneayea.
Information about the meeting agenda at http://wiki.mediagoblin.org/Meeting#Next_Meeting

[18:02] <chaosgoblin> Useful Commands: #action #agreed #info #idea #link #topic.

[18:02] <paroneayea> there we go

[18:02] <paroneayea> hello everyone!

[18:02] <ayleph> o/

[18:02] -*- tsyesika waves

[18:02] <paroneayea> :)

[18:03] -*- ersi waves

[18:03] <paroneayea> https://wiki.mediagoblin.org/Meeting#Next_Meeting here's the current agenda!

[18:03] <chaosgoblin> Title: Meeting - GNU MediaGoblin Wiki (at wiki.mediagoblin.org)

[18:03] <-- angelo1 left (Ping timeout: 276 seconds)

[18:03] <paroneayea> feel free to add something, though let us know

[18:03] <paroneayea> #topic 0.9.0 release (imminent!)

[18:04] <paroneayea> so, we're actually close on this

[18:04] <paroneayea> on the code side, it's mostly the Alembic + plugins issue which is holding us up,
which I hope to deal with this weekend

[18:04] -*- tsyesika adds things

[18:04] <paroneayea> on the PR side, I sent Deb an outline for the blogpost, we'll talk monday,
and the release art is done

[18:04] --> angelo1 joined #mediagoblin

[18:05] <paroneayea> though I did it on paper and there isn't a good scanner here ;)

[18:05] <paroneayea> oh well! release art may be a bit grainy looking till I get home

[18:05] <ayleph> My only outstanding ticket on 0.9.0 is #5376
and I've just pushed a couple more fixes for it.
I've changed the ticket severity for the remaining task.
If we went ahead and released without fixing the very last bit of #5376,
I'd be okay addressing it later.

[18:05] <paroneayea> https://wiki.mediagoblin.org/Meeting#Next_Meeting

[18:05] <chaosgoblin> Title: Meeting - GNU MediaGoblin Wiki (at wiki.mediagoblin.org)

[18:06] <paroneayea> great ayleph

[18:06] <paroneayea> so I got distracted because I gave a talk yesterday,
but now that that's over, this weekend is devoted to the plugin stuff for me

[18:06] <paroneayea> I've made *some* headway

[18:06] <paroneayea> here's what I'm thinking though:

[18:07] <paroneayea> I don't think merging this is necessary for the release,
because it's kind of a feature, but proving that we have a way forward
with something to merge after 0.9.0 is out

[18:07] <paroneayea> *is* necessary

[18:07] <paroneayea> I think it might be safer to merge after 0.9.0
since 0.9.0's migrations work and adding such a big thing
so close to release might do something unexpected

[18:07] <paroneayea> what do people think?

[18:07] <tsyesika> err

[18:08] <paroneayea> tsyesika does not agree ;)

[18:08] <tsyesika> the alembic migrations + plugins?

[18:08] <paroneayea> tsyesika: yes

[18:08] <tsyesika> I think we should do it prior

[18:08] <tsyesika> and we should also have alembic making the initial database,
it causes problems if we don't

[18:09] <paroneayea> tsyesika: ok... well, I'll try for having that ready to merge this weekend.
Maybe we should look at the code and check in on Monday?

[18:09] <paroneayea> hopefully it can be ready by then!

[18:09] <tsyesika> i think it's important to have this merged

[18:10] <paroneayea> you're probably right, I'm just nervous
about doing the wrong thing so close to release :\

[18:10] <tsyesika> currently we have a bug where if an alembic migration makes structural changes
it errors as the db is initiated from models.py so at the very least that needs fixing

[18:10] <tsyesika> but i think the plugins alembic migration should be added too
then we can scrap the sqlalchemy generation based of models.py

[18:11] <paroneayea> tsyesika: okay, yeah that's a blocker I suppose

[18:11] <paroneayea> okay, I'll do my best this weekend.

[18:11] <paroneayea> is there anything else to say on the release then?

[18:12] <ayleph> I wanted to throw something out there

[18:12] <tsyesika> don't think so, if you can't get it done this weekend, push the release back a few days

[18:12] <ayleph> I've added some fixes for the blog mediatype

[18:12] <paroneayea> ayleph: shoot

[18:12] <paroneayea> ayleph: ah yeah

[18:12] <ayleph> i haven't marked it with 0.9.0 yet

[18:12] <paroneayea> ayleph: I'm okay with blog fixes being merged

[18:12] <ayleph> it's got a migration (my first), and it's dead simple, but it's something to be aware of if we merge

[18:12] <paroneayea> ayleph: ah yeah... hm! this might be tricky

[18:13] <paroneayea> because of the forementioned alembic + plugins thing

[18:13] <paroneayea> I'd say hold off till after release, if that's ok?

[18:13] <ayleph> absolutely

[18:13] <paroneayea> cool.

[18:13] <paroneayea> oh, there's one more thing I wanted to bring up on the plugin migrations front

[18:14] <paroneayea> there are really two paths: doing things the way we did with sqlalchemy-migrate
where plugins are treated kind of as their own applications (if that's possible...)

[18:14] <paroneayea> or using the "branching" feature of alembic

[18:14] <paroneayea> the branching feature is probably a better route

[18:14] <ayleph> actually, i think that maybe i did the migration wrong...
i added it in the normal migrations path, not in the plugin migrations path.
didn't think about that.

[18:14] <paroneayea> though it's warned heavily that it's "beta"

[18:14] <paroneayea> ayleph: ah yeah, it should be in the plugin migrations stuff. Hold off on it!

[18:14] <ayleph> roger

[18:15] <paroneayea> I guess which route to take requires more investigation by me this weekend?

[18:16] <paroneayea> hopefully this can be resolved with a clear solution fast

[18:16] <paroneayea> ok! should we go onto the next topic?

[18:16] <ayleph> I'm afraid this is beyond my experience enough that I can't make a useful contribution

[18:16] <ayleph> regarding choosing which way forward

[18:16] <paroneayea> ok

[18:16] <paroneayea> we'll see then!

[18:16] <paroneayea> I know some other people are doing plugins + branching

[18:16] <paroneayea> so it's probably good enough to go that route

[18:17] <paroneayea> ok.

[18:17] <paroneayea> next item!

[18:17] <paroneayea> #topic GSoC

[18:18] <paroneayea> so, I guess the most important question I have on this one is,
is anyone else interested in mentoring? :)

[18:18] <paroneayea> right now breton and I are listed https://wiki.mediagoblin.org/GSOC_2016

[18:18] <chaosgoblin> Title: GSOC 2016 - GNU MediaGoblin Wiki (at wiki.mediagoblin.org)

[18:18] <tsyesika> i have no idea how busy i will be yet, when's the deadline

[18:19] <paroneayea> https://developers.google.com/open-source/gsoc/timeline

[18:19] <chaosgoblin> Title: Google Summer of Code 2016 Timeline | Google Summer of Code
| Google Developers (at developers.google.com)

[18:19] --> fdhj joined #mediagoblin

[18:19] <fdhj> any have a pluc service with mediaglobin ?

[18:19] <paroneayea> not sure what the deadline is for mentors, though I guess ideally before March 14th

[18:19] <paroneayea> fdhj: we're in a meeting, though I don't know what that is

[18:20] --> j12t joined #mediagoblin

[18:20] <tsyesika> ah, probably won't know so don't want to put myself down
in case i won't be able to take the role

[18:20] <tsyesika> maybe next year though :)

[18:20] <paroneayea> tsyesika: totally justified

[18:20] <paroneayea> ok, well if you're interested, you can aldo contact me

[18:20] <paroneayea> also

[18:20] <fdhj> sorry

[18:20] <paroneayea> fdhj: no worries!

[18:20] <fdhj> public service

[18:21] <paroneayea> does anyone else have anything to bring up on gsoc?

[18:21] <paroneayea> or should we move on?

[18:21] <-- saksham1115 left (Remote host closed the connection)

[18:22] --> saksham1115 joined #mediagoblin

[18:22] <-- saksham1115 left (Remote host closed the connection)

[18:23] <paroneayea> guess not :)

[18:23] <paroneayea> so move on!

[18:23] --> saksham1115 joined #mediagoblin

[18:23] <paroneayea> #topic Federation mini-update

[18:23] <paroneayea> this one's all tsyesika

[18:23] <paroneayea> take it away!

[18:23] <tsyesika> :)

[18:24] <tsyesika> well a lot of progress has been made and If you've been following me on pump
and in places I've shown some pictures but federation is coming along

[18:24] <-- j12t left (Ping timeout: 252 seconds)

[18:24] <tsyesika> We've now got to the stage where you can specify the audience on the upload form
and it automatically federates to both remote and local users

[18:25] <tsyesika> we also this week I got some code in place to do some federation back
(http://tsyesika.se/something_cool.png shows comment federation from pump.io to mediagoblin)

[18:25] <tsyesika> I'm aiming to get this to a mergable point in the next few days
so it can be merged after 0.9.0 but before next weekend

[18:25] <-- saksham1115 left (Remote host closed the connection)

[18:26] <tsyesika> I'll appriciate lots of testing once it has been merged :)

[18:26] --> saksham1115 joined #mediagoblin

[18:27] <paroneayea> :) :)

[18:27] <paroneayea> \o/

[18:27] <tsyesika> :)

[18:27] <paroneayea> you are doing amazing work tsyesika

[18:27] <paroneayea> thanks for all your hard effort

[18:27] <tsyesika> no problem :) It

[18:27] <tsyesika> * I'm glad it's all coming together

[18:27] <paroneayea> me too!

[18:28] <-- saksham1115 left (Remote host closed the connection)

[18:28] --> saksham1115 joined #mediagoblin

[18:28] <paroneayea> cool, anyone have questions on federation?

[18:28] <ayleph> what pump client has tsyesika been using for testing lately?

[18:28] <tsyesika> pumpa

[18:28] -*- ayleph has had trouble getting dianara and pumpa to connect recently

[18:29] <ayleph> okay cool. maybe something on my end then.

[18:29] <paroneayea> ayleph: what server are you on?

[18:29] <paroneayea> microca.st has been down for me

[18:29] <tsyesika> ayleph: apache by default strips the Authorization header,
there is an extra config header you need to specify to stop it doing that

[18:29] <paroneayea> oh

[18:29] <paroneayea> you mean for mediagoblin testing ;)

[18:29] <paroneayea> har

[18:29] <paroneayea> har

[18:29] <ayleph> paroneayea: Oh, I run my own pump server which works fine for me
(if I rememeber to enable it), but yeah, I mean mediagoblin testing :)

[18:29] -*- paroneayea a dope :)

[18:30] <tsyesika> also when people do test, federation to some pump.io servers might not work
until the next pump.io release as I had to fix a bug in pump :)

[18:30] <tsyesika> but the fix is in master so all is well if you run from that

[18:30] <ayleph> tsyesika: I use lighttpd. I used to be able to connect to master with pumpa,
but it's not working since i upgraded pumpa

[18:30] <tsyesika> hm

[18:30] <tsyesika> interesting

[18:30] <tsyesika> ayleph: file a bug, i'll see if i can track it down once i've finished up
with the federation stuff

[18:30] <ayleph> sounds good

[18:33] <paroneayea> woo

[18:33] <paroneayea> so, anything else?

[18:33] <paroneayea> also tsyesika it sounded like you had something you wanted to discuss?

[18:33] <paroneayea> maybe I misread!

[18:33] <tsyesika> I'd like to bring up that both me and paroneayea will be at LP :)

[18:33] <paroneayea> oh yes!

[18:33] <paroneayea> we will!

[18:33] <paroneayea> LP == LibrePlanet

[18:33] <ayleph> when and where is that?

[18:34] <tsyesika> https://libreplanet.org/2016/ (March 19th to 20th at MIT, MA)

[18:34] <chaosgoblin> Title: LibrePlanet 2016 (at libreplanet.org)

[18:34] <ayleph> oh, that's just a couple weeks away. cool

[18:34] <paroneayea> yeah

[18:34] <paroneayea> I'll be speaking with davexunit, too

[18:35] <paroneayea> about "Solving the deployment crisis with GNU Guix"

[18:37] <paroneayea> so!

[18:37] <paroneayea> maybe see some of you there?

[18:37] <paroneayea> and with that, I think we're at meeting end?

[18:37] -*- tsyesika nods

[18:37] <paroneayea> thanks everyone for coming! :)

[18:38] <paroneayea> and let's end the meeting with an ascii art version of a ghost cat

[18:38] <paroneayea> /\/\

[18:38] <paroneayea> ( o_o)

[18:38] <paroneayea> ( > >

[18:38] <paroneayea> ~ ----

[18:38] <paroneayea> booo!

[18:38] <paroneayea> horray for ghosts! (boo!)

[18:38] <biotedd> miaouu

[18:38] <paroneayea> #endmeeting

[18:38] <chaosgoblin> Meeting ended Sat Mar 5 17:38:47 2016 UTC.
Minutes: http://mediagoblin.org/irclogs/irc_meeting-2016-03-05.html

[18:38] <chaosgoblin> Minutes (text): http://mediagoblin.org/irclogs/irc_meeting-2016-03-05.txt

[18:38] <chaosgoblin> Log: http://mediagoblin.org/irclogs/irc_meeting-2016-03-05.log.html

[18:38] <chaosgoblin> ######################

</nowiki>

Meeting

2016-04-02T19:25:56Z

Larjona: /* Past Meetings */

== 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. [http://mediagoblin.org/irclogs/ Logs for past meetings.]

== Next Meeting ==

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

=== May 7, 2016 ===

== Past Meetings ==

=== 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

=== 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]

20160402 Log

2016-04-02T19:25:29Z

Larjona:

<nowiki>

[18:04] <chaosgoblin> ######################

[18:04] <chaosgoblin> Meeting started Sat Apr 2 16:04:20 2016 UTC.
The chair is breton.
Information about the meeting agenda at http://wiki.mediagoblin.org/Meeting#Next_Meeting

[18:04] <chaosgoblin> Useful Commands: #action #agreed #info #idea #link #topic.

[18:04] <breton> - 0.9.0

[18:05] <breton> - GSoC

[18:05] <breton> - 1.0?

[18:07] -*- breton double-checks that he is not wrong with the time

[18:07] <breton> https://www.timeanddate.com/worldclock/fixedtime.html?iso=20160402T09&p1=224&ah=1
looks like not

[18:07] <chaosgoblin> Title: Event Time Announcer (at www.timeanddate.com)

[18:07] <breton> ok then!

[18:07] <breton> #topic 0.9.0

[18:07] <breton> It released!

[18:08] <breton> http://mediagoblin.org/news/mediagoblin-0.9.0-three-goblineers.html

[18:08] <chaosgoblin> Title: MediaGoblin 0.9.0: The Three Goblineers | MediaGoblin (at mediagoblin.org)

[18:08] <breton> #link http://mediagoblin.org/news/mediagoblin-0.9.0-three-goblineers.html

[18:10] <breton> things seem to be going good, except some issues with python3 i see above in scrollback

[18:11] -*- breton waits for several more minutes

[18:16] <breton> ok than!

[18:16] <breton> #topic GSoC

[18:16] <breton> we have 2 proposals this time

[18:19] <breton> we have already requested our slots and now waiting for the results;
they will be after 16th of April afaik

[18:20] <breton> and the selected projects will be announced on 22nd of April

[18:21] <breton> #topic 1.0

[18:22] <breton> by this time i wanted paroneayea to chime in, but it seems he is not here

[18:22] <breton> i don't know what is planned for 1.0, so i'll leave it hanging for some time now

[18:24] --> angelo1 joined #mediagoblin

[18:29] <-- angelo1 left #mediagoblin

[18:29] --> angelo1 joined a #mediagoblin

[18:34] <paroneayea> hello!

[18:34] <paroneayea> I'm here now!

[18:34] <paroneayea> (oops)

[18:34] <paroneayea> I can chime in on 1.0 :)

[18:34] <paroneayea> the "main goal" of 1.0 is to get federation merged, and then cleaned up

[18:35] <paroneayea> tsyesika has a branch with most things ready to be merged for "federation basics"

[18:35] <paroneayea> I need to go through it

[18:35] <breton> lets just merge it

[18:35] <breton> and see how it goes

[18:35] <paroneayea> also she's somewhat busy the next few weeks so

[18:35] <paroneayea> hm

[18:35] <breton> it will be more eyes after all

[18:35] <paroneayea> breton: I think yes, except that some sqlite migrations are failing

[18:35] <paroneayea> those should be fixed first.

[18:36] <paroneayea> but other than that, I'm not sure what should go into 1.0.
I think we need to see as we start playing with it how long it'll take
to make federation "nice enough" for a 1.0 release.

[18:36] <paroneayea> and I think other things might be mergable in the window that we're cleaning that up

[18:37] <paroneayea> and we should merge those, as always :)

[18:38] <paroneayea> I'm not sure what else to say on that topic!

[18:38] <paroneayea> I'm going to review tsyesika's code today and hopefully talk to her on monday

[18:39] <paroneayea> I should also say: Jessica's time on MediaGoblin ended this week

[18:39] <paroneayea> well, paid :)

[18:39] <paroneayea> she will be volunteering

[18:40] <paroneayea> breton: I think I'm done updating :)

[18:40] <paroneayea> unless anyone has questions

[18:42] <breton> i have a question, but not about 1.0

[18:42] <paroneayea> breton: ask your question!

[18:42] <breton> paroneayea: how much time do you have at Stripe? (it was them, right?)

[18:43] <paroneayea> breton: right! I have one month left to focus on mediagoblin.

[18:43] <paroneayea> breton: in which case, after thta, I'll be figuring out what's next

[18:43] --> JoldWebb joined #mediagoblin

[18:43] <paroneayea> which

[18:43] <paroneayea> mediagoblin will be involved in some way

[18:43] <paroneayea> but how focused will depend on what happens

[18:44] <-- GoldenNeko left (Ping timeout: 268 seconds)

[18:45] <paroneayea> I'm doing my best to bring the mediagoblin an dederation dream true!
but funding is hard :)

[18:45] -*- breton has no more questions

[18:45] <paroneayea> cool

[18:47] <paroneayea> so is that it for the meeting? :)

[18:48] <breton> looks like it!

[18:48] <breton> #endmeeting

[18:48] <chaosgoblin> Meeting ended Sat Apr 2 16:48:08 2016 UTC.
Minutes: http://mediagoblin.org/irclogs/irc_meeting-2016-04-02.html

[18:48] <chaosgoblin> Minutes (text): http://mediagoblin.org/irclogs/irc_meeting-2016-04-02.txt

[18:48] <chaosgoblin> Log: http://mediagoblin.org/irclogs/irc_meeting-2016-04-02.log.html

[18:48] <chaosgoblin> ######################

</nowiki>

Meeting

2016-04-02T19:20:27Z

Larjona: /* March 5, 2016, 9:00AM Pacific Time, 17:00 UTC */

== 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. [http://mediagoblin.org/irclogs/ Logs for past meetings.]

== Next Meeting ==

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

=== May 7, 2016 ===

== Past Meetings ==

=== 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]

20160402 Log

2016-04-02T19:19:02Z

Larjona: /* Past Meetings */ Add 2016/04/02 meeting

<nowiki>

[18:04] <chaosgoblin> ######################

[18:04] <chaosgoblin> Meeting started Sat Apr 2 16:04:20 2016 UTC. The chair is breton. Information about the meeting agenda at http://wiki.mediagoblin.org/Meeting#Next_Meeting

[18:04] <chaosgoblin> Useful Commands: #action #agreed #info #idea #link #topic.

[18:04] <breton> - 0.9.0

[18:05] <breton> - GSoC

[18:05] <breton> - 1.0?

[18:07] -*- breton double-checks that he is not wrong with the time

[18:07] <breton> https://www.timeanddate.com/worldclock/fixedtime.html?iso=20160402T09&p1=224&ah=1 looks like not

[18:07] <chaosgoblin> Title: Event Time Announcer (at www.timeanddate.com)

[18:07] <breton> ok then!

[18:07] <breton> #topic 0.9.0

[18:07] <breton> It released!

[18:08] <breton> http://mediagoblin.org/news/mediagoblin-0.9.0-three-goblineers.html

[18:08] <chaosgoblin> Title: MediaGoblin 0.9.0: The Three Goblineers | MediaGoblin (at mediagoblin.org)

[18:08] <breton> #link http://mediagoblin.org/news/mediagoblin-0.9.0-three-goblineers.html

[18:10] <breton> things seem to be going good, except some issues with python3 i see above in scrollback

[18:11] -*- breton waits for several more minutes

[18:16] <breton> ok than!

[18:16] <breton> #topic GSoC

[18:16] <breton> we have 2 proposals this time

[18:19] <breton> we have already requested our slots and now waiting for the results; they will be after 16th of April afaik

[18:20] <breton> and the selected projects will be announced on 22nd of April

[18:21] <breton> #topic 1.0

[18:22] <breton> by this time i wanted paroneayea to chime in, but it seems he is not here

[18:22] <breton> i don't know what is planned for 1.0, so i'll leave it hanging for some time now

[18:24] --> angelo1 joined #mediagoblin

[18:29] <-- angelo1 left #mediagoblin

[18:29] --> angelo1 joined a #mediagoblin

[18:34] <paroneayea> hello!

[18:34] <paroneayea> I'm here now!

[18:34] <paroneayea> (oops)

[18:34] <paroneayea> I can chime in on 1.0 :)

[18:34] <paroneayea> the "main goal" of 1.0 is to get federation merged, and then cleaned up

[18:35] <paroneayea> tsyesika has a branch with most things ready to be merged for "federation basics"

[18:35] <paroneayea> I need to go through it

[18:35] <breton> lets just merge it

[18:35] <breton> and see how it goes

[18:35] <paroneayea> also she's somewhat busy the next few weeks so

[18:35] <paroneayea> hm

[18:35] <breton> it will be more eyes after all

[18:35] <paroneayea> breton: I think yes, except that some sqlite migrations are failing

[18:35] <paroneayea> those should be fixed first.

[18:36] <paroneayea> but other than that, I'm not sure what should go into 1.0. I think we need to see as we start playing with it how long it'll take to make federation "nice enough" for a 1.0 release.

[18:36] <paroneayea> and I think other things might be mergable in the window that we're cleaning that up

[18:37] <paroneayea> and we should merge those, as always :)

[18:38] <paroneayea> I'm not sure what else to say on that topic!

[18:38] <paroneayea> I'm going to review tsyesika's code today and hopefully talk to her on monday

[18:39] <paroneayea> I should also say: Jessica's time on MediaGoblin ended this week

[18:39] <paroneayea> well, paid :)

[18:39] <paroneayea> she will be volunteering

[18:40] <paroneayea> breton: I think I'm done updating :)

[18:40] <paroneayea> unless anyone has questions

[18:42] <breton> i have a question, but not about 1.0

[18:42] <paroneayea> breton: ask your question!

[18:42] <breton> paroneayea: how much time do you have at Stripe? (it was them, right?)

[18:43] <paroneayea> breton: right! I have one month left to focus on mediagoblin.

[18:43] <paroneayea> breton: in which case, after thta, I'll be figuring out what's next

[18:43] --> JoldWebb joined #mediagoblin

[18:43] <paroneayea> which

[18:43] <paroneayea> mediagoblin will be involved in some way

[18:43] <paroneayea> but how focused will depend on what happens

[18:44] <-- GoldenNeko left (Ping timeout: 268 seconds)

[18:45] <paroneayea> I'm doing my best to bring the mediagoblin an dederation dream true! but funding is hard :)

[18:45] -*- breton has no more questions

[18:45] <paroneayea> cool

[18:47] <paroneayea> so is that it for the meeting? :)

[18:48] <breton> looks like it!

[18:48] <breton> #endmeeting

[18:48] <chaosgoblin> Meeting ended Sat Apr 2 16:48:08 2016 UTC. Minutes: http://mediagoblin.org/irclogs/irc_meeting-2016-04-02.html

[18:48] <chaosgoblin> Minutes (text): http://mediagoblin.org/irclogs/irc_meeting-2016-04-02.txt

[18:48] <chaosgoblin> Log: http://mediagoblin.org/irclogs/irc_meeting-2016-04-02.log.html

[18:48] <chaosgoblin> ######################

</nowiki>

Git workflow

2016-03-23T00:31:16Z

Larjona: remove the warning about outdated

GNU MediaGoblin uses git for all our version control and we have the
repositories hosted on [https://savannah.gnu.org/projects/mediagoblin Savannah]. We have
two repositories:

* MediaGoblin software: http://git.savannah.gnu.org/cgit/mediagoblin.git
* MediaGoblin website: FIXME! Pending add URL

It's most likely you want to look at the software repository -- not the
website one.

The rest of this chapter talks about using the software repository.

The short of it is: we do not use merge requests. Instead, create a "feature branch" in git that you push somewhere, and link to it on a ticket. Details below.

= How to clone the project =

Do::

git clone git://git.savannah.gnu.org/mediagoblin.git

= How to contribute changes =

== Tie your changes to issues in the issue tracker ==

All patches should be tied to issues in the
[http://issues.mediagoblin.org/ issue tracker].
That makes it a lot easier for everyone to track proposed changes and
make sure your hard work doesn't get dropped on the floor! If there
isn't an issue for what you're working on, please create one. The
better the description of what it is you're trying to fix/implement,
the better everyone else is able to understand why you're doing what
you're doing.

== Use bugfix branches to make changes ==

The best way to isolate your changes is to create a branch based off
of the MediaGoblin repository master branch, do the changes related to
that one issue there, and then let us know how to get it.

It's much easier on us if you isolate your changes to a branch focused
on the issue. Then we don't have to sift through things.

It's much easier on you if you isolate your changes to a branch
focused on the issue. Then when we merge your changes in, you just
have to do a {{Cmd|git fetch}} and that's it. This is especially true if
we reject some of your changes, but accept others or otherwise tweak
your changes.

Further, if you isolate your changes to a branch, then you can work on
multiple issues at the same time and they don't conflict with one
another.

Name your branches using the isue number and something that makes it clear
what it's about. For example, if you were working on tagging, you
might name your branch "360_tagging".

== Properly document your changes ==

Include comments in the code.

Write comprehensive commit messages. The better your commit message
is at describing what you did and why, the easier it is for us to
quickly accept your patch.

Write comprehensive comments in the issue tracker about what you're
doing and why.

== How to send us your changes ==

There are two ways to let us know how to get it:

=== push changes to publicly available git clone and let us know where to find it ===

''This is the preferred method of sending changes.''

Push your feature/bugfix/issue branch to your publicly available
git clone and add a comment to the issue with the url for your
clone and the branch to look at.

=== attaching the patch files to the issue ===

Run

{{Cmd|git format-patch --stdout <remote>/master > issue_<number>.patch}}

<tt>format-patch</tt> creates a patch of all the commits that are in
your branch that aren't in <tt><remote>/master</tt>. The <tt>--stdout</tt>
flag causes all this output to go to stdout where it's redirected
to a file named <tt>issue_<number>.patch</tt>. That file should be
based on the issue you're working with. For example,
<tt>issue_42.patch</tt> is a good filename and <tt>issue_42_rev2.patch</tt>
is good if you did a revision of it.

Having said all that, the filename isn't wildly important.

= Example workflow =

Here's an example workflow.

== Contributing changes ==

Slartibartfast from the planet Magrathea far off in the universe has
decided that he is bored with fjords and wants to fix issue 42 (the
meaning of life bug) and send us the changes.

Slartibartfast has cloned the MediaGoblin repository and his clone
lives on repo.or.cz.

Slartibartfast works locally. The remote named ``origin`` points to
his clone on repo.or.cz. The remote named ``gmg`` points to the
MediaGoblin repository.

Slartibartfast does the following:

1. Fetches the latest from the MediaGoblin repository::

git fetch --all -p

This tells <tt>git fetch</tt> to fetch all the recent data from all of
the remotes (<tt>--all</tt>) and prune any branches that have been
deleted in the remotes (<tt>-p</tt>).

2. Creates a branch from the tip of the MediaGoblin repository (the remote is named <tt>gmg</tt>) master branch called <tt>bug42_meaning_of_life</tt>:

git checkout -b bug42_meaning_of_life gmg/master

This creates a new branch (<tt>-b</tt>) named <tt>bug42_meaning_of_life</tt> based
on the tip of the <tt>master</tt> branch of the remote named <tt>gmg</tt> and checks
it out.

3. Slartibartfast works hard on his changes in the <tt>bug42_meaning_of_life</tt> branch. When done, he wants to notify us that he has made changes he wants us to see.

4. Slartibartfast pushes his changes to his clone:

git push origin bug42_meaning_of_life --set-upstream

This pushes the changes in the <tt>bug42_meaning_of_life</tt> branch to the remote named <tt>origin</tt>.

5. Slartibartfast adds a comment to issue 42 with the url for his repository and the name of the branch he put the code in. He also explains what he did and why it addresses the issue.

== Updating a contribution ==

Slartibartfast brushes his hands off with the sense of accomplishment
that comes with the knowledge of a job well done. He stands, wanders
over to get a cup of water, then realizes that he forgot to run the
unit tests!

He runs the unit tests and discovers there's a bug in the code!

Then he does this:

1. He checks out the <tt>bug42_meaning_of_life</tt> branch::

git checkout bug42_meaning_of_life

2. He fixes the bug and checks it into the <tt>bug42_meaning_of_life</tt> branch.

3. He pushes his changes to his clone (the remote is named <tt>origin</tt>):

git push origin bug42_meaning_of_life

4. He adds another comment to issue 42 explaining about the mistake and how he fixed it and that he's pushed the new change to the <tt>bug42_meaning_of_life</tt> branch of his publicly available clone.

== What happens next ==

Slartibartfast is once again happy with his work. He finds issue 42
in the issue tracker and adds a comment saying he submitted a merge
request with his changes and explains what they are.
: "merge request"? http://git.savannah.gnu.org/cgit/mediagoblin says "We don't use no stinking merge requests"

Later, someone checks out his code and finds a problem with it. He
adds a comment to the issue tracker specifying the problem and asks
Slartibartfast to fix it. Slartibartfst goes through the above steps
again, fixes the issue, pushes it to his
<tt>bug42_meaning_of_life</tt> branch and adds another comment to the
issue tracker about how he fixed it.

Later, someone checks out his code and is happy with it. Someone
pulls it into the master branch of the MediaGoblin repository and adds
another comment to the issue and probably closes the issue out.

Slartibartfast is notified of this. Slartibartfast does a:

git fetch --all

The changes show up in the <tt>master</tt> branch of the <tt>gmg</tt> remote.
Slartibartfast now deletes his <tt>bug42_meaning_of_life</tt> branch
because he doesn't need it anymore.

= How to learn git =

[[BeginnersCorner#Learning_git]]

Git workflow

2016-03-23T00:29:23Z

Larjona: Changing gitorious for savannah for Mediagoblin, and gitorious for repo.or.cz for contributor's repo

'''HELP!''' This workflow is no longer correct. We're no longer hosted on gitorious.org and are rather [https://savannah.gnu.org/projects/mediagoblin hosted on Savannah]. We need to update this guide appropriately.

GNU MediaGoblin uses git for all our version control and we have the
repositories hosted on [http://gitorious.org/ Gitorious]. We have
two repositories:

* MediaGoblin software: http://git.savannah.gnu.org/cgit/mediagoblin.git
* MediaGoblin website:

It's most likely you want to look at the software repository -- not the
website one.

The rest of this chapter talks about using the software repository.

The short of it is: we do not use merge requests. Instead, create a "feature branch" in git that you push somewhere, and link to it on a ticket. Details below.

= How to clone the project =

Do::

git clone git://git.savannah.gnu.org/mediagoblin.git

= How to contribute changes =

== Tie your changes to issues in the issue tracker ==

All patches should be tied to issues in the
[http://issues.mediagoblin.org/ issue tracker].
That makes it a lot easier for everyone to track proposed changes and
make sure your hard work doesn't get dropped on the floor! If there
isn't an issue for what you're working on, please create one. The
better the description of what it is you're trying to fix/implement,
the better everyone else is able to understand why you're doing what
you're doing.

== Use bugfix branches to make changes ==

The best way to isolate your changes is to create a branch based off
of the MediaGoblin repository master branch, do the changes related to
that one issue there, and then let us know how to get it.

It's much easier on us if you isolate your changes to a branch focused
on the issue. Then we don't have to sift through things.

It's much easier on you if you isolate your changes to a branch
focused on the issue. Then when we merge your changes in, you just
have to do a {{Cmd|git fetch}} and that's it. This is especially true if
we reject some of your changes, but accept others or otherwise tweak
your changes.

Further, if you isolate your changes to a branch, then you can work on
multiple issues at the same time and they don't conflict with one
another.

Name your branches using the isue number and something that makes it clear
what it's about. For example, if you were working on tagging, you
might name your branch "360_tagging".

== Properly document your changes ==

Include comments in the code.

Write comprehensive commit messages. The better your commit message
is at describing what you did and why, the easier it is for us to
quickly accept your patch.

Write comprehensive comments in the issue tracker about what you're
doing and why.

== How to send us your changes ==

There are two ways to let us know how to get it:

=== push changes to publicly available git clone and let us know where to find it ===

''This is the preferred method of sending changes.''

Push your feature/bugfix/issue branch to your publicly available
git clone and add a comment to the issue with the url for your
clone and the branch to look at.

=== attaching the patch files to the issue ===

Run

{{Cmd|git format-patch --stdout <remote>/master > issue_<number>.patch}}

<tt>format-patch</tt> creates a patch of all the commits that are in
your branch that aren't in <tt><remote>/master</tt>. The <tt>--stdout</tt>
flag causes all this output to go to stdout where it's redirected
to a file named <tt>issue_<number>.patch</tt>. That file should be
based on the issue you're working with. For example,
<tt>issue_42.patch</tt> is a good filename and <tt>issue_42_rev2.patch</tt>
is good if you did a revision of it.

Having said all that, the filename isn't wildly important.

= Example workflow =

Here's an example workflow.

== Contributing changes ==

Slartibartfast from the planet Magrathea far off in the universe has
decided that he is bored with fjords and wants to fix issue 42 (the
meaning of life bug) and send us the changes.

Slartibartfast has cloned the MediaGoblin repository and his clone
lives on repo.or.cz.

Slartibartfast works locally. The remote named ``origin`` points to
his clone on repo.or.cz. The remote named ``gmg`` points to the
MediaGoblin repository.

Slartibartfast does the following:

1. Fetches the latest from the MediaGoblin repository::

git fetch --all -p

This tells <tt>git fetch</tt> to fetch all the recent data from all of
the remotes (<tt>--all</tt>) and prune any branches that have been
deleted in the remotes (<tt>-p</tt>).

2. Creates a branch from the tip of the MediaGoblin repository (the remote is named <tt>gmg</tt>) master branch called <tt>bug42_meaning_of_life</tt>:

git checkout -b bug42_meaning_of_life gmg/master

This creates a new branch (<tt>-b</tt>) named <tt>bug42_meaning_of_life</tt> based
on the tip of the <tt>master</tt> branch of the remote named <tt>gmg</tt> and checks
it out.

3. Slartibartfast works hard on his changes in the <tt>bug42_meaning_of_life</tt> branch. When done, he wants to notify us that he has made changes he wants us to see.

4. Slartibartfast pushes his changes to his clone:

git push origin bug42_meaning_of_life --set-upstream

This pushes the changes in the <tt>bug42_meaning_of_life</tt> branch to the remote named <tt>origin</tt>.

5. Slartibartfast adds a comment to issue 42 with the url for his repository and the name of the branch he put the code in. He also explains what he did and why it addresses the issue.

== Updating a contribution ==

Slartibartfast brushes his hands off with the sense of accomplishment
that comes with the knowledge of a job well done. He stands, wanders
over to get a cup of water, then realizes that he forgot to run the
unit tests!

He runs the unit tests and discovers there's a bug in the code!

Then he does this:

1. He checks out the <tt>bug42_meaning_of_life</tt> branch::

git checkout bug42_meaning_of_life

2. He fixes the bug and checks it into the <tt>bug42_meaning_of_life</tt> branch.

3. He pushes his changes to his clone (the remote is named <tt>origin</tt>):

git push origin bug42_meaning_of_life

4. He adds another comment to issue 42 explaining about the mistake and how he fixed it and that he's pushed the new change to the <tt>bug42_meaning_of_life</tt> branch of his publicly available clone.

== What happens next ==

Slartibartfast is once again happy with his work. He finds issue 42
in the issue tracker and adds a comment saying he submitted a merge
request with his changes and explains what they are.
: "merge request"? http://git.savannah.gnu.org/cgit/mediagoblin says "We don't use no stinking merge requests"

Later, someone checks out his code and finds a problem with it. He
adds a comment to the issue tracker specifying the problem and asks
Slartibartfast to fix it. Slartibartfst goes through the above steps
again, fixes the issue, pushes it to his
<tt>bug42_meaning_of_life</tt> branch and adds another comment to the
issue tracker about how he fixed it.

Later, someone checks out his code and is happy with it. Someone
pulls it into the master branch of the MediaGoblin repository and adds
another comment to the issue and probably closes the issue out.

Slartibartfast is notified of this. Slartibartfast does a:

git fetch --all

The changes show up in the <tt>master</tt> branch of the <tt>gmg</tt> remote.
Slartibartfast now deletes his <tt>bug42_meaning_of_life</tt> branch
because he doesn't need it anymore.

= How to learn git =

[[BeginnersCorner#Learning_git]]

20160206 Log

2016-02-07T11:14:06Z

Larjona:

<nowiki>

[18:01] <chaosgoblin> ######################

[18:01] <chaosgoblin> Meeting started Sat Feb 6 17:01:22 2016 UTC.

The chair is paroneayea.

Information about the meeting agenda at http://wiki.mediagoblin.org/Meeting#Next_Meeting

[18:01] <chaosgoblin> Useful Commands: #action #agreed #info #idea #link #topic.

[18:01] <-- marxistvegan left (Ping timeout: 264 seconds)

[18:01] <paroneayea> hello, *!

[18:01] <paroneayea> (maybe I should do a qquick reminder of the meeting on the social networks?)

[18:01] <paroneayea> meanwhile, everyone say hi!

[18:02] <ayleph> o/

[18:04] <paroneayea> okay

[18:04] <paroneayea> whoo!

[18:04] -*- paroneayea pulls up the topics

[18:04] -*- paroneayea blasted out a reminder, also

[18:05] <paroneayea> okay

[18:05] <paroneayea> so first item is:

[18:05] <paroneayea> #topic Continuous integration / Commit Notifications

[18:06] <paroneayea> does someone want to step forward to lead this part of the meeting?

[18:06] <paroneayea> no? :) I can do it, though I might not be the best fit :)

[18:07] <paroneayea> ok

[18:07] -*- ayleph doesn't know anything about this one

[18:07] <paroneayea> so, we had continuous integration at one point,

which was generously donated by asheesh, but asheesh isn't running that anymore,

and that's okay because we're just glad he did it at one point!

[18:08] <paroneayea> so if we want to do it again, what do we do?

[18:08] <paroneayea> if someone wants to step forward to do this, and commit notifications, I'm like: "great"

[18:08] <paroneayea> though

[18:08] <paroneayea> I don't want to set up hosting for that until we have a more community-manage'able way of handling servers.

[18:09] <paroneayea> it's one more thing to manage, and clearly I'm not the best sysadmin, and simonft is busy already

[18:09] <ayleph> if someone were to mirror the mediagoblin project on github, would that somehow give us automatic travis-ci capabilities?

[18:09] <ayleph> less of a suggestion and more of a question

[18:10] <paroneayea> ayleph: it might, I dunno

[18:10] <paroneayea> ayleph: having an "official-ish" mirror could cause problems:

my experience is that everyone starts to try to submit changes through github there

[18:10] <breton> what are the requirements for the server to host it?

[18:10] <ayleph> paroneayea: yeah, roger that

[18:11] <paroneayea> breton: we could do it on mediagoblin.org, it's not too expensive iirc,

the main thing is that it's one more thing to maintain

[18:11] <breton> is there a one-... ./configure-make-makeinstall for it?

[18:11] <paroneayea> breton: jenkins is pretty standard in distros these days

[18:11] <paroneayea> but I think the config takes a bit of work

[18:11] <paroneayea> my personal opinion is: if someone wants to step forward to do this on their own server, great

[18:12] <paroneayea> and if not, let's wait until we have a way to do community sysadmin stuff,

via some config managmeent system

[18:12] <paroneayea> otherwise I'm going to just have less time to work on mediagoblin itself

and probably will do a bad job of running it

[18:13] -*- breton is a bad sysadmin

[18:14] <paroneayea> ok

[18:14] <paroneayea> everyone agree with that generally?

[18:14] <paroneayea> time to move on?

[18:14] <ayleph> sure, and sure

[18:14] <paroneayea> cool

[18:14] <paroneayea> so the next one is a pretty big one...

[18:14] <paroneayea> #topic Move sqlite to development-only? (no more migrations)

[18:15] <paroneayea> so, a few things:

[18:15] <breton> *(no more migrations for sqlite)

[18:15] <paroneayea> right

[18:15] <paroneayea> 1) this wouldn't happen until after 0.9.0 is out

[18:15] <paroneayea> 2) we probably need to raise this on-list,

because it's a pretty big change and may affect people,

and we might need some way to help people transition from sqlite -> postgres

[18:16] <paroneayea> but... I think there's good reason to do this

[18:16] <ayleph> for the record, what issues are prompting this?

[18:16] <paroneayea> one of the reasons the federation switchover took so long

is that sqlite doesn't have proper alter table support

[18:16] <paroneayea> and we've been plagued by stuff like that for ages

[18:16] --> jamilgnu joined #mediagoblin

[18:16] <paroneayea> ayleph: mostly: migrations are insane to write with sqlite

and break all the time and result in really bad code

[18:17] <ayleph> i don't suppose moving to alembic helps this then?

[18:17] <paroneayea> ayleph: I guess I don't know

[18:17] <paroneayea> we could wait and see

[18:18] <paroneayea> the alembic developers are fairly negative about sqlite themselves

[18:18] <paroneayea> for this very reason

[18:18] <paroneayea> I've talked to them about it

[18:18] <paroneayea> in fact the reason we initially went with sqlalchemy-migrate

was because the alembic people at that point didn't have and were disinterested in sqlite

[18:18] <paroneayea> and well, now they have sqlite support

[18:19] <paroneayea> so

[18:19] <paroneayea> I guess maybe the answer is, we should look a bit more post-release at alembic

[18:19] <paroneayea> and how well it does

[18:19] <paroneayea> and raise this on list if we do decide to deprecate

[18:20] <paroneayea> ayleph: breton: to be clear, do either of you feel strongly on this one way or another?

[18:20] <ayleph> i'm for deprecating sqlite if it makes for a better product,

but it would be nice if we could maybe support a sqlite branch with some bugfixes for a while,

for those who won't/can't migrate

[18:20] <paroneayea> ayleph: yeah, maybe it could be a slow deprecation

[18:20] <paroneayea> or

[18:20] <paroneayea> support the branch

[18:20] <-- Spacedogg_iie left (Ping timeout: 264 seconds)

[18:20] --> Spacedog_ie joined a #mediagoblin

[18:20] <paroneayea> 0.9.0 supported with fixes for a bit, I dunno

[18:20] <ayleph> you mentioned looking into a migration tool, which i think would be wise

[18:20] <paroneayea> we've never done that before but I guess a LTS-ish branch in this case makes sense

[18:21] <paroneayea> ayleph: yes I think so

[18:21] <breton> ayleph: the problem is not in supporting running on sqlite

[18:22] <breton> but in upgrades

[18:22] <breton> supporting sqlite branch means that we shall have to write migrations for it

[18:22] <breton> which is our pain point

[18:23] <ayleph> yeah, understood. but if mainline gets security fixes after a migration,

maybe we could just cherry-pick the security fixes back to the sqlite branch, and not the migrations.

[18:23] <ayleph> guess it depends on whether migrations are involved/required for fixes.

[18:23] <breton> if we don't cherry-pick the migrations, the databses will differ in sqlite and non-sqlite cases

[18:23] <paroneayea> supporting security updates for a while that are easy to support would be okay

[18:23] <paroneayea> the sqlite branch would probably kind of bitrot away

[18:23] <paroneayea> and I think that would be the goal

[18:24] <breton> from my point of view

[18:24] <ayleph> you mentioned having sqlite for development still

[18:24] <breton> oh, will describe my pov later

[18:24] <ayleph> does that mean that we'd still support rolling out a new mediagoblin instance

with sqlite for testing, but it just wouldn't received migration updates?

[18:24] <breton> yep

[18:24] <ayleph> i think that's okay

[18:25] <breton> to run a migration, you'll have to rm your mediagoblin.db

[18:25] <breton> so

[18:25] <breton> from my point of view

[18:26] <breton> sqlite is the simplest thing for the user

[18:26] <breton> postresql is the most complex

[18:26] <breton> because by default it requires signing in with another user with su

[18:27] <breton> and it took me a lot of time to figure out how to manage it

[18:27] <breton> if we drop sqlite, I think we should support mysql

[18:27] <ayleph> that sounds like a whole lot of work :)

[18:27] <paroneayea> ahhhhh

[18:27] <paroneayea> mysql would add a whole different kind of work

[18:28] <ayleph> the more i use postgresql, the more i prefer it to mysql

[18:28] <breton> which is more popular and has more unofficial docs, like blogposts

[18:28] <breton> yeah, yeah, we all know that postgresql is better

[18:28] <paroneayea> yeah I think mysql is pretty much "living in the past"

[18:28] <paroneayea> ok, well

[18:28] <paroneayea> I'm going to declare this conversation a "tentative maybe"

[18:29] <paroneayea> and we'll explore it after the next release

[18:29] <paroneayea> to see for feasibility

[18:29] <ayleph> i like the general direction of moving toward postgresql as default

[18:29] <ayleph> perhaps we could scriptify the postgresql commands to make it easier for users

[18:29] --> hijkhgr joined #mediagoblin

[18:29] <paroneayea> ayleph: that's a good idea

[18:29] <paroneayea> ok!

[18:29] <paroneayea> how about next topic? :)

[18:29] <breton> (btw, in openstack we DO NOT support postresql)

[18:30] <breton> (like, at all)

[18:30] <paroneayea> breton: what does that mean?

[18:30] <breton> paroneayea: no one tests, no one runs

[18:30] <breton> paroneayea: no installator/manager sets up posgresql or has an option for that

[18:31] <paroneayea> hm

[18:31] <paroneayea> well

[18:31] <paroneayea> I still say we move on :)

[18:31] <paroneayea> I think we've drained this topic :)

[18:32] <paroneayea> and we'll see post 0.9.0

[18:32] <paroneayea> speaking of!

[18:32] <paroneayea> #topic Upcoming 0.9.0 release

[18:32] <paroneayea> so, I said I was going to freeze yesterday and I didn't,

because I packaged the last piece I needed to go fulltime on guixsd as my host distro yesterday ;)

[18:32] <paroneayea> but

[18:32] <paroneayea> I'll freeze today.

[18:33] <paroneayea> any and all "make mediagoblin work on python 3" bugs are fair game during freeze though

[18:33] <paroneayea> as bugs usually are, but *especially* those are, even if they look like features :)

[18:33] <paroneayea> I think python 3 as a first class citizen is going to be a major feature of 0.9.0

[18:33] <ayleph> we're not dropping py2 yet, are we?

[18:33] <paroneayea> nope

[18:34] <paroneayea> py2.7 will be around for some time

[18:34] <ayleph> okay cool

[18:34] <paroneayea> we're just saying "yes, we finally support python 3 as an option"

[18:34] <-- hijkhgr left #mediagoblin ("Leaving")

[18:34] <paroneayea> freedeb has suggested "The Three Goblineers" as a release name

[18:34] <paroneayea> as a play on The Three Musketeers

[18:34] <paroneayea> I like it

[18:34] <ayleph> bd

[18:35] <paroneayea> :)

[18:35] --> hijkhgr joined #mediagoblin

[18:35] <paroneayea> so I guess we should aim for a date.

We usually aim for a week and then don't hit it ;)

[18:35] <ayleph> i don't think a week sounds realistic at all, given how many tickets

are associated with 0.8.2 and 0.9.0

[18:36] <ayleph> 19 at the moment

[18:36] <paroneayea> how about the 22nd?

[18:36] <breton> given that 0.9.0 is mainly a bugfixing release

[18:36] <paroneayea> well right, there are some bugs there we can move over,

because we're moving into bugs-only mode

[18:36] <paroneayea> er, some features

[18:36] <paroneayea> we can roll the features over into next release

[18:37] <breton> I think that we can move bugs to the next release too

[18:37] <-- hijkhgr left (Quit: Leaving)

[18:37] --> hijkhgr joined #mediagoblin

[18:37] <ayleph> there are still some potential big issues with the federation migrations

that have been ongoing.

[18:37] <ayleph> things that cause server crashes when you click on links or load pages

[18:38] <paroneayea> ayleph: yes I'm concerned about those...

[18:38] <paroneayea> ayleph: I'll try to help with them.... eg the comment on postgres one

[18:38] <ayleph> unfortunately i seem to be experiencing them more than others,

with my big existing database

[18:38] -*- paroneayea nods

[18:39] <breton> mark them as critical

[18:39] <paroneayea> yes

[18:39] <ayleph> i believe i have, but i'll check

[18:39] <ayleph> actually, i was marking some as blockers

[18:39] <paroneayea> blockers is also good

[18:39] <breton> ugh.

[18:39] <paroneayea> ugh?

[18:39] <breton> it's bad that we don't fix critical/blocker bugs :(

[18:40] <paroneayea> yeah

[18:40] <paroneayea> so I'm going to do my best to dig in and help with that

[18:40] <ayleph> tsyesika_ and paroneayea have been trying to replicate the issues,

but they haven't had luck

[18:40] <paroneayea> ayleph: I also didn't try with postgres

[18:40] <ayleph> and i've been working out of town since the end of 2015,

so i haven't had much time to figure them out yet

[18:40] <paroneayea> I'm going to try with postgres today

[18:40] <-- hijkhgr left (Client Quit)

[18:40] <ayleph> (I'm on-site in an aircraft factory right now, slacking off on the job)

[18:40] <paroneayea> ayleph: oh, cool :)

[18:41] <paroneayea> (what are you doing there?)

[18:41] <paroneayea> I guess that can be discussed post meeting if you like :)

[18:41] <ayleph> haha, sure. maybe don't want that in the meeting notes :)

[18:41] <paroneayea> yeah

[18:41] <paroneayea> ok!

[18:41] <paroneayea> so is everyone ok with tentative date of the 22nd?

[18:41] <paroneayea> for the release?

[18:42] <paroneayea> I'll make working on these db issues my #1 priority.

[18:42] <breton> tes

[18:42] <breton> *yes

[18:42] <paroneayea> cool

[18:42] <ayleph> yep

[18:42] <paroneayea> onwards and upwards toward 0.9.0, then! :)

[18:42] <paroneayea> next topic?

[18:43] <paroneayea> #topic Path to 1.0

[18:43] <paroneayea> I didn't see any objections, but we can backtrack if there's still 0.9.0 stuff

[18:43] <paroneayea> so my goal is to get 1.0 out in the next couple of months,

which is a tight timeline! This means that we need tsyesika_ really focused on federation totally

[18:44] <paroneayea> since we only have the funds to pay her till end of march especially ... :(

[18:44] --> pizzaiolo joined #mediagoblin

[18:44] <paroneayea> so we'll see

[18:44] <pizzaiolo> am I late to the meeting?

[18:44] <paroneayea> hi pizzaiolo, yes, but welcome!

[18:44] <paroneayea> we're talking about the work towards the 1.0 release

[18:44] <pizzaiolo> oh, cool!

[18:45] <pizzaiolo> any tl;dr of the meeting? :P

[18:45] <paroneayea> so, after 0.9.0 comes out, I think I'll be hunkering down

and helping tsyesika_ with 1.0 as much as possible

[18:45] <paroneayea> pizzaiolo: https://wiki.mediagoblin.org/Meeting#Next_Meeting topics

[18:45] <chaosgoblin> Title: Meeting - GNU MediaGoblin Wiki (at wiki.mediagoblin.org)

[18:45] <pizzaiolo> coolio

[18:45] <paroneayea> I dunno, is there anything more to talk about on this subject? breton, ayleph ?

[18:45] <paroneayea> other than "1.0 is the initial federation release"

[18:46] <ayleph> anyone heard from sapienTech recently?

[18:46] <paroneayea> which is a pretty bold thing to say we'll hit in a couple of months,

but the big db challenges are over at least...

[18:46] <pizzaiolo> paroneayea: anything on the activitypub protocol?

[18:46] <paroneayea> ayleph: ah.... I haven't

[18:46] <paroneayea> pizzaiolo: that's later in the meeting, see the topics

[18:46] <ayleph> curious what we'll need to do to get his app working with the 1.0 release,

if things change.

[18:46] <paroneayea> ayleph: well

[18:46] <paroneayea> I did

[18:46] <paroneayea> actually

[18:46] <paroneayea> I blanked out for a second

[18:46] <paroneayea> we met up a few weeks ago!

[18:46] <paroneayea> sorry, my brain is not working

[18:46] <ayleph> oh cool!

[18:46] <pizzaiolo> okie

[18:46] <paroneayea> he showed me a live demo of the latest goblinoid release

[18:46] <paroneayea> it's looking *very* nice

[18:47] <paroneayea> and he's super interested in getting things updated

to work with things as we do them

[18:47] <pizzaiolo> paroneayea: would love to see this go forward

https://f-droid.org/forums/topic/goblinoid-mediagoblin-app/

[18:47] <pizzaiolo> :)

[18:47] <paroneayea> pizzaiolo: yes that would be really useful

[18:47] <paroneayea> what's the current status? I think they're still hung up on building kivy applications?

[18:48] <pizzaiolo> https://gitlab.com/fdroid/fdroiddata/merge_requests/1034

[18:48] --> j1mc joined #mediagoblin

[18:48] <chaosgoblin> Title: Add MediaGoblin to F-Droid repository (#1034) · Merge Requests · F-Droid / Data · GitLab (at gitlab.com)

[18:48] <ayleph> Last I heard, sapienTech had been trying to weeks or months to get onto F-Droid,

but they weren't ready for kivy builds

[18:48] <ayleph> I had a little trouble building the app myself, so I resorted to having sapienTech

send me binaries to host

[18:48] <paroneayea> https://gitlab.com/fdroid/fdroiddata/commit/dbb7e3f2ea73132454fd1f089412e507741fbd91 wait

[18:49] <chaosgoblin> "Title: Merge branch 'master' into 'master'\r (dbb7e3f2) \xc2\xb7 Commits \xc2\xb7 F-Droid / Data \xc2\xb7 GitLab (at gitlab.com)"

[18:49] <ayleph> I couldn't get the same filesize or hash as him on the binaries,

so I'm not sure I had the right code.

[18:49] <paroneayea> did it get added???

[18:49] <paroneayea> a few days ago?

[18:50] <pizzaiolo> paroneayea: a quick search does not show it in F-Droid

[18:50] <paroneayea> pizzaiolo: it might be in git master

[18:50] <pizzaiolo> hmm

[18:50] <paroneayea> anyway, this is something to check up on post-meeting I think

[18:50] <paroneayea> we have a lot of topics still and only 10 mins left

[18:50] <paroneayea> so I'm taking initiative to blast ahead on topics

[18:51] <paroneayea> #topic Stripe retreat update

[18:51] <paroneayea> so the first week I was here I worked on getting ActivityPub to First Public Working Draft (it is now!)

[18:51] <paroneayea> and second week I spent at and preparing for FOSDEM mostly

[18:52] <paroneayea> and I've done some tickets and have updated my system to GuixSD

(important, davexunit and I hope to do a live demo of mediagoblin deployed on guixsd at libreplanet next month)

[18:52] <pizzaiolo> woo!

[18:52] <paroneayea> and from here on out my main thing is "focus on mediagoblin code itself,

while also trying to advance activitypub mostly on weekends"

[18:52] <paroneayea> so it's been very productive so far.

[18:52] <paroneayea> also FOSDEM was incredible

[18:53] <paroneayea> 80 people capacity in the guile/guix room and full almost the whole time

[18:53] <ayleph> I saw a little chatter in here during FOSDEM. sounds like a great time.

[18:53] <paroneayea> lots of other good things came out of it but we don't have time to go into it right now :)

[18:53] <paroneayea> yes

[18:53] <paroneayea> it was super great

[18:53] <paroneayea> anyway, I wanted to blast through that rundown

[18:53] <paroneayea> I'll be mostly head down on mediagoblin from here on out,

excepting being at libreplanet and working on activitypub

[18:54] <paroneayea> I'm also going to blast forward on topic again unless there's a question

[18:54] <paroneayea> #topic ActivityPub update (related!)

[18:54] <paroneayea> https://identi.ca/mediagoblin/note/CkpUdPDaSryfybqolTkUSg says most of it all :)

[18:54] <chaosgoblin> Title: First Public Working Drafts of ActivityPub and Micropub published - Identi.ca (at identi.ca)

[18:54] <pizzaiolo> sorry, you mentioned stripe, is that stripe.js?

[18:54] <paroneayea> pizzaiolo: I'm at the Stripe Open Source Retreat

[18:55] <pizzaiolo> oh ok nvm

[18:55] <paroneayea> they're paying me to work on mediagoblin out of their office for a few months

[18:55] <pizzaiolo> that's incredible

[18:55] <paroneayea> pretty cool, like "coder in resident"

[18:55] <paroneayea> so, ActivityPub is at FPWD status, which means we have a real w3c url now

[18:55] <paroneayea> http://www.w3.org/TR/activitypub/

[18:55] <chaosgoblin> Title: ActivityPub (at www.w3.org)

[18:55] <paroneayea> I'm going to keep it short: there's a ton to do in working on the spec still

[18:56] <paroneayea> and right before libreplanet is the next w3c face to face

[18:56] <paroneayea> so it's a good thing stripe's office is so nice because between that

and gmg I'll be pulling a lot of long nights here :)

[18:56] <paroneayea> sorry to textwall on these updates, they were mostly from-me updates

[18:56] <paroneayea> and I really wanted to get to this next topic

[18:56] <ayleph> wow, that's really cool seeing your name and tsyesika_'s name as editors on a w3c draft

[18:57] <paroneayea> ayleph: yeah :)

[18:57] <paroneayea> it's happeniningggggg

[18:57] <paroneayea> #topic GSOC ideas, and volunteers?

[18:57] <paroneayea> unless there are any questions on the last topic

[18:57] <paroneayea> but we only have a few minutes for this, so :)

[18:57] <paroneayea> we had a wiki link somewhere right?

[18:58] <paroneayea> https://wiki.mediagoblin.org/GSOC_2016

[18:58] <chaosgoblin> Title: GSOC 2016 - GNU MediaGoblin Wiki (at wiki.mediagoblin.org)

[18:58] <paroneayea> right now breton and I are listed as possible mentors

[18:58] <paroneayea> gnu still needs to be accepted to gsoc, but it probably will be

[18:58] <paroneayea> does anyone else want to mentor something? :)

[18:58] <paroneayea> or anything else to say?

[18:59] <ayleph> ooh, can i ask an unrelated question?

[18:59] <paroneayea> ayleph: go for ti

[18:59] <paroneayea> it

[18:59] <ayleph> do the last fundraiser rewards fit into the 1.0 schedule anywhere?

[18:59] <ayleph> i guess that was mostly federation anyway

[18:59] <ayleph> but also premium hosting?

[19:00] <paroneayea> ayleph: premium hosting is what motivated me to work on guixsd

[19:00] <ayleph> ah okay

[19:00] <paroneayea> because I realized there's no way I can manage to maintain servers in the current state of affairs

[19:00] <ayleph> yeah

[19:00] <paroneayea> so in a sense, the libreplanet demo

[19:00] <paroneayea> is on track for that :)

[19:00] <ayleph> cool

[19:00] <paroneayea> I haven't forgotten!

[19:00] <paroneayea> I was glad to hear breton thought I was mostly sane in my persual of that

[19:00] <paroneayea> I think we're all tired of the fear of server upgrades

[19:00] <ayleph> hehe

[19:01] --> marxistvegan joined #mediagoblin

[19:01] <-- marxistvegan left (Changing host)

[19:01] --> marxistvegan joined #mediagoblin

[19:01] <paroneayea> okay, I guess no gsoc update questions eh?

[19:01] <pizzaiolo> paroneayea: too bad I can't follow cwebber@identi.ca from

nicolasmaia@quitter.se (hopefully it's something activitypub will fix)

[19:01] <breton> I wonder

[19:01] <paroneayea> pizzaiolo: I'm hoping activitypub will be integrated into statusnet

[19:02] <paroneayea> er

[19:02] <paroneayea> gnu social :)

[19:02] <breton> how do we advertise our GSoC

[19:02] <breton> because last year we didn't have many participants

[19:02] <paroneayea> breton: last year I also failed to promote it

[19:02] <paroneayea> this year we'll promote it a lot better, once it's clear we're accepted

[19:02] <paroneayea> it's easier because I'm fulltime on mediagoblin again right now

[19:03] <paroneayea> which means I can justify that time a bit better

[19:03] <breton> and I would like to have a situations with more proposals than tasks

[19:03] <ayleph> i think svetlana mentioned something about promoting it to students locally

[19:03] <paroneayea> ah right :)

[19:03] <paroneayea> svetlana: that'd be cool :)

[19:03] <paroneayea> so anything more on that, or are we done?

[19:04] <-- depate_ left (Ping timeout: 245 seconds)

[19:04] -*- breton thinks we're done

[19:04] <paroneayea> cool

[19:04] <paroneayea> how about an ascii art to seal the meeting?

[19:04] <paroneayea> *INCOMING ASCII*

[19:04] <paroneayea> * .-. .

[19:04] <paroneayea> ( ) . * *

[19:04] <paroneayea> _ '-' , , ,

[19:04] <paroneayea> (_) _ / \.--.\ . \\___// .

[19:05] <paroneayea> _ >(_) " ;" _ ; o o\ _

[19:05] <paroneayea> (_) ( / ) / '------' \

[19:05] <paroneayea> ;._/." . O () "._o_o_o_o."

[19:05] <paroneayea> * \.' . . *

[19:05] <paroneayea> .

[19:05] <paroneayea> HAVE A COSMIC HAPPY GNU YEAR 2016!

[19:05] <paroneayea> a bit late, that was my supporter ascii art for this year's fsf new years email :)

[19:05] <paroneayea> and we're done!

[19:05] <paroneayea> thank you all for coming, breton, ayleph, pizzaiolo!

[19:05] <paroneayea> #endmeeting

[19:05] <chaosgoblin> Meeting ended Sat Feb 6 18:05:37 2016 UTC. Minutes: http://mediagoblin.org/irclogs/irc_meeting-2016-02-06.html

[19:05] <chaosgoblin> Minutes (text): http://mediagoblin.org/irclogs/irc_meeting-2016-02-06.txt

[19:05] <chaosgoblin> Log: http://mediagoblin.org/irclogs/irc_meeting-2016-02-06.log.html

[19:05] <chaosgoblin> ######################
</nowiki>

Meeting

2016-02-07T10:56:53Z

Larjona: /* February 6, 2016, 9:00AM Pacific Time, 17:00 UTC */

== 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. [http://mediagoblin.org/irclogs/ Logs for past meetings.]

== Next Meeting ==

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

=== March 5, 2016, 9:00AM Pacific Time, 17:00 UTC ===

== Past Meetings ==

=== 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]

20160205 Log

2016-02-07T10:56:20Z

Larjona: Larjona moved page 20160205 Log to 20160206 Log

#REDIRECT [[20160206 Log]]

20160206 Log

2016-02-07T10:56:20Z

Larjona: Larjona moved page 20160205 Log to 20160206 Log

<nowiki>

[18:01] <chaosgoblin> ######################

[18:01] <chaosgoblin> Meeting started Sat Feb 6 17:01:22 2016 UTC. The chair is paroneayea. Information about the meeting agenda at http://wiki.mediagoblin.org/Meeting#Next_Meeting

[18:01] <chaosgoblin> Useful Commands: #action #agreed #info #idea #link #topic.

[18:01] <-- marxistvegan left (Ping timeout: 264 seconds)

[18:01] <paroneayea> hello, *!

[18:01] <paroneayea> (maybe I should do a qquick reminder of the meeting on the social networks?)

[18:01] <paroneayea> meanwhile, everyone say hi!

[18:02] <ayleph> o/

[18:04] <paroneayea> okay

[18:04] <paroneayea> whoo!

[18:04] -*- paroneayea pulls up the topics

[18:04] -*- paroneayea blasted out a reminder, also

[18:05] <paroneayea> okay

[18:05] <paroneayea> so first item is:

[18:05] <paroneayea> #topic Continuous integration / Commit Notifications

[18:06] <paroneayea> does someone want to step forward to lead this part of the meeting?

[18:06] <paroneayea> no? :) I can do it, though I might not be the best fit :)

[18:07] <paroneayea> ok

[18:07] -*- ayleph doesn't know anything about this one

[18:07] <paroneayea> so, we had continuous integration at one point, which was generously donated by asheesh, but asheesh isn't running that anymore, and that's okay because we're just glad he did it at one point!

[18:08] <paroneayea> so if we want to do it again, what do we do?

[18:08] <paroneayea> if someone wants to step forward to do this, and commit notifications, I'm like: "great"

[18:08] <paroneayea> though

[18:08] <paroneayea> I don't want to set up hosting for that until we have a more community-manage'able way of handling servers.

[18:09] <paroneayea> it's one more thing to manage, and clearly I'm not the best sysadmin, and simonft is busy already

[18:09] <ayleph> if someone were to mirror the mediagoblin project on github, would that somehow give us automatic travis-ci capabilities?

[18:09] <ayleph> less of a suggestion and more of a question

[18:10] <paroneayea> ayleph: it might, I dunno

[18:10] <paroneayea> ayleph: having an "official-ish" mirror could cause problems: my experience is that everyone starts to try to submit changes through github there

[18:10] <breton> what are the requirements for the server to host it?

[18:10] <ayleph> paroneayea: yeah, roger that

[18:11] <paroneayea> breton: we could do it on mediagoblin.org, it's not too expensive iirc, the main thing is that it's one more thing to maintain

[18:11] <breton> is there a one-... ./configure-make-makeinstall for it?

[18:11] <paroneayea> breton: jenkins is pretty standard in distros these days

[18:11] <paroneayea> but I think the config takes a bit of work

[18:11] <paroneayea> my personal opinion is: if someone wants to step forward to do this on their own server, great

[18:12] <paroneayea> and if not, let's wait until we have a way to do community sysadmin stuff, via some config managmeent system

[18:12] <paroneayea> otherwise I'm going to just have less time to work on mediagoblin itself and probably will do a bad job of running it

[18:13] -*- breton is a bad sysadmin

[18:14] <paroneayea> ok

[18:14] <paroneayea> everyone agree with that generally?

[18:14] <paroneayea> time to move on?

[18:14] <ayleph> sure, and sure

[18:14] <paroneayea> cool

[18:14] <paroneayea> so the next one is a pretty big one...

[18:14] <paroneayea> #topic Move sqlite to development-only? (no more migrations)

[18:15] <paroneayea> so, a few things:

[18:15] <breton> *(no more migrations for sqlite)

[18:15] <paroneayea> right

[18:15] <paroneayea> 1) this wouldn't happen until after 0.9.0 is out

[18:15] <paroneayea> 2) we probably need to raise this on-list, because it's a pretty big change and may affect people, and we might need some way to help people transition from sqlite -> postgres

[18:16] <paroneayea> but... I think there's good reason to do this

[18:16] <ayleph> for the record, what issues are prompting this?

[18:16] <paroneayea> one of the reasons the federation switchover took so long is that sqlite doesn't have proper alter table support

[18:16] <paroneayea> and we've been plagued by stuff like that for ages

[18:16] --> jamilgnu joined #mediagoblin

[18:16] <paroneayea> ayleph: mostly: migrations are insane to write with sqlite and break all the time and result in really bad code

[18:17] <ayleph> i don't suppose moving to alembic helps this then?

[18:17] <paroneayea> ayleph: I guess I don't know

[18:17] <paroneayea> we could wait and see

[18:18] <paroneayea> the alembic developers are fairly negative about sqlite themselves

[18:18] <paroneayea> for this very reason

[18:18] <paroneayea> I've talked to them about it

[18:18] <paroneayea> in fact the reason we initially went with sqlalchemy-migrate was because the alembic people at that point didn't have and were disinterested in sqlite

[18:18] <paroneayea> and well, now they have sqlite support

[18:19] <paroneayea> so

[18:19] <paroneayea> I guess maybe the answer is, we should look a bit more post-release at alembic

[18:19] <paroneayea> and how well it does

[18:19] <paroneayea> and raise this on list if we do decide to deprecate

[18:20] <paroneayea> ayleph: breton: to be clear, do either of you feel strongly on this one way or another?

[18:20] <ayleph> i'm for deprecating sqlite if it makes for a better product, but it would be nice if we could maybe support a sqlite branch with some bugfixes for a while, for those who won't/can't migrate

[18:20] <paroneayea> ayleph: yeah, maybe it could be a slow deprecation

[18:20] <paroneayea> or

[18:20] <paroneayea> support the branch

[18:20] <-- Spacedogg_iie left (Ping timeout: 264 seconds)

[18:20] --> Spacedog_ie joined a #mediagoblin

[18:20] <paroneayea> 0.9.0 supported with fixes for a bit, I dunno

[18:20] <ayleph> you mentioned looking into a migration tool, which i think would be wise

[18:20] <paroneayea> we've never done that before but I guess a LTS-ish branch in this case makes sense

[18:21] <paroneayea> ayleph: yes I think so

[18:21] <breton> ayleph: the problem is not in supporting running on sqlite

[18:22] <breton> but in upgrades

[18:22] <breton> supporting sqlite branch means that we shall have to write migrations for it

[18:22] <breton> which is our pain point

[18:23] <ayleph> yeah, understood. but if mainline gets security fixes after a migration, maybe we could just cherry-pick the security fixes back to the sqlite branch, and not the migrations.

[18:23] <ayleph> guess it depends on whether migrations are involved/required for fixes.

[18:23] <breton> if we don't cherry-pick the migrations, the databses will differ in sqlite and non-sqlite cases

[18:23] <paroneayea> supporting security updates for a while that are easy to support would be okay

[18:23] <paroneayea> the sqlite branch would probably kind of bitrot away

[18:23] <paroneayea> and I think that would be the goal

[18:24] <breton> from my point of view

[18:24] <ayleph> you mentioned having sqlite for development still

[18:24] <breton> oh, will describe my pov later

[18:24] <ayleph> does that mean that we'd still support rolling out a new mediagoblin instance with sqlite for testing, but it just wouldn't received migration updates?

[18:24] <breton> yep

[18:24] <ayleph> i think that's okay

[18:25] <breton> to run a migration, you'll have to rm your mediagoblin.db

[18:25] <breton> so

[18:25] <breton> from my point of view

[18:26] <breton> sqlite is the simplest thing for the user

[18:26] <breton> postresql is the most complex

[18:26] <breton> because by default it requires signing in with another user with su

[18:27] <breton> and it took me a lot of time to figure out how to manage it

[18:27] <breton> if we drop sqlite, I think we should support mysql

[18:27] <ayleph> that sounds like a whole lot of work :)

[18:27] <paroneayea> ahhhhh

[18:27] <paroneayea> mysql would add a whole different kind of work

[18:28] <ayleph> the more i use postgresql, the more i prefer it to mysql

[18:28] <breton> which is more popular and has more unofficial docs, like blogposts

[18:28] <breton> yeah, yeah, we all know that postgresql is better

[18:28] <paroneayea> yeah I think mysql is pretty much "living in the past"

[18:28] <paroneayea> ok, well

[18:28] <paroneayea> I'm going to declare this conversation a "tentative maybe"

[18:29] <paroneayea> and we'll explore it after the next release

[18:29] <paroneayea> to see for feasibility

[18:29] <ayleph> i like the general direction of moving toward postgresql as default

[18:29] <ayleph> perhaps we could scriptify the postgresql commands to make it easier for users

[18:29] --> hijkhgr joined #mediagoblin

[18:29] <paroneayea> ayleph: that's a good idea

[18:29] <paroneayea> ok!

[18:29] <paroneayea> how about next topic? :)

[18:29] <breton> (btw, in openstack we DO NOT support postresql)

[18:30] <breton> (like, at all)

[18:30] <paroneayea> breton: what does that mean?

[18:30] <breton> paroneayea: no one tests, no one runs

[18:30] <breton> paroneayea: no installator/manager sets up posgresql or has an option for that

[18:31] <paroneayea> hm

[18:31] <paroneayea> well

[18:31] <paroneayea> I still say we move on :)

[18:31] <paroneayea> I think we've drained this topic :)

[18:32] <paroneayea> and we'll see post 0.9.0

[18:32] <paroneayea> speaking of!

[18:32] <paroneayea> #topic Upcoming 0.9.0 release

[18:32] <paroneayea> so, I said I was going to freeze yesterday and I didn't, because I packaged the last piece I needed to go fulltime on guixsd as my host distro yesterday ;)

[18:32] <paroneayea> but

[18:32] <paroneayea> I'll freeze today.

[18:33] <paroneayea> any and all "make mediagoblin work on python 3" bugs are fair game during freeze though

[18:33] <paroneayea> as bugs usually are, but *especially* those are, even if they look like features :)

[18:33] <paroneayea> I think python 3 as a first class citizen is going to be a major feature of 0.9.0

[18:33] <ayleph> we're not dropping py2 yet, are we?

[18:33] <paroneayea> nope

[18:34] <paroneayea> py2.7 will be around for some time

[18:34] <ayleph> okay cool

[18:34] <paroneayea> we're just saying "yes, we finally support python 3 as an option"

[18:34] <-- hijkhgr left #mediagoblin ("Leaving")

[18:34] <paroneayea> freedeb has suggested "The Three Goblineers" as a release name

[18:34] <paroneayea> as a play on The Three Musketeers

[18:34] <paroneayea> I like it

[18:34] <ayleph> bd

[18:35] <paroneayea> :)

[18:35] --> hijkhgr joined #mediagoblin

[18:35] <paroneayea> so I guess we should aim for a date. We usually aim for a week and then don't hit it ;)

[18:35] <ayleph> i don't think a week sounds realistic at all, given how many tickets are associated with 0.8.2 and 0.9.0

[18:36] <ayleph> 19 at the moment

[18:36] <paroneayea> how about the 22nd?

[18:36] <breton> given that 0.9.0 is mainly a bugfixing release

[18:36] <paroneayea> well right, there are some bugs there we can move over, because we're moving into bugs-only mode

[18:36] <paroneayea> er, some features

[18:36] <paroneayea> we can roll the features over into next release

[18:37] <breton> I think that we can move bugs to the next release too

[18:37] <-- hijkhgr left (Quit: Leaving)

[18:37] --> hijkhgr joined #mediagoblin

[18:37] <ayleph> there are still some potential big issues with the federation migrations that have been ongoing.

[18:37] <ayleph> things that cause server crashes when you click on links or load pages

[18:38] <paroneayea> ayleph: yes I'm concerned about those...

[18:38] <paroneayea> ayleph: I'll try to help with them.... eg the comment on postgres one

[18:38] <ayleph> unfortunately i seem to be experiencing them more than others, with my big existing database

[18:38] -*- paroneayea nods

[18:39] <breton> mark them as critical

[18:39] <paroneayea> yes

[18:39] <ayleph> i believe i have, but i'll check

[18:39] <ayleph> actually, i was marking some as blockers

[18:39] <paroneayea> blockers is also good

[18:39] <breton> ugh.

[18:39] <paroneayea> ugh?

[18:39] <breton> it's bad that we don't fix critical/blocker bugs :(

[18:40] <paroneayea> yeah

[18:40] <paroneayea> so I'm going to do my best to dig in and help with that

[18:40] <ayleph> tsyesika_ and paroneayea have been trying to replicate the issues, but they haven't had luck

[18:40] <paroneayea> ayleph: I also didn't try with postgres

[18:40] <ayleph> and i've been working out of town since the end of 2015, so i haven't had much time to figure them out yet

[18:40] <paroneayea> I'm going to try with postgres today

[18:40] <-- hijkhgr left (Client Quit)

[18:40] <ayleph> (I'm on-site in an aircraft factory right now, slacking off on the job)

[18:40] <paroneayea> ayleph: oh, cool :)

[18:41] <paroneayea> (what are you doing there?)

[18:41] <paroneayea> I guess that can be discussed post meeting if you like :)

[18:41] <ayleph> haha, sure. maybe don't want that in the meeting notes :)

[18:41] <paroneayea> yeah

[18:41] <paroneayea> ok!

[18:41] <paroneayea> so is everyone ok with tentative date of the 22nd?

[18:41] <paroneayea> for the release?

[18:42] <paroneayea> I'll make working on these db issues my #1 priority.

[18:42] <breton> tes

[18:42] <breton> *yes

[18:42] <paroneayea> cool

[18:42] <ayleph> yep

[18:42] <paroneayea> onwards and upwards toward 0.9.0, then! :)

[18:42] <paroneayea> next topic?

[18:43] <paroneayea> #topic Path to 1.0

[18:43] <paroneayea> I didn't see any objections, but we can backtrack if there's still 0.9.0 stuff

[18:43] <paroneayea> so my goal is to get 1.0 out in the next couple of months, which is a tight timeline! This means that we need tsyesika_ really focused on federation totally

[18:44] <paroneayea> since we only have the funds to pay her till end of march especially ... :(

[18:44] --> pizzaiolo joined #mediagoblin

[18:44] <paroneayea> so we'll see

[18:44] <pizzaiolo> am I late to the meeting?

[18:44] <paroneayea> hi pizzaiolo, yes, but welcome!

[18:44] <paroneayea> we're talking about the work towards the 1.0 release

[18:44] <pizzaiolo> oh, cool!

[18:45] <pizzaiolo> any tl;dr of the meeting? :P

[18:45] <paroneayea> so, after 0.9.0 comes out, I think I'll be hunkering down and helping tsyesika_ with 1.0 as much as possible

[18:45] <paroneayea> pizzaiolo: https://wiki.mediagoblin.org/Meeting#Next_Meeting topics

[18:45] <chaosgoblin> Title: Meeting - GNU MediaGoblin Wiki (at wiki.mediagoblin.org)

[18:45] <pizzaiolo> coolio

[18:45] <paroneayea> I dunno, is there anything more to talk about on this subject? breton, ayleph ?

[18:45] <paroneayea> other than "1.0 is the initial federation release"

[18:46] <ayleph> anyone heard from sapienTech recently?

[18:46] <paroneayea> which is a pretty bold thing to say we'll hit in a couple of months, but the big db challenges are over at least...

[18:46] <pizzaiolo> paroneayea: anything on the activitypub protocol?

[18:46] <paroneayea> ayleph: ah.... I haven't

[18:46] <paroneayea> pizzaiolo: that's later in the meeting, see the topics

[18:46] <ayleph> curious what we'll need to do to get his app working with the 1.0 release, if things change.

[18:46] <paroneayea> ayleph: well

[18:46] <paroneayea> I did

[18:46] <paroneayea> actually

[18:46] <paroneayea> I blanked out for a second

[18:46] <paroneayea> we met up a few weeks ago!

[18:46] <paroneayea> sorry, my brain is not working

[18:46] <ayleph> oh cool!

[18:46] <pizzaiolo> okie

[18:46] <paroneayea> he showed me a live demo of the latest goblinoid release

[18:46] <paroneayea> it's looking *very* nice

[18:47] <paroneayea> and he's super interested in getting things updated to work with things as we do them

[18:47] <pizzaiolo> paroneayea: would love to see this go forward https://f-droid.org/forums/topic/goblinoid-mediagoblin-app/

[18:47] <pizzaiolo> :)

[18:47] <paroneayea> pizzaiolo: yes that would be really useful

[18:47] <paroneayea> what's the current status? I think they're still hung up on building kivy applications?

[18:48] <pizzaiolo> https://gitlab.com/fdroid/fdroiddata/merge_requests/1034

[18:48] --> j1mc joined #mediagoblin

[18:48] <chaosgoblin> Title: Add MediaGoblin to F-Droid repository (#1034) · Merge Requests · F-Droid / Data · GitLab (at gitlab.com)

[18:48] <ayleph> Last I heard, sapienTech had been trying to weeks or months to get onto F-Droid, but they weren't ready for kivy builds

[18:48] <ayleph> I had a little trouble building the app myself, so I resorted to having sapienTech send me binaries to host

[18:48] <paroneayea> https://gitlab.com/fdroid/fdroiddata/commit/dbb7e3f2ea73132454fd1f089412e507741fbd91 wait

[18:49] <chaosgoblin> "Title: Merge branch 'master' into 'master'\r (dbb7e3f2) \xc2\xb7 Commits \xc2\xb7 F-Droid / Data \xc2\xb7 GitLab (at gitlab.com)"

[18:49] <ayleph> I couldn't get the same filesize or hash as him on the binaries, so I'm not sure I had the right code.

[18:49] <paroneayea> did it get added???

[18:49] <paroneayea> a few days ago?

[18:50] <pizzaiolo> paroneayea: a quick search does not show it in F-Droid

[18:50] <paroneayea> pizzaiolo: it might be in git master

[18:50] <pizzaiolo> hmm

[18:50] <paroneayea> anyway, this is something to check up on post-meeting I think

[18:50] <paroneayea> we have a lot of topics still and only 10 mins left

[18:50] <paroneayea> so I'm taking initiative to blast ahead on topics

[18:51] <paroneayea> #topic Stripe retreat update

[18:51] <paroneayea> so the first week I was here I worked on getting ActivityPub to First Public Working Draft (it is now!)

[18:51] <paroneayea> and second week I spent at and preparing for FOSDEM mostly

[18:52] <paroneayea> and I've done some tickets and have updated my system to GuixSD (important, davexunit and I hope to do a live demo of mediagoblin deployed on guixsd at libreplanet next month)

[18:52] <pizzaiolo> woo!

[18:52] <paroneayea> and from here on out my main thing is "focus on mediagoblin code itself, while also trying to advance activitypub mostly on weekends"

[18:52] <paroneayea> so it's been very productive so far.

[18:52] <paroneayea> also FOSDEM was incredible

[18:53] <paroneayea> 80 people capacity in the guile/guix room and full almost the whole time

[18:53] <ayleph> I saw a little chatter in here during FOSDEM. sounds like a great time.

[18:53] <paroneayea> lots of other good things came out of it but we don't have time to go into it right now :)

[18:53] <paroneayea> yes

[18:53] <paroneayea> it was super great

[18:53] <paroneayea> anyway, I wanted to blast through that rundown

[18:53] <paroneayea> I'll be mostly head down on mediagoblin from here on out, excepting being at libreplanet and working on activitypub

[18:54] <paroneayea> I'm also going to blast forward on topic again unless there's a question

[18:54] <paroneayea> #topic ActivityPub update (related!)

[18:54] <paroneayea> https://identi.ca/mediagoblin/note/CkpUdPDaSryfybqolTkUSg says most of it all :)

[18:54] <chaosgoblin> Title: First Public Working Drafts of ActivityPub and Micropub published - Identi.ca (at identi.ca)

[18:54] <pizzaiolo> sorry, you mentioned stripe, is that stripe.js?

[18:54] <paroneayea> pizzaiolo: I'm at the Stripe Open Source Retreat

[18:55] <pizzaiolo> oh ok nvm

[18:55] <paroneayea> they're paying me to work on mediagoblin out of their office for a few months

[18:55] <pizzaiolo> that's incredible

[18:55] <paroneayea> pretty cool, like "coder in resident"

[18:55] <paroneayea> so, ActivityPub is at FPWD status, which means we have a real w3c url now

[18:55] <paroneayea> http://www.w3.org/TR/activitypub/

[18:55] <chaosgoblin> Title: ActivityPub (at www.w3.org)

[18:55] <paroneayea> I'm going to keep it short: there's a ton to do in working on the spec still

[18:56] <paroneayea> and right before libreplanet is the next w3c face to face

[18:56] <paroneayea> so it's a good thing stripe's office is so nice because between that and gmg I'll be pulling a lot of long nights here :)

[18:56] <paroneayea> sorry to textwall on these updates, they were mostly from-me updates

[18:56] <paroneayea> and I really wanted to get to this next topic

[18:56] <ayleph> wow, that's really cool seeing your name and tsyesika_'s name as editors on a w3c draft

[18:57] <paroneayea> ayleph: yeah :)

[18:57] <paroneayea> it's happeniningggggg

[18:57] <paroneayea> #topic GSOC ideas, and volunteers?

[18:57] <paroneayea> unless there are any questions on the last topic

[18:57] <paroneayea> but we only have a few minutes for this, so :)

[18:57] <paroneayea> we had a wiki link somewhere right?

[18:58] <paroneayea> https://wiki.mediagoblin.org/GSOC_2016

[18:58] <chaosgoblin> Title: GSOC 2016 - GNU MediaGoblin Wiki (at wiki.mediagoblin.org)

[18:58] <paroneayea> right now breton and I are listed as possible mentors

[18:58] <paroneayea> gnu still needs to be accepted to gsoc, but it probably will be

[18:58] <paroneayea> does anyone else want to mentor something? :)

[18:58] <paroneayea> or anything else to say?

[18:59] <ayleph> ooh, can i ask an unrelated question?

[18:59] <paroneayea> ayleph: go for ti

[18:59] <paroneayea> it

[18:59] <ayleph> do the last fundraiser rewards fit into the 1.0 schedule anywhere?

[18:59] <ayleph> i guess that was mostly federation anyway

[18:59] <ayleph> but also premium hosting?

[19:00] <paroneayea> ayleph: premium hosting is what motivated me to work on guixsd

[19:00] <ayleph> ah okay

[19:00] <paroneayea> because I realized there's no way I can manage to maintain servers in the current state of affairs

[19:00] <ayleph> yeah

[19:00] <paroneayea> so in a sense, the libreplanet demo

[19:00] <paroneayea> is on track for that :)

[19:00] <ayleph> cool

[19:00] <paroneayea> I haven't forgotten!

[19:00] <paroneayea> I was glad to hear breton thought I was mostly sane in my persual of that

[19:00] <paroneayea> I think we're all tired of the fear of server upgrades

[19:00] <ayleph> hehe

[19:01] --> marxistvegan joined #mediagoblin

[19:01] <-- marxistvegan left (Changing host)

[19:01] --> marxistvegan joined #mediagoblin

[19:01] <paroneayea> okay, I guess no gsoc update questions eh?

[19:01] <pizzaiolo> paroneayea: too bad I can't follow cwebber@identi.ca from nicolasmaia@quitter.se (hopefully it's something activitypub will fix)

[19:01] <breton> I wonder

[19:01] <paroneayea> pizzaiolo: I'm hoping activitypub will be integrated into statusnet

[19:02] <paroneayea> er

[19:02] <paroneayea> gnu social :)

[19:02] <breton> how do we advertise our GSoC

[19:02] <breton> because last year we didn't have many participants

[19:02] <paroneayea> breton: last year I also failed to promote it

[19:02] <paroneayea> this year we'll promote it a lot better, once it's clear we're accepted

[19:02] <paroneayea> it's easier because I'm fulltime on mediagoblin again right now

[19:03] <paroneayea> which means I can justify that time a bit better

[19:03] <breton> and I would like to have a situations with more proposals than tasks

[19:03] <ayleph> i think svetlana mentioned something about promoting it to students locally

[19:03] <paroneayea> ah right :)

[19:03] <paroneayea> svetlana: that'd be cool :)

[19:03] <paroneayea> so anything more on that, or are we done?

[19:04] <-- depate_ left (Ping timeout: 245 seconds)

[19:04] -*- breton thinks we're done

[19:04] <paroneayea> cool

[19:04] <paroneayea> how about an ascii art to seal the meeting?

[19:04] <paroneayea> *INCOMING ASCII*

[19:04] <paroneayea> * .-. .

[19:04] <paroneayea> ( ) . * *

[19:04] <paroneayea> _ '-' , , ,

[19:04] <paroneayea> (_) _ / \.--.\ . \\___// .

[19:05] <paroneayea> _ >(_) " ;" _ ; o o\ _

[19:05] <paroneayea> (_) ( / ) / '------' \

[19:05] <paroneayea> ;._/." . O () "._o_o_o_o."

[19:05] <paroneayea> * \.' . . *

[19:05] <paroneayea> .

[19:05] <paroneayea> HAVE A COSMIC HAPPY GNU YEAR 2016!

[19:05] <paroneayea> a bit late, that was my supporter ascii art for this year's fsf new years email :)

[19:05] <paroneayea> and we're done!

[19:05] <paroneayea> thank you all for coming, breton, ayleph, pizzaiolo!

[19:05] <paroneayea> #endmeeting

[19:05] <chaosgoblin> Meeting ended Sat Feb 6 18:05:37 2016 UTC. Minutes: http://mediagoblin.org/irclogs/irc_meeting-2016-02-06.html

[19:05] <chaosgoblin> Minutes (text): http://mediagoblin.org/irclogs/irc_meeting-2016-02-06.txt

[19:05] <chaosgoblin> Log: http://mediagoblin.org/irclogs/irc_meeting-2016-02-06.log.html

[19:05] <chaosgoblin> ######################
</nowiki>

20160206 Log

2016-02-07T10:45:08Z

Larjona: Created page with " <nowiki> [18:01] <chaosgoblin> ###################### [18:01] <chaosgoblin> Meeting started Sat Feb 6 17:01:22 2016 UTC. The chair is paroneayea. Information about the me..."

<nowiki>

[18:01] <chaosgoblin> ######################

[18:01] <chaosgoblin> Meeting started Sat Feb 6 17:01:22 2016 UTC. The chair is paroneayea. Information about the meeting agenda at http://wiki.mediagoblin.org/Meeting#Next_Meeting

[18:01] <chaosgoblin> Useful Commands: #action #agreed #info #idea #link #topic.

[18:01] <-- marxistvegan left (Ping timeout: 264 seconds)

[18:01] <paroneayea> hello, *!

[18:01] <paroneayea> (maybe I should do a qquick reminder of the meeting on the social networks?)

[18:01] <paroneayea> meanwhile, everyone say hi!

[18:02] <ayleph> o/

[18:04] <paroneayea> okay

[18:04] <paroneayea> whoo!

[18:04] -*- paroneayea pulls up the topics

[18:04] -*- paroneayea blasted out a reminder, also

[18:05] <paroneayea> okay

[18:05] <paroneayea> so first item is:

[18:05] <paroneayea> #topic Continuous integration / Commit Notifications

[18:06] <paroneayea> does someone want to step forward to lead this part of the meeting?

[18:06] <paroneayea> no? :) I can do it, though I might not be the best fit :)

[18:07] <paroneayea> ok

[18:07] -*- ayleph doesn't know anything about this one

[18:07] <paroneayea> so, we had continuous integration at one point, which was generously donated by asheesh, but asheesh isn't running that anymore, and that's okay because we're just glad he did it at one point!

[18:08] <paroneayea> so if we want to do it again, what do we do?

[18:08] <paroneayea> if someone wants to step forward to do this, and commit notifications, I'm like: "great"

[18:08] <paroneayea> though

[18:08] <paroneayea> I don't want to set up hosting for that until we have a more community-manage'able way of handling servers.

[18:09] <paroneayea> it's one more thing to manage, and clearly I'm not the best sysadmin, and simonft is busy already

[18:09] <ayleph> if someone were to mirror the mediagoblin project on github, would that somehow give us automatic travis-ci capabilities?

[18:09] <ayleph> less of a suggestion and more of a question

[18:10] <paroneayea> ayleph: it might, I dunno

[18:10] <paroneayea> ayleph: having an "official-ish" mirror could cause problems: my experience is that everyone starts to try to submit changes through github there

[18:10] <breton> what are the requirements for the server to host it?

[18:10] <ayleph> paroneayea: yeah, roger that

[18:11] <paroneayea> breton: we could do it on mediagoblin.org, it's not too expensive iirc, the main thing is that it's one more thing to maintain

[18:11] <breton> is there a one-... ./configure-make-makeinstall for it?

[18:11] <paroneayea> breton: jenkins is pretty standard in distros these days

[18:11] <paroneayea> but I think the config takes a bit of work

[18:11] <paroneayea> my personal opinion is: if someone wants to step forward to do this on their own server, great

[18:12] <paroneayea> and if not, let's wait until we have a way to do community sysadmin stuff, via some config managmeent system

[18:12] <paroneayea> otherwise I'm going to just have less time to work on mediagoblin itself and probably will do a bad job of running it

[18:13] -*- breton is a bad sysadmin

[18:14] <paroneayea> ok

[18:14] <paroneayea> everyone agree with that generally?

[18:14] <paroneayea> time to move on?

[18:14] <ayleph> sure, and sure

[18:14] <paroneayea> cool

[18:14] <paroneayea> so the next one is a pretty big one...

[18:14] <paroneayea> #topic Move sqlite to development-only? (no more migrations)

[18:15] <paroneayea> so, a few things:

[18:15] <breton> *(no more migrations for sqlite)

[18:15] <paroneayea> right

[18:15] <paroneayea> 1) this wouldn't happen until after 0.9.0 is out

[18:15] <paroneayea> 2) we probably need to raise this on-list, because it's a pretty big change and may affect people, and we might need some way to help people transition from sqlite -> postgres

[18:16] <paroneayea> but... I think there's good reason to do this

[18:16] <ayleph> for the record, what issues are prompting this?

[18:16] <paroneayea> one of the reasons the federation switchover took so long is that sqlite doesn't have proper alter table support

[18:16] <paroneayea> and we've been plagued by stuff like that for ages

[18:16] --> jamilgnu joined #mediagoblin

[18:16] <paroneayea> ayleph: mostly: migrations are insane to write with sqlite and break all the time and result in really bad code

[18:17] <ayleph> i don't suppose moving to alembic helps this then?

[18:17] <paroneayea> ayleph: I guess I don't know

[18:17] <paroneayea> we could wait and see

[18:18] <paroneayea> the alembic developers are fairly negative about sqlite themselves

[18:18] <paroneayea> for this very reason

[18:18] <paroneayea> I've talked to them about it

[18:18] <paroneayea> in fact the reason we initially went with sqlalchemy-migrate was because the alembic people at that point didn't have and were disinterested in sqlite

[18:18] <paroneayea> and well, now they have sqlite support

[18:19] <paroneayea> so

[18:19] <paroneayea> I guess maybe the answer is, we should look a bit more post-release at alembic

[18:19] <paroneayea> and how well it does

[18:19] <paroneayea> and raise this on list if we do decide to deprecate

[18:20] <paroneayea> ayleph: breton: to be clear, do either of you feel strongly on this one way or another?

[18:20] <ayleph> i'm for deprecating sqlite if it makes for a better product, but it would be nice if we could maybe support a sqlite branch with some bugfixes for a while, for those who won't/can't migrate

[18:20] <paroneayea> ayleph: yeah, maybe it could be a slow deprecation

[18:20] <paroneayea> or

[18:20] <paroneayea> support the branch

[18:20] <-- Spacedogg_iie left (Ping timeout: 264 seconds)

[18:20] --> Spacedog_ie joined a #mediagoblin

[18:20] <paroneayea> 0.9.0 supported with fixes for a bit, I dunno

[18:20] <ayleph> you mentioned looking into a migration tool, which i think would be wise

[18:20] <paroneayea> we've never done that before but I guess a LTS-ish branch in this case makes sense

[18:21] <paroneayea> ayleph: yes I think so

[18:21] <breton> ayleph: the problem is not in supporting running on sqlite

[18:22] <breton> but in upgrades

[18:22] <breton> supporting sqlite branch means that we shall have to write migrations for it

[18:22] <breton> which is our pain point

[18:23] <ayleph> yeah, understood. but if mainline gets security fixes after a migration, maybe we could just cherry-pick the security fixes back to the sqlite branch, and not the migrations.

[18:23] <ayleph> guess it depends on whether migrations are involved/required for fixes.

[18:23] <breton> if we don't cherry-pick the migrations, the databses will differ in sqlite and non-sqlite cases

[18:23] <paroneayea> supporting security updates for a while that are easy to support would be okay

[18:23] <paroneayea> the sqlite branch would probably kind of bitrot away

[18:23] <paroneayea> and I think that would be the goal

[18:24] <breton> from my point of view

[18:24] <ayleph> you mentioned having sqlite for development still

[18:24] <breton> oh, will describe my pov later

[18:24] <ayleph> does that mean that we'd still support rolling out a new mediagoblin instance with sqlite for testing, but it just wouldn't received migration updates?

[18:24] <breton> yep

[18:24] <ayleph> i think that's okay

[18:25] <breton> to run a migration, you'll have to rm your mediagoblin.db

[18:25] <breton> so

[18:25] <breton> from my point of view

[18:26] <breton> sqlite is the simplest thing for the user

[18:26] <breton> postresql is the most complex

[18:26] <breton> because by default it requires signing in with another user with su

[18:27] <breton> and it took me a lot of time to figure out how to manage it

[18:27] <breton> if we drop sqlite, I think we should support mysql

[18:27] <ayleph> that sounds like a whole lot of work :)

[18:27] <paroneayea> ahhhhh

[18:27] <paroneayea> mysql would add a whole different kind of work

[18:28] <ayleph> the more i use postgresql, the more i prefer it to mysql

[18:28] <breton> which is more popular and has more unofficial docs, like blogposts

[18:28] <breton> yeah, yeah, we all know that postgresql is better

[18:28] <paroneayea> yeah I think mysql is pretty much "living in the past"

[18:28] <paroneayea> ok, well

[18:28] <paroneayea> I'm going to declare this conversation a "tentative maybe"

[18:29] <paroneayea> and we'll explore it after the next release

[18:29] <paroneayea> to see for feasibility

[18:29] <ayleph> i like the general direction of moving toward postgresql as default

[18:29] <ayleph> perhaps we could scriptify the postgresql commands to make it easier for users

[18:29] --> hijkhgr joined #mediagoblin

[18:29] <paroneayea> ayleph: that's a good idea

[18:29] <paroneayea> ok!

[18:29] <paroneayea> how about next topic? :)

[18:29] <breton> (btw, in openstack we DO NOT support postresql)

[18:30] <breton> (like, at all)

[18:30] <paroneayea> breton: what does that mean?

[18:30] <breton> paroneayea: no one tests, no one runs

[18:30] <breton> paroneayea: no installator/manager sets up posgresql or has an option for that

[18:31] <paroneayea> hm

[18:31] <paroneayea> well

[18:31] <paroneayea> I still say we move on :)

[18:31] <paroneayea> I think we've drained this topic :)

[18:32] <paroneayea> and we'll see post 0.9.0

[18:32] <paroneayea> speaking of!

[18:32] <paroneayea> #topic Upcoming 0.9.0 release

[18:32] <paroneayea> so, I said I was going to freeze yesterday and I didn't, because I packaged the last piece I needed to go fulltime on guixsd as my host distro yesterday ;)

[18:32] <paroneayea> but

[18:32] <paroneayea> I'll freeze today.

[18:33] <paroneayea> any and all "make mediagoblin work on python 3" bugs are fair game during freeze though

[18:33] <paroneayea> as bugs usually are, but *especially* those are, even if they look like features :)

[18:33] <paroneayea> I think python 3 as a first class citizen is going to be a major feature of 0.9.0

[18:33] <ayleph> we're not dropping py2 yet, are we?

[18:33] <paroneayea> nope

[18:34] <paroneayea> py2.7 will be around for some time

[18:34] <ayleph> okay cool

[18:34] <paroneayea> we're just saying "yes, we finally support python 3 as an option"

[18:34] <-- hijkhgr left #mediagoblin ("Leaving")

[18:34] <paroneayea> freedeb has suggested "The Three Goblineers" as a release name

[18:34] <paroneayea> as a play on The Three Musketeers

[18:34] <paroneayea> I like it

[18:34] <ayleph> bd

[18:35] <paroneayea> :)

[18:35] --> hijkhgr joined #mediagoblin

[18:35] <paroneayea> so I guess we should aim for a date. We usually aim for a week and then don't hit it ;)

[18:35] <ayleph> i don't think a week sounds realistic at all, given how many tickets are associated with 0.8.2 and 0.9.0

[18:36] <ayleph> 19 at the moment

[18:36] <paroneayea> how about the 22nd?

[18:36] <breton> given that 0.9.0 is mainly a bugfixing release

[18:36] <paroneayea> well right, there are some bugs there we can move over, because we're moving into bugs-only mode

[18:36] <paroneayea> er, some features

[18:36] <paroneayea> we can roll the features over into next release

[18:37] <breton> I think that we can move bugs to the next release too

[18:37] <-- hijkhgr left (Quit: Leaving)

[18:37] --> hijkhgr joined #mediagoblin

[18:37] <ayleph> there are still some potential big issues with the federation migrations that have been ongoing.

[18:37] <ayleph> things that cause server crashes when you click on links or load pages

[18:38] <paroneayea> ayleph: yes I'm concerned about those...

[18:38] <paroneayea> ayleph: I'll try to help with them.... eg the comment on postgres one

[18:38] <ayleph> unfortunately i seem to be experiencing them more than others, with my big existing database

[18:38] -*- paroneayea nods

[18:39] <breton> mark them as critical

[18:39] <paroneayea> yes

[18:39] <ayleph> i believe i have, but i'll check

[18:39] <ayleph> actually, i was marking some as blockers

[18:39] <paroneayea> blockers is also good

[18:39] <breton> ugh.

[18:39] <paroneayea> ugh?

[18:39] <breton> it's bad that we don't fix critical/blocker bugs :(

[18:40] <paroneayea> yeah

[18:40] <paroneayea> so I'm going to do my best to dig in and help with that

[18:40] <ayleph> tsyesika_ and paroneayea have been trying to replicate the issues, but they haven't had luck

[18:40] <paroneayea> ayleph: I also didn't try with postgres

[18:40] <ayleph> and i've been working out of town since the end of 2015, so i haven't had much time to figure them out yet

[18:40] <paroneayea> I'm going to try with postgres today

[18:40] <-- hijkhgr left (Client Quit)

[18:40] <ayleph> (I'm on-site in an aircraft factory right now, slacking off on the job)

[18:40] <paroneayea> ayleph: oh, cool :)

[18:41] <paroneayea> (what are you doing there?)

[18:41] <paroneayea> I guess that can be discussed post meeting if you like :)

[18:41] <ayleph> haha, sure. maybe don't want that in the meeting notes :)

[18:41] <paroneayea> yeah

[18:41] <paroneayea> ok!

[18:41] <paroneayea> so is everyone ok with tentative date of the 22nd?

[18:41] <paroneayea> for the release?

[18:42] <paroneayea> I'll make working on these db issues my #1 priority.

[18:42] <breton> tes

[18:42] <breton> *yes

[18:42] <paroneayea> cool

[18:42] <ayleph> yep

[18:42] <paroneayea> onwards and upwards toward 0.9.0, then! :)

[18:42] <paroneayea> next topic?

[18:43] <paroneayea> #topic Path to 1.0

[18:43] <paroneayea> I didn't see any objections, but we can backtrack if there's still 0.9.0 stuff

[18:43] <paroneayea> so my goal is to get 1.0 out in the next couple of months, which is a tight timeline! This means that we need tsyesika_ really focused on federation totally

[18:44] <paroneayea> since we only have the funds to pay her till end of march especially ... :(

[18:44] --> pizzaiolo joined #mediagoblin

[18:44] <paroneayea> so we'll see

[18:44] <pizzaiolo> am I late to the meeting?

[18:44] <paroneayea> hi pizzaiolo, yes, but welcome!

[18:44] <paroneayea> we're talking about the work towards the 1.0 release

[18:44] <pizzaiolo> oh, cool!

[18:45] <pizzaiolo> any tl;dr of the meeting? :P

[18:45] <paroneayea> so, after 0.9.0 comes out, I think I'll be hunkering down and helping tsyesika_ with 1.0 as much as possible

[18:45] <paroneayea> pizzaiolo: https://wiki.mediagoblin.org/Meeting#Next_Meeting topics

[18:45] <chaosgoblin> Title: Meeting - GNU MediaGoblin Wiki (at wiki.mediagoblin.org)

[18:45] <pizzaiolo> coolio

[18:45] <paroneayea> I dunno, is there anything more to talk about on this subject? breton, ayleph ?

[18:45] <paroneayea> other than "1.0 is the initial federation release"

[18:46] <ayleph> anyone heard from sapienTech recently?

[18:46] <paroneayea> which is a pretty bold thing to say we'll hit in a couple of months, but the big db challenges are over at least...

[18:46] <pizzaiolo> paroneayea: anything on the activitypub protocol?

[18:46] <paroneayea> ayleph: ah.... I haven't

[18:46] <paroneayea> pizzaiolo: that's later in the meeting, see the topics

[18:46] <ayleph> curious what we'll need to do to get his app working with the 1.0 release, if things change.

[18:46] <paroneayea> ayleph: well

[18:46] <paroneayea> I did

[18:46] <paroneayea> actually

[18:46] <paroneayea> I blanked out for a second

[18:46] <paroneayea> we met up a few weeks ago!

[18:46] <paroneayea> sorry, my brain is not working

[18:46] <ayleph> oh cool!

[18:46] <pizzaiolo> okie

[18:46] <paroneayea> he showed me a live demo of the latest goblinoid release

[18:46] <paroneayea> it's looking *very* nice

[18:47] <paroneayea> and he's super interested in getting things updated to work with things as we do them

[18:47] <pizzaiolo> paroneayea: would love to see this go forward https://f-droid.org/forums/topic/goblinoid-mediagoblin-app/

[18:47] <pizzaiolo> :)

[18:47] <paroneayea> pizzaiolo: yes that would be really useful

[18:47] <paroneayea> what's the current status? I think they're still hung up on building kivy applications?

[18:48] <pizzaiolo> https://gitlab.com/fdroid/fdroiddata/merge_requests/1034

[18:48] --> j1mc joined #mediagoblin

[18:48] <chaosgoblin> Title: Add MediaGoblin to F-Droid repository (#1034) · Merge Requests · F-Droid / Data · GitLab (at gitlab.com)

[18:48] <ayleph> Last I heard, sapienTech had been trying to weeks or months to get onto F-Droid, but they weren't ready for kivy builds

[18:48] <ayleph> I had a little trouble building the app myself, so I resorted to having sapienTech send me binaries to host

[18:48] <paroneayea> https://gitlab.com/fdroid/fdroiddata/commit/dbb7e3f2ea73132454fd1f089412e507741fbd91 wait

[18:49] <chaosgoblin> "Title: Merge branch 'master' into 'master'\r (dbb7e3f2) \xc2\xb7 Commits \xc2\xb7 F-Droid / Data \xc2\xb7 GitLab (at gitlab.com)"

[18:49] <ayleph> I couldn't get the same filesize or hash as him on the binaries, so I'm not sure I had the right code.

[18:49] <paroneayea> did it get added???

[18:49] <paroneayea> a few days ago?

[18:50] <pizzaiolo> paroneayea: a quick search does not show it in F-Droid

[18:50] <paroneayea> pizzaiolo: it might be in git master

[18:50] <pizzaiolo> hmm

[18:50] <paroneayea> anyway, this is something to check up on post-meeting I think

[18:50] <paroneayea> we have a lot of topics still and only 10 mins left

[18:50] <paroneayea> so I'm taking initiative to blast ahead on topics

[18:51] <paroneayea> #topic Stripe retreat update

[18:51] <paroneayea> so the first week I was here I worked on getting ActivityPub to First Public Working Draft (it is now!)

[18:51] <paroneayea> and second week I spent at and preparing for FOSDEM mostly

[18:52] <paroneayea> and I've done some tickets and have updated my system to GuixSD (important, davexunit and I hope to do a live demo of mediagoblin deployed on guixsd at libreplanet next month)

[18:52] <pizzaiolo> woo!

[18:52] <paroneayea> and from here on out my main thing is "focus on mediagoblin code itself, while also trying to advance activitypub mostly on weekends"

[18:52] <paroneayea> so it's been very productive so far.

[18:52] <paroneayea> also FOSDEM was incredible

[18:53] <paroneayea> 80 people capacity in the guile/guix room and full almost the whole time

[18:53] <ayleph> I saw a little chatter in here during FOSDEM. sounds like a great time.

[18:53] <paroneayea> lots of other good things came out of it but we don't have time to go into it right now :)

[18:53] <paroneayea> yes

[18:53] <paroneayea> it was super great

[18:53] <paroneayea> anyway, I wanted to blast through that rundown

[18:53] <paroneayea> I'll be mostly head down on mediagoblin from here on out, excepting being at libreplanet and working on activitypub

[18:54] <paroneayea> I'm also going to blast forward on topic again unless there's a question

[18:54] <paroneayea> #topic ActivityPub update (related!)

[18:54] <paroneayea> https://identi.ca/mediagoblin/note/CkpUdPDaSryfybqolTkUSg says most of it all :)

[18:54] <chaosgoblin> Title: First Public Working Drafts of ActivityPub and Micropub published - Identi.ca (at identi.ca)

[18:54] <pizzaiolo> sorry, you mentioned stripe, is that stripe.js?

[18:54] <paroneayea> pizzaiolo: I'm at the Stripe Open Source Retreat

[18:55] <pizzaiolo> oh ok nvm

[18:55] <paroneayea> they're paying me to work on mediagoblin out of their office for a few months

[18:55] <pizzaiolo> that's incredible

[18:55] <paroneayea> pretty cool, like "coder in resident"

[18:55] <paroneayea> so, ActivityPub is at FPWD status, which means we have a real w3c url now

[18:55] <paroneayea> http://www.w3.org/TR/activitypub/

[18:55] <chaosgoblin> Title: ActivityPub (at www.w3.org)

[18:55] <paroneayea> I'm going to keep it short: there's a ton to do in working on the spec still

[18:56] <paroneayea> and right before libreplanet is the next w3c face to face

[18:56] <paroneayea> so it's a good thing stripe's office is so nice because between that and gmg I'll be pulling a lot of long nights here :)

[18:56] <paroneayea> sorry to textwall on these updates, they were mostly from-me updates

[18:56] <paroneayea> and I really wanted to get to this next topic

[18:56] <ayleph> wow, that's really cool seeing your name and tsyesika_'s name as editors on a w3c draft

[18:57] <paroneayea> ayleph: yeah :)

[18:57] <paroneayea> it's happeniningggggg

[18:57] <paroneayea> #topic GSOC ideas, and volunteers?

[18:57] <paroneayea> unless there are any questions on the last topic

[18:57] <paroneayea> but we only have a few minutes for this, so :)

[18:57] <paroneayea> we had a wiki link somewhere right?

[18:58] <paroneayea> https://wiki.mediagoblin.org/GSOC_2016

[18:58] <chaosgoblin> Title: GSOC 2016 - GNU MediaGoblin Wiki (at wiki.mediagoblin.org)

[18:58] <paroneayea> right now breton and I are listed as possible mentors

[18:58] <paroneayea> gnu still needs to be accepted to gsoc, but it probably will be

[18:58] <paroneayea> does anyone else want to mentor something? :)

[18:58] <paroneayea> or anything else to say?

[18:59] <ayleph> ooh, can i ask an unrelated question?

[18:59] <paroneayea> ayleph: go for ti

[18:59] <paroneayea> it

[18:59] <ayleph> do the last fundraiser rewards fit into the 1.0 schedule anywhere?

[18:59] <ayleph> i guess that was mostly federation anyway

[18:59] <ayleph> but also premium hosting?

[19:00] <paroneayea> ayleph: premium hosting is what motivated me to work on guixsd

[19:00] <ayleph> ah okay

[19:00] <paroneayea> because I realized there's no way I can manage to maintain servers in the current state of affairs

[19:00] <ayleph> yeah

[19:00] <paroneayea> so in a sense, the libreplanet demo

[19:00] <paroneayea> is on track for that :)

[19:00] <ayleph> cool

[19:00] <paroneayea> I haven't forgotten!

[19:00] <paroneayea> I was glad to hear breton thought I was mostly sane in my persual of that

[19:00] <paroneayea> I think we're all tired of the fear of server upgrades

[19:00] <ayleph> hehe

[19:01] --> marxistvegan joined #mediagoblin

[19:01] <-- marxistvegan left (Changing host)

[19:01] --> marxistvegan joined #mediagoblin

[19:01] <paroneayea> okay, I guess no gsoc update questions eh?

[19:01] <pizzaiolo> paroneayea: too bad I can't follow cwebber@identi.ca from nicolasmaia@quitter.se (hopefully it's something activitypub will fix)

[19:01] <breton> I wonder

[19:01] <paroneayea> pizzaiolo: I'm hoping activitypub will be integrated into statusnet

[19:02] <paroneayea> er

[19:02] <paroneayea> gnu social :)

[19:02] <breton> how do we advertise our GSoC

[19:02] <breton> because last year we didn't have many participants

[19:02] <paroneayea> breton: last year I also failed to promote it

[19:02] <paroneayea> this year we'll promote it a lot better, once it's clear we're accepted

[19:02] <paroneayea> it's easier because I'm fulltime on mediagoblin again right now

[19:03] <paroneayea> which means I can justify that time a bit better

[19:03] <breton> and I would like to have a situations with more proposals than tasks

[19:03] <ayleph> i think svetlana mentioned something about promoting it to students locally

[19:03] <paroneayea> ah right :)

[19:03] <paroneayea> svetlana: that'd be cool :)

[19:03] <paroneayea> so anything more on that, or are we done?

[19:04] <-- depate_ left (Ping timeout: 245 seconds)

[19:04] -*- breton thinks we're done

[19:04] <paroneayea> cool

[19:04] <paroneayea> how about an ascii art to seal the meeting?

[19:04] <paroneayea> *INCOMING ASCII*

[19:04] <paroneayea> * .-. .

[19:04] <paroneayea> ( ) . * *

[19:04] <paroneayea> _ '-' , , ,

[19:04] <paroneayea> (_) _ / \.--.\ . \\___// .

[19:05] <paroneayea> _ >(_) " ;" _ ; o o\ _

[19:05] <paroneayea> (_) ( / ) / '------' \

[19:05] <paroneayea> ;._/." . O () "._o_o_o_o."

[19:05] <paroneayea> * \.' . . *

[19:05] <paroneayea> .

[19:05] <paroneayea> HAVE A COSMIC HAPPY GNU YEAR 2016!

[19:05] <paroneayea> a bit late, that was my supporter ascii art for this year's fsf new years email :)

[19:05] <paroneayea> and we're done!

[19:05] <paroneayea> thank you all for coming, breton, ayleph, pizzaiolo!

[19:05] <paroneayea> #endmeeting

[19:05] <chaosgoblin> Meeting ended Sat Feb 6 18:05:37 2016 UTC. Minutes: http://mediagoblin.org/irclogs/irc_meeting-2016-02-06.html

[19:05] <chaosgoblin> Minutes (text): http://mediagoblin.org/irclogs/irc_meeting-2016-02-06.txt

[19:05] <chaosgoblin> Log: http://mediagoblin.org/irclogs/irc_meeting-2016-02-06.log.html

[19:05] <chaosgoblin> ######################
</nowiki>

Meeting

2016-02-07T10:43:43Z

Larjona: /* Past Meetings */

== 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. [http://mediagoblin.org/irclogs/ Logs for past meetings.]

== Next Meeting ==

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

=== March 5, 2016, 9:00AM Pacific Time, 17:00 UTC ===

== Past Meetings ==

=== 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?

[[20160205_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]

Meeting

2016-02-07T10:43:03Z

Larjona: /* Next Meeting */

== 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. [http://mediagoblin.org/irclogs/ Logs for past meetings.]

== Next Meeting ==

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

=== March 5, 2016, 9:00AM Pacific Time, 17:00 UTC ===

== Past Meetings ==

=== 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]

20160102 Log

2016-01-26T18:22:56Z

Larjona:

<nowiki>
[18:01] <chaosgoblin> ######################

[18:01] <chaosgoblin> Meeting started Sat Jan 2 17:01:00 2016 UTC. The chair is breton. Information about the meeting agenda at http://wiki.mediagoblin.org/Meeting#Next_Meeting

[18:01] <chaosgoblin> Useful Commands: #action #agreed #info #idea #link #topic.

[18:01] <breton> Oh

[18:01] <breton> Topics:

[18:01] <breton> - 0.9.0

[18:01] <breton> - FOSDEM

[18:02] <R13ose> - 0.8.2

[18:04] <breton> OK then!

[18:04] <R13ose> Is mediagoblin down?

[18:04] --> shymega has joined #mediagoblin

[18:04] <breton> wow

[18:04] <breton> seems like ti

[18:05] <breton> looks like the whole server is down

[18:07] <breton> it's NY now, so I guess when everyone wakes up after it they will fix it

[18:08] <breton> anyway

[18:08] <breton> - 0.9.0

[18:08] <breton> #topic 0.9.0

[18:08] <breton> I've pushed some code with the new admin media panel

[18:09] <R13ose> I remember talk to chris about making Python 3 one of the big things that gets fixed in 0.9.0 as there are a lot of tickets related to that.

[18:09] <breton> the code from old gsoc and was finally rebased

[18:10] -*- breton shrugs

[18:10] <R13ose> which old gsoc?

[18:10] <breton> 2014 one

[18:10] <breton> I could takle py3

[18:10] <breton> anyway, I have vacation till the 10th of January

[18:11] <breton> and I expect to code something for MG

[18:11] <breton> I didn't plan py3 though

[18:11] <breton> maybe not in 0.9.0, maybe in 1.0

[18:11] <R13ose> Is there a timeline for release of 0.9.0?

[18:12] <breton> I'd like to release it at FOSDEM

[18:12] <breton> (which I plan to attend, though don't have visa yet)

[18:12] <breton> it's in ~28 days from now

[18:13] <R13ose> Maybe making Thursday ticket days bigger would help get that out and move py3 closer too.

[18:13] <-- shymega left (Quit: My uptime! The goggles do nothing!)

[18:14] <breton> or make thursday ticket days py3-tickets days

[18:14] <breton> (for some time)

[18:15] <R13ose> that could work better

[18:15] <breton> lets have it next Thursday then!

[18:15] <R13ose> I will get everyone who wants my help with tickets to focus on py3 tickets

[18:16] --> shymega has joined #mediagoblin

[18:17] <breton> awesome

[18:17] <breton> lets get to the next topic

[18:17] <breton> #topic FOSDEM

[18:18] <breton> I just wanted to tell that I still don't have visa for Belgium and still not sure that I'm going

[18:18] <breton> the application is in the embassy though

[18:18] <breton> not sure if Chris and Jessica need visas

[18:19] <R13ose> What is happening there?

[18:19] <breton> I don't know. People talk I guess.

[18:20] <R13ose> Can you followup with Chris and Jessica about FOSDEM?

[18:20] <breton> when I get the visa, yes

[18:21] <ersi> (Jessica don't need a visa by the way)

[18:21] <-- shymega left (Quit: My uptime! The goggles do nothing!)

[18:22] <breton> OK, and the next topic

[18:22] <breton> #topic 0.8.2

[18:23] <breton> I don't really know what to tell about it

[18:23] <breton> have all fixes that were before that security bug got into 0.8.1?

[18:23] <R13ose> not sure what you are asking but 0.8.1 was released.

[18:24] <R13ose> Well from the tickets I looked at before, most of the 0.8.2 ones left are Jessica's.

[18:26] <R13ose> shouldn't 0.8.2 be out before 0.9.0?

[18:27] <breton> nope

[18:27] <breton> they are independent I think

[18:29] <breton> from what I see

[18:29] <breton> the changes between 0.8.0 and that security fix are in 0.8.1 now

[18:29] <breton> my guess is that it makes 0.8.2 low priority

[18:31] <R13ose> well, what about Jessica's tickets? Don't they move into 0.9.0 after they are fixed in 0.8.2?

[18:31] <breton> after they are fixed in 0.8.2 they will automatically get to 0.9.0

[18:32] <breton> (if 0.9.0 is not released)

[18:32] <breton> if 0.9.0 is released... I am not sure that we will support 0.8.x any more

[18:32] <larjona> oh, late to the meeting

[18:32] -*- larjona will read backlog now and try to catch up

[18:34] <R13ose> well, I think my timeline should be 0.8.2 then 0.9.0 but if people higher in the project see this differently that is okay.

[18:36] <breton> I think it's not "higher in the project" thing :) I think it's just who wants to work on these releases

[18:37] --> titoko has joined #mediagoblin

[18:37] <larjona> Well, I suppose the question is if tsyesika can get the fixes for 0.8.2 and release, before FOSDEM

[18:38] <R13ose> Jessica has said that the tickets will be worked on soon but she is busy busy.

[18:41] <breton> OK then!

[18:41] <breton> thanks everyone for attending

[18:41] <breton> #endmeeting

[18:41] <chaosgoblin> Meeting ended Sat Jan 2 17:41:40 2016 UTC. Minutes: http://mediagoblin.org/irclogs/irc_meeting-2016-01-02.html

[18:41] <chaosgoblin> Minutes (text): http://mediagoblin.org/irclogs/irc_meeting-2016-01-02.txt

[18:41] <chaosgoblin> Log: http://mediagoblin.org/irclogs/irc_meeting-2016-01-02.log.html

[18:41] <chaosgoblin> ######################

</nowiki>

20160102 Log

2016-01-26T18:21:40Z

Larjona:

20160102 Log

2016-01-26T18:20:54Z

Larjona: add log

<nowiki>

[18:01] <chaosgoblin> ######################
[18:01] <chaosgoblin> Meeting started Sat Jan 2 17:01:00 2016 UTC. The chair is breton. Information about the meeting agenda at http://wiki.mediagoblin.org/Meeting#Next_Meeting
[18:01] <chaosgoblin> Useful Commands: #action #agreed #info #idea #link #topic.
[18:01] <breton> Oh
[18:01] <breton> Topics:
[18:01] <breton> - 0.9.0
[18:01] <breton> - FOSDEM
[18:02] <R13ose> - 0.8.2
[18:04] <breton> OK then!
[18:04] <R13ose> Is mediagoblin down?
[18:04] --> shymega has joined #mediagoblin
[18:04] <breton> wow
[18:04] <breton> seems like ti
[18:05] <breton> looks like the whole server is down
[18:07] <breton> it's NY now, so I guess when everyone wakes up after it they will fix it
[18:08] <breton> anyway
[18:08] <breton> - 0.9.0
[18:08] <breton> #topic 0.9.0
[18:08] <breton> I've pushed some code with the new admin media panel
[18:09] <R13ose> I remember talk to chris about making Python 3 one of the big things that gets fixed in 0.9.0 as there are a lot of tickets related to that.
[18:09] <breton> the code from old gsoc and was finally rebased
[18:10] -*- breton shrugs
[18:10] <R13ose> which old gsoc?
[18:10] <breton> 2014 one
[18:10] <breton> I could takle py3
[18:10] <breton> anyway, I have vacation till the 10th of January
[18:11] <breton> and I expect to code something for MG
[18:11] <breton> I didn't plan py3 though
[18:11] <breton> maybe not in 0.9.0, maybe in 1.0
[18:11] <R13ose> Is there a timeline for release of 0.9.0?
[18:12] <breton> I'd like to release it at FOSDEM
[18:12] <breton> (which I plan to attend, though don't have visa yet)
[18:12] <breton> it's in ~28 days from now
[18:13] <R13ose> Maybe making Thursday ticket days bigger would help get that out and move py3 closer too.
[18:13] <-- shymega left (Quit: My uptime! The goggles do nothing!)
[18:14] <breton> or make thursday ticket days py3-tickets days
[18:14] <breton> (for some time)
[18:15] <R13ose> that could work better
[18:15] <breton> lets have it next Thursday then!
[18:15] <R13ose> I will get everyone who wants my help with tickets to focus on py3 tickets
[18:16] --> shymega has joined #mediagoblin
[18:17] <breton> awesome
[18:17] <breton> lets get to the next topic
[18:17] <breton> #topic FOSDEM
[18:18] <breton> I just wanted to tell that I still don't have visa for Belgium and still not sure that I'm going
[18:18] <breton> the application is in the embassy though
[18:18] <breton> not sure if Chris and Jessica need visas
[18:19] <R13ose> What is happening there?
[18:19] <breton> I don't know. People talk I guess.
[18:20] <R13ose> Can you followup with Chris and Jessica about FOSDEM?
[18:20] <breton> when I get the visa, yes
[18:21] <ersi> (Jessica don't need a visa by the way)
[18:21] <-- shymega left (Quit: My uptime! The goggles do nothing!)
[18:22] <breton> OK, and the next topic
[18:22] <breton> #topic 0.8.2
[18:23] <breton> I don't really know what to tell about it
[18:23] <breton> have all fixes that were before that security bug got into 0.8.1?
[18:23] <R13ose> not sure what you are asking but 0.8.1 was released.
[18:24] <R13ose> Well from the tickets I looked at before, most of the 0.8.2 ones left are Jessica's.
[18:26] <R13ose> shouldn't 0.8.2 be out before 0.9.0?
[18:27] <breton> nope
[18:27] <breton> they are independent I think
[18:29] <breton> from what I see
[18:29] <breton> the changes between 0.8.0 and that security fix are in 0.8.1 now
[18:29] <breton> my guess is that it makes 0.8.2 low priority
[18:31] <R13ose> well, what about Jessica's tickets? Don't they move into 0.9.0 after they are fixed in 0.8.2?
[18:31] <breton> after they are fixed in 0.8.2 they will automatically get to 0.9.0
[18:32] <breton> (if 0.9.0 is not released)
[18:32] <breton> if 0.9.0 is released... I am not sure that we will support 0.8.x any more
[18:32] <larjona> oh, late to the meeting
[18:32] -*- larjona will read backlog now and try to catch up
[18:34] <R13ose> well, I think my timeline should be 0.8.2 then 0.9.0 but if people higher in the project see this differently that is okay.
[18:36] <breton> I think it's not "higher in the project" thing :) I think it's just who wants to work on these releases
[18:37] --> titoko has joined #mediagoblin
[18:37] <larjona> Well, I suppose the question is if tsyesika can get the fixes for 0.8.2 and release, before FOSDEM
[18:38] <R13ose> Jessica has said that the tickets will be worked on soon but she is busy busy.
[18:41] <breton> OK then!
[18:41] <breton> thanks everyone for attending
[18:41] <breton> #endmeeting
[18:41] <chaosgoblin> Meeting ended Sat Jan 2 17:41:40 2016 UTC. Minutes: http://mediagoblin.org/irclogs/irc_meeting-2016-01-02.html
[18:41] <chaosgoblin> Minutes (text): http://mediagoblin.org/irclogs/irc_meeting-2016-01-02.txt
[18:41] <chaosgoblin> Log: http://mediagoblin.org/irclogs/irc_meeting-2016-01-02.log.html
[18:41] <chaosgoblin> ######################

</nowiki>

Meeting

2016-01-26T18:19:10Z

Larjona: /* January 2, 2016, 9:00AM Pacific Time, 17:00 UTC */

== 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. [http://mediagoblin.org/irclogs/ Logs for past meetings.]

== Next Meeting ==

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

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

* Continuous integration / Commit Notifications

== Past Meetings ==

=== 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]

Meeting

2016-01-26T18:17:08Z

Larjona: /* Past Meetings */ Add 2016/01/02 meeting

== 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. [http://mediagoblin.org/irclogs/ Logs for past meetings.]

== Next Meeting ==

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

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

* Continuous integration / Commit Notifications

== Past Meetings ==

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

* 0.9.0
* FOSDEM
* 0.8.2
[[File:20160102.log.txt]]

=== 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]

CommunityGovernance

2015-06-06T18:05:42Z

Larjona: /* MediaGoblin issue tracker */

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

== MediaGoblin website ==

* People with permissions to handle website outages

* Publish pages (for example new releases)

== MediaGoblin wiki ==

* Wiki administration

== MediaGoblin issue tracker ==

* Help triaging bugs:

* People with permissions to create accounts in trac

* People with permissions to delete users/issues/comments in trac

* Volunteers for spam cleaning: LArjona

== 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.

== MediaGoblin IRC channel and mailing list ==

* Change IRC topic, channel operators

CommunityGovernance

2015-06-06T18:04:33Z

Larjona: /* MediaGoblin translation platform */

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

== MediaGoblin website ==

* People with permissions to handle website outages

* Publish pages (for example new releases)

== MediaGoblin wiki ==

* Wiki administration

== MediaGoblin issue tracker ==

* Help triaging bugs:

* People with permissions to create accounts in trac

* People with permissions to delete users/issues/comments in trac (spam cleaning)

== 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.

== MediaGoblin IRC channel and mailing list ==

* Change IRC topic, channel operators

CommunityGovernance

2015-06-06T17:56:10Z

Larjona: Initial draft

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

== MediaGoblin website ==

* People with permissions to handle website outages

* Publish pages (for example new releases)

== MediaGoblin wiki ==

* Wiki administration

== MediaGoblin issue tracker ==

* Help triaging bugs:

* People with permissions to create accounts in trac

* People with permissions to delete users/issues/comments in trac (spam cleaning)

== MediaGoblin translation platform ==

* If there is need of manual import/export files between Pootle and the MediaGoblin codebase, who can help on that

== MediaGoblin IRC channel and mailing list ==

* Change IRC topic, channel operators

Translations

2015-02-12T12:03:26Z

Larjona: /* Troubleshooting */

= For translators =

<pre style="color: red;">This section has changed recently, since now Mediagoblin lives on Pootle.
Here you can find the basic information for translating.
For further details about using Pootle, please have a look at Pootle's Documentation:
http://docs.translatehouse.org/projects/pootle/en/stable-2.5.1/
or you can ask about more details using one of methods listed on http://mediagoblin.org/pages/join.html</pre>

It is very easy to add or complete the translation of MediaGoblin! We use the web interface provided by the GNU instance of Pootle to do the translations. You can see the current status of the translations per language [https://chapters.gnu.org/projects/mediagoblin/ here].

To start translating, just:

# If it's the first time you are translating in the GNU instance of Pootle, then [https://chapters.gnu.org/accounts/register/ register an account]. You will receive an email for activating your account.
# Then you can [https://chapters.gnu.org/accounts/login log in]
# Go to Projects > mediagoblin ([https://chapters.gnu.org/projects/mediagoblin/ direct URL] and click in your language
# Click on "Continue translation".

By default, Pootle only shows you strings that currently have no translation. You can click in the "Translate" tab to show the already translated strings, in case you want to improve any of them.
There are no translation teams, so you can just edit the strings (but try to be nice and consistent with the current translation). If you are a regular contributor to the translations, you might want to add some notes to the [[#Notes for some language teams|per-language section on this page]] to coordinate consistent translations.

Note: please don't translate the words "MediaGoblin" or "GNU" into your native language. Those words should be retained as-is for branding reasons. :)

==Fixing or improving translations ==

If you click in the "Overview" tab, you will see the status of the translation of MediaGoblin to your language. If you click on "Expand details" you will find some statistics and the results of several quality checks (about capitalization, punctuation matching or not the original and the translation) which may help you to fix or improve the translation.

== Notes for some language teams ==
=== German ===

Interessante Hinweise zur Übersetzung finden sich bei Gnome:
* http://live.gnome.org/de/UebersetzungsRichtlinien

In Abweichung von diesen Richtlinien wird momentan "Du" für die Anrede benutzt. "Du" und "Deine" werden groß geschrieben. Benutze die folgenden Begriffe um konsistent zu bleiben:

Benutzerkonto/Nutzerkonto, E-Mail, E-Mail-Adresse, Aktivierungsmail, Konto "aktivieren" (verify email), Album (collection), Kurztitel (slug)

=== Spanish ===

Se está adoptando la siguiente convención para la traducción al español. Si crees que alguna traducción se puede mejorar, sugiérela en la página de discusión de este artículo.

{|
!Inglés
!Español
!Comentarios
|-
|you
|tú
|(segunda persona del singular, expresión informal)
|-
|media
|contenido
|-
|slug
|ficha
|}

=== '''العربية''' ===

.سنتخذ الاصطلاحات التالية للترجمة العربية. إذا كنت تريد تحسين الترجمة يرجى اقتراح التغبرات في صفحة النقاش في هذا المقال
{|
!الانجليزية
!العربية
|-
|MediaGoblin .
|ميدياغوبلن
|-
|media .
|الميديا
|-
|slug .
|المسار
|}

= For developers =
== Marking strings for translation ==
=== In Jinja2 ===

See: http://jinja.pocoo.org/docs/templates/#i18n

Mostly like Django template i18n support, if you have any experience with that.

=== In python code ===

Usually, like this:

<pre>
from mediagoblin.util import pass_to_ugettext as _

def some_func(something):
return _(u'This string would tooootally be translatable now.')
</pre>

Except, in form modules we don't actually want to translate things because for various reasons that doesn't work, so we do the translation call template-side. So write the module to use the fake ugettext passthrough (which doesn't do any translation but still wraps things in _() so that Babel will know to extract these strings):

<pre>
from mediagoblin.util import fake_ugettext_passthrough as _

class FunkyMonkeyForm(wtforms.Form):
funky = wtforms.TextAreaField(
_('Funkiness description'))
</pre>

== Extracting translations ==

If you run buildout it should create a script called 'pybabel'. Use it to extract translations like so:

<pre>
./bin/pybabel extract -F babel.ini -o mediagoblin/i18n/en/LC_MESSAGES/mediagoblin.po .
</pre>

== Compiling translations ==

<pre>
./bin/pybabel compile -D mediagoblin -d mediagoblin/i18n/
</pre>

== Pulling translations from Transifex (Warning! Obsolete) ==

<pre style="color: red;">This section contains obsolete information. Now Mediagoblin lives on Pootle.
Before the section is updated, you can ask about the process using one of methods listed on
http://mediagoblin.org/pages/join.html</pre>

Unfortunately until the next release of transifex-client which has been patched to have proper entry points, you have to run transifex-client from a virtualenv or from site-packages. But assuming that's done, pulling translations is easy:

<pre>
tx pull -a
</pre>

== Pushing new translations to Transifex (Warning! Obsolete) ==

<pre style="color: red;">This section contains obsolete information. Now Mediagoblin lives on Pootle.
Before the section is updated, you can ask about the process using one of methods listed on
http://mediagoblin.org/pages/join.html</pre>

<pre>
tx push -s
</pre>

= Troubleshooting (Warning! Obsolete) =

<pre style="color: red;">This section contains obsolete information. Now Mediagoblin lives on Pootle.
Before the section is updated, you can ask about the process using one of methods listed on
http://mediagoblin.org/pages/join.html</pre>

Got an error on Transifex like:

"Translation must start with a newline (\n)"?

The problem here is when we have something like:

{% trans register_url=request.urlgen('mediagoblin.auth.register') %}
<a class="header_submit_highlight" href="{{ register_url }}">Create a free account</a>
or
<a class="header_submit" href="http://wiki.mediagoblin.org/HackingHowto">Set up MediaGoblin on your own server</a>
{% endtrans %}

instead of:

{% trans register_url=request.urlgen('mediagoblin.auth.register') -%}
<a class="header_submit_highlight" href="{{ register_url }}">Create a free account</a>
or
<a class="header_submit" href="http://wiki.mediagoblin.org/HackingHowto">Set up MediaGoblin on your own server</a>
{%- endtrans %}

The distinction might not be obvious... look for the %} versus -%} and {% versus {%- on the first and last lines. The thing about this is this tells Jinja2 to strip the whitespace. Without that, Transifex sees that there's a "\n" on the first line of the original but not on the future translation, and gets upset.

If this happens the template should be updated to strip whitespace and translations should be pushed to transifex.

Translations

2015-02-12T12:03:08Z

Larjona: /* Pushing new translations to Transifex */

= For translators =

<pre style="color: red;">This section has changed recently, since now Mediagoblin lives on Pootle.
Here you can find the basic information for translating.
For further details about using Pootle, please have a look at Pootle's Documentation:
http://docs.translatehouse.org/projects/pootle/en/stable-2.5.1/
or you can ask about more details using one of methods listed on http://mediagoblin.org/pages/join.html</pre>

It is very easy to add or complete the translation of MediaGoblin! We use the web interface provided by the GNU instance of Pootle to do the translations. You can see the current status of the translations per language [https://chapters.gnu.org/projects/mediagoblin/ here].

To start translating, just:

# If it's the first time you are translating in the GNU instance of Pootle, then [https://chapters.gnu.org/accounts/register/ register an account]. You will receive an email for activating your account.
# Then you can [https://chapters.gnu.org/accounts/login log in]
# Go to Projects > mediagoblin ([https://chapters.gnu.org/projects/mediagoblin/ direct URL] and click in your language
# Click on "Continue translation".

By default, Pootle only shows you strings that currently have no translation. You can click in the "Translate" tab to show the already translated strings, in case you want to improve any of them.
There are no translation teams, so you can just edit the strings (but try to be nice and consistent with the current translation). If you are a regular contributor to the translations, you might want to add some notes to the [[#Notes for some language teams|per-language section on this page]] to coordinate consistent translations.

Note: please don't translate the words "MediaGoblin" or "GNU" into your native language. Those words should be retained as-is for branding reasons. :)

==Fixing or improving translations ==

If you click in the "Overview" tab, you will see the status of the translation of MediaGoblin to your language. If you click on "Expand details" you will find some statistics and the results of several quality checks (about capitalization, punctuation matching or not the original and the translation) which may help you to fix or improve the translation.

== Notes for some language teams ==
=== German ===

Interessante Hinweise zur Übersetzung finden sich bei Gnome:
* http://live.gnome.org/de/UebersetzungsRichtlinien

In Abweichung von diesen Richtlinien wird momentan "Du" für die Anrede benutzt. "Du" und "Deine" werden groß geschrieben. Benutze die folgenden Begriffe um konsistent zu bleiben:

Benutzerkonto/Nutzerkonto, E-Mail, E-Mail-Adresse, Aktivierungsmail, Konto "aktivieren" (verify email), Album (collection), Kurztitel (slug)

=== Spanish ===

Se está adoptando la siguiente convención para la traducción al español. Si crees que alguna traducción se puede mejorar, sugiérela en la página de discusión de este artículo.

{|
!Inglés
!Español
!Comentarios
|-
|you
|tú
|(segunda persona del singular, expresión informal)
|-
|media
|contenido
|-
|slug
|ficha
|}

=== '''العربية''' ===

.سنتخذ الاصطلاحات التالية للترجمة العربية. إذا كنت تريد تحسين الترجمة يرجى اقتراح التغبرات في صفحة النقاش في هذا المقال
{|
!الانجليزية
!العربية
|-
|MediaGoblin .
|ميدياغوبلن
|-
|media .
|الميديا
|-
|slug .
|المسار
|}

= For developers =
== Marking strings for translation ==
=== In Jinja2 ===

See: http://jinja.pocoo.org/docs/templates/#i18n

Mostly like Django template i18n support, if you have any experience with that.

=== In python code ===

Usually, like this:

<pre>
from mediagoblin.util import pass_to_ugettext as _

def some_func(something):
return _(u'This string would tooootally be translatable now.')
</pre>

Except, in form modules we don't actually want to translate things because for various reasons that doesn't work, so we do the translation call template-side. So write the module to use the fake ugettext passthrough (which doesn't do any translation but still wraps things in _() so that Babel will know to extract these strings):

<pre>
from mediagoblin.util import fake_ugettext_passthrough as _

class FunkyMonkeyForm(wtforms.Form):
funky = wtforms.TextAreaField(
_('Funkiness description'))
</pre>

== Extracting translations ==

If you run buildout it should create a script called 'pybabel'. Use it to extract translations like so:

<pre>
./bin/pybabel extract -F babel.ini -o mediagoblin/i18n/en/LC_MESSAGES/mediagoblin.po .
</pre>

== Compiling translations ==

<pre>
./bin/pybabel compile -D mediagoblin -d mediagoblin/i18n/
</pre>

== Pulling translations from Transifex (Warning! Obsolete) ==

<pre style="color: red;">This section contains obsolete information. Now Mediagoblin lives on Pootle.
Before the section is updated, you can ask about the process using one of methods listed on
http://mediagoblin.org/pages/join.html</pre>

Unfortunately until the next release of transifex-client which has been patched to have proper entry points, you have to run transifex-client from a virtualenv or from site-packages. But assuming that's done, pulling translations is easy:

<pre>
tx pull -a
</pre>

== Pushing new translations to Transifex (Warning! Obsolete) ==

<pre style="color: red;">This section contains obsolete information. Now Mediagoblin lives on Pootle.
Before the section is updated, you can ask about the process using one of methods listed on
http://mediagoblin.org/pages/join.html</pre>

<pre>
tx push -s
</pre>

= Troubleshooting =

<pre style="color: red;">This section contains obsolete information. Now Mediagoblin lives on Pootle.
Before the section is updated, you can ask about the process using one of methods listed on
http://mediagoblin.org/pages/join.html</pre>

Got an error on Transifex like:

"Translation must start with a newline (\n)"?

The problem here is when we have something like:

{% trans register_url=request.urlgen('mediagoblin.auth.register') %}
<a class="header_submit_highlight" href="{{ register_url }}">Create a free account</a>
or
<a class="header_submit" href="http://wiki.mediagoblin.org/HackingHowto">Set up MediaGoblin on your own server</a>
{% endtrans %}

instead of:

{% trans register_url=request.urlgen('mediagoblin.auth.register') -%}
<a class="header_submit_highlight" href="{{ register_url }}">Create a free account</a>
or
<a class="header_submit" href="http://wiki.mediagoblin.org/HackingHowto">Set up MediaGoblin on your own server</a>
{%- endtrans %}

The distinction might not be obvious... look for the %} versus -%} and {% versus {%- on the first and last lines. The thing about this is this tells Jinja2 to strip the whitespace. Without that, Transifex sees that there's a "\n" on the first line of the original but not on the future translation, and gets upset.

If this happens the template should be updated to strip whitespace and translations should be pushed to transifex.

Translations

2015-02-12T12:02:56Z

Larjona: /* Pulling translations from Transifex */

= For translators =

<pre style="color: red;">This section has changed recently, since now Mediagoblin lives on Pootle.
Here you can find the basic information for translating.
For further details about using Pootle, please have a look at Pootle's Documentation:
http://docs.translatehouse.org/projects/pootle/en/stable-2.5.1/
or you can ask about more details using one of methods listed on http://mediagoblin.org/pages/join.html</pre>

It is very easy to add or complete the translation of MediaGoblin! We use the web interface provided by the GNU instance of Pootle to do the translations. You can see the current status of the translations per language [https://chapters.gnu.org/projects/mediagoblin/ here].

To start translating, just:

# If it's the first time you are translating in the GNU instance of Pootle, then [https://chapters.gnu.org/accounts/register/ register an account]. You will receive an email for activating your account.
# Then you can [https://chapters.gnu.org/accounts/login log in]
# Go to Projects > mediagoblin ([https://chapters.gnu.org/projects/mediagoblin/ direct URL] and click in your language
# Click on "Continue translation".

By default, Pootle only shows you strings that currently have no translation. You can click in the "Translate" tab to show the already translated strings, in case you want to improve any of them.
There are no translation teams, so you can just edit the strings (but try to be nice and consistent with the current translation). If you are a regular contributor to the translations, you might want to add some notes to the [[#Notes for some language teams|per-language section on this page]] to coordinate consistent translations.

Note: please don't translate the words "MediaGoblin" or "GNU" into your native language. Those words should be retained as-is for branding reasons. :)

==Fixing or improving translations ==

If you click in the "Overview" tab, you will see the status of the translation of MediaGoblin to your language. If you click on "Expand details" you will find some statistics and the results of several quality checks (about capitalization, punctuation matching or not the original and the translation) which may help you to fix or improve the translation.

== Notes for some language teams ==
=== German ===

Interessante Hinweise zur Übersetzung finden sich bei Gnome:
* http://live.gnome.org/de/UebersetzungsRichtlinien

In Abweichung von diesen Richtlinien wird momentan "Du" für die Anrede benutzt. "Du" und "Deine" werden groß geschrieben. Benutze die folgenden Begriffe um konsistent zu bleiben:

Benutzerkonto/Nutzerkonto, E-Mail, E-Mail-Adresse, Aktivierungsmail, Konto "aktivieren" (verify email), Album (collection), Kurztitel (slug)

=== Spanish ===

Se está adoptando la siguiente convención para la traducción al español. Si crees que alguna traducción se puede mejorar, sugiérela en la página de discusión de este artículo.

{|
!Inglés
!Español
!Comentarios
|-
|you
|tú
|(segunda persona del singular, expresión informal)
|-
|media
|contenido
|-
|slug
|ficha
|}

=== '''العربية''' ===

.سنتخذ الاصطلاحات التالية للترجمة العربية. إذا كنت تريد تحسين الترجمة يرجى اقتراح التغبرات في صفحة النقاش في هذا المقال
{|
!الانجليزية
!العربية
|-
|MediaGoblin .
|ميدياغوبلن
|-
|media .
|الميديا
|-
|slug .
|المسار
|}

= For developers =
== Marking strings for translation ==
=== In Jinja2 ===

See: http://jinja.pocoo.org/docs/templates/#i18n

Mostly like Django template i18n support, if you have any experience with that.

=== In python code ===

Usually, like this:

<pre>
from mediagoblin.util import pass_to_ugettext as _

def some_func(something):
return _(u'This string would tooootally be translatable now.')
</pre>

Except, in form modules we don't actually want to translate things because for various reasons that doesn't work, so we do the translation call template-side. So write the module to use the fake ugettext passthrough (which doesn't do any translation but still wraps things in _() so that Babel will know to extract these strings):

<pre>
from mediagoblin.util import fake_ugettext_passthrough as _

class FunkyMonkeyForm(wtforms.Form):
funky = wtforms.TextAreaField(
_('Funkiness description'))
</pre>

== Extracting translations ==

If you run buildout it should create a script called 'pybabel'. Use it to extract translations like so:

<pre>
./bin/pybabel extract -F babel.ini -o mediagoblin/i18n/en/LC_MESSAGES/mediagoblin.po .
</pre>

== Compiling translations ==

<pre>
./bin/pybabel compile -D mediagoblin -d mediagoblin/i18n/
</pre>

== Pulling translations from Transifex (Warning! Obsolete) ==

<pre style="color: red;">This section contains obsolete information. Now Mediagoblin lives on Pootle.
Before the section is updated, you can ask about the process using one of methods listed on
http://mediagoblin.org/pages/join.html</pre>

Unfortunately until the next release of transifex-client which has been patched to have proper entry points, you have to run transifex-client from a virtualenv or from site-packages. But assuming that's done, pulling translations is easy:

<pre>
tx pull -a
</pre>

== Pushing new translations to Transifex ==

<pre style="color: red;">This section contains obsolete information. Now Mediagoblin lives on Pootle.
Before the section is updated, you can ask about the process using one of methods listed on
http://mediagoblin.org/pages/join.html</pre>

<pre>
tx push -s
</pre>

= Troubleshooting =

<pre style="color: red;">This section contains obsolete information. Now Mediagoblin lives on Pootle.
Before the section is updated, you can ask about the process using one of methods listed on
http://mediagoblin.org/pages/join.html</pre>

Got an error on Transifex like:

"Translation must start with a newline (\n)"?

The problem here is when we have something like:

{% trans register_url=request.urlgen('mediagoblin.auth.register') %}
<a class="header_submit_highlight" href="{{ register_url }}">Create a free account</a>
or
<a class="header_submit" href="http://wiki.mediagoblin.org/HackingHowto">Set up MediaGoblin on your own server</a>
{% endtrans %}

instead of:

{% trans register_url=request.urlgen('mediagoblin.auth.register') -%}
<a class="header_submit_highlight" href="{{ register_url }}">Create a free account</a>
or
<a class="header_submit" href="http://wiki.mediagoblin.org/HackingHowto">Set up MediaGoblin on your own server</a>
{%- endtrans %}

The distinction might not be obvious... look for the %} versus -%} and {% versus {%- on the first and last lines. The thing about this is this tells Jinja2 to strip the whitespace. Without that, Transifex sees that there's a "\n" on the first line of the original but not on the future translation, and gets upset.

If this happens the template should be updated to strip whitespace and translations should be pushed to transifex.

Translations

2015-02-12T12:02:24Z

Larjona: /* Troubleshooting */

= For translators =

<pre style="color: red;">This section has changed recently, since now Mediagoblin lives on Pootle.
Here you can find the basic information for translating.
For further details about using Pootle, please have a look at Pootle's Documentation:
http://docs.translatehouse.org/projects/pootle/en/stable-2.5.1/
or you can ask about more details using one of methods listed on http://mediagoblin.org/pages/join.html</pre>

It is very easy to add or complete the translation of MediaGoblin! We use the web interface provided by the GNU instance of Pootle to do the translations. You can see the current status of the translations per language [https://chapters.gnu.org/projects/mediagoblin/ here].

To start translating, just:

# If it's the first time you are translating in the GNU instance of Pootle, then [https://chapters.gnu.org/accounts/register/ register an account]. You will receive an email for activating your account.
# Then you can [https://chapters.gnu.org/accounts/login log in]
# Go to Projects > mediagoblin ([https://chapters.gnu.org/projects/mediagoblin/ direct URL] and click in your language
# Click on "Continue translation".

By default, Pootle only shows you strings that currently have no translation. You can click in the "Translate" tab to show the already translated strings, in case you want to improve any of them.
There are no translation teams, so you can just edit the strings (but try to be nice and consistent with the current translation). If you are a regular contributor to the translations, you might want to add some notes to the [[#Notes for some language teams|per-language section on this page]] to coordinate consistent translations.

Note: please don't translate the words "MediaGoblin" or "GNU" into your native language. Those words should be retained as-is for branding reasons. :)

==Fixing or improving translations ==

If you click in the "Overview" tab, you will see the status of the translation of MediaGoblin to your language. If you click on "Expand details" you will find some statistics and the results of several quality checks (about capitalization, punctuation matching or not the original and the translation) which may help you to fix or improve the translation.

== Notes for some language teams ==
=== German ===

Interessante Hinweise zur Übersetzung finden sich bei Gnome:
* http://live.gnome.org/de/UebersetzungsRichtlinien

In Abweichung von diesen Richtlinien wird momentan "Du" für die Anrede benutzt. "Du" und "Deine" werden groß geschrieben. Benutze die folgenden Begriffe um konsistent zu bleiben:

Benutzerkonto/Nutzerkonto, E-Mail, E-Mail-Adresse, Aktivierungsmail, Konto "aktivieren" (verify email), Album (collection), Kurztitel (slug)

=== Spanish ===

Se está adoptando la siguiente convención para la traducción al español. Si crees que alguna traducción se puede mejorar, sugiérela en la página de discusión de este artículo.

{|
!Inglés
!Español
!Comentarios
|-
|you
|tú
|(segunda persona del singular, expresión informal)
|-
|media
|contenido
|-
|slug
|ficha
|}

=== '''العربية''' ===

.سنتخذ الاصطلاحات التالية للترجمة العربية. إذا كنت تريد تحسين الترجمة يرجى اقتراح التغبرات في صفحة النقاش في هذا المقال
{|
!الانجليزية
!العربية
|-
|MediaGoblin .
|ميدياغوبلن
|-
|media .
|الميديا
|-
|slug .
|المسار
|}

= For developers =
== Marking strings for translation ==
=== In Jinja2 ===

See: http://jinja.pocoo.org/docs/templates/#i18n

Mostly like Django template i18n support, if you have any experience with that.

=== In python code ===

Usually, like this:

<pre>
from mediagoblin.util import pass_to_ugettext as _

def some_func(something):
return _(u'This string would tooootally be translatable now.')
</pre>

Except, in form modules we don't actually want to translate things because for various reasons that doesn't work, so we do the translation call template-side. So write the module to use the fake ugettext passthrough (which doesn't do any translation but still wraps things in _() so that Babel will know to extract these strings):

<pre>
from mediagoblin.util import fake_ugettext_passthrough as _

class FunkyMonkeyForm(wtforms.Form):
funky = wtforms.TextAreaField(
_('Funkiness description'))
</pre>

== Extracting translations ==

If you run buildout it should create a script called 'pybabel'. Use it to extract translations like so:

<pre>
./bin/pybabel extract -F babel.ini -o mediagoblin/i18n/en/LC_MESSAGES/mediagoblin.po .
</pre>

== Compiling translations ==

<pre>
./bin/pybabel compile -D mediagoblin -d mediagoblin/i18n/
</pre>

== Pulling translations from Transifex ==

<pre style="color: red;">This section contains obsolete information. Now Mediagoblin lives on Pootle.
Before the section is updated, you can ask about the process using one of methods listed on
http://mediagoblin.org/pages/join.html</pre>

Unfortunately until the next release of transifex-client which has been patched to have proper entry points, you have to run transifex-client from a virtualenv or from site-packages. But assuming that's done, pulling translations is easy:

<pre>
tx pull -a
</pre>

== Pushing new translations to Transifex ==

<pre style="color: red;">This section contains obsolete information. Now Mediagoblin lives on Pootle.
Before the section is updated, you can ask about the process using one of methods listed on
http://mediagoblin.org/pages/join.html</pre>

<pre>
tx push -s
</pre>

= Troubleshooting =

<pre style="color: red;">This section contains obsolete information. Now Mediagoblin lives on Pootle.
Before the section is updated, you can ask about the process using one of methods listed on
http://mediagoblin.org/pages/join.html</pre>

Got an error on Transifex like:

"Translation must start with a newline (\n)"?

The problem here is when we have something like:

{% trans register_url=request.urlgen('mediagoblin.auth.register') %}
<a class="header_submit_highlight" href="{{ register_url }}">Create a free account</a>
or
<a class="header_submit" href="http://wiki.mediagoblin.org/HackingHowto">Set up MediaGoblin on your own server</a>
{% endtrans %}

instead of:

{% trans register_url=request.urlgen('mediagoblin.auth.register') -%}
<a class="header_submit_highlight" href="{{ register_url }}">Create a free account</a>
or
<a class="header_submit" href="http://wiki.mediagoblin.org/HackingHowto">Set up MediaGoblin on your own server</a>
{%- endtrans %}

The distinction might not be obvious... look for the %} versus -%} and {% versus {%- on the first and last lines. The thing about this is this tells Jinja2 to strip the whitespace. Without that, Transifex sees that there's a "\n" on the first line of the original but not on the future translation, and gets upset.

If this happens the template should be updated to strip whitespace and translations should be pushed to transifex.

Translations

2015-02-12T12:02:08Z

Larjona: /* Pushing new translations to Transifex */

= For translators =

<pre style="color: red;">This section has changed recently, since now Mediagoblin lives on Pootle.
Here you can find the basic information for translating.
For further details about using Pootle, please have a look at Pootle's Documentation:
http://docs.translatehouse.org/projects/pootle/en/stable-2.5.1/
or you can ask about more details using one of methods listed on http://mediagoblin.org/pages/join.html</pre>

It is very easy to add or complete the translation of MediaGoblin! We use the web interface provided by the GNU instance of Pootle to do the translations. You can see the current status of the translations per language [https://chapters.gnu.org/projects/mediagoblin/ here].

To start translating, just:

# If it's the first time you are translating in the GNU instance of Pootle, then [https://chapters.gnu.org/accounts/register/ register an account]. You will receive an email for activating your account.
# Then you can [https://chapters.gnu.org/accounts/login log in]
# Go to Projects > mediagoblin ([https://chapters.gnu.org/projects/mediagoblin/ direct URL] and click in your language
# Click on "Continue translation".

By default, Pootle only shows you strings that currently have no translation. You can click in the "Translate" tab to show the already translated strings, in case you want to improve any of them.
There are no translation teams, so you can just edit the strings (but try to be nice and consistent with the current translation). If you are a regular contributor to the translations, you might want to add some notes to the [[#Notes for some language teams|per-language section on this page]] to coordinate consistent translations.

Note: please don't translate the words "MediaGoblin" or "GNU" into your native language. Those words should be retained as-is for branding reasons. :)

==Fixing or improving translations ==

If you click in the "Overview" tab, you will see the status of the translation of MediaGoblin to your language. If you click on "Expand details" you will find some statistics and the results of several quality checks (about capitalization, punctuation matching or not the original and the translation) which may help you to fix or improve the translation.

== Notes for some language teams ==
=== German ===

Interessante Hinweise zur Übersetzung finden sich bei Gnome:
* http://live.gnome.org/de/UebersetzungsRichtlinien

In Abweichung von diesen Richtlinien wird momentan "Du" für die Anrede benutzt. "Du" und "Deine" werden groß geschrieben. Benutze die folgenden Begriffe um konsistent zu bleiben:

Benutzerkonto/Nutzerkonto, E-Mail, E-Mail-Adresse, Aktivierungsmail, Konto "aktivieren" (verify email), Album (collection), Kurztitel (slug)

=== Spanish ===

Se está adoptando la siguiente convención para la traducción al español. Si crees que alguna traducción se puede mejorar, sugiérela en la página de discusión de este artículo.

{|
!Inglés
!Español
!Comentarios
|-
|you
|tú
|(segunda persona del singular, expresión informal)
|-
|media
|contenido
|-
|slug
|ficha
|}

=== '''العربية''' ===

.سنتخذ الاصطلاحات التالية للترجمة العربية. إذا كنت تريد تحسين الترجمة يرجى اقتراح التغبرات في صفحة النقاش في هذا المقال
{|
!الانجليزية
!العربية
|-
|MediaGoblin .
|ميدياغوبلن
|-
|media .
|الميديا
|-
|slug .
|المسار
|}

= For developers =
== Marking strings for translation ==
=== In Jinja2 ===

See: http://jinja.pocoo.org/docs/templates/#i18n

Mostly like Django template i18n support, if you have any experience with that.

=== In python code ===

Usually, like this:

<pre>
from mediagoblin.util import pass_to_ugettext as _

def some_func(something):
return _(u'This string would tooootally be translatable now.')
</pre>

Except, in form modules we don't actually want to translate things because for various reasons that doesn't work, so we do the translation call template-side. So write the module to use the fake ugettext passthrough (which doesn't do any translation but still wraps things in _() so that Babel will know to extract these strings):

<pre>
from mediagoblin.util import fake_ugettext_passthrough as _

class FunkyMonkeyForm(wtforms.Form):
funky = wtforms.TextAreaField(
_('Funkiness description'))
</pre>

== Extracting translations ==

If you run buildout it should create a script called 'pybabel'. Use it to extract translations like so:

<pre>
./bin/pybabel extract -F babel.ini -o mediagoblin/i18n/en/LC_MESSAGES/mediagoblin.po .
</pre>

== Compiling translations ==

<pre>
./bin/pybabel compile -D mediagoblin -d mediagoblin/i18n/
</pre>

== Pulling translations from Transifex ==

<pre style="color: red;">This section contains obsolete information. Now Mediagoblin lives on Pootle.
Before the section is updated, you can ask about the process using one of methods listed on
http://mediagoblin.org/pages/join.html</pre>

Unfortunately until the next release of transifex-client which has been patched to have proper entry points, you have to run transifex-client from a virtualenv or from site-packages. But assuming that's done, pulling translations is easy:

<pre>
tx pull -a
</pre>

== Pushing new translations to Transifex ==

<pre style="color: red;">This section contains obsolete information. Now Mediagoblin lives on Pootle.
Before the section is updated, you can ask about the process using one of methods listed on
http://mediagoblin.org/pages/join.html</pre>

<pre>
tx push -s
</pre>

= Troubleshooting =

Got an error on Transifex like:

"Translation must start with a newline (\n)"?

The problem here is when we have something like:

{% trans register_url=request.urlgen('mediagoblin.auth.register') %}
<a class="header_submit_highlight" href="{{ register_url }}">Create a free account</a>
or
<a class="header_submit" href="http://wiki.mediagoblin.org/HackingHowto">Set up MediaGoblin on your own server</a>
{% endtrans %}

instead of:

{% trans register_url=request.urlgen('mediagoblin.auth.register') -%}
<a class="header_submit_highlight" href="{{ register_url }}">Create a free account</a>
or
<a class="header_submit" href="http://wiki.mediagoblin.org/HackingHowto">Set up MediaGoblin on your own server</a>
{%- endtrans %}

The distinction might not be obvious... look for the %} versus -%} and {% versus {%- on the first and last lines. The thing about this is this tells Jinja2 to strip the whitespace. Without that, Transifex sees that there's a "\n" on the first line of the original but not on the future translation, and gets upset.

If this happens the template should be updated to strip whitespace and translations should be pushed to transifex.

Translations

2015-02-12T12:01:58Z

Larjona: /* Pulling translations from Transifex */ Put obsolete warning

= For translators =

<pre style="color: red;">This section has changed recently, since now Mediagoblin lives on Pootle.
Here you can find the basic information for translating.
For further details about using Pootle, please have a look at Pootle's Documentation:
http://docs.translatehouse.org/projects/pootle/en/stable-2.5.1/
or you can ask about more details using one of methods listed on http://mediagoblin.org/pages/join.html</pre>

It is very easy to add or complete the translation of MediaGoblin! We use the web interface provided by the GNU instance of Pootle to do the translations. You can see the current status of the translations per language [https://chapters.gnu.org/projects/mediagoblin/ here].

To start translating, just:

# If it's the first time you are translating in the GNU instance of Pootle, then [https://chapters.gnu.org/accounts/register/ register an account]. You will receive an email for activating your account.
# Then you can [https://chapters.gnu.org/accounts/login log in]
# Go to Projects > mediagoblin ([https://chapters.gnu.org/projects/mediagoblin/ direct URL] and click in your language
# Click on "Continue translation".

By default, Pootle only shows you strings that currently have no translation. You can click in the "Translate" tab to show the already translated strings, in case you want to improve any of them.
There are no translation teams, so you can just edit the strings (but try to be nice and consistent with the current translation). If you are a regular contributor to the translations, you might want to add some notes to the [[#Notes for some language teams|per-language section on this page]] to coordinate consistent translations.

Note: please don't translate the words "MediaGoblin" or "GNU" into your native language. Those words should be retained as-is for branding reasons. :)

==Fixing or improving translations ==

If you click in the "Overview" tab, you will see the status of the translation of MediaGoblin to your language. If you click on "Expand details" you will find some statistics and the results of several quality checks (about capitalization, punctuation matching or not the original and the translation) which may help you to fix or improve the translation.

== Notes for some language teams ==
=== German ===

Interessante Hinweise zur Übersetzung finden sich bei Gnome:
* http://live.gnome.org/de/UebersetzungsRichtlinien

In Abweichung von diesen Richtlinien wird momentan "Du" für die Anrede benutzt. "Du" und "Deine" werden groß geschrieben. Benutze die folgenden Begriffe um konsistent zu bleiben:

Benutzerkonto/Nutzerkonto, E-Mail, E-Mail-Adresse, Aktivierungsmail, Konto "aktivieren" (verify email), Album (collection), Kurztitel (slug)

=== Spanish ===

Se está adoptando la siguiente convención para la traducción al español. Si crees que alguna traducción se puede mejorar, sugiérela en la página de discusión de este artículo.

{|
!Inglés
!Español
!Comentarios
|-
|you
|tú
|(segunda persona del singular, expresión informal)
|-
|media
|contenido
|-
|slug
|ficha
|}

=== '''العربية''' ===

.سنتخذ الاصطلاحات التالية للترجمة العربية. إذا كنت تريد تحسين الترجمة يرجى اقتراح التغبرات في صفحة النقاش في هذا المقال
{|
!الانجليزية
!العربية
|-
|MediaGoblin .
|ميدياغوبلن
|-
|media .
|الميديا
|-
|slug .
|المسار
|}

= For developers =
== Marking strings for translation ==
=== In Jinja2 ===

See: http://jinja.pocoo.org/docs/templates/#i18n

Mostly like Django template i18n support, if you have any experience with that.

=== In python code ===

Usually, like this:

<pre>
from mediagoblin.util import pass_to_ugettext as _

def some_func(something):
return _(u'This string would tooootally be translatable now.')
</pre>

Except, in form modules we don't actually want to translate things because for various reasons that doesn't work, so we do the translation call template-side. So write the module to use the fake ugettext passthrough (which doesn't do any translation but still wraps things in _() so that Babel will know to extract these strings):

<pre>
from mediagoblin.util import fake_ugettext_passthrough as _

class FunkyMonkeyForm(wtforms.Form):
funky = wtforms.TextAreaField(
_('Funkiness description'))
</pre>

== Extracting translations ==

If you run buildout it should create a script called 'pybabel'. Use it to extract translations like so:

<pre>
./bin/pybabel extract -F babel.ini -o mediagoblin/i18n/en/LC_MESSAGES/mediagoblin.po .
</pre>

== Compiling translations ==

<pre>
./bin/pybabel compile -D mediagoblin -d mediagoblin/i18n/
</pre>

== Pulling translations from Transifex ==

<pre style="color: red;">This section contains obsolete information. Now Mediagoblin lives on Pootle.
Before the section is updated, you can ask about the process using one of methods listed on
http://mediagoblin.org/pages/join.html</pre>

Unfortunately until the next release of transifex-client which has been patched to have proper entry points, you have to run transifex-client from a virtualenv or from site-packages. But assuming that's done, pulling translations is easy:

<pre>
tx pull -a
</pre>

== Pushing new translations to Transifex ==

<pre>
tx push -s
</pre>

= Troubleshooting =

Got an error on Transifex like:

"Translation must start with a newline (\n)"?

The problem here is when we have something like:

{% trans register_url=request.urlgen('mediagoblin.auth.register') %}
<a class="header_submit_highlight" href="{{ register_url }}">Create a free account</a>
or
<a class="header_submit" href="http://wiki.mediagoblin.org/HackingHowto">Set up MediaGoblin on your own server</a>
{% endtrans %}

instead of:

{% trans register_url=request.urlgen('mediagoblin.auth.register') -%}
<a class="header_submit_highlight" href="{{ register_url }}">Create a free account</a>
or
<a class="header_submit" href="http://wiki.mediagoblin.org/HackingHowto">Set up MediaGoblin on your own server</a>
{%- endtrans %}

The distinction might not be obvious... look for the %} versus -%} and {% versus {%- on the first and last lines. The thing about this is this tells Jinja2 to strip the whitespace. Without that, Transifex sees that there's a "\n" on the first line of the original but not on the future translation, and gets upset.

If this happens the template should be updated to strip whitespace and translations should be pushed to transifex.

Translations

2015-02-12T11:58:51Z

Larjona: /* For translators */ Move up the section about fixing translations

= For translators =

<pre style="color: red;">This section has changed recently, since now Mediagoblin lives on Pootle.
Here you can find the basic information for translating.
For further details about using Pootle, please have a look at Pootle's Documentation:
http://docs.translatehouse.org/projects/pootle/en/stable-2.5.1/
or you can ask about more details using one of methods listed on http://mediagoblin.org/pages/join.html</pre>

It is very easy to add or complete the translation of MediaGoblin! We use the web interface provided by the GNU instance of Pootle to do the translations. You can see the current status of the translations per language [https://chapters.gnu.org/projects/mediagoblin/ here].

To start translating, just:

# If it's the first time you are translating in the GNU instance of Pootle, then [https://chapters.gnu.org/accounts/register/ register an account]. You will receive an email for activating your account.
# Then you can [https://chapters.gnu.org/accounts/login log in]
# Go to Projects > mediagoblin ([https://chapters.gnu.org/projects/mediagoblin/ direct URL] and click in your language
# Click on "Continue translation".

By default, Pootle only shows you strings that currently have no translation. You can click in the "Translate" tab to show the already translated strings, in case you want to improve any of them.
There are no translation teams, so you can just edit the strings (but try to be nice and consistent with the current translation). If you are a regular contributor to the translations, you might want to add some notes to the [[#Notes for some language teams|per-language section on this page]] to coordinate consistent translations.

Note: please don't translate the words "MediaGoblin" or "GNU" into your native language. Those words should be retained as-is for branding reasons. :)

==Fixing or improving translations ==

If you click in the "Overview" tab, you will see the status of the translation of MediaGoblin to your language. If you click on "Expand details" you will find some statistics and the results of several quality checks (about capitalization, punctuation matching or not the original and the translation) which may help you to fix or improve the translation.

== Notes for some language teams ==
=== German ===

Interessante Hinweise zur Übersetzung finden sich bei Gnome:
* http://live.gnome.org/de/UebersetzungsRichtlinien

In Abweichung von diesen Richtlinien wird momentan "Du" für die Anrede benutzt. "Du" und "Deine" werden groß geschrieben. Benutze die folgenden Begriffe um konsistent zu bleiben:

Benutzerkonto/Nutzerkonto, E-Mail, E-Mail-Adresse, Aktivierungsmail, Konto "aktivieren" (verify email), Album (collection), Kurztitel (slug)

=== Spanish ===

Se está adoptando la siguiente convención para la traducción al español. Si crees que alguna traducción se puede mejorar, sugiérela en la página de discusión de este artículo.

{|
!Inglés
!Español
!Comentarios
|-
|you
|tú
|(segunda persona del singular, expresión informal)
|-
|media
|contenido
|-
|slug
|ficha
|}

=== '''العربية''' ===

.سنتخذ الاصطلاحات التالية للترجمة العربية. إذا كنت تريد تحسين الترجمة يرجى اقتراح التغبرات في صفحة النقاش في هذا المقال
{|
!الانجليزية
!العربية
|-
|MediaGoblin .
|ميدياغوبلن
|-
|media .
|الميديا
|-
|slug .
|المسار
|}

= For developers =
== Marking strings for translation ==
=== In Jinja2 ===

See: http://jinja.pocoo.org/docs/templates/#i18n

Mostly like Django template i18n support, if you have any experience with that.

=== In python code ===

Usually, like this:

<pre>
from mediagoblin.util import pass_to_ugettext as _

def some_func(something):
return _(u'This string would tooootally be translatable now.')
</pre>

Except, in form modules we don't actually want to translate things because for various reasons that doesn't work, so we do the translation call template-side. So write the module to use the fake ugettext passthrough (which doesn't do any translation but still wraps things in _() so that Babel will know to extract these strings):

<pre>
from mediagoblin.util import fake_ugettext_passthrough as _

class FunkyMonkeyForm(wtforms.Form):
funky = wtforms.TextAreaField(
_('Funkiness description'))
</pre>

== Extracting translations ==

If you run buildout it should create a script called 'pybabel'. Use it to extract translations like so:

<pre>
./bin/pybabel extract -F babel.ini -o mediagoblin/i18n/en/LC_MESSAGES/mediagoblin.po .
</pre>

== Compiling translations ==

<pre>
./bin/pybabel compile -D mediagoblin -d mediagoblin/i18n/
</pre>

== Pulling translations from Transifex ==

Unfortunately until the next release of transifex-client which has been patched to have proper entry points, you have to run transifex-client from a virtualenv or from site-packages. But assuming that's done, pulling translations is easy:

<pre>
tx pull -a
</pre>

== Pushing new translations to Transifex ==

<pre>
tx push -s
</pre>

= Troubleshooting =

Got an error on Transifex like:

"Translation must start with a newline (\n)"?

The problem here is when we have something like:

{% trans register_url=request.urlgen('mediagoblin.auth.register') %}
<a class="header_submit_highlight" href="{{ register_url }}">Create a free account</a>
or
<a class="header_submit" href="http://wiki.mediagoblin.org/HackingHowto">Set up MediaGoblin on your own server</a>
{% endtrans %}

instead of:

{% trans register_url=request.urlgen('mediagoblin.auth.register') -%}
<a class="header_submit_highlight" href="{{ register_url }}">Create a free account</a>
or
<a class="header_submit" href="http://wiki.mediagoblin.org/HackingHowto">Set up MediaGoblin on your own server</a>
{%- endtrans %}

The distinction might not be obvious... look for the %} versus -%} and {% versus {%- on the first and last lines. The thing about this is this tells Jinja2 to strip the whitespace. Without that, Transifex sees that there's a "\n" on the first line of the original but not on the future translation, and gets upset.

If this happens the template should be updated to strip whitespace and translations should be pushed to transifex.

Translations

2015-02-12T11:58:21Z

Larjona: /* Fixing or improving translations */ Moving up this section

= For translators =

<pre style="color: red;">This section has changed recently, since now Mediagoblin lives on Pootle.
Here you can find the basic information for translating.
For further details about using Pootle, please have a look at Pootle's Documentation:
http://docs.translatehouse.org/projects/pootle/en/stable-2.5.1/
or you can ask about more details using one of methods listed on http://mediagoblin.org/pages/join.html</pre>

It is very easy to add or complete the translation of MediaGoblin! We use the web interface provided by the GNU instance of Pootle to do the translations. You can see the current status of the translations per language [https://chapters.gnu.org/projects/mediagoblin/ here].

To start translating, just:

# If it's the first time you are translating in the GNU instance of Pootle, then [https://chapters.gnu.org/accounts/register/ register an account]. You will receive an email for activating your account.
# Then you can [https://chapters.gnu.org/accounts/login log in]
# Go to Projects > mediagoblin ([https://chapters.gnu.org/projects/mediagoblin/ direct URL] and click in your language
# Click on "Continue translation".

By default, Pootle only shows you strings that currently have no translation. You can click in the "Translate" tab to show the already translated strings, in case you want to improve any of them.
There are no translation teams, so you can just edit the strings (but try to be nice and consistent with the current translation). If you are a regular contributor to the translations, you might want to add some notes to the [[#Notes for some language teams|per-language section on this page]] to coordinate consistent translations.

Note: please don't translate the words "MediaGoblin" or "GNU" into your native language. Those words should be retained as-is for branding reasons. :)

== Notes for some language teams ==
=== German ===

Interessante Hinweise zur Übersetzung finden sich bei Gnome:
* http://live.gnome.org/de/UebersetzungsRichtlinien

In Abweichung von diesen Richtlinien wird momentan "Du" für die Anrede benutzt. "Du" und "Deine" werden groß geschrieben. Benutze die folgenden Begriffe um konsistent zu bleiben:

Benutzerkonto/Nutzerkonto, E-Mail, E-Mail-Adresse, Aktivierungsmail, Konto "aktivieren" (verify email), Album (collection), Kurztitel (slug)

=== Spanish ===

Se está adoptando la siguiente convención para la traducción al español. Si crees que alguna traducción se puede mejorar, sugiérela en la página de discusión de este artículo.

{|
!Inglés
!Español
!Comentarios
|-
|you
|tú
|(segunda persona del singular, expresión informal)
|-
|media
|contenido
|-
|slug
|ficha
|}

=== '''العربية''' ===

.سنتخذ الاصطلاحات التالية للترجمة العربية. إذا كنت تريد تحسين الترجمة يرجى اقتراح التغبرات في صفحة النقاش في هذا المقال
{|
!الانجليزية
!العربية
|-
|MediaGoblin .
|ميدياغوبلن
|-
|media .
|الميديا
|-
|slug .
|المسار
|}

= For developers =
== Marking strings for translation ==
=== In Jinja2 ===

See: http://jinja.pocoo.org/docs/templates/#i18n

Mostly like Django template i18n support, if you have any experience with that.

=== In python code ===

Usually, like this:

<pre>
from mediagoblin.util import pass_to_ugettext as _

def some_func(something):
return _(u'This string would tooootally be translatable now.')
</pre>

Except, in form modules we don't actually want to translate things because for various reasons that doesn't work, so we do the translation call template-side. So write the module to use the fake ugettext passthrough (which doesn't do any translation but still wraps things in _() so that Babel will know to extract these strings):

<pre>
from mediagoblin.util import fake_ugettext_passthrough as _

class FunkyMonkeyForm(wtforms.Form):
funky = wtforms.TextAreaField(
_('Funkiness description'))
</pre>

== Extracting translations ==

If you run buildout it should create a script called 'pybabel'. Use it to extract translations like so:

<pre>
./bin/pybabel extract -F babel.ini -o mediagoblin/i18n/en/LC_MESSAGES/mediagoblin.po .
</pre>

== Compiling translations ==

<pre>
./bin/pybabel compile -D mediagoblin -d mediagoblin/i18n/
</pre>

== Pulling translations from Transifex ==

Unfortunately until the next release of transifex-client which has been patched to have proper entry points, you have to run transifex-client from a virtualenv or from site-packages. But assuming that's done, pulling translations is easy:

<pre>
tx pull -a
</pre>

== Pushing new translations to Transifex ==

<pre>
tx push -s
</pre>

= Troubleshooting =

Got an error on Transifex like:

"Translation must start with a newline (\n)"?

The problem here is when we have something like:

{% trans register_url=request.urlgen('mediagoblin.auth.register') %}
<a class="header_submit_highlight" href="{{ register_url }}">Create a free account</a>
or
<a class="header_submit" href="http://wiki.mediagoblin.org/HackingHowto">Set up MediaGoblin on your own server</a>
{% endtrans %}

instead of:

{% trans register_url=request.urlgen('mediagoblin.auth.register') -%}
<a class="header_submit_highlight" href="{{ register_url }}">Create a free account</a>
or
<a class="header_submit" href="http://wiki.mediagoblin.org/HackingHowto">Set up MediaGoblin on your own server</a>
{%- endtrans %}

The distinction might not be obvious... look for the %} versus -%} and {% versus {%- on the first and last lines. The thing about this is this tells Jinja2 to strip the whitespace. Without that, Transifex sees that there's a "\n" on the first line of the original but not on the future translation, and gets upset.

If this happens the template should be updated to strip whitespace and translations should be pushed to transifex.

Translations

2015-02-12T11:57:29Z

Larjona: /* Fixing translations */ Add comment about the Pootle quality checks

= For translators =

<pre style="color: red;">This section has changed recently, since now Mediagoblin lives on Pootle.
Here you can find the basic information for translating.
For further details about using Pootle, please have a look at Pootle's Documentation:
http://docs.translatehouse.org/projects/pootle/en/stable-2.5.1/
or you can ask about more details using one of methods listed on http://mediagoblin.org/pages/join.html</pre>

It is very easy to add or complete the translation of MediaGoblin! We use the web interface provided by the GNU instance of Pootle to do the translations. You can see the current status of the translations per language [https://chapters.gnu.org/projects/mediagoblin/ here].

To start translating, just:

# If it's the first time you are translating in the GNU instance of Pootle, then [https://chapters.gnu.org/accounts/register/ register an account]. You will receive an email for activating your account.
# Then you can [https://chapters.gnu.org/accounts/login log in]
# Go to Projects > mediagoblin ([https://chapters.gnu.org/projects/mediagoblin/ direct URL] and click in your language
# Click on "Continue translation".

By default, Pootle only shows you strings that currently have no translation. You can click in the "Translate" tab to show the already translated strings, in case you want to improve any of them.
There are no translation teams, so you can just edit the strings (but try to be nice and consistent with the current translation). If you are a regular contributor to the translations, you might want to add some notes to the [[#Notes for some language teams|per-language section on this page]] to coordinate consistent translations.

Note: please don't translate the words "MediaGoblin" or "GNU" into your native language. Those words should be retained as-is for branding reasons. :)

== Notes for some language teams ==
=== German ===

Interessante Hinweise zur Übersetzung finden sich bei Gnome:
* http://live.gnome.org/de/UebersetzungsRichtlinien

In Abweichung von diesen Richtlinien wird momentan "Du" für die Anrede benutzt. "Du" und "Deine" werden groß geschrieben. Benutze die folgenden Begriffe um konsistent zu bleiben:

Benutzerkonto/Nutzerkonto, E-Mail, E-Mail-Adresse, Aktivierungsmail, Konto "aktivieren" (verify email), Album (collection), Kurztitel (slug)

=== Spanish ===

Se está adoptando la siguiente convención para la traducción al español. Si crees que alguna traducción se puede mejorar, sugiérela en la página de discusión de este artículo.

{|
!Inglés
!Español
!Comentarios
|-
|you
|tú
|(segunda persona del singular, expresión informal)
|-
|media
|contenido
|-
|slug
|ficha
|}

=== '''العربية''' ===

.سنتخذ الاصطلاحات التالية للترجمة العربية. إذا كنت تريد تحسين الترجمة يرجى اقتراح التغبرات في صفحة النقاش في هذا المقال
{|
!الانجليزية
!العربية
|-
|MediaGoblin .
|ميدياغوبلن
|-
|media .
|الميديا
|-
|slug .
|المسار
|}

==Fixing or improving translations ==

If you click in the "Overview" tab, you will see the status of the translation of MediaGoblin to your language. If you click on "Expand details" you will find some statistics and the results of several quality checks (about capitalization, punctuation matching or not the original and the translation) which may help you to fix or improve the translation.

= For developers =
== Marking strings for translation ==
=== In Jinja2 ===

See: http://jinja.pocoo.org/docs/templates/#i18n

Mostly like Django template i18n support, if you have any experience with that.

=== In python code ===

Usually, like this:

<pre>
from mediagoblin.util import pass_to_ugettext as _

def some_func(something):
return _(u'This string would tooootally be translatable now.')
</pre>

Except, in form modules we don't actually want to translate things because for various reasons that doesn't work, so we do the translation call template-side. So write the module to use the fake ugettext passthrough (which doesn't do any translation but still wraps things in _() so that Babel will know to extract these strings):

<pre>
from mediagoblin.util import fake_ugettext_passthrough as _

class FunkyMonkeyForm(wtforms.Form):
funky = wtforms.TextAreaField(
_('Funkiness description'))
</pre>

== Extracting translations ==

If you run buildout it should create a script called 'pybabel'. Use it to extract translations like so:

<pre>
./bin/pybabel extract -F babel.ini -o mediagoblin/i18n/en/LC_MESSAGES/mediagoblin.po .
</pre>

== Compiling translations ==

<pre>
./bin/pybabel compile -D mediagoblin -d mediagoblin/i18n/
</pre>

== Pulling translations from Transifex ==

Unfortunately until the next release of transifex-client which has been patched to have proper entry points, you have to run transifex-client from a virtualenv or from site-packages. But assuming that's done, pulling translations is easy:

<pre>
tx pull -a
</pre>

== Pushing new translations to Transifex ==

<pre>
tx push -s
</pre>

= Troubleshooting =

Got an error on Transifex like:

"Translation must start with a newline (\n)"?

The problem here is when we have something like:

{% trans register_url=request.urlgen('mediagoblin.auth.register') %}
<a class="header_submit_highlight" href="{{ register_url }}">Create a free account</a>
or
<a class="header_submit" href="http://wiki.mediagoblin.org/HackingHowto">Set up MediaGoblin on your own server</a>
{% endtrans %}

instead of:

{% trans register_url=request.urlgen('mediagoblin.auth.register') -%}
<a class="header_submit_highlight" href="{{ register_url }}">Create a free account</a>
or
<a class="header_submit" href="http://wiki.mediagoblin.org/HackingHowto">Set up MediaGoblin on your own server</a>
{%- endtrans %}

The distinction might not be obvious... look for the %} versus -%} and {% versus {%- on the first and last lines. The thing about this is this tells Jinja2 to strip the whitespace. Without that, Transifex sees that there's a "\n" on the first line of the original but not on the future translation, and gets upset.

If this happens the template should be updated to strip whitespace and translations should be pushed to transifex.

Translations

2015-02-12T11:49:58Z

Larjona: /* For translators */

= For translators =

<pre style="color: red;">This section has changed recently, since now Mediagoblin lives on Pootle.
Here you can find the basic information for translating.
For further details about using Pootle, please have a look at Pootle's Documentation:
http://docs.translatehouse.org/projects/pootle/en/stable-2.5.1/
or you can ask about more details using one of methods listed on http://mediagoblin.org/pages/join.html</pre>

It is very easy to add or complete the translation of MediaGoblin! We use the web interface provided by the GNU instance of Pootle to do the translations. You can see the current status of the translations per language [https://chapters.gnu.org/projects/mediagoblin/ here].

To start translating, just:

# If it's the first time you are translating in the GNU instance of Pootle, then [https://chapters.gnu.org/accounts/register/ register an account]. You will receive an email for activating your account.
# Then you can [https://chapters.gnu.org/accounts/login log in]
# Go to Projects > mediagoblin ([https://chapters.gnu.org/projects/mediagoblin/ direct URL] and click in your language
# Click on "Continue translation".

By default, Pootle only shows you strings that currently have no translation. You can click in the "Translate" tab to show the already translated strings, in case you want to improve any of them.
There are no translation teams, so you can just edit the strings (but try to be nice and consistent with the current translation). If you are a regular contributor to the translations, you might want to add some notes to the [[#Notes for some language teams|per-language section on this page]] to coordinate consistent translations.

Note: please don't translate the words "MediaGoblin" or "GNU" into your native language. Those words should be retained as-is for branding reasons. :)

== Notes for some language teams ==
=== German ===

Interessante Hinweise zur Übersetzung finden sich bei Gnome:
* http://live.gnome.org/de/UebersetzungsRichtlinien

In Abweichung von diesen Richtlinien wird momentan "Du" für die Anrede benutzt. "Du" und "Deine" werden groß geschrieben. Benutze die folgenden Begriffe um konsistent zu bleiben:

Benutzerkonto/Nutzerkonto, E-Mail, E-Mail-Adresse, Aktivierungsmail, Konto "aktivieren" (verify email), Album (collection), Kurztitel (slug)

=== Spanish ===

Se está adoptando la siguiente convención para la traducción al español. Si crees que alguna traducción se puede mejorar, sugiérela en la página de discusión de este artículo.

{|
!Inglés
!Español
!Comentarios
|-
|you
|tú
|(segunda persona del singular, expresión informal)
|-
|media
|contenido
|-
|slug
|ficha
|}

=== '''العربية''' ===

.سنتخذ الاصطلاحات التالية للترجمة العربية. إذا كنت تريد تحسين الترجمة يرجى اقتراح التغبرات في صفحة النقاش في هذا المقال
{|
!الانجليزية
!العربية
|-
|MediaGoblin .
|ميدياغوبلن
|-
|media .
|الميديا
|-
|slug .
|المسار
|}

==Fixing translations ==

= For developers =
== Marking strings for translation ==
=== In Jinja2 ===

See: http://jinja.pocoo.org/docs/templates/#i18n

Mostly like Django template i18n support, if you have any experience with that.

=== In python code ===

Usually, like this:

<pre>
from mediagoblin.util import pass_to_ugettext as _

def some_func(something):
return _(u'This string would tooootally be translatable now.')
</pre>

Except, in form modules we don't actually want to translate things because for various reasons that doesn't work, so we do the translation call template-side. So write the module to use the fake ugettext passthrough (which doesn't do any translation but still wraps things in _() so that Babel will know to extract these strings):

<pre>
from mediagoblin.util import fake_ugettext_passthrough as _

class FunkyMonkeyForm(wtforms.Form):
funky = wtforms.TextAreaField(
_('Funkiness description'))
</pre>

== Extracting translations ==

If you run buildout it should create a script called 'pybabel'. Use it to extract translations like so:

<pre>
./bin/pybabel extract -F babel.ini -o mediagoblin/i18n/en/LC_MESSAGES/mediagoblin.po .
</pre>

== Compiling translations ==

<pre>
./bin/pybabel compile -D mediagoblin -d mediagoblin/i18n/
</pre>

== Pulling translations from Transifex ==

Unfortunately until the next release of transifex-client which has been patched to have proper entry points, you have to run transifex-client from a virtualenv or from site-packages. But assuming that's done, pulling translations is easy:

<pre>
tx pull -a
</pre>

== Pushing new translations to Transifex ==

<pre>
tx push -s
</pre>

= Troubleshooting =

Got an error on Transifex like:

"Translation must start with a newline (\n)"?

The problem here is when we have something like:

{% trans register_url=request.urlgen('mediagoblin.auth.register') %}
<a class="header_submit_highlight" href="{{ register_url }}">Create a free account</a>
or
<a class="header_submit" href="http://wiki.mediagoblin.org/HackingHowto">Set up MediaGoblin on your own server</a>
{% endtrans %}

instead of:

{% trans register_url=request.urlgen('mediagoblin.auth.register') -%}
<a class="header_submit_highlight" href="{{ register_url }}">Create a free account</a>
or
<a class="header_submit" href="http://wiki.mediagoblin.org/HackingHowto">Set up MediaGoblin on your own server</a>
{%- endtrans %}

The distinction might not be obvious... look for the %} versus -%} and {% versus {%- on the first and last lines. The thing about this is this tells Jinja2 to strip the whitespace. Without that, Transifex sees that there's a "\n" on the first line of the original but not on the future translation, and gets upset.

If this happens the template should be updated to strip whitespace and translations should be pushed to transifex.

Translations

2015-02-12T11:49:41Z

Larjona: /* For translators */ Improve layout

= For translators =

<pre style="color: red;">This section has changed recently, since now Mediagoblin lives on Pootle.
Here you can find the basic information for translating.
For further details about using Pootle, please have a look at Pootle's Documentation:

http://docs.translatehouse.org/projects/pootle/en/stable-2.5.1/

or you can ask about more details using one of methods listed on http://mediagoblin.org/pages/join.html</pre>

It is very easy to add or complete the translation of MediaGoblin! We use the web interface provided by the GNU instance of Pootle to do the translations. You can see the current status of the translations per language [https://chapters.gnu.org/projects/mediagoblin/ here].

To start translating, just:

# If it's the first time you are translating in the GNU instance of Pootle, then [https://chapters.gnu.org/accounts/register/ register an account]. You will receive an email for activating your account.
# Then you can [https://chapters.gnu.org/accounts/login log in]
# Go to Projects > mediagoblin ([https://chapters.gnu.org/projects/mediagoblin/ direct URL] and click in your language
# Click on "Continue translation".

By default, Pootle only shows you strings that currently have no translation. You can click in the "Translate" tab to show the already translated strings, in case you want to improve any of them.
There are no translation teams, so you can just edit the strings (but try to be nice and consistent with the current translation). If you are a regular contributor to the translations, you might want to add some notes to the [[#Notes for some language teams|per-language section on this page]] to coordinate consistent translations.

Note: please don't translate the words "MediaGoblin" or "GNU" into your native language. Those words should be retained as-is for branding reasons. :)

== Notes for some language teams ==
=== German ===

Interessante Hinweise zur Übersetzung finden sich bei Gnome:
* http://live.gnome.org/de/UebersetzungsRichtlinien

In Abweichung von diesen Richtlinien wird momentan "Du" für die Anrede benutzt. "Du" und "Deine" werden groß geschrieben. Benutze die folgenden Begriffe um konsistent zu bleiben:

Benutzerkonto/Nutzerkonto, E-Mail, E-Mail-Adresse, Aktivierungsmail, Konto "aktivieren" (verify email), Album (collection), Kurztitel (slug)

=== Spanish ===

Se está adoptando la siguiente convención para la traducción al español. Si crees que alguna traducción se puede mejorar, sugiérela en la página de discusión de este artículo.

{|
!Inglés
!Español
!Comentarios
|-
|you
|tú
|(segunda persona del singular, expresión informal)
|-
|media
|contenido
|-
|slug
|ficha
|}

=== '''العربية''' ===

.سنتخذ الاصطلاحات التالية للترجمة العربية. إذا كنت تريد تحسين الترجمة يرجى اقتراح التغبرات في صفحة النقاش في هذا المقال
{|
!الانجليزية
!العربية
|-
|MediaGoblin .
|ميدياغوبلن
|-
|media .
|الميديا
|-
|slug .
|المسار
|}

==Fixing translations ==

= For developers =
== Marking strings for translation ==
=== In Jinja2 ===

See: http://jinja.pocoo.org/docs/templates/#i18n

Mostly like Django template i18n support, if you have any experience with that.

=== In python code ===

Usually, like this:

<pre>
from mediagoblin.util import pass_to_ugettext as _

def some_func(something):
return _(u'This string would tooootally be translatable now.')
</pre>

Except, in form modules we don't actually want to translate things because for various reasons that doesn't work, so we do the translation call template-side. So write the module to use the fake ugettext passthrough (which doesn't do any translation but still wraps things in _() so that Babel will know to extract these strings):

<pre>
from mediagoblin.util import fake_ugettext_passthrough as _

class FunkyMonkeyForm(wtforms.Form):
funky = wtforms.TextAreaField(
_('Funkiness description'))
</pre>

== Extracting translations ==

If you run buildout it should create a script called 'pybabel'. Use it to extract translations like so:

<pre>
./bin/pybabel extract -F babel.ini -o mediagoblin/i18n/en/LC_MESSAGES/mediagoblin.po .
</pre>

== Compiling translations ==

<pre>
./bin/pybabel compile -D mediagoblin -d mediagoblin/i18n/
</pre>

== Pulling translations from Transifex ==

Unfortunately until the next release of transifex-client which has been patched to have proper entry points, you have to run transifex-client from a virtualenv or from site-packages. But assuming that's done, pulling translations is easy:

<pre>
tx pull -a
</pre>

== Pushing new translations to Transifex ==

<pre>
tx push -s
</pre>

= Troubleshooting =

Got an error on Transifex like:

"Translation must start with a newline (\n)"?

The problem here is when we have something like:

{% trans register_url=request.urlgen('mediagoblin.auth.register') %}
<a class="header_submit_highlight" href="{{ register_url }}">Create a free account</a>
or
<a class="header_submit" href="http://wiki.mediagoblin.org/HackingHowto">Set up MediaGoblin on your own server</a>
{% endtrans %}

instead of:

{% trans register_url=request.urlgen('mediagoblin.auth.register') -%}
<a class="header_submit_highlight" href="{{ register_url }}">Create a free account</a>
or
<a class="header_submit" href="http://wiki.mediagoblin.org/HackingHowto">Set up MediaGoblin on your own server</a>
{%- endtrans %}

The distinction might not be obvious... look for the %} versus -%} and {% versus {%- on the first and last lines. The thing about this is this tells Jinja2 to strip the whitespace. Without that, Transifex sees that there's a "\n" on the first line of the original but not on the future translation, and gets upset.

If this happens the template should be updated to strip whitespace and translations should be pushed to transifex.

Translations

2015-02-12T11:48:54Z

Larjona: /* For translators */ Update the warning about this recently updated section

= For translators =

<pre style="color: red;">This section has changed recently, since now Mediagoblin lives on Pootle.
Here you can find the basic information for translating.
For further details about using Pootle, please [http://docs.translatehouse.org/projects/pootle/en/stable-2.5.1/ have a look at Pootle's Documentation], or you can ask about more details using one of methods listed on http://mediagoblin.org/pages/join.html</pre>

It is very easy to add or complete the translation of MediaGoblin! We use the web interface provided by the GNU instance of Pootle to do the translations. You can see the current status of the translations per language [https://chapters.gnu.org/projects/mediagoblin/ here].

To start translating, just:

# If it's the first time you are translating in the GNU instance of Pootle, then [https://chapters.gnu.org/accounts/register/ register an account]. You will receive an email for activating your account.
# Then you can [https://chapters.gnu.org/accounts/login log in]
# Go to Projects > mediagoblin ([https://chapters.gnu.org/projects/mediagoblin/ direct URL] and click in your language
# Click on "Continue translation".

By default, Pootle only shows you strings that currently have no translation. You can click in the "Translate" tab to show the already translated strings, in case you want to improve any of them.
There are no translation teams, so you can just edit the strings (but try to be nice and consistent with the current translation). If you are a regular contributor to the translations, you might want to add some notes to the [[#Notes for some language teams|per-language section on this page]] to coordinate consistent translations.

Note: please don't translate the words "MediaGoblin" or "GNU" into your native language. Those words should be retained as-is for branding reasons. :)

== Notes for some language teams ==
=== German ===

Interessante Hinweise zur Übersetzung finden sich bei Gnome:
* http://live.gnome.org/de/UebersetzungsRichtlinien

In Abweichung von diesen Richtlinien wird momentan "Du" für die Anrede benutzt. "Du" und "Deine" werden groß geschrieben. Benutze die folgenden Begriffe um konsistent zu bleiben:

Benutzerkonto/Nutzerkonto, E-Mail, E-Mail-Adresse, Aktivierungsmail, Konto "aktivieren" (verify email), Album (collection), Kurztitel (slug)

=== Spanish ===

Se está adoptando la siguiente convención para la traducción al español. Si crees que alguna traducción se puede mejorar, sugiérela en la página de discusión de este artículo.

{|
!Inglés
!Español
!Comentarios
|-
|you
|tú
|(segunda persona del singular, expresión informal)
|-
|media
|contenido
|-
|slug
|ficha
|}

=== '''العربية''' ===

.سنتخذ الاصطلاحات التالية للترجمة العربية. إذا كنت تريد تحسين الترجمة يرجى اقتراح التغبرات في صفحة النقاش في هذا المقال
{|
!الانجليزية
!العربية
|-
|MediaGoblin .
|ميدياغوبلن
|-
|media .
|الميديا
|-
|slug .
|المسار
|}

==Fixing translations ==

= For developers =
== Marking strings for translation ==
=== In Jinja2 ===

See: http://jinja.pocoo.org/docs/templates/#i18n

Mostly like Django template i18n support, if you have any experience with that.

=== In python code ===

Usually, like this:

<pre>
from mediagoblin.util import pass_to_ugettext as _

def some_func(something):
return _(u'This string would tooootally be translatable now.')
</pre>

Except, in form modules we don't actually want to translate things because for various reasons that doesn't work, so we do the translation call template-side. So write the module to use the fake ugettext passthrough (which doesn't do any translation but still wraps things in _() so that Babel will know to extract these strings):

<pre>
from mediagoblin.util import fake_ugettext_passthrough as _

class FunkyMonkeyForm(wtforms.Form):
funky = wtforms.TextAreaField(
_('Funkiness description'))
</pre>

== Extracting translations ==

If you run buildout it should create a script called 'pybabel'. Use it to extract translations like so:

<pre>
./bin/pybabel extract -F babel.ini -o mediagoblin/i18n/en/LC_MESSAGES/mediagoblin.po .
</pre>

== Compiling translations ==

<pre>
./bin/pybabel compile -D mediagoblin -d mediagoblin/i18n/
</pre>

== Pulling translations from Transifex ==

Unfortunately until the next release of transifex-client which has been patched to have proper entry points, you have to run transifex-client from a virtualenv or from site-packages. But assuming that's done, pulling translations is easy:

<pre>
tx pull -a
</pre>

== Pushing new translations to Transifex ==

<pre>
tx push -s
</pre>

= Troubleshooting =

Got an error on Transifex like:

"Translation must start with a newline (\n)"?

The problem here is when we have something like:

{% trans register_url=request.urlgen('mediagoblin.auth.register') %}
<a class="header_submit_highlight" href="{{ register_url }}">Create a free account</a>
or
<a class="header_submit" href="http://wiki.mediagoblin.org/HackingHowto">Set up MediaGoblin on your own server</a>
{% endtrans %}

instead of:

{% trans register_url=request.urlgen('mediagoblin.auth.register') -%}
<a class="header_submit_highlight" href="{{ register_url }}">Create a free account</a>
or
<a class="header_submit" href="http://wiki.mediagoblin.org/HackingHowto">Set up MediaGoblin on your own server</a>
{%- endtrans %}

The distinction might not be obvious... look for the %} versus -%} and {% versus {%- on the first and last lines. The thing about this is this tells Jinja2 to strip the whitespace. Without that, Transifex sees that there's a "\n" on the first line of the original but not on the future translation, and gets upset.

If this happens the template should be updated to strip whitespace and translations should be pushed to transifex.

Translations

2015-02-12T11:43:25Z

Larjona: /* For translators */ We have moved to Pootle

= For translators =

<pre style="color: red;">This section contains obsolete information. Now Mediagoblin lives on Pootle.
Before the section is updated, you can ask about the process using one of methods listed on
http://mediagoblin.org/pages/join.html</pre>

It is very easy to add or complete the translation of MediaGoblin! We use the web interface provided by the GNU instance of Pootle to do the translations. You can see the current status of the translations per language [https://chapters.gnu.org/projects/mediagoblin/ here].

To start translating, just:

# If it's the first time you are translating in the GNU instance of Pootle, then [https://chapters.gnu.org/accounts/register/ register an account]. You will receive an email for activating your account.
# If you already have your account, or just after activation, please [https://chapters.gnu.org/accounts/login log in]
# Then, go to Projects > mediagoblin ([https://chapters.gnu.org/projects/mediagoblin/ direct URL] and click in your language
# click on "Continue translation".

By default, Pootle only shows you strings that currently have no translation. You can click in the "Translate" tab to show the already translated strings, in case you want to improve any of them.
There are no translation teams, so you can just edit the strings (but try to be nice and consistent with the current translation). If you are a regular contributor to the translations, you might want to add some notes to the [[#Notes for some language teams|per-language section on this page]] to coordinate consistent translations.

Note: please don't translate the words "MediaGoblin" or "GNU" into your native language. Those words should be retained as-is for branding reasons. :)

== Notes for some language teams ==
=== German ===

Interessante Hinweise zur Übersetzung finden sich bei Gnome:
* http://live.gnome.org/de/UebersetzungsRichtlinien

In Abweichung von diesen Richtlinien wird momentan "Du" für die Anrede benutzt. "Du" und "Deine" werden groß geschrieben. Benutze die folgenden Begriffe um konsistent zu bleiben:

Benutzerkonto/Nutzerkonto, E-Mail, E-Mail-Adresse, Aktivierungsmail, Konto "aktivieren" (verify email), Album (collection), Kurztitel (slug)

=== Spanish ===

Se está adoptando la siguiente convención para la traducción al español. Si crees que alguna traducción se puede mejorar, sugiérela en la página de discusión de este artículo.

{|
!Inglés
!Español
!Comentarios
|-
|you
|tú
|(segunda persona del singular, expresión informal)
|-
|media
|contenido
|-
|slug
|ficha
|}

=== '''العربية''' ===

.سنتخذ الاصطلاحات التالية للترجمة العربية. إذا كنت تريد تحسين الترجمة يرجى اقتراح التغبرات في صفحة النقاش في هذا المقال
{|
!الانجليزية
!العربية
|-
|MediaGoblin .
|ميدياغوبلن
|-
|media .
|الميديا
|-
|slug .
|المسار
|}

==Fixing translations ==

= For developers =
== Marking strings for translation ==
=== In Jinja2 ===

See: http://jinja.pocoo.org/docs/templates/#i18n

Mostly like Django template i18n support, if you have any experience with that.

=== In python code ===

Usually, like this:

<pre>
from mediagoblin.util import pass_to_ugettext as _

def some_func(something):
return _(u'This string would tooootally be translatable now.')
</pre>

Except, in form modules we don't actually want to translate things because for various reasons that doesn't work, so we do the translation call template-side. So write the module to use the fake ugettext passthrough (which doesn't do any translation but still wraps things in _() so that Babel will know to extract these strings):

<pre>
from mediagoblin.util import fake_ugettext_passthrough as _

class FunkyMonkeyForm(wtforms.Form):
funky = wtforms.TextAreaField(
_('Funkiness description'))
</pre>

== Extracting translations ==

If you run buildout it should create a script called 'pybabel'. Use it to extract translations like so:

<pre>
./bin/pybabel extract -F babel.ini -o mediagoblin/i18n/en/LC_MESSAGES/mediagoblin.po .
</pre>

== Compiling translations ==

<pre>
./bin/pybabel compile -D mediagoblin -d mediagoblin/i18n/
</pre>

== Pulling translations from Transifex ==

Unfortunately until the next release of transifex-client which has been patched to have proper entry points, you have to run transifex-client from a virtualenv or from site-packages. But assuming that's done, pulling translations is easy:

<pre>
tx pull -a
</pre>

== Pushing new translations to Transifex ==

<pre>
tx push -s
</pre>

= Troubleshooting =

Got an error on Transifex like:

"Translation must start with a newline (\n)"?

The problem here is when we have something like:

{% trans register_url=request.urlgen('mediagoblin.auth.register') %}
<a class="header_submit_highlight" href="{{ register_url }}">Create a free account</a>
or
<a class="header_submit" href="http://wiki.mediagoblin.org/HackingHowto">Set up MediaGoblin on your own server</a>
{% endtrans %}

instead of:

{% trans register_url=request.urlgen('mediagoblin.auth.register') -%}
<a class="header_submit_highlight" href="{{ register_url }}">Create a free account</a>
or
<a class="header_submit" href="http://wiki.mediagoblin.org/HackingHowto">Set up MediaGoblin on your own server</a>
{%- endtrans %}

The distinction might not be obvious... look for the %} versus -%} and {% versus {%- on the first and last lines. The thing about this is this tells Jinja2 to strip the whitespace. Without that, Transifex sees that there's a "\n" on the first line of the original but not on the future translation, and gets upset.

If this happens the template should be updated to strip whitespace and translations should be pushed to transifex.

Search

2014-03-01T16:30:38Z

Larjona: Update page about 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)]

Campaign Sightings

2014-03-01T01:26:45Z

Larjona: /* Spanish */ Post in gnulinuxvagos.es

This page lists sightings of things that link to the campaign page at http://mediagoblin.org/pages/campaign.html for the 2014 campaign.

If you dented, tweeted, blogged about, or otherwise got a link to the campaign page, add a link to it on this page!

If you see something that's not listed on this page, add a link to it on this page!

Sightings for the previous campaign: [[Campaign Sightings/2012]].

=== English ===
* 2014-02-27: [http://libregraphicsworld.org/blog/entry/mediagoblin-launches-fundraiser-to-unite-distributed-media-platforms MediaGoblin launches fundraiser to unite distributed media platforms] (by AP)

* 2014-02-27: [http://blogs.gnome.org/gnomg/2014/02/27/support-mediagoblin/ Support MediaGoblin!] (by Karen Sandler)

* 2014-02-27: [http://fundraiser.pitivi.org/ Pitivi fundraiser campaign linking to MediaGoblin campaign]

=== Russian ===
* 2014-02-27: [http://www.opennet.ru/opennews/art.shtml?num=39210 Началась вторая кампания по сбору средств для MediaGoblin]

=== Spanish ===
* 2014-02-27: [http://elbinario.net/2014/02/27/campana-de-soporte-a-mediagoblin/ MediaGoblin apuesta de nuevo por CiviCRM en su Crowdfunding]

* 2014-02-27: [https://identi.ca/larjona/note/hClqIpW6QA6uHpfSFGx-EA Campaña de financiación MediaGoblin (pump.io note)]

* 2014-02-27: [https://twitter.com/larjona99/status/439041511444189184 Campaña de financiación MediaGoblin (tweet)]

* 2014-02-28: [http://gnulinuxvagos.es/topic/2661-campa%C3%B1a-mediagoblin-2014-por-la-federaci%C3%B3n-y-la-privacidad/ Campaña MediaGoblin 2014 por la federación y la privacidad]

Campaign Sightings

2014-03-01T01:22:57Z

Larjona: /* Spanish */ fixing external links

Campaign Sightings

2014-03-01T01:22:34Z

Larjona: /* English */ Add 2 more links

This page lists sightings of things that link to the campaign page at http://mediagoblin.org/pages/campaign.html for the 2014 campaign.

If you dented, tweeted, blogged about, or otherwise got a link to the campaign page, add a link to it on this page!

If you see something that's not listed on this page, add a link to it on this page!

Sightings for the previous campaign: [[Campaign Sightings/2012]].

=== English ===
* 2014-02-27: [http://libregraphicsworld.org/blog/entry/mediagoblin-launches-fundraiser-to-unite-distributed-media-platforms MediaGoblin launches fundraiser to unite distributed media platforms] (by AP)

* 2014-02-27: [http://blogs.gnome.org/gnomg/2014/02/27/support-mediagoblin/ Support MediaGoblin!] (by Karen Sandler)

* 2014-02-27: [http://fundraiser.pitivi.org/ Pitivi fundraiser campaign linking to MediaGoblin campaign]

=== Russian ===
* 2014-02-27: [http://www.opennet.ru/opennews/art.shtml?num=39210 Началась вторая кампания по сбору средств для MediaGoblin]

=== Spanish ===
* 2014-02-27: [http://elbinario.net/2014/02/27/campana-de-soporte-a-mediagoblin/](MediaGoblin apuesta de nuevo por CiviCRM en su Crowdfunding)

* 2014-02-27: [https://identi.ca/larjona/note/hClqIpW6QA6uHpfSFGx-EA Campaña de financiación MediaGoblin (pump.io note)]

* 2014-02-27: [https://twitter.com/larjona99/status/439041511444189184 Campaña de financiación MediaGoblin (tweet)]

Campaign Sightings

2014-02-28T21:52:15Z

Larjona: Add some links in Spanish

This page lists sightings of things that link to the campaign page at http://mediagoblin.org/pages/campaign.html for the 2014 campaign.

If you dented, tweeted, blogged about, or otherwise got a link to the campaign page, add a link to it on this page!

If you see something that's not listed on this page, add a link to it on this page!

Sightings for the previous campaign: [[Campaign Sightings/2012]].

=== English ===
* 2014-02-27: [http://libregraphicsworld.org/blog/entry/mediagoblin-launches-fundraiser-to-unite-distributed-media-platforms MediaGoblin launches fundraiser to unite distributed media platforms] (by AP)

=== Russian ===
* 2014-02-27: [http://www.opennet.ru/opennews/art.shtml?num=39210 Началась вторая кампания по сбору средств для MediaGoblin]

=== Spanish ===
* 2014-02-27: [http://elbinario.net/2014/02/27/campana-de-soporte-a-mediagoblin/](MediaGoblin apuesta de nuevo por CiviCRM en su Crowdfunding)

* 2014-02-27: [https://identi.ca/larjona/note/hClqIpW6QA6uHpfSFGx-EA Campaña de financiación MediaGoblin (pump.io note)]

* 2014-02-27: [https://twitter.com/larjona99/status/439041511444189184 Campaña de financiación MediaGoblin (tweet)]

Campaign Sightings/2012

2012-10-28T14:52:06Z

Larjona: Add links in Spanish

This page lists sightings of things that link to the campaign page at http://mediagoblin.org/pages/campaign.html .

If you dented, tweeted, blogged about, or otherwise got a link to the campaign page, add a link to it on this page!

If you see something that's not listed on this page, add a link to it on this page!

=== English ===
* “On the MediaGoblin fundraising campaign part 1: FSF vs Kickstarter” http://dustycloud.org/blog/mediagoblin-campaign (Chris Webber blog)
* “Donate to GNU MediaGoblin! Help us cross the chasm!” http://bluesock.org/~willg/blog/gmg/fundraising_2012.html (Will Kahn-Greene blog)
* “GNU MediaGoblin offers what you've been missing in an Internet media-sharing system” https://www.fsf.org/blogs/community/gnu-mediagoblin-offers-what-youve-been-missing-in-an-internet-media-sharing-system (Zak Rogoff in the FSF community blog)
* http://mail.chicagolug.org/ (Chicago GNU/Linux User Group)
* “FSF: Free media-sharing system picking up steam” https://lwn.net/Articles/520100/
* “GNU MediaGoblin is 25% into its FSF-backed crowdfunding campaign” http://www.fsdaily.com/Community/GNU_MediaGoblin_is_25_into_its_FSF_backed_crowdfunding_campaign at FSDaily
* “MediaGoblin: Saving the Internet Through Federation” http://www.linux-magazine.com/Online/Features/MediaGoblin-Saving-the-Internet-Through-Federation (by Bruce Byfield in Linux Magazine Online)

=== Russian ===
* https://www.linux.org.ru/news/gnu/8335276

=== German ===
* “Spende für MediaGoblin” http://oskar.twoday.net/stories/169431527/ (Oskar Welzl's blog)

=== Spanish ===
* ¡Apoya a MediaGoblin! (Spanish translation of the campaign) http://mediagoblin.org/pages/campaign.es.html
* "Por qué apoyo a GNU MediaGoblin" http://larjona.wordpress.com/2012/10/28/por-que-apoyo-a-gnu-mediagoblin/ (Laura Arjona's blog)