From GNU MediaGoblin Wiki
Jump to navigation Jump to search

MediaGoblin Monthly Meeting

At 16:00 UTC the first saturday of each month, unless otherwise announced on the mailing list, there is an IRC meeting. 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?

Upcoming and Recent Meetings

2012-02 (planned for 2012-02-04)

  • Where: IRC #mediagoblin on
  • When: Sat Feb 4 09:00:00 2012 Pacific Time (2012-02-04T17:00 UTC).

Preliminary Agenda:

Past Meetings

2011-12 (held 2011-12-03)

Preliminary Agenda (in progress):

  • We plan to create a plugin system. Do we want to create that soon or push it off until things settle a bit more? (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 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:
    • 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)

Preliminary Agenda and preliminary results (in progress):

  • 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
      • 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?
      • 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!)

IRC log

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

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)

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