GNU MediaGoblin Wiki - User contributions [en]

CommunityGovernance

2016-11-26T16:13:05Z

Helen Christian: /* MediaGoblin translation platform */ Added Fullstops.

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

* Current committers: https://savannah.gnu.org/project/memberlist.php?group=mediagoblin
* General stuff: breton, Elrond (via PM on IRC)
* Python 3 support: berkerpeksag (berker on IRC), breton
* Audio/Video: breton
* Documentation: jcampbell / j1mc

== MediaGoblin website ==

* People with permissions to handle website outages
** breton
** simonft
** Chris Webber (paroneayea on freenode)

* Publish pages (for example new releases)

== MediaGoblin wiki ==

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

== MediaGoblin issue tracker ==

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

== MediaGoblin translation platform ==

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

== MediaGoblin IRC channel and mailing list ==

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

Feature Ideas/Reprocessing

2016-11-26T16:09:15Z

Helen Christian: /* When should we try to reprocess? */ Added Fullstop.

See also: [[MediaTypeRefactor]]

== Rationale ==

In MediaGoblin, processing refers to the act of transforming an original media file in various ways to make it suitable to serve. For example, with images, we prepare resized versions for thumbnail and gallery views. With video, we capture a thumbnail frame, and transcode a medium-sized version for embedded viewing.

Normally, we process media as soon as we can after it's been uploaded to the site. Sometimes, we want to reprocess some media. There are a couple of reasons why this might happen:

* <p>The original processing attempt failed. This could be for lots of reasons: maybe a transcoding process was killed by a crazed sysadmin, or the file is corrupted, or there might even be a bug in MediaGoblin (crazy, I know!).</p><p>Right now, when this happens, the unprocessed media lives in the database forever, a zombie. Instead of that, we should periodically retry processing the media, when it makes sense. Maybe we'll have better luck next time; if we do, it'll make the user happy.</p>

* Something has changed on the site such that we ought to reprocess media that has already been processed. Maybe the administrator changed the size of thumbnail views, or in the future the MediaGoblin code will use a different audio codec. For an event like this, we need to reprocess all the affected existing media to make sure we can effectively serve them in the new way. These events should only take place when a site administrator requests it, and maybe when the site configuration changes to demand it.

Brett plans to work on this. If you want to help, get in touch! This is [http://issues.mediagoblin.org/ticket/420 bug #420].

== Reprocessing design ==

=== When should we try to reprocess? ===

If we're reprocessing media because previous attempts failed, we're likely to be more or less successful depending on ''why'' we failed. If we failed because the machine was low on memory or disk at the time, reprocessing stands a good chance of succeeding. If we failed because the media is corrupt, reprocessing will never work unless some code has changed in the meantime.

TODO: We should collect known cases of when processing failed, what it looked like. That will help us write code to determine why processing failed, and whether or not it's worthwhile to retry. (maybe this bug is a good start [http://issues.mediagoblin.org/ticket/438 bug#438] ?).

=== When should we start reprocessing? ===

There are two forces pushing us in different directions on this. On the one hand, the more often we retry, the sooner the user's media will appear on the site, which makes them happy. On the other hand, if we retry so often that not much can change between different attempts, we're just wasting computing resources to little end. This could hurt our general site performance on deployments without resources to spare, like SheevaPlugs or Raspberry Pi systems.

Like scheduling code in GNU/Linux, there are a million different ways we could approach this, and no one system is going to be perfect for every site. We should instead strive to give hosts the tools they need to easily configure MediaGoblin according to their needs and their desires.

The first piece of this puzzle is to make full use of Celery's task routing capabilities. Each task should use an exchange that indicates at least:

* the media type
* whether this processing is for
** a new upload
** retry after failed processing
** reprocessing at administrator request

With this framework in place, a host has the capability to configure Celery with different worker pools for each of these exchanges depending on their needs and preferences.

However, Celery doesn't handle scheduling of tasks outside the constraints of worker pools. It's up to us to decide, and write in the code, issues like how long to wait between reprocessing attempts and when to give up completely. (For version 1, I'm planning an exponential backoff algorithm with a maximum wait of 1 day. TODO: Should there be different configuration knobs for each media type? That's a lot more complexity, but it's pretty hard to argue against the idea that expectations for processing ASCII art should be different from processing video.) Key values should be stored in and read from the global MediaGoblin configuration.

TODO: Discuss (at a meeting?) general priorities about how we want to balance "users see their media ASAP" vs. general site performance out of the box. Get feedback about the version 1 scheme, and maybe get alternative proposals.

=== cwebber's vague thoughts ===

<nowiki>09:09 < paroneayea> I've been thinking vaguely about a few things related to
that like
09:10 < paroneayea> "what if you don't have the original anymore? Does it
reprocess it into something more lossy?"
09:11 < paroneayea> "Should we set it up so that things can determine
conditionally if they should be reprocessed? Ie, if
resolutions have changed, but this one was smaller than the
new lowest resolution anyway?"
09:11 < paroneayea> I'm not sure what the answer to those are but I've only
thought vaguely about them.</nowiki>

=== Shackra said... ===

Take in count the people using OpenStack for file storage. In case of re-encoding of audio files, for example, because MediaGoblin switched to ogg, will be impossible at least, if you deleted the original file and re-upload the new one.

== Reprocessing implementation ==

=== Base Task class ===

I think we can write a common subclass of Celery's Task that will serve as the base for all of our processing tasks. It would provide an <tt>on_failure</tt> method to decide whether or not a retry is appropriate, and if so, handle rewriting the exchange (to mark this as a retry), calculate the exponential backoff time, and reschedule the task.

This class could also serve as a unifying place to collect utility functions that many processing tasks need. There's a lot of file handling code that's repeated with minor variation throughout the processing tasks right now; that could be abstracted into methods of this class to reduce redundancy in the code.

=== Splitting up tasks ===

Right now, our processing tasks are monolithic beasts: one single task performs all of the transformations necessary for the media to be considered "processed." We could improve code readability and maintainability, site reliability, and possibly even performance by splitting tasks up appropriately.

The basic idea here is that each processing task would, after successful completion, queue up a "check if finished" task, which would in turn do quick checks to see if all the necessary results of processing are in place. When it finds that they are, it marks the media entry as processed, and performs clean-up jobs like removing the original queued file, so that the media shows up in the gallery and so on.

(Alternatively, the "check if finished" task could be more stateful, keeping track of which tasks fire it off, and then performing its own work when the last task reports in. This approach seems more fragile and error-prone, so I prefer an approach that checks whether the subtasks actually did their jobs, but that might not always be possible, so I'm making a note of this.)

As an example: image processing includes four jobs: making a thumbnail, a medium image, stashing the original file (with slight renaming as appropriate), and saving EXIF and GPS data to the database. These four tasks could each be run individually. They all fire a "check if finished" task that examines if the media entry has files stashed from all these tasks (in other words, it peeks at <tt>media_files_dict</tt>). When all the files are in place, it marks the entry as processed, and performs necessary cleanup.

We can potentially save a lot of work with this approach. Consider a video where transcoding succeeds but generating a thumbnail fails. By splitting tasks up, the resource-intensive transcoding will only run once, while we retry thumbnail generation appropriately.

== User visibility ==

After we have reprocessing code, logged in users should be able to see information about where their entries stand in the queue: it's going to be processed, it's going to be reprocessed by such-and-such time, it failed completely. There are already some bugs about this (TODO: collect them here). The current panel would be a good starting point for publishing this information generally. There are also specific places where we could conditionally show useful information: for instance, mention around the media submission page that the media might be slow to appear if processing queues are unusually large.

This is a big enough job that it could probably justify its own feature page...

Themes

2016-11-26T16:08:13Z

Helen Christian: Added Fullstop.

This page should list a bunch of user-created themes that are publicly available.

* [https://github.com/pztrn/stricted-mediagoblin-theme stricted] -- A clean, light'n'dark mediagoblin theme ([http://media.pztrn.ru/ example site]).

GSOC 2014

2016-11-26T16:06:41Z

Helen Christian: /* Port migrations to Alembic */ Added Fullstop

We are hoping to participate in GSOC 2014 under the GNU umbrella.

= Possible projects =

== Input, processing ==

=== Gstreamer audio/video code cleanup ===

Investigate and fix the issues with thumbnailing in the video processing pipeline. Investigate the rest of the gstreamer code, clean up and document.

Show progress on gstreamer pipeline.

=== Processing panel improvements ===

Could be combined with the above.

Better indication of the status of media processing. This includes better representation of current processing progress, as well as representation of possible errors.

=== Submission by email ===
https://issues.mediagoblin.org/ticket/663

== Output, media-specific stuff with user-facing parts ==

=== Client-side audio rendering ===

This one's a low-maybe on priorities, compared to others. The goal is to make it themable.

Switch the audio spectrogram rendering to be done on the user's end. During processing, the relevant data should be extracted and stored as metadata, but should be presented to the user.

(Could possibly be combined with the above two; student should talk to paroneayea on IRC before doing so and also get some sense of the existing processing code)

=== Media embedding and OEmbed support ===

=== Subtitles support ===
For video and audio. https://issues.mediagoblin.org/ticket/750

=== A way for a reader to see thumbnails/resized versions in other sizes ===
Generating multiple versions, like Flickr or MediaWiki can.
https://issues.mediagoblin.org/ticket/260

=== Support For Ogg Vorbis+Theora ===
https://issues.mediagoblin.org/ticket/567

== Multi-file output stuff ==

=== Podcasting support / new feed library? ===

Switch to or write a new feed library that is capable of handling enclosures and port MediaGoblin to it.

=== Nested collections ===
https://issues.mediagoblin.org/ticket/522

=== Slideshow ===
* For images? https://issues.mediagoblin.org/ticket/574
* Audio/video https://issues.mediagoblin.org/ticket/701

=== Enable "favoriting" of media ===
https://issues.mediagoblin.org/ticket/744
(compat see also: "Favoriting across instances" https://issues.mediagoblin.org/ticket/604 )

=== Cross-instance collections/galleries (think Flickr pool) ===
https://issues.mediagoblin.org/ticket/605

=== Tag clouds ===
https://issues.mediagoblin.org/ticket/183

== Port migrations to Alembic ==

Currently we use sqlalchemy-migrate, but it's fairly outdated and unmaintained.

Port the migration infrastructure to using [http://alembic.readthedocs.org/ Alembic] instead.

This includes making sure that sqlite can be continued to be used with MediaGoblin's migrations (which may require working on some upstream contributions... this is unclear at the time of writing).

== Import/export ==
* "Liberate my data" (data export button): https://issues.mediagoblin.org/ticket/600
* Import from Flickr (if not implemented yet; note also possible API changes): https://issues.mediagoblin.org/ticket/229

== Python 3 port ==

Port all of MediaGoblin's code to python 3: https://issues.mediagoblin.org/ticket/813

Design/Appearance

2016-11-26T16:05:15Z

Helen Christian: /* Logo */ Added Fullstop

This page describes MediaGoblin's appearance and style. If you're looking to contribute to its design, this is good reading material.

It is, however, '''not meant to be a definitive up-to-date guide'''. It serves as an introduction, but experiments with the design are common and the latest design specifications will always be found in the MediaGoblin software itself.

== Default theme ==

By default, MediaGoblin the software and many of the MediaGoblin websites use a dark, relatively neutral theme. While beauty is important, we try to keep the theme simple and avoid unnecessary decoration. One of the reasons for this is that we believe MediaGoblin itself should stay in the background and put media in the spotlight. Another is that this makes it easier for others to theme their own MediaGoblin instances, which is also why we try to use as little images as possible in the design.

* Text: we use a typeface called [http://www.google.com/webfonts/specimen/Lato Lato], created by Łukasz Dziedzic. The MediaGoblin logo is a custom design, though it takes hints from Lato.
* Background: a very dark grey with a slight texture. The texture was added to make it easier to distinguish the background from media with similar colors. Fallback color is #161616.
[[File:Background.png]]

The basic color palette used for MediaGoblin is shown below. Many other colors based on the same hues are also used.

{| class="wikitable" width="400px"
! Color || Hex || Sample || Used for e.g.
|-
| Text grey || #C3C3C3 || [[File:Color_text_grey.png]] || Body text
|-
| Pure white || #FFFFFF || [[File:Color_pure_white.png]] || Headers, logo
|-
| Highlight green || #86D4B1 || [[File:Color_highlight_green.png]] || Links, buttons
|-
| Faint red || #D49086 || [[File:Color_faint_red.png]] || Form headers
|}

== Light theme ==

Besides the regular theme, we've created a lighter version for use on the wiki, documentation and other places that might require reading longer pieces of text. It is meant to increase readability through the use of a black-on-white design and increased contrast.

Color differences include:

{| class="wikitable" width="400px"
! Color || Hex || Sample
|-
| A light background || #FCFCFC || [[File:Color_light_background.png]]
|-
| Dark text || #3C3C3C || [[File:Color_light_text.png]]
|-
| Black headers || #000000 || [[File:Color_light_headers.png]]
|-
| Adapted link color || #499776 || [[File:Color_light_link.png]]
|}

== Logo ==

Get and use the MediaGoblin logo at http://www.mediagoblin.org/pages/logo.html .

HackingHowto

2016-11-26T16:03:35Z

Helen Christian: /* Running a shell */ Added Fullstops.

= Hacking HOWTO =

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

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

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

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

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

Third you'll need to get the requirements.

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

== Python 2 vs Python 3 ==

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

=== Python 3 Issues ===

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

== Getting requirements ==

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

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

=== GNU/Linux ===

==== Debian and derivatives ====

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

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

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

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

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

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

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

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

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

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

{{Cmd|sudo yum update}}

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

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

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

once installed:

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

==== openSUSE ====

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

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

==== ArchLinux / Parabola ====

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

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

=== Mac OS X ===

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

Download the Newest Python.

Git is already installed.

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

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

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

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

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

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

=== Microsoft Windows ===

''Thanks wctype!''

==== Getting requirements ====

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

----

'''You can help:'''

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

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

'''Requirements'''

No additional requirements.

'''Create a development environment'''

After installing the requirements, follow these steps:

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

That's it!

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

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

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

== Updating an existing environment ==

'''Updating for dependency changes'''

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

To do that, run:

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

'''Updating for code changes'''

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

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

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

== Running the server ==

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

{{Cmd|./lazyserver.sh}}

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

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

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

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

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

== Running celeryd ==

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

Run:

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

== Running the test suite ==

Run:

{{Cmd|./runtests.sh}}

== Running a shell ==

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

Run:

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

== Troubleshooting ==

== Wiping your user data ==

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

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

'''Note:'''

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

== Quickstart for Django programmers ==

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

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

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

'''YouCanHelp'''

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

== Showing off your work with PageKite ==

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

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

== Bite-sized bugs to start with ==

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

API

2016-02-16T00:34:01Z

Helen Christian: /* Possible design problems. */ fullstop & spacing ; punctuation.

This page describes a JSON-based API for MediaGoblin. It is a '''WORK IN PROGRESS''' at the moment while it is being drafted before it gets implemented. Currently it only includes a submission API, based on a specific scenario which might not work in general for MediaGoblin but can be used as a springboard for further API improvements and specifications.

= Scenario. =

A MediaGoblin server (''MGS'') is used for media storage/repository on behalf of a few other servers, called user servers (''US'') . A user of one ''US'' submits a multimedia file. The file is sent to the ''MGS'' and categorized on the ''US'' in some server specific way. All future use of the multimedia file on the ''US'' is processed by the ''MGS''.

The collection of multimedia files from all of the ''US'''s is accessible through the ''MGS'' interface and through specific categorizations on each ''US'' via API or direct links to the content on the ''MGS''.

== Submission. ==

Since all files are processed automatically when they are uploaded there is no need for a specific submission api. Media files should therefore just be uploaded using a normal HTTP POST which is made available via the API using some sort of an authentication mechanism. An extra variable, containing a webhook/callback URL, can be sent alongside the file upload. The callback provides a URL to the file in the public store. The ''MGS'' allows the ''US'' to send metadata (for example license information) for the file.

The process is as follows:

# User fills in a form on a ''US''. The form is in fact based up of two forms
#* One for categorization on the ''US''
#* One is a file form for the ''MGS''
# ''US'' saves a pending object with the categorization
# The ''MGS'' processes the file as usual
# When the ''MGS'' has finished processing it notifies the ''US'' through a special callback url provided that the processing is finished and the file is available in the public store through a specific url
# ''US'' moves the object from a pending state to a real object with direct links (or api specific information which might be designed later) to the ''MGS''
# ''US'' sends metadata to attach to the file.

=== Callback/finished processing API. ===

The callback function of the ''US'' should read and accept MediaGoblin JSON objects according to the following proposed schema when sent to the callback url provided alongside the original upload:

<source lang="javascript">
{
"name":"Callback",
"properties":
{
"success":
{
"type":"boolean",
"description":"Boolean to indicate whether the processing of the file was successful or not",
"required":true
},
"message":
{
"type":"string",
"description":"Optional message used when processing was unsuccessful to explain the reason for the failure",
"required":false
},
"location":
{
"type":"array",
"required":true,
"description":"Array of locations for the processed file (or files, e.g. when video file is encoded into the three possible HTML5 video formats",
"items":
{
"type":"object",
"properties":
{
"mimetype":
{
"type":"string",
"description":"Mimetype to categorize the file",
"required":true,
},
"location":
{
"type":"string",
"format":"url",
"description":"URL of the file in the public store",
"required":true,
},
}
}
"mediatype":
{
"type":"string",
"description":"Media type of the file categorization, e.g. video, audio, image",
"required":false
}
}
}
</source>

The MediaGoblin expects status codes 204 (No content) on success (to imitate pubsubhubbub protocol) or normal error codes (4xx or 5xx) to indicate failures. It is possible to further define JSON objects in responses but probably unnecessary.

== Metadata. ==

It should be possible to add metadata to a specific file at any time. This could be information such as license information, related files (e.g. derivative work), views on site or something. In this case we only start with a Creative Commons license.

=== Metadata API. ===

A proposed json-based api to attach metadata to a file uploaded to a MediaGoblin instance. Other metadata information can be added later. This is just something to start with. It is necessary to check if the calling application is the same as the uploading application (to restrict others from setting metadata to other people's files).

The following is the JSON Schema for metadata:

<source lang="javascript">
{
"name":"Metadata",
"properties":
{
"file":
{
"type":"string",
"format":"url",
"description":"URL to the resource (file) to which metadata should be attached",
"required":true
},
"metadata":
{
"type":"array",
"description":"URL to the resource (file) to which metadata should be attached",
"required":true,
"items":
{
"type":"object",
"properties":
{
"creativecommons":
{
"type":"object",
"required":false,
"properties":
{
"author":
{
"type":"string",
"description":"Original author of the work, used for attribution",
"required":true,
},
"license":
{
"type":"string",
"format":"url",
"description":"URL pointing to the Creative Commons license used",
"required":true,
}
}
}
}
}
}
}
}
</source>

An example of a Claim in JSON would be (it remains to decide how to handle user uploads from sites where users aren't registerd on MediaGoblin):

<source lang="javascript">
{
"file":"http://media.goblin.com/u/artcollection/water-lilies.jpg",
"metadata":
[
"creativecommons":
{
"author":"Claude Monet",
"licence":"http://creativecommons.org/publicdomain/mark/1.0/"
}
]
}
</source>

== Possible design problems. ==

* MediaGoblin is user based but who is the user when files are sent in by users on a specific site ? Use OAuth/OpenID ? Perhaps tie closely with OStatus federation. Probably best to follow Twitter API where applications must be registered and get an API key for uploading.
* Mediatype for callback needs a better definition in the API (what can be sent, e.g. .).

API

2016-02-16T00:33:23Z

Helen Christian: /* Possible design problems */ fullstop punctuation.

This page describes a JSON-based API for MediaGoblin. It is a '''WORK IN PROGRESS''' at the moment while it is being drafted before it gets implemented. Currently it only includes a submission API, based on a specific scenario which might not work in general for MediaGoblin but can be used as a springboard for further API improvements and specifications.

= Scenario. =

A MediaGoblin server (''MGS'') is used for media storage/repository on behalf of a few other servers, called user servers (''US'') . A user of one ''US'' submits a multimedia file. The file is sent to the ''MGS'' and categorized on the ''US'' in some server specific way. All future use of the multimedia file on the ''US'' is processed by the ''MGS''.

The collection of multimedia files from all of the ''US'''s is accessible through the ''MGS'' interface and through specific categorizations on each ''US'' via API or direct links to the content on the ''MGS''.

== Submission. ==

Since all files are processed automatically when they are uploaded there is no need for a specific submission api. Media files should therefore just be uploaded using a normal HTTP POST which is made available via the API using some sort of an authentication mechanism. An extra variable, containing a webhook/callback URL, can be sent alongside the file upload. The callback provides a URL to the file in the public store. The ''MGS'' allows the ''US'' to send metadata (for example license information) for the file.

The process is as follows:

# User fills in a form on a ''US''. The form is in fact based up of two forms
#* One for categorization on the ''US''
#* One is a file form for the ''MGS''
# ''US'' saves a pending object with the categorization
# The ''MGS'' processes the file as usual
# When the ''MGS'' has finished processing it notifies the ''US'' through a special callback url provided that the processing is finished and the file is available in the public store through a specific url
# ''US'' moves the object from a pending state to a real object with direct links (or api specific information which might be designed later) to the ''MGS''
# ''US'' sends metadata to attach to the file.

=== Callback/finished processing API. ===

The callback function of the ''US'' should read and accept MediaGoblin JSON objects according to the following proposed schema when sent to the callback url provided alongside the original upload:

<source lang="javascript">
{
"name":"Callback",
"properties":
{
"success":
{
"type":"boolean",
"description":"Boolean to indicate whether the processing of the file was successful or not",
"required":true
},
"message":
{
"type":"string",
"description":"Optional message used when processing was unsuccessful to explain the reason for the failure",
"required":false
},
"location":
{
"type":"array",
"required":true,
"description":"Array of locations for the processed file (or files, e.g. when video file is encoded into the three possible HTML5 video formats",
"items":
{
"type":"object",
"properties":
{
"mimetype":
{
"type":"string",
"description":"Mimetype to categorize the file",
"required":true,
},
"location":
{
"type":"string",
"format":"url",
"description":"URL of the file in the public store",
"required":true,
},
}
}
"mediatype":
{
"type":"string",
"description":"Media type of the file categorization, e.g. video, audio, image",
"required":false
}
}
}
</source>

The MediaGoblin expects status codes 204 (No content) on success (to imitate pubsubhubbub protocol) or normal error codes (4xx or 5xx) to indicate failures. It is possible to further define JSON objects in responses but probably unnecessary.

== Metadata. ==

It should be possible to add metadata to a specific file at any time. This could be information such as license information, related files (e.g. derivative work), views on site or something. In this case we only start with a Creative Commons license.

=== Metadata API. ===

A proposed json-based api to attach metadata to a file uploaded to a MediaGoblin instance. Other metadata information can be added later. This is just something to start with. It is necessary to check if the calling application is the same as the uploading application (to restrict others from setting metadata to other people's files).

The following is the JSON Schema for metadata:

<source lang="javascript">
{
"name":"Metadata",
"properties":
{
"file":
{
"type":"string",
"format":"url",
"description":"URL to the resource (file) to which metadata should be attached",
"required":true
},
"metadata":
{
"type":"array",
"description":"URL to the resource (file) to which metadata should be attached",
"required":true,
"items":
{
"type":"object",
"properties":
{
"creativecommons":
{
"type":"object",
"required":false,
"properties":
{
"author":
{
"type":"string",
"description":"Original author of the work, used for attribution",
"required":true,
},
"license":
{
"type":"string",
"format":"url",
"description":"URL pointing to the Creative Commons license used",
"required":true,
}
}
}
}
}
}
}
}
</source>

An example of a Claim in JSON would be (it remains to decide how to handle user uploads from sites where users aren't registerd on MediaGoblin):

<source lang="javascript">
{
"file":"http://media.goblin.com/u/artcollection/water-lilies.jpg",
"metadata":
[
"creativecommons":
{
"author":"Claude Monet",
"licence":"http://creativecommons.org/publicdomain/mark/1.0/"
}
]
}
</source>

== Possible design problems. ==

* MediaGoblin is user based but who is the user when files are sent in by users on a specific site? Use OAuth/OpenID? Perhaps tie closely with OStatus federation. Probably best to follow Twitter API where applications must be registered and get an API key for uploading.
* Mediatype for callback needs a better definition in the API (what can be sent, e.g. .)

API

2016-02-16T00:32:59Z

Helen Christian: /* Metadata */ fullstop punctuation.

This page describes a JSON-based API for MediaGoblin. It is a '''WORK IN PROGRESS''' at the moment while it is being drafted before it gets implemented. Currently it only includes a submission API, based on a specific scenario which might not work in general for MediaGoblin but can be used as a springboard for further API improvements and specifications.

= Scenario. =

A MediaGoblin server (''MGS'') is used for media storage/repository on behalf of a few other servers, called user servers (''US'') . A user of one ''US'' submits a multimedia file. The file is sent to the ''MGS'' and categorized on the ''US'' in some server specific way. All future use of the multimedia file on the ''US'' is processed by the ''MGS''.

The collection of multimedia files from all of the ''US'''s is accessible through the ''MGS'' interface and through specific categorizations on each ''US'' via API or direct links to the content on the ''MGS''.

== Submission. ==

Since all files are processed automatically when they are uploaded there is no need for a specific submission api. Media files should therefore just be uploaded using a normal HTTP POST which is made available via the API using some sort of an authentication mechanism. An extra variable, containing a webhook/callback URL, can be sent alongside the file upload. The callback provides a URL to the file in the public store. The ''MGS'' allows the ''US'' to send metadata (for example license information) for the file.

The process is as follows:

# User fills in a form on a ''US''. The form is in fact based up of two forms
#* One for categorization on the ''US''
#* One is a file form for the ''MGS''
# ''US'' saves a pending object with the categorization
# The ''MGS'' processes the file as usual
# When the ''MGS'' has finished processing it notifies the ''US'' through a special callback url provided that the processing is finished and the file is available in the public store through a specific url
# ''US'' moves the object from a pending state to a real object with direct links (or api specific information which might be designed later) to the ''MGS''
# ''US'' sends metadata to attach to the file.

=== Callback/finished processing API. ===

The callback function of the ''US'' should read and accept MediaGoblin JSON objects according to the following proposed schema when sent to the callback url provided alongside the original upload:

<source lang="javascript">
{
"name":"Callback",
"properties":
{
"success":
{
"type":"boolean",
"description":"Boolean to indicate whether the processing of the file was successful or not",
"required":true
},
"message":
{
"type":"string",
"description":"Optional message used when processing was unsuccessful to explain the reason for the failure",
"required":false
},
"location":
{
"type":"array",
"required":true,
"description":"Array of locations for the processed file (or files, e.g. when video file is encoded into the three possible HTML5 video formats",
"items":
{
"type":"object",
"properties":
{
"mimetype":
{
"type":"string",
"description":"Mimetype to categorize the file",
"required":true,
},
"location":
{
"type":"string",
"format":"url",
"description":"URL of the file in the public store",
"required":true,
},
}
}
"mediatype":
{
"type":"string",
"description":"Media type of the file categorization, e.g. video, audio, image",
"required":false
}
}
}
</source>

The MediaGoblin expects status codes 204 (No content) on success (to imitate pubsubhubbub protocol) or normal error codes (4xx or 5xx) to indicate failures. It is possible to further define JSON objects in responses but probably unnecessary.

== Metadata. ==

It should be possible to add metadata to a specific file at any time. This could be information such as license information, related files (e.g. derivative work), views on site or something. In this case we only start with a Creative Commons license.

=== Metadata API. ===

A proposed json-based api to attach metadata to a file uploaded to a MediaGoblin instance. Other metadata information can be added later. This is just something to start with. It is necessary to check if the calling application is the same as the uploading application (to restrict others from setting metadata to other people's files).

The following is the JSON Schema for metadata:

<source lang="javascript">
{
"name":"Metadata",
"properties":
{
"file":
{
"type":"string",
"format":"url",
"description":"URL to the resource (file) to which metadata should be attached",
"required":true
},
"metadata":
{
"type":"array",
"description":"URL to the resource (file) to which metadata should be attached",
"required":true,
"items":
{
"type":"object",
"properties":
{
"creativecommons":
{
"type":"object",
"required":false,
"properties":
{
"author":
{
"type":"string",
"description":"Original author of the work, used for attribution",
"required":true,
},
"license":
{
"type":"string",
"format":"url",
"description":"URL pointing to the Creative Commons license used",
"required":true,
}
}
}
}
}
}
}
}
</source>

An example of a Claim in JSON would be (it remains to decide how to handle user uploads from sites where users aren't registerd on MediaGoblin):

<source lang="javascript">
{
"file":"http://media.goblin.com/u/artcollection/water-lilies.jpg",
"metadata":
[
"creativecommons":
{
"author":"Claude Monet",
"licence":"http://creativecommons.org/publicdomain/mark/1.0/"
}
]
}
</source>

== Possible design problems ==

* MediaGoblin is user based but who is the user when files are sent in by users on a specific site? Use OAuth/OpenID? Perhaps tie closely with OStatus federation. Probably best to follow Twitter API where applications must be registered and get an API key for uploading.
* Mediatype for callback needs a better definition in the API (what can be sent, e.g. .)

API

2016-02-16T00:32:35Z

Helen Christian: /* Callback/finished processing API */ fullstop punctuation.

This page describes a JSON-based API for MediaGoblin. It is a '''WORK IN PROGRESS''' at the moment while it is being drafted before it gets implemented. Currently it only includes a submission API, based on a specific scenario which might not work in general for MediaGoblin but can be used as a springboard for further API improvements and specifications.

= Scenario. =

A MediaGoblin server (''MGS'') is used for media storage/repository on behalf of a few other servers, called user servers (''US'') . A user of one ''US'' submits a multimedia file. The file is sent to the ''MGS'' and categorized on the ''US'' in some server specific way. All future use of the multimedia file on the ''US'' is processed by the ''MGS''.

The collection of multimedia files from all of the ''US'''s is accessible through the ''MGS'' interface and through specific categorizations on each ''US'' via API or direct links to the content on the ''MGS''.

== Submission. ==

Since all files are processed automatically when they are uploaded there is no need for a specific submission api. Media files should therefore just be uploaded using a normal HTTP POST which is made available via the API using some sort of an authentication mechanism. An extra variable, containing a webhook/callback URL, can be sent alongside the file upload. The callback provides a URL to the file in the public store. The ''MGS'' allows the ''US'' to send metadata (for example license information) for the file.

The process is as follows:

# User fills in a form on a ''US''. The form is in fact based up of two forms
#* One for categorization on the ''US''
#* One is a file form for the ''MGS''
# ''US'' saves a pending object with the categorization
# The ''MGS'' processes the file as usual
# When the ''MGS'' has finished processing it notifies the ''US'' through a special callback url provided that the processing is finished and the file is available in the public store through a specific url
# ''US'' moves the object from a pending state to a real object with direct links (or api specific information which might be designed later) to the ''MGS''
# ''US'' sends metadata to attach to the file.

=== Callback/finished processing API. ===

The callback function of the ''US'' should read and accept MediaGoblin JSON objects according to the following proposed schema when sent to the callback url provided alongside the original upload:

<source lang="javascript">
{
"name":"Callback",
"properties":
{
"success":
{
"type":"boolean",
"description":"Boolean to indicate whether the processing of the file was successful or not",
"required":true
},
"message":
{
"type":"string",
"description":"Optional message used when processing was unsuccessful to explain the reason for the failure",
"required":false
},
"location":
{
"type":"array",
"required":true,
"description":"Array of locations for the processed file (or files, e.g. when video file is encoded into the three possible HTML5 video formats",
"items":
{
"type":"object",
"properties":
{
"mimetype":
{
"type":"string",
"description":"Mimetype to categorize the file",
"required":true,
},
"location":
{
"type":"string",
"format":"url",
"description":"URL of the file in the public store",
"required":true,
},
}
}
"mediatype":
{
"type":"string",
"description":"Media type of the file categorization, e.g. video, audio, image",
"required":false
}
}
}
</source>

The MediaGoblin expects status codes 204 (No content) on success (to imitate pubsubhubbub protocol) or normal error codes (4xx or 5xx) to indicate failures. It is possible to further define JSON objects in responses but probably unnecessary.

== Metadata ==

It should be possible to add metadata to a specific file at any time. This could be information such as license information, related files (e.g. derivative work), views on site or something. In this case we only start with a Creative Commons license.

=== Metadata API ===

A proposed json-based api to attach metadata to a file uploaded to a MediaGoblin instance. Other metadata information can be added later. This is just something to start with. It is necessary to check if the calling application is the same as the uploading application (to restrict others from setting metadata to other people's files).

The following is the JSON Schema for metadata:

<source lang="javascript">
{
"name":"Metadata",
"properties":
{
"file":
{
"type":"string",
"format":"url",
"description":"URL to the resource (file) to which metadata should be attached",
"required":true
},
"metadata":
{
"type":"array",
"description":"URL to the resource (file) to which metadata should be attached",
"required":true,
"items":
{
"type":"object",
"properties":
{
"creativecommons":
{
"type":"object",
"required":false,
"properties":
{
"author":
{
"type":"string",
"description":"Original author of the work, used for attribution",
"required":true,
},
"license":
{
"type":"string",
"format":"url",
"description":"URL pointing to the Creative Commons license used",
"required":true,
}
}
}
}
}
}
}
}
</source>

An example of a Claim in JSON would be (it remains to decide how to handle user uploads from sites where users aren't registerd on MediaGoblin):

<source lang="javascript">
{
"file":"http://media.goblin.com/u/artcollection/water-lilies.jpg",
"metadata":
[
"creativecommons":
{
"author":"Claude Monet",
"licence":"http://creativecommons.org/publicdomain/mark/1.0/"
}
]
}
</source>

== Possible design problems ==

* MediaGoblin is user based but who is the user when files are sent in by users on a specific site? Use OAuth/OpenID? Perhaps tie closely with OStatus federation. Probably best to follow Twitter API where applications must be registered and get an API key for uploading.
* Mediatype for callback needs a better definition in the API (what can be sent, e.g. .)

API

2016-02-16T00:32:21Z

Helen Christian: /* Submission */ fullstop punctuation.

This page describes a JSON-based API for MediaGoblin. It is a '''WORK IN PROGRESS''' at the moment while it is being drafted before it gets implemented. Currently it only includes a submission API, based on a specific scenario which might not work in general for MediaGoblin but can be used as a springboard for further API improvements and specifications.

= Scenario. =

A MediaGoblin server (''MGS'') is used for media storage/repository on behalf of a few other servers, called user servers (''US'') . A user of one ''US'' submits a multimedia file. The file is sent to the ''MGS'' and categorized on the ''US'' in some server specific way. All future use of the multimedia file on the ''US'' is processed by the ''MGS''.

The collection of multimedia files from all of the ''US'''s is accessible through the ''MGS'' interface and through specific categorizations on each ''US'' via API or direct links to the content on the ''MGS''.

== Submission. ==

Since all files are processed automatically when they are uploaded there is no need for a specific submission api. Media files should therefore just be uploaded using a normal HTTP POST which is made available via the API using some sort of an authentication mechanism. An extra variable, containing a webhook/callback URL, can be sent alongside the file upload. The callback provides a URL to the file in the public store. The ''MGS'' allows the ''US'' to send metadata (for example license information) for the file.

The process is as follows:

# User fills in a form on a ''US''. The form is in fact based up of two forms
#* One for categorization on the ''US''
#* One is a file form for the ''MGS''
# ''US'' saves a pending object with the categorization
# The ''MGS'' processes the file as usual
# When the ''MGS'' has finished processing it notifies the ''US'' through a special callback url provided that the processing is finished and the file is available in the public store through a specific url
# ''US'' moves the object from a pending state to a real object with direct links (or api specific information which might be designed later) to the ''MGS''
# ''US'' sends metadata to attach to the file.

=== Callback/finished processing API ===

The callback function of the ''US'' should read and accept MediaGoblin JSON objects according to the following proposed schema when sent to the callback url provided alongside the original upload:

<source lang="javascript">
{
"name":"Callback",
"properties":
{
"success":
{
"type":"boolean",
"description":"Boolean to indicate whether the processing of the file was successful or not",
"required":true
},
"message":
{
"type":"string",
"description":"Optional message used when processing was unsuccessful to explain the reason for the failure",
"required":false
},
"location":
{
"type":"array",
"required":true,
"description":"Array of locations for the processed file (or files, e.g. when video file is encoded into the three possible HTML5 video formats",
"items":
{
"type":"object",
"properties":
{
"mimetype":
{
"type":"string",
"description":"Mimetype to categorize the file",
"required":true,
},
"location":
{
"type":"string",
"format":"url",
"description":"URL of the file in the public store",
"required":true,
},
}
}
"mediatype":
{
"type":"string",
"description":"Media type of the file categorization, e.g. video, audio, image",
"required":false
}
}
}
</source>

The MediaGoblin expects status codes 204 (No content) on success (to imitate pubsubhubbub protocol) or normal error codes (4xx or 5xx) to indicate failures. It is possible to further define JSON objects in responses but probably unnecessary.

== Metadata ==

It should be possible to add metadata to a specific file at any time. This could be information such as license information, related files (e.g. derivative work), views on site or something. In this case we only start with a Creative Commons license.

=== Metadata API ===

A proposed json-based api to attach metadata to a file uploaded to a MediaGoblin instance. Other metadata information can be added later. This is just something to start with. It is necessary to check if the calling application is the same as the uploading application (to restrict others from setting metadata to other people's files).

The following is the JSON Schema for metadata:

<source lang="javascript">
{
"name":"Metadata",
"properties":
{
"file":
{
"type":"string",
"format":"url",
"description":"URL to the resource (file) to which metadata should be attached",
"required":true
},
"metadata":
{
"type":"array",
"description":"URL to the resource (file) to which metadata should be attached",
"required":true,
"items":
{
"type":"object",
"properties":
{
"creativecommons":
{
"type":"object",
"required":false,
"properties":
{
"author":
{
"type":"string",
"description":"Original author of the work, used for attribution",
"required":true,
},
"license":
{
"type":"string",
"format":"url",
"description":"URL pointing to the Creative Commons license used",
"required":true,
}
}
}
}
}
}
}
}
</source>

An example of a Claim in JSON would be (it remains to decide how to handle user uploads from sites where users aren't registerd on MediaGoblin):

<source lang="javascript">
{
"file":"http://media.goblin.com/u/artcollection/water-lilies.jpg",
"metadata":
[
"creativecommons":
{
"author":"Claude Monet",
"licence":"http://creativecommons.org/publicdomain/mark/1.0/"
}
]
}
</source>

== Possible design problems ==

* MediaGoblin is user based but who is the user when files are sent in by users on a specific site? Use OAuth/OpenID? Perhaps tie closely with OStatus federation. Probably best to follow Twitter API where applications must be registered and get an API key for uploading.
* Mediatype for callback needs a better definition in the API (what can be sent, e.g. .)

API

2016-02-16T00:32:06Z

Helen Christian: /* Scenario */ fullstop punctuation.

This page describes a JSON-based API for MediaGoblin. It is a '''WORK IN PROGRESS''' at the moment while it is being drafted before it gets implemented. Currently it only includes a submission API, based on a specific scenario which might not work in general for MediaGoblin but can be used as a springboard for further API improvements and specifications.

= Scenario. =

A MediaGoblin server (''MGS'') is used for media storage/repository on behalf of a few other servers, called user servers (''US'') . A user of one ''US'' submits a multimedia file. The file is sent to the ''MGS'' and categorized on the ''US'' in some server specific way. All future use of the multimedia file on the ''US'' is processed by the ''MGS''.

The collection of multimedia files from all of the ''US'''s is accessible through the ''MGS'' interface and through specific categorizations on each ''US'' via API or direct links to the content on the ''MGS''.

== Submission ==

Since all files are processed automatically when they are uploaded there is no need for a specific submission api. Media files should therefore just be uploaded using a normal HTTP POST which is made available via the API using some sort of an authentication mechanism. An extra variable, containing a webhook/callback URL, can be sent alongside the file upload. The callback provides a URL to the file in the public store. The ''MGS'' allows the ''US'' to send metadata (for example license information) for the file.

The process is as follows:

# User fills in a form on a ''US''. The form is in fact based up of two forms
#* One for categorization on the ''US''
#* One is a file form for the ''MGS''
# ''US'' saves a pending object with the categorization
# The ''MGS'' processes the file as usual
# When the ''MGS'' has finished processing it notifies the ''US'' through a special callback url provided that the processing is finished and the file is available in the public store through a specific url
# ''US'' moves the object from a pending state to a real object with direct links (or api specific information which might be designed later) to the ''MGS''
# ''US'' sends metadata to attach to the file.

=== Callback/finished processing API ===

The callback function of the ''US'' should read and accept MediaGoblin JSON objects according to the following proposed schema when sent to the callback url provided alongside the original upload:

<source lang="javascript">
{
"name":"Callback",
"properties":
{
"success":
{
"type":"boolean",
"description":"Boolean to indicate whether the processing of the file was successful or not",
"required":true
},
"message":
{
"type":"string",
"description":"Optional message used when processing was unsuccessful to explain the reason for the failure",
"required":false
},
"location":
{
"type":"array",
"required":true,
"description":"Array of locations for the processed file (or files, e.g. when video file is encoded into the three possible HTML5 video formats",
"items":
{
"type":"object",
"properties":
{
"mimetype":
{
"type":"string",
"description":"Mimetype to categorize the file",
"required":true,
},
"location":
{
"type":"string",
"format":"url",
"description":"URL of the file in the public store",
"required":true,
},
}
}
"mediatype":
{
"type":"string",
"description":"Media type of the file categorization, e.g. video, audio, image",
"required":false
}
}
}
</source>

The MediaGoblin expects status codes 204 (No content) on success (to imitate pubsubhubbub protocol) or normal error codes (4xx or 5xx) to indicate failures. It is possible to further define JSON objects in responses but probably unnecessary.

== Metadata ==

It should be possible to add metadata to a specific file at any time. This could be information such as license information, related files (e.g. derivative work), views on site or something. In this case we only start with a Creative Commons license.

=== Metadata API ===

A proposed json-based api to attach metadata to a file uploaded to a MediaGoblin instance. Other metadata information can be added later. This is just something to start with. It is necessary to check if the calling application is the same as the uploading application (to restrict others from setting metadata to other people's files).

The following is the JSON Schema for metadata:

<source lang="javascript">
{
"name":"Metadata",
"properties":
{
"file":
{
"type":"string",
"format":"url",
"description":"URL to the resource (file) to which metadata should be attached",
"required":true
},
"metadata":
{
"type":"array",
"description":"URL to the resource (file) to which metadata should be attached",
"required":true,
"items":
{
"type":"object",
"properties":
{
"creativecommons":
{
"type":"object",
"required":false,
"properties":
{
"author":
{
"type":"string",
"description":"Original author of the work, used for attribution",
"required":true,
},
"license":
{
"type":"string",
"format":"url",
"description":"URL pointing to the Creative Commons license used",
"required":true,
}
}
}
}
}
}
}
}
</source>

An example of a Claim in JSON would be (it remains to decide how to handle user uploads from sites where users aren't registerd on MediaGoblin):

<source lang="javascript">
{
"file":"http://media.goblin.com/u/artcollection/water-lilies.jpg",
"metadata":
[
"creativecommons":
{
"author":"Claude Monet",
"licence":"http://creativecommons.org/publicdomain/mark/1.0/"
}
]
}
</source>

== Possible design problems ==

* MediaGoblin is user based but who is the user when files are sent in by users on a specific site? Use OAuth/OpenID? Perhaps tie closely with OStatus federation. Probably best to follow Twitter API where applications must be registered and get an API key for uploading.
* Mediatype for callback needs a better definition in the API (what can be sent, e.g. .)

MediaGoblin.org v2

2016-02-16T00:31:26Z

Helen Christian: /* Reasons for the redesign. */ spacing punctuation.

This page tracks the MediaGoblin.org website redesign and is maintained by [[User:schendje|schendje]].

== Reasons for the redesign. ==

I was also the one who created the current [http://www.mediagoblin.org MediaGoblin.org] design. However, it could use some serious updating. I had several things I wish to see improve :

* '''Immediately and clearly explain what MediaGoblin is and what it does.''' I do not think this is clear at all on our current homepage. It begins with "The perfect tool to show and share your media ! " which sounds positive, but doesn't really explain anything. It goes on with four more bullet points, about the community and the GNU project among other things, but none of these provide any information about MediaGoblin's functionality.

* '''Provide an easier way to get started with MediaGoblin.''' The current design has a big line of text in the middle saying "Get started with the latest MediaGoblin release", which seems pretty straightforward. But then it provides you with three choices, or maybe three steps, and it is unclear which one you should pick or start with.

* '''Remove the need for a separate tour page.''' Currently, we point visitors to our Tour page to learn more. This page contains plenty of information and screenshots, which is good. However, I think it would me more effective if MediaGoblin was introduced like this right on the homepage. Therefore, I wanted to combine the homepage and the tour page into a single page.

The homepage should also contain other information, such as links to the repository and [http://issues.mediagoblin.org/ bug tracker], but in my opinion its primary function should be to explain what MediaGoblin is and to get people started with it quickly.

== Request for feedback. ==

One of the reasons I created this page was to gather feedback. If you are interested, please keep checking this page for any updates and let me ([[User:schendje|schendje]]) know what you think. The best place to reach me would be the MediaGoblin IRC channel, which is also where I'll announce any updates.

'''Quick note #1:''' these mockups are free for you to adapt. A picture is worth a thousand words so if you'd like to change something, download and edit the [http://schendje.fedorapeople.org/goblin/homepage/wireframe.svg SVG source file] and show it around!

'''Quick note #2:''' virtually all of the copy in the current mockups is placeholder text. Therefore, comments on the content of the page will not yet be of much use. I will be working on replacing it with proper copy as soon as possible, so we can also gather feedback on that part of the design.

== Mockups (most recent one at the top). ==

=== Third iteration. ===

http://schendje.fedorapeople.org/goblin/homepage/wireframe3.png

* Almost the same as previous, but added screenshots.
* A short explanation for this layout: http://schendje.fedorapeople.org/goblin/homepage/layout_explained.png

Questions:
* Is it obvious that the images are screenshots ? They can of course be clicked to show a bigger version.
* What is a good position for the "quick links" ? They will be in the top corner on any other page on the website, but I think they may demand too much attention if we put them at the top of the homepage as well.

=== Second iteration. ===
* Slightly higher fidelity.
* Includes several changes to the layout.

http://schendje.fedorapeople.org/goblin/homepage/wireframe2.png

=== First iteration. ===
A first low-fidelity wireframe: http://schendje.fedorapeople.org/goblin/homepage/wireframe.png

=== Old design. ===

A mockup of the current [https://wiki.mediagoblin.org/Main_Page MediaGoblin.org] design: http://schendje.fedorapeople.org/goblin/homepage/final.png

MediaGoblin.org v2

2016-02-16T00:30:35Z

Helen Christian: /* Mockups (most recent one at the top). */ fullstops punctuation.

This page tracks the MediaGoblin.org website redesign and is maintained by [[User:schendje|schendje]].

== Reasons for the redesign. ==

I was also the one who created the current [http://www.mediagoblin.org MediaGoblin.org] design. However, it could use some serious updating. I had several things I wish to see improve :

* '''Immediately and clearly explain what MediaGoblin is and what it does.''' I do not think this is clear at all on our current homepage. It begins with "The perfect tool to show and share your media !" which sounds positive, but doesn't really explain anything. It goes on with four more bullet points, about the community and the GNU project among other things, but none of these provide any information about MediaGoblin's functionality.

* '''Provide an easier way to get started with MediaGoblin.''' The current design has a big line of text in the middle saying "Get started with the latest MediaGoblin release", which seems pretty straightforward. But then it provides you with three choices, or maybe three steps, and it is unclear which one you should pick or start with.

* '''Remove the need for a separate tour page.''' Currently, we point visitors to our Tour page to learn more. This page contains plenty of information and screenshots, which is good. However, I think it would me more effective if MediaGoblin was introduced like this right on the homepage. Therefore, I wanted to combine the homepage and the tour page into a single page.

The homepage should also contain other information, such as links to the repository and [http://issues.mediagoblin.org/ bug tracker], but in my opinion its primary function should be to explain what MediaGoblin is and to get people started with it quickly.

== Request for feedback. ==

One of the reasons I created this page was to gather feedback. If you are interested, please keep checking this page for any updates and let me ([[User:schendje|schendje]]) know what you think. The best place to reach me would be the MediaGoblin IRC channel, which is also where I'll announce any updates.

'''Quick note #1:''' these mockups are free for you to adapt. A picture is worth a thousand words so if you'd like to change something, download and edit the [http://schendje.fedorapeople.org/goblin/homepage/wireframe.svg SVG source file] and show it around!

'''Quick note #2:''' virtually all of the copy in the current mockups is placeholder text. Therefore, comments on the content of the page will not yet be of much use. I will be working on replacing it with proper copy as soon as possible, so we can also gather feedback on that part of the design.

== Mockups (most recent one at the top). ==

=== Third iteration. ===

http://schendje.fedorapeople.org/goblin/homepage/wireframe3.png

* Almost the same as previous, but added screenshots.
* A short explanation for this layout: http://schendje.fedorapeople.org/goblin/homepage/layout_explained.png

Questions:
* Is it obvious that the images are screenshots ? They can of course be clicked to show a bigger version.
* What is a good position for the "quick links" ? They will be in the top corner on any other page on the website, but I think they may demand too much attention if we put them at the top of the homepage as well.

=== Second iteration. ===
* Slightly higher fidelity.
* Includes several changes to the layout.

http://schendje.fedorapeople.org/goblin/homepage/wireframe2.png

=== First iteration. ===
A first low-fidelity wireframe: http://schendje.fedorapeople.org/goblin/homepage/wireframe.png

=== Old design. ===

A mockup of the current [https://wiki.mediagoblin.org/Main_Page MediaGoblin.org] design: http://schendje.fedorapeople.org/goblin/homepage/final.png

MediaGoblin.org v2

2016-02-16T00:29:59Z

Helen Christian: /* Mockups (most recent one at the top) */ fullstop punctuation.

This page tracks the MediaGoblin.org website redesign and is maintained by [[User:schendje|schendje]].

== Reasons for the redesign. ==

I was also the one who created the current [http://www.mediagoblin.org MediaGoblin.org] design. However, it could use some serious updating. I had several things I wish to see improve :

* '''Immediately and clearly explain what MediaGoblin is and what it does.''' I do not think this is clear at all on our current homepage. It begins with "The perfect tool to show and share your media !" which sounds positive, but doesn't really explain anything. It goes on with four more bullet points, about the community and the GNU project among other things, but none of these provide any information about MediaGoblin's functionality.

* '''Provide an easier way to get started with MediaGoblin.''' The current design has a big line of text in the middle saying "Get started with the latest MediaGoblin release", which seems pretty straightforward. But then it provides you with three choices, or maybe three steps, and it is unclear which one you should pick or start with.

* '''Remove the need for a separate tour page.''' Currently, we point visitors to our Tour page to learn more. This page contains plenty of information and screenshots, which is good. However, I think it would me more effective if MediaGoblin was introduced like this right on the homepage. Therefore, I wanted to combine the homepage and the tour page into a single page.

The homepage should also contain other information, such as links to the repository and [http://issues.mediagoblin.org/ bug tracker], but in my opinion its primary function should be to explain what MediaGoblin is and to get people started with it quickly.

== Request for feedback. ==

One of the reasons I created this page was to gather feedback. If you are interested, please keep checking this page for any updates and let me ([[User:schendje|schendje]]) know what you think. The best place to reach me would be the MediaGoblin IRC channel, which is also where I'll announce any updates.

'''Quick note #1:''' these mockups are free for you to adapt. A picture is worth a thousand words so if you'd like to change something, download and edit the [http://schendje.fedorapeople.org/goblin/homepage/wireframe.svg SVG source file] and show it around!

'''Quick note #2:''' virtually all of the copy in the current mockups is placeholder text. Therefore, comments on the content of the page will not yet be of much use. I will be working on replacing it with proper copy as soon as possible, so we can also gather feedback on that part of the design.

== Mockups (most recent one at the top). ==

=== Third iteration ===

http://schendje.fedorapeople.org/goblin/homepage/wireframe3.png

* Almost the same as previous, but added screenshots.
* A short explanation for this layout: http://schendje.fedorapeople.org/goblin/homepage/layout_explained.png

Questions:
* Is it obvious that the images are screenshots ? They can of course be clicked to show a bigger version.
* What is a good position for the "quick links" ? They will be in the top corner on any other page on the website, but I think they may demand too much attention if we put them at the top of the homepage as well.

=== Second iteration ===
* Slightly higher fidelity.
* Includes several changes to the layout.

http://schendje.fedorapeople.org/goblin/homepage/wireframe2.png

=== First iteration ===
A first low-fidelity wireframe: http://schendje.fedorapeople.org/goblin/homepage/wireframe.png

=== Old design ===

A mockup of the current [https://wiki.mediagoblin.org/Main_Page MediaGoblin.org] design: http://schendje.fedorapeople.org/goblin/homepage/final.png

MediaGoblin.org v2

2016-02-16T00:29:37Z

Helen Christian: /* Request for feedback */ fullstop punctuation.

This page tracks the MediaGoblin.org website redesign and is maintained by [[User:schendje|schendje]].

== Reasons for the redesign. ==

I was also the one who created the current [http://www.mediagoblin.org MediaGoblin.org] design. However, it could use some serious updating. I had several things I wish to see improve :

* '''Immediately and clearly explain what MediaGoblin is and what it does.''' I do not think this is clear at all on our current homepage. It begins with "The perfect tool to show and share your media !" which sounds positive, but doesn't really explain anything. It goes on with four more bullet points, about the community and the GNU project among other things, but none of these provide any information about MediaGoblin's functionality.

* '''Provide an easier way to get started with MediaGoblin.''' The current design has a big line of text in the middle saying "Get started with the latest MediaGoblin release", which seems pretty straightforward. But then it provides you with three choices, or maybe three steps, and it is unclear which one you should pick or start with.

* '''Remove the need for a separate tour page.''' Currently, we point visitors to our Tour page to learn more. This page contains plenty of information and screenshots, which is good. However, I think it would me more effective if MediaGoblin was introduced like this right on the homepage. Therefore, I wanted to combine the homepage and the tour page into a single page.

The homepage should also contain other information, such as links to the repository and [http://issues.mediagoblin.org/ bug tracker], but in my opinion its primary function should be to explain what MediaGoblin is and to get people started with it quickly.

== Request for feedback. ==

One of the reasons I created this page was to gather feedback. If you are interested, please keep checking this page for any updates and let me ([[User:schendje|schendje]]) know what you think. The best place to reach me would be the MediaGoblin IRC channel, which is also where I'll announce any updates.

'''Quick note #1:''' these mockups are free for you to adapt. A picture is worth a thousand words so if you'd like to change something, download and edit the [http://schendje.fedorapeople.org/goblin/homepage/wireframe.svg SVG source file] and show it around!

'''Quick note #2:''' virtually all of the copy in the current mockups is placeholder text. Therefore, comments on the content of the page will not yet be of much use. I will be working on replacing it with proper copy as soon as possible, so we can also gather feedback on that part of the design.

== Mockups (most recent one at the top) ==

=== Third iteration ===

http://schendje.fedorapeople.org/goblin/homepage/wireframe3.png

* Almost the same as previous, but added screenshots.
* A short explanation for this layout: http://schendje.fedorapeople.org/goblin/homepage/layout_explained.png

Questions:
* Is it obvious that the images are screenshots ? They can of course be clicked to show a bigger version.
* What is a good position for the "quick links" ? They will be in the top corner on any other page on the website, but I think they may demand too much attention if we put them at the top of the homepage as well.

=== Second iteration ===
* Slightly higher fidelity.
* Includes several changes to the layout.

http://schendje.fedorapeople.org/goblin/homepage/wireframe2.png

=== First iteration ===
A first low-fidelity wireframe: http://schendje.fedorapeople.org/goblin/homepage/wireframe.png

=== Old design ===

A mockup of the current [https://wiki.mediagoblin.org/Main_Page MediaGoblin.org] design: http://schendje.fedorapeople.org/goblin/homepage/final.png

MediaGoblin.org v2

2016-02-16T00:29:21Z

Helen Christian: /* Reasons for the redesign */ fullstop punctuation.

This page tracks the MediaGoblin.org website redesign and is maintained by [[User:schendje|schendje]].

== Reasons for the redesign. ==

I was also the one who created the current [http://www.mediagoblin.org MediaGoblin.org] design. However, it could use some serious updating. I had several things I wish to see improve :

* '''Immediately and clearly explain what MediaGoblin is and what it does.''' I do not think this is clear at all on our current homepage. It begins with "The perfect tool to show and share your media !" which sounds positive, but doesn't really explain anything. It goes on with four more bullet points, about the community and the GNU project among other things, but none of these provide any information about MediaGoblin's functionality.

* '''Provide an easier way to get started with MediaGoblin.''' The current design has a big line of text in the middle saying "Get started with the latest MediaGoblin release", which seems pretty straightforward. But then it provides you with three choices, or maybe three steps, and it is unclear which one you should pick or start with.

* '''Remove the need for a separate tour page.''' Currently, we point visitors to our Tour page to learn more. This page contains plenty of information and screenshots, which is good. However, I think it would me more effective if MediaGoblin was introduced like this right on the homepage. Therefore, I wanted to combine the homepage and the tour page into a single page.

The homepage should also contain other information, such as links to the repository and [http://issues.mediagoblin.org/ bug tracker], but in my opinion its primary function should be to explain what MediaGoblin is and to get people started with it quickly.

== Request for feedback ==

One of the reasons I created this page was to gather feedback. If you are interested, please keep checking this page for any updates and let me ([[User:schendje|schendje]]) know what you think. The best place to reach me would be the MediaGoblin IRC channel, which is also where I'll announce any updates.

'''Quick note #1:''' these mockups are free for you to adapt. A picture is worth a thousand words so if you'd like to change something, download and edit the [http://schendje.fedorapeople.org/goblin/homepage/wireframe.svg SVG source file] and show it around!

'''Quick note #2:''' virtually all of the copy in the current mockups is placeholder text. Therefore, comments on the content of the page will not yet be of much use. I will be working on replacing it with proper copy as soon as possible, so we can also gather feedback on that part of the design.

== Mockups (most recent one at the top) ==

=== Third iteration ===

http://schendje.fedorapeople.org/goblin/homepage/wireframe3.png

* Almost the same as previous, but added screenshots.
* A short explanation for this layout: http://schendje.fedorapeople.org/goblin/homepage/layout_explained.png

Questions:
* Is it obvious that the images are screenshots ? They can of course be clicked to show a bigger version.
* What is a good position for the "quick links" ? They will be in the top corner on any other page on the website, but I think they may demand too much attention if we put them at the top of the homepage as well.

=== Second iteration ===
* Slightly higher fidelity.
* Includes several changes to the layout.

http://schendje.fedorapeople.org/goblin/homepage/wireframe2.png

=== First iteration ===
A first low-fidelity wireframe: http://schendje.fedorapeople.org/goblin/homepage/wireframe.png

=== Old design ===

A mockup of the current [https://wiki.mediagoblin.org/Main_Page MediaGoblin.org] design: http://schendje.fedorapeople.org/goblin/homepage/final.png

MediaGoblin.org v2

2016-02-16T00:28:43Z

Helen Christian: /* Old design */ WebLink to Main Page.

This page tracks the MediaGoblin.org website redesign and is maintained by [[User:schendje|schendje]].

== Reasons for the redesign ==

I was also the one who created the current [http://www.mediagoblin.org MediaGoblin.org] design. However, it could use some serious updating. I had several things I wish to see improve :

* '''Immediately and clearly explain what MediaGoblin is and what it does.''' I do not think this is clear at all on our current homepage. It begins with "The perfect tool to show and share your media !" which sounds positive, but doesn't really explain anything. It goes on with four more bullet points, about the community and the GNU project among other things, but none of these provide any information about MediaGoblin's functionality.

* '''Provide an easier way to get started with MediaGoblin.''' The current design has a big line of text in the middle saying "Get started with the latest MediaGoblin release", which seems pretty straightforward. But then it provides you with three choices, or maybe three steps, and it is unclear which one you should pick or start with.

* '''Remove the need for a separate tour page.''' Currently, we point visitors to our Tour page to learn more. This page contains plenty of information and screenshots, which is good. However, I think it would me more effective if MediaGoblin was introduced like this right on the homepage. Therefore, I wanted to combine the homepage and the tour page into a single page.

The homepage should also contain other information, such as links to the repository and [http://issues.mediagoblin.org/ bug tracker], but in my opinion its primary function should be to explain what MediaGoblin is and to get people started with it quickly.

== Request for feedback ==

One of the reasons I created this page was to gather feedback. If you are interested, please keep checking this page for any updates and let me ([[User:schendje|schendje]]) know what you think. The best place to reach me would be the MediaGoblin IRC channel, which is also where I'll announce any updates.

'''Quick note #1:''' these mockups are free for you to adapt. A picture is worth a thousand words so if you'd like to change something, download and edit the [http://schendje.fedorapeople.org/goblin/homepage/wireframe.svg SVG source file] and show it around!

'''Quick note #2:''' virtually all of the copy in the current mockups is placeholder text. Therefore, comments on the content of the page will not yet be of much use. I will be working on replacing it with proper copy as soon as possible, so we can also gather feedback on that part of the design.

== Mockups (most recent one at the top) ==

=== Third iteration ===

http://schendje.fedorapeople.org/goblin/homepage/wireframe3.png

* Almost the same as previous, but added screenshots.
* A short explanation for this layout: http://schendje.fedorapeople.org/goblin/homepage/layout_explained.png

Questions:
* Is it obvious that the images are screenshots ? They can of course be clicked to show a bigger version.
* What is a good position for the "quick links" ? They will be in the top corner on any other page on the website, but I think they may demand too much attention if we put them at the top of the homepage as well.

=== Second iteration ===
* Slightly higher fidelity.
* Includes several changes to the layout.

http://schendje.fedorapeople.org/goblin/homepage/wireframe2.png

=== First iteration ===
A first low-fidelity wireframe: http://schendje.fedorapeople.org/goblin/homepage/wireframe.png

=== Old design ===

A mockup of the current [https://wiki.mediagoblin.org/Main_Page MediaGoblin.org] design: http://schendje.fedorapeople.org/goblin/homepage/final.png

MediaGoblin.org v2

2016-02-16T00:27:59Z

Helen Christian: /* Second iteration */ full stops.

This page tracks the MediaGoblin.org website redesign and is maintained by [[User:schendje|schendje]].

== Reasons for the redesign ==

I was also the one who created the current [http://www.mediagoblin.org MediaGoblin.org] design. However, it could use some serious updating. I had several things I wish to see improve :

* '''Immediately and clearly explain what MediaGoblin is and what it does.''' I do not think this is clear at all on our current homepage. It begins with "The perfect tool to show and share your media !" which sounds positive, but doesn't really explain anything. It goes on with four more bullet points, about the community and the GNU project among other things, but none of these provide any information about MediaGoblin's functionality.

* '''Provide an easier way to get started with MediaGoblin.''' The current design has a big line of text in the middle saying "Get started with the latest MediaGoblin release", which seems pretty straightforward. But then it provides you with three choices, or maybe three steps, and it is unclear which one you should pick or start with.

* '''Remove the need for a separate tour page.''' Currently, we point visitors to our Tour page to learn more. This page contains plenty of information and screenshots, which is good. However, I think it would me more effective if MediaGoblin was introduced like this right on the homepage. Therefore, I wanted to combine the homepage and the tour page into a single page.

The homepage should also contain other information, such as links to the repository and [http://issues.mediagoblin.org/ bug tracker], but in my opinion its primary function should be to explain what MediaGoblin is and to get people started with it quickly.

== Request for feedback ==

One of the reasons I created this page was to gather feedback. If you are interested, please keep checking this page for any updates and let me ([[User:schendje|schendje]]) know what you think. The best place to reach me would be the MediaGoblin IRC channel, which is also where I'll announce any updates.

'''Quick note #1:''' these mockups are free for you to adapt. A picture is worth a thousand words so if you'd like to change something, download and edit the [http://schendje.fedorapeople.org/goblin/homepage/wireframe.svg SVG source file] and show it around!

'''Quick note #2:''' virtually all of the copy in the current mockups is placeholder text. Therefore, comments on the content of the page will not yet be of much use. I will be working on replacing it with proper copy as soon as possible, so we can also gather feedback on that part of the design.

== Mockups (most recent one at the top) ==

=== Third iteration ===

http://schendje.fedorapeople.org/goblin/homepage/wireframe3.png

* Almost the same as previous, but added screenshots.
* A short explanation for this layout: http://schendje.fedorapeople.org/goblin/homepage/layout_explained.png

Questions:
* Is it obvious that the images are screenshots ? They can of course be clicked to show a bigger version.
* What is a good position for the "quick links" ? They will be in the top corner on any other page on the website, but I think they may demand too much attention if we put them at the top of the homepage as well.

=== Second iteration ===
* Slightly higher fidelity.
* Includes several changes to the layout.

http://schendje.fedorapeople.org/goblin/homepage/wireframe2.png

=== First iteration ===
A first low-fidelity wireframe: http://schendje.fedorapeople.org/goblin/homepage/wireframe.png

=== Old design ===

A mockup of the current MediaGoblin.org design: http://schendje.fedorapeople.org/goblin/homepage/final.png

MediaGoblin.org v2

2016-02-16T00:27:34Z

Helen Christian: /* Third iteration */ punctuation fullstops and ? QM's.

This page tracks the MediaGoblin.org website redesign and is maintained by [[User:schendje|schendje]].

== Reasons for the redesign ==

I was also the one who created the current [http://www.mediagoblin.org MediaGoblin.org] design. However, it could use some serious updating. I had several things I wish to see improve :

* '''Immediately and clearly explain what MediaGoblin is and what it does.''' I do not think this is clear at all on our current homepage. It begins with "The perfect tool to show and share your media !" which sounds positive, but doesn't really explain anything. It goes on with four more bullet points, about the community and the GNU project among other things, but none of these provide any information about MediaGoblin's functionality.

* '''Provide an easier way to get started with MediaGoblin.''' The current design has a big line of text in the middle saying "Get started with the latest MediaGoblin release", which seems pretty straightforward. But then it provides you with three choices, or maybe three steps, and it is unclear which one you should pick or start with.

* '''Remove the need for a separate tour page.''' Currently, we point visitors to our Tour page to learn more. This page contains plenty of information and screenshots, which is good. However, I think it would me more effective if MediaGoblin was introduced like this right on the homepage. Therefore, I wanted to combine the homepage and the tour page into a single page.

The homepage should also contain other information, such as links to the repository and [http://issues.mediagoblin.org/ bug tracker], but in my opinion its primary function should be to explain what MediaGoblin is and to get people started with it quickly.

== Request for feedback ==

One of the reasons I created this page was to gather feedback. If you are interested, please keep checking this page for any updates and let me ([[User:schendje|schendje]]) know what you think. The best place to reach me would be the MediaGoblin IRC channel, which is also where I'll announce any updates.

'''Quick note #1:''' these mockups are free for you to adapt. A picture is worth a thousand words so if you'd like to change something, download and edit the [http://schendje.fedorapeople.org/goblin/homepage/wireframe.svg SVG source file] and show it around!

'''Quick note #2:''' virtually all of the copy in the current mockups is placeholder text. Therefore, comments on the content of the page will not yet be of much use. I will be working on replacing it with proper copy as soon as possible, so we can also gather feedback on that part of the design.

== Mockups (most recent one at the top) ==

=== Third iteration ===

http://schendje.fedorapeople.org/goblin/homepage/wireframe3.png

* Almost the same as previous, but added screenshots.
* A short explanation for this layout: http://schendje.fedorapeople.org/goblin/homepage/layout_explained.png

Questions:
* Is it obvious that the images are screenshots ? They can of course be clicked to show a bigger version.
* What is a good position for the "quick links" ? They will be in the top corner on any other page on the website, but I think they may demand too much attention if we put them at the top of the homepage as well.

=== Second iteration ===
* Slightly higher fidelity
* Includes several changes to the layout

http://schendje.fedorapeople.org/goblin/homepage/wireframe2.png

=== First iteration ===
A first low-fidelity wireframe: http://schendje.fedorapeople.org/goblin/homepage/wireframe.png

=== Old design ===

A mockup of the current MediaGoblin.org design: http://schendje.fedorapeople.org/goblin/homepage/final.png

User:Schendje

2016-02-16T00:26:20Z

Helen Christian: Sorry for pinging you I couldn't get anyone on IRChat as it's a holiday - you can delete this as Spam if you wish, when the Talk./Discussion bug is resolved. Thank-you.

I'm Jef and I have [http://www.jefvanschendel.nl a website].

For MediaGoblin, I design things and pretend to be able to code.

To contact me about MediaGoblin-related things, look me up on the MediaGoblin IRC channel.

== "Let people know what you think." ==

Sorry for editing this page, I really didn't mean to ping you. but, but, How are we supposed to [https://wiki.mediagoblin.org/MediaGoblin.org_v2#Request_for_feedback let you/users know what we think] if we can not edit the "discussion" page of our MediaGoblin Wiki's ??

MediaGoblin.org v2

2016-02-16T00:20:23Z

Helen Christian: /* Reasons for the redesign */ bug tracker webLink

This page tracks the MediaGoblin.org website redesign and is maintained by [[User:schendje|schendje]].

== Reasons for the redesign ==

I was also the one who created the current [http://www.mediagoblin.org MediaGoblin.org] design. However, it could use some serious updating. I had several things I wish to see improve :

* '''Immediately and clearly explain what MediaGoblin is and what it does.''' I do not think this is clear at all on our current homepage. It begins with "The perfect tool to show and share your media !" which sounds positive, but doesn't really explain anything. It goes on with four more bullet points, about the community and the GNU project among other things, but none of these provide any information about MediaGoblin's functionality.

* '''Provide an easier way to get started with MediaGoblin.''' The current design has a big line of text in the middle saying "Get started with the latest MediaGoblin release", which seems pretty straightforward. But then it provides you with three choices, or maybe three steps, and it is unclear which one you should pick or start with.

* '''Remove the need for a separate tour page.''' Currently, we point visitors to our Tour page to learn more. This page contains plenty of information and screenshots, which is good. However, I think it would me more effective if MediaGoblin was introduced like this right on the homepage. Therefore, I wanted to combine the homepage and the tour page into a single page.

The homepage should also contain other information, such as links to the repository and [http://issues.mediagoblin.org/ bug tracker], but in my opinion its primary function should be to explain what MediaGoblin is and to get people started with it quickly.

== Request for feedback ==

One of the reasons I created this page was to gather feedback. If you are interested, please keep checking this page for any updates and let me ([[User:schendje|schendje]]) know what you think. The best place to reach me would be the MediaGoblin IRC channel, which is also where I'll announce any updates.

'''Quick note #1:''' these mockups are free for you to adapt. A picture is worth a thousand words so if you'd like to change something, download and edit the [http://schendje.fedorapeople.org/goblin/homepage/wireframe.svg SVG source file] and show it around!

'''Quick note #2:''' virtually all of the copy in the current mockups is placeholder text. Therefore, comments on the content of the page will not yet be of much use. I will be working on replacing it with proper copy as soon as possible, so we can also gather feedback on that part of the design.

== Mockups (most recent one at the top) ==

=== Third iteration ===

http://schendje.fedorapeople.org/goblin/homepage/wireframe3.png

* Almost the same as previous, but added screenshots
* A short explanation for this layout: http://schendje.fedorapeople.org/goblin/homepage/layout_explained.png

Questions:
* Is it obvious that the images are screenshots? They can of course be clicked to show a bigger version.
* What is a good position for the "quick links"? They will be in the top corner on any other page on the website, but I think they may demand too much attention if we put them at the top of the homepage as well.

=== Second iteration ===
* Slightly higher fidelity
* Includes several changes to the layout

http://schendje.fedorapeople.org/goblin/homepage/wireframe2.png

=== First iteration ===
A first low-fidelity wireframe: http://schendje.fedorapeople.org/goblin/homepage/wireframe.png

=== Old design ===

A mockup of the current MediaGoblin.org design: http://schendje.fedorapeople.org/goblin/homepage/final.png

MediaGoblin.org v2

2016-02-16T00:11:57Z

Helen Christian: /* Reasons for the redesign */ punctuation '!' gapped.

This page tracks the MediaGoblin.org website redesign and is maintained by [[User:schendje|schendje]].

== Reasons for the redesign ==

I was also the one who created the current [http://www.mediagoblin.org MediaGoblin.org] design. However, it could use some serious updating. I had several things I wish to see improve :

* '''Immediately and clearly explain what MediaGoblin is and what it does.''' I do not think this is clear at all on our current homepage. It begins with "The perfect tool to show and share your media !" which sounds positive, but doesn't really explain anything. It goes on with four more bullet points, about the community and the GNU project among other things, but none of these provide any information about MediaGoblin's functionality.

* '''Provide an easier way to get started with MediaGoblin.''' The current design has a big line of text in the middle saying "Get started with the latest MediaGoblin release", which seems pretty straightforward. But then it provides you with three choices, or maybe three steps, and it is unclear which one you should pick or start with.

* '''Remove the need for a separate tour page.''' Currently, we point visitors to our Tour page to learn more. This page contains plenty of information and screenshots, which is good. However, I think it would me more effective if MediaGoblin was introduced like this right on the homepage. Therefore, I wanted to combine the homepage and the tour page into a single page.

The homepage should also contain other information, such as links to the repository and bug tracker, but in my opinion its primary function should be to explain what MediaGoblin is and to get people started with it quickly.

== Request for feedback ==

One of the reasons I created this page was to gather feedback. If you are interested, please keep checking this page for any updates and let me ([[User:schendje|schendje]]) know what you think. The best place to reach me would be the MediaGoblin IRC channel, which is also where I'll announce any updates.

'''Quick note #1:''' these mockups are free for you to adapt. A picture is worth a thousand words so if you'd like to change something, download and edit the [http://schendje.fedorapeople.org/goblin/homepage/wireframe.svg SVG source file] and show it around!

'''Quick note #2:''' virtually all of the copy in the current mockups is placeholder text. Therefore, comments on the content of the page will not yet be of much use. I will be working on replacing it with proper copy as soon as possible, so we can also gather feedback on that part of the design.

== Mockups (most recent one at the top) ==

=== Third iteration ===

http://schendje.fedorapeople.org/goblin/homepage/wireframe3.png

* Almost the same as previous, but added screenshots
* A short explanation for this layout: http://schendje.fedorapeople.org/goblin/homepage/layout_explained.png

Questions:
* Is it obvious that the images are screenshots? They can of course be clicked to show a bigger version.
* What is a good position for the "quick links"? They will be in the top corner on any other page on the website, but I think they may demand too much attention if we put them at the top of the homepage as well.

=== Second iteration ===
* Slightly higher fidelity
* Includes several changes to the layout

http://schendje.fedorapeople.org/goblin/homepage/wireframe2.png

=== First iteration ===
A first low-fidelity wireframe: http://schendje.fedorapeople.org/goblin/homepage/wireframe.png

=== Old design ===

A mockup of the current MediaGoblin.org design: http://schendje.fedorapeople.org/goblin/homepage/final.png

MediaGoblin.org v2

2016-02-16T00:11:10Z

Helen Christian: /* Reasons for the redesign */ changed 'wanted to' to 'wished to see :'

This page tracks the MediaGoblin.org website redesign and is maintained by [[User:schendje|schendje]].

== Reasons for the redesign ==

I was also the one who created the current [http://www.mediagoblin.org MediaGoblin.org] design. However, it could use some serious updating. I had several things I wish to see improve :

* '''Immediately and clearly explain what MediaGoblin is and what it does.''' I do not think this is clear at all on our current homepage. It begins with "The perfect tool to show and share your media!" which sounds positive, but doesn't really explain anything. It goes on with four more bullet points, about the community and the GNU project among other things, but none of these provide any information about MediaGoblin's functionality.

* '''Provide an easier way to get started with MediaGoblin.''' The current design has a big line of text in the middle saying "Get started with the latest MediaGoblin release", which seems pretty straightforward. But then it provides you with three choices, or maybe three steps, and it is unclear which one you should pick or start with.

* '''Remove the need for a separate tour page.''' Currently, we point visitors to our Tour page to learn more. This page contains plenty of information and screenshots, which is good. However, I think it would me more effective if MediaGoblin was introduced like this right on the homepage. Therefore, I wanted to combine the homepage and the tour page into a single page.

The homepage should also contain other information, such as links to the repository and bug tracker, but in my opinion its primary function should be to explain what MediaGoblin is and to get people started with it quickly.

== Request for feedback ==

One of the reasons I created this page was to gather feedback. If you are interested, please keep checking this page for any updates and let me ([[User:schendje|schendje]]) know what you think. The best place to reach me would be the MediaGoblin IRC channel, which is also where I'll announce any updates.

'''Quick note #1:''' these mockups are free for you to adapt. A picture is worth a thousand words so if you'd like to change something, download and edit the [http://schendje.fedorapeople.org/goblin/homepage/wireframe.svg SVG source file] and show it around!

'''Quick note #2:''' virtually all of the copy in the current mockups is placeholder text. Therefore, comments on the content of the page will not yet be of much use. I will be working on replacing it with proper copy as soon as possible, so we can also gather feedback on that part of the design.

== Mockups (most recent one at the top) ==

=== Third iteration ===

http://schendje.fedorapeople.org/goblin/homepage/wireframe3.png

* Almost the same as previous, but added screenshots
* A short explanation for this layout: http://schendje.fedorapeople.org/goblin/homepage/layout_explained.png

Questions:
* Is it obvious that the images are screenshots? They can of course be clicked to show a bigger version.
* What is a good position for the "quick links"? They will be in the top corner on any other page on the website, but I think they may demand too much attention if we put them at the top of the homepage as well.

=== Second iteration ===
* Slightly higher fidelity
* Includes several changes to the layout

http://schendje.fedorapeople.org/goblin/homepage/wireframe2.png

=== First iteration ===
A first low-fidelity wireframe: http://schendje.fedorapeople.org/goblin/homepage/wireframe.png

=== Old design ===

A mockup of the current MediaGoblin.org design: http://schendje.fedorapeople.org/goblin/homepage/final.png

GSOC 2017

2016-02-15T23:38:47Z

Helen Christian: /* Multiple qualities of video. */ better use of links for 4k .

We are hoping to participate in [https://developers.google.com/open-source/gsoc/ GSOC 2016] under the GNU umbrella.

You may want to check for a "possible mentor" before applying for this topic. If you have your own idea, probably bring it up in #mediagoblin on irc.freenode.net !

= How do I apply as a student ? =

* [https://developers.google.com/open-source/gsoc/ Submit your application]. Please see the application submission template on the [http://www.gnu.org/software/soc-projects/guidelines.html GNU GSoC guidelines page].
* [http://mediagoblin.org/pages/join.html Join us] on IRC and on our mailing lists.
* Set up a development environment via our [[HackingHowto]]
* If you have never done web development in python before, MediaGoblin is a pretty good place to start ! However, we highly recommend going through the [https://docs.djangoproject.com/en/1.7/intro/tutorial01/ Django tutorial]... this isn't a requirement, but it will help you be better prepared.
* Work on a small task, and mention it in your application. The [http://issues.mediagoblin.org/query?status=!closed&keywords=~bitesized bitesized list] is often helpful.
* Also, be aware when submitting: Summer of Code applicants are expected to work '''40 hours per week'''... so, a full time internship ! If you propose, please be sure you are ready to make that level of commitment.

It's important that you communicate... most MediaGoblin communication happens on IRC, so you should [http://webchat.freenode.net/?channels=mediagoblin join us there] and discuss (#mediagoblin on irc.freenode.net)! Please, please join our channel and introduce yourself. We would love to hear from you !

= Possible projects with mentors. =
== Chunked uploads / multi-upload UI. ==

We want to have multi-upload from cli (usecase: go to my directory with photos and upload them all) and from web-interface (using maybe zip, maybe html5 feature). There is already https://github.com/VenKamikaze/mediagoblin-html5-multi-upload which might be what we need, so before choosing this task please verify.

'''Possible Mentors:''' Christopher Allan Webber, Boris Bobrov .

== Subtitle interface. ==

'''Possible Mentors:''' Christopher Allan Webber, Boris Bobrov .

We want subtitle support for our player. Subtitles should be supported as separate files and as embedded into video/audio files. Popular formats should be supported. Also, there can be multiple subtitles per video. It will require work on front-end and maybe some fixes to backend.

== Multiple qualities of video. ==

Now MediaGoblin supports only a single quality of video files. We want to fix that and support multiple qualities: 360p, 480p, 720p, 1080p, [https://en.wikipedia.org/wiki/Ultra-high-definition_television 4k]. This requires changes to frontend and to backend. To implement it, one must have some experience in JavaScript and Python.

'''Possible mentors''': Boris Bobrov .

GSOC 2017

2016-02-15T23:35:50Z

Helen Christian: /* Multiple qualities of video. */ 4k or UHDT definition wikipedia.org reference.

We are hoping to participate in [https://developers.google.com/open-source/gsoc/ GSOC 2016] under the GNU umbrella.

You may want to check for a "possible mentor" before applying for this topic. If you have your own idea, probably bring it up in #mediagoblin on irc.freenode.net !

= How do I apply as a student ? =

* [https://developers.google.com/open-source/gsoc/ Submit your application]. Please see the application submission template on the [http://www.gnu.org/software/soc-projects/guidelines.html GNU GSoC guidelines page].
* [http://mediagoblin.org/pages/join.html Join us] on IRC and on our mailing lists.
* Set up a development environment via our [[HackingHowto]]
* If you have never done web development in python before, MediaGoblin is a pretty good place to start ! However, we highly recommend going through the [https://docs.djangoproject.com/en/1.7/intro/tutorial01/ Django tutorial]... this isn't a requirement, but it will help you be better prepared.
* Work on a small task, and mention it in your application. The [http://issues.mediagoblin.org/query?status=!closed&keywords=~bitesized bitesized list] is often helpful.
* Also, be aware when submitting: Summer of Code applicants are expected to work '''40 hours per week'''... so, a full time internship ! If you propose, please be sure you are ready to make that level of commitment.

It's important that you communicate... most MediaGoblin communication happens on IRC, so you should [http://webchat.freenode.net/?channels=mediagoblin join us there] and discuss (#mediagoblin on irc.freenode.net)! Please, please join our channel and introduce yourself. We would love to hear from you !

= Possible projects with mentors. =
== Chunked uploads / multi-upload UI. ==

We want to have multi-upload from cli (usecase: go to my directory with photos and upload them all) and from web-interface (using maybe zip, maybe html5 feature). There is already https://github.com/VenKamikaze/mediagoblin-html5-multi-upload which might be what we need, so before choosing this task please verify.

'''Possible Mentors:''' Christopher Allan Webber, Boris Bobrov .

== Subtitle interface. ==

'''Possible Mentors:''' Christopher Allan Webber, Boris Bobrov .

We want subtitle support for our player. Subtitles should be supported as separate files and as embedded into video/audio files. Popular formats should be supported. Also, there can be multiple subtitles per video. It will require work on front-end and maybe some fixes to backend.

== Multiple qualities of video. ==

Now MediaGoblin supports only a single quality of video files. We want to fix that and support multiple qualities: 360p, 480p, 720p, 1080p, [4k][https://en.wikipedia.org/wiki/Ultra-high-definition_television]. This requires changes to frontend and to backend. To implement it, one must have some experience in JavaScript and Python.

'''Possible mentors''': Boris Bobrov .

GSOC 2017

2016-02-15T23:29:11Z

Helen Christian: /* Multiple qualities of video. */ punctuation fullstop .

We are hoping to participate in [https://developers.google.com/open-source/gsoc/ GSOC 2016] under the GNU umbrella.

You may want to check for a "possible mentor" before applying for this topic. If you have your own idea, probably bring it up in #mediagoblin on irc.freenode.net !

= How do I apply as a student ? =

* [https://developers.google.com/open-source/gsoc/ Submit your application]. Please see the application submission template on the [http://www.gnu.org/software/soc-projects/guidelines.html GNU GSoC guidelines page].
* [http://mediagoblin.org/pages/join.html Join us] on IRC and on our mailing lists.
* Set up a development environment via our [[HackingHowto]]
* If you have never done web development in python before, MediaGoblin is a pretty good place to start ! However, we highly recommend going through the [https://docs.djangoproject.com/en/1.7/intro/tutorial01/ Django tutorial]... this isn't a requirement, but it will help you be better prepared.
* Work on a small task, and mention it in your application. The [http://issues.mediagoblin.org/query?status=!closed&keywords=~bitesized bitesized list] is often helpful.
* Also, be aware when submitting: Summer of Code applicants are expected to work '''40 hours per week'''... so, a full time internship ! If you propose, please be sure you are ready to make that level of commitment.

It's important that you communicate... most MediaGoblin communication happens on IRC, so you should [http://webchat.freenode.net/?channels=mediagoblin join us there] and discuss (#mediagoblin on irc.freenode.net)! Please, please join our channel and introduce yourself. We would love to hear from you !

= Possible projects with mentors. =
== Chunked uploads / multi-upload UI. ==

We want to have multi-upload from cli (usecase: go to my directory with photos and upload them all) and from web-interface (using maybe zip, maybe html5 feature). There is already https://github.com/VenKamikaze/mediagoblin-html5-multi-upload which might be what we need, so before choosing this task please verify.

'''Possible Mentors:''' Christopher Allan Webber, Boris Bobrov .

== Subtitle interface. ==

'''Possible Mentors:''' Christopher Allan Webber, Boris Bobrov .

We want subtitle support for our player. Subtitles should be supported as separate files and as embedded into video/audio files. Popular formats should be supported. Also, there can be multiple subtitles per video. It will require work on front-end and maybe some fixes to backend.

== Multiple qualities of video. ==

Now MediaGoblin supports only a single quality of video files. We want to fix that and support multiple qualities: 360p, 480p, 720p, 1080p, 4k. This requires changes to frontend and to backend. To implement it, one must have some experience in JavaScript and Python.

'''Possible mentors''': Boris Bobrov .

GSOC 2017

2016-02-15T23:28:49Z

Helen Christian: /* Subtitle interface. */ punctuation fullstop .

We are hoping to participate in [https://developers.google.com/open-source/gsoc/ GSOC 2016] under the GNU umbrella.

You may want to check for a "possible mentor" before applying for this topic. If you have your own idea, probably bring it up in #mediagoblin on irc.freenode.net !

= How do I apply as a student ? =

* [https://developers.google.com/open-source/gsoc/ Submit your application]. Please see the application submission template on the [http://www.gnu.org/software/soc-projects/guidelines.html GNU GSoC guidelines page].
* [http://mediagoblin.org/pages/join.html Join us] on IRC and on our mailing lists.
* Set up a development environment via our [[HackingHowto]]
* If you have never done web development in python before, MediaGoblin is a pretty good place to start ! However, we highly recommend going through the [https://docs.djangoproject.com/en/1.7/intro/tutorial01/ Django tutorial]... this isn't a requirement, but it will help you be better prepared.
* Work on a small task, and mention it in your application. The [http://issues.mediagoblin.org/query?status=!closed&keywords=~bitesized bitesized list] is often helpful.
* Also, be aware when submitting: Summer of Code applicants are expected to work '''40 hours per week'''... so, a full time internship ! If you propose, please be sure you are ready to make that level of commitment.

It's important that you communicate... most MediaGoblin communication happens on IRC, so you should [http://webchat.freenode.net/?channels=mediagoblin join us there] and discuss (#mediagoblin on irc.freenode.net)! Please, please join our channel and introduce yourself. We would love to hear from you !

= Possible projects with mentors. =
== Chunked uploads / multi-upload UI. ==

We want to have multi-upload from cli (usecase: go to my directory with photos and upload them all) and from web-interface (using maybe zip, maybe html5 feature). There is already https://github.com/VenKamikaze/mediagoblin-html5-multi-upload which might be what we need, so before choosing this task please verify.

'''Possible Mentors:''' Christopher Allan Webber, Boris Bobrov .

== Subtitle interface. ==

'''Possible Mentors:''' Christopher Allan Webber, Boris Bobrov .

We want subtitle support for our player. Subtitles should be supported as separate files and as embedded into video/audio files. Popular formats should be supported. Also, there can be multiple subtitles per video. It will require work on front-end and maybe some fixes to backend.

== Multiple qualities of video. ==

Now MediaGoblin supports only a single quality of video files. We want to fix that and support multiple qualities: 360p, 480p, 720p, 1080p, 4k. This requires changes to frontend and to backend. To implement it, one must have some experience in JavaScript and Python.

'''Possible mentors''': Boris Bobrov

GSOC 2017

2016-02-15T23:28:21Z

Helen Christian: /* Chunked uploads / multi-upload UI. */ punctuation fullstop.

We are hoping to participate in [https://developers.google.com/open-source/gsoc/ GSOC 2016] under the GNU umbrella.

You may want to check for a "possible mentor" before applying for this topic. If you have your own idea, probably bring it up in #mediagoblin on irc.freenode.net !

= How do I apply as a student ? =

* [https://developers.google.com/open-source/gsoc/ Submit your application]. Please see the application submission template on the [http://www.gnu.org/software/soc-projects/guidelines.html GNU GSoC guidelines page].
* [http://mediagoblin.org/pages/join.html Join us] on IRC and on our mailing lists.
* Set up a development environment via our [[HackingHowto]]
* If you have never done web development in python before, MediaGoblin is a pretty good place to start ! However, we highly recommend going through the [https://docs.djangoproject.com/en/1.7/intro/tutorial01/ Django tutorial]... this isn't a requirement, but it will help you be better prepared.
* Work on a small task, and mention it in your application. The [http://issues.mediagoblin.org/query?status=!closed&keywords=~bitesized bitesized list] is often helpful.
* Also, be aware when submitting: Summer of Code applicants are expected to work '''40 hours per week'''... so, a full time internship ! If you propose, please be sure you are ready to make that level of commitment.

It's important that you communicate... most MediaGoblin communication happens on IRC, so you should [http://webchat.freenode.net/?channels=mediagoblin join us there] and discuss (#mediagoblin on irc.freenode.net)! Please, please join our channel and introduce yourself. We would love to hear from you !

= Possible projects with mentors. =
== Chunked uploads / multi-upload UI. ==

We want to have multi-upload from cli (usecase: go to my directory with photos and upload them all) and from web-interface (using maybe zip, maybe html5 feature). There is already https://github.com/VenKamikaze/mediagoblin-html5-multi-upload which might be what we need, so before choosing this task please verify.

'''Possible Mentors:''' Christopher Allan Webber, Boris Bobrov .

== Subtitle interface. ==

'''Possible Mentors:''' Christopher Allan Webber, Boris Bobrov

We want subtitle support for our player. Subtitles should be supported as separate files and as embedded into video/audio files. Popular formats should be supported. Also, there can be multiple subtitles per video. It will require work on front-end and maybe some fixes to backend.

== Multiple qualities of video. ==

Now MediaGoblin supports only a single quality of video files. We want to fix that and support multiple qualities: 360p, 480p, 720p, 1080p, 4k. This requires changes to frontend and to backend. To implement it, one must have some experience in JavaScript and Python.

'''Possible mentors''': Boris Bobrov

GSOC 2017

2016-02-15T23:27:29Z

Helen Christian: /* How do I apply as a student ? */ changing 'start!' and 'internship!' to 'start !' etc respectively.

We are hoping to participate in [https://developers.google.com/open-source/gsoc/ GSOC 2016] under the GNU umbrella.

You may want to check for a "possible mentor" before applying for this topic. If you have your own idea, probably bring it up in #mediagoblin on irc.freenode.net !

= How do I apply as a student ? =

* [https://developers.google.com/open-source/gsoc/ Submit your application]. Please see the application submission template on the [http://www.gnu.org/software/soc-projects/guidelines.html GNU GSoC guidelines page].
* [http://mediagoblin.org/pages/join.html Join us] on IRC and on our mailing lists.
* Set up a development environment via our [[HackingHowto]]
* If you have never done web development in python before, MediaGoblin is a pretty good place to start ! However, we highly recommend going through the [https://docs.djangoproject.com/en/1.7/intro/tutorial01/ Django tutorial]... this isn't a requirement, but it will help you be better prepared.
* Work on a small task, and mention it in your application. The [http://issues.mediagoblin.org/query?status=!closed&keywords=~bitesized bitesized list] is often helpful.
* Also, be aware when submitting: Summer of Code applicants are expected to work '''40 hours per week'''... so, a full time internship ! If you propose, please be sure you are ready to make that level of commitment.

It's important that you communicate... most MediaGoblin communication happens on IRC, so you should [http://webchat.freenode.net/?channels=mediagoblin join us there] and discuss (#mediagoblin on irc.freenode.net)! Please, please join our channel and introduce yourself. We would love to hear from you !

= Possible projects with mentors. =
== Chunked uploads / multi-upload UI. ==

We want to have multi-upload from cli (usecase: go to my directory with photos and upload them all) and from web-interface (using maybe zip, maybe html5 feature). There is already https://github.com/VenKamikaze/mediagoblin-html5-multi-upload which might be what we need, so before choosing this task please verify.

'''Possible Mentors:''' Christopher Allan Webber, Boris Bobrov

== Subtitle interface. ==

'''Possible Mentors:''' Christopher Allan Webber, Boris Bobrov

We want subtitle support for our player. Subtitles should be supported as separate files and as embedded into video/audio files. Popular formats should be supported. Also, there can be multiple subtitles per video. It will require work on front-end and maybe some fixes to backend.

== Multiple qualities of video. ==

Now MediaGoblin supports only a single quality of video files. We want to fix that and support multiple qualities: 360p, 480p, 720p, 1080p, 4k. This requires changes to frontend and to backend. To implement it, one must have some experience in JavaScript and Python.

'''Possible mentors''': Boris Bobrov

GSOC 2017

2016-02-15T23:21:06Z

Helen Christian: changing irc.freenode.net! to irc.freenode.net !

We are hoping to participate in [https://developers.google.com/open-source/gsoc/ GSOC 2016] under the GNU umbrella.

You may want to check for a "possible mentor" before applying for this topic. If you have your own idea, probably bring it up in #mediagoblin on irc.freenode.net !

= How do I apply as a student ? =

* [https://developers.google.com/open-source/gsoc/ Submit your application]. Please see the application submission template on the [http://www.gnu.org/software/soc-projects/guidelines.html GNU GSoC guidelines page].
* [http://mediagoblin.org/pages/join.html Join us] on IRC and on our mailing lists.
* Set up a development environment via our [[HackingHowto]]
* If you have never done web development in python before, MediaGoblin is a pretty good place to start! However, we highly recommend going through the [https://docs.djangoproject.com/en/1.7/intro/tutorial01/ Django tutorial]... this isn't a requirement, but it will help you be better prepared.
* Work on a small task, and mention it in your application. The [http://issues.mediagoblin.org/query?status=!closed&keywords=~bitesized bitesized list] is often helpful.
* Also, be aware when submitting: Summer of Code applicants are expected to work '''40 hours per week'''... so, a full time internship! If you propose, please be sure you are ready to make that level of commitment.

It's important that you communicate... most MediaGoblin communication happens on IRC, so you should [http://webchat.freenode.net/?channels=mediagoblin join us there] and discuss (#mediagoblin on irc.freenode.net)! Please, please join our channel and introduce yourself. We would love to hear from you !

= Possible projects with mentors. =
== Chunked uploads / multi-upload UI. ==

We want to have multi-upload from cli (usecase: go to my directory with photos and upload them all) and from web-interface (using maybe zip, maybe html5 feature). There is already https://github.com/VenKamikaze/mediagoblin-html5-multi-upload which might be what we need, so before choosing this task please verify.

'''Possible Mentors:''' Christopher Allan Webber, Boris Bobrov

== Subtitle interface. ==

'''Possible Mentors:''' Christopher Allan Webber, Boris Bobrov

We want subtitle support for our player. Subtitles should be supported as separate files and as embedded into video/audio files. Popular formats should be supported. Also, there can be multiple subtitles per video. It will require work on front-end and maybe some fixes to backend.

== Multiple qualities of video. ==

Now MediaGoblin supports only a single quality of video files. We want to fix that and support multiple qualities: 360p, 480p, 720p, 1080p, 4k. This requires changes to frontend and to backend. To implement it, one must have some experience in JavaScript and Python.

'''Possible mentors''': Boris Bobrov

GSOC 2017

2016-02-15T23:16:01Z

Helen Christian: /* How do I apply as a student ? */ changing we'd to we would. Don't use we'd :-)

We are hoping to participate in [https://developers.google.com/open-source/gsoc/ GSOC 2016] under the GNU umbrella.

You may want to check for a "possible mentor" before applying for this topic. If you have your own idea, probably bring it up in #mediagoblin on irc.freenode.net!

= How do I apply as a student ? =

* [https://developers.google.com/open-source/gsoc/ Submit your application]. Please see the application submission template on the [http://www.gnu.org/software/soc-projects/guidelines.html GNU GSoC guidelines page].
* [http://mediagoblin.org/pages/join.html Join us] on IRC and on our mailing lists.
* Set up a development environment via our [[HackingHowto]]
* If you have never done web development in python before, MediaGoblin is a pretty good place to start! However, we highly recommend going through the [https://docs.djangoproject.com/en/1.7/intro/tutorial01/ Django tutorial]... this isn't a requirement, but it will help you be better prepared.
* Work on a small task, and mention it in your application. The [http://issues.mediagoblin.org/query?status=!closed&keywords=~bitesized bitesized list] is often helpful.
* Also, be aware when submitting: Summer of Code applicants are expected to work '''40 hours per week'''... so, a full time internship! If you propose, please be sure you are ready to make that level of commitment.

It's important that you communicate... most MediaGoblin communication happens on IRC, so you should [http://webchat.freenode.net/?channels=mediagoblin join us there] and discuss (#mediagoblin on irc.freenode.net)! Please, please join our channel and introduce yourself. We would love to hear from you !

= Possible projects with mentors. =
== Chunked uploads / multi-upload UI. ==

We want to have multi-upload from cli (usecase: go to my directory with photos and upload them all) and from web-interface (using maybe zip, maybe html5 feature). There is already https://github.com/VenKamikaze/mediagoblin-html5-multi-upload which might be what we need, so before choosing this task please verify.

'''Possible Mentors:''' Christopher Allan Webber, Boris Bobrov

== Subtitle interface. ==

'''Possible Mentors:''' Christopher Allan Webber, Boris Bobrov

We want subtitle support for our player. Subtitles should be supported as separate files and as embedded into video/audio files. Popular formats should be supported. Also, there can be multiple subtitles per video. It will require work on front-end and maybe some fixes to backend.

== Multiple qualities of video. ==

Now MediaGoblin supports only a single quality of video files. We want to fix that and support multiple qualities: 360p, 480p, 720p, 1080p, 4k. This requires changes to frontend and to backend. To implement it, one must have some experience in JavaScript and Python.

'''Possible mentors''': Boris Bobrov

GSOC 2017

2016-02-15T23:14:20Z

Helen Christian: punctuation change 'fullstops' after headings.

We are hoping to participate in [https://developers.google.com/open-source/gsoc/ GSOC 2016] under the GNU umbrella.

You may want to check for a "possible mentor" before applying for this topic. If you have your own idea, probably bring it up in #mediagoblin on irc.freenode.net!

= How do I apply as a student ? =

* [https://developers.google.com/open-source/gsoc/ Submit your application]. Please see the application submission template on the [http://www.gnu.org/software/soc-projects/guidelines.html GNU GSoC guidelines page].
* [http://mediagoblin.org/pages/join.html Join us] on IRC and on our mailing lists.
* Set up a development environment via our [[HackingHowto]]
* If you have never done web development in python before, MediaGoblin is a pretty good place to start! However, we highly recommend going through the [https://docs.djangoproject.com/en/1.7/intro/tutorial01/ Django tutorial]... this isn't a requirement, but it will help you be better prepared.
* Work on a small task, and mention it in your application. The [http://issues.mediagoblin.org/query?status=!closed&keywords=~bitesized bitesized list] is often helpful.
* Also, be aware when submitting: Summer of Code applicants are expected to work '''40 hours per week'''... so, a full time internship! If you propose, please be sure you are ready to make that level of commitment.

It's important that you communicate... most MediaGoblin communication happens on IRC, so you should [http://webchat.freenode.net/?channels=mediagoblin join us there] and discuss (#mediagoblin on irc.freenode.net)! Please, please join our channel and introduce yourself. We'd love to hear from you!

= Possible projects with mentors. =
== Chunked uploads / multi-upload UI. ==

We want to have multi-upload from cli (usecase: go to my directory with photos and upload them all) and from web-interface (using maybe zip, maybe html5 feature). There is already https://github.com/VenKamikaze/mediagoblin-html5-multi-upload which might be what we need, so before choosing this task please verify.

'''Possible Mentors:''' Christopher Allan Webber, Boris Bobrov

== Subtitle interface. ==

'''Possible Mentors:''' Christopher Allan Webber, Boris Bobrov

We want subtitle support for our player. Subtitles should be supported as separate files and as embedded into video/audio files. Popular formats should be supported. Also, there can be multiple subtitles per video. It will require work on front-end and maybe some fixes to backend.

== Multiple qualities of video. ==

Now MediaGoblin supports only a single quality of video files. We want to fix that and support multiple qualities: 360p, 480p, 720p, 1080p, 4k. This requires changes to frontend and to backend. To implement it, one must have some experience in JavaScript and Python.

'''Possible mentors''': Boris Bobrov

GSOC 2017

2016-02-15T23:11:28Z

Helen Christian: punctuation change from 'student?' to 'student ?'

We are hoping to participate in [https://developers.google.com/open-source/gsoc/ GSOC 2016] under the GNU umbrella.

You may want to check for a "possible mentor" before applying for this topic. If you have your own idea, probably bring it up in #mediagoblin on irc.freenode.net!

= How do I apply as a student ? =

* [https://developers.google.com/open-source/gsoc/ Submit your application]. Please see the application submission template on the [http://www.gnu.org/software/soc-projects/guidelines.html GNU GSoC guidelines page].
* [http://mediagoblin.org/pages/join.html Join us] on IRC and on our mailing lists.
* Set up a development environment via our [[HackingHowto]]
* If you have never done web development in python before, MediaGoblin is a pretty good place to start! However, we highly recommend going through the [https://docs.djangoproject.com/en/1.7/intro/tutorial01/ Django tutorial]... this isn't a requirement, but it will help you be better prepared.
* Work on a small task, and mention it in your application. The [http://issues.mediagoblin.org/query?status=!closed&keywords=~bitesized bitesized list] is often helpful.
* Also, be aware when submitting: Summer of Code applicants are expected to work '''40 hours per week'''... so, a full time internship! If you propose, please be sure you are ready to make that level of commitment.

It's important that you communicate... most MediaGoblin communication happens on IRC, so you should [http://webchat.freenode.net/?channels=mediagoblin join us there] and discuss (#mediagoblin on irc.freenode.net)! Please, please join our channel and introduce yourself. We'd love to hear from you!

= Possible projects with mentors =
== Chunked uploads / multi-upload UI ==

We want to have multi-upload from cli (usecase: go to my directory with photos and upload them all) and from web-interface (using maybe zip, maybe html5 feature). There is already https://github.com/VenKamikaze/mediagoblin-html5-multi-upload which might be what we need, so before choosing this task please verify.

'''Possible Mentors:''' Christopher Allan Webber, Boris Bobrov

== Subtitle interface ==

'''Possible Mentors:''' Christopher Allan Webber, Boris Bobrov

We want subtitle support for our player. Subtitles should be supported as separate files and as embedded into video/audio files. Popular formats should be supported. Also, there can be multiple subtitles per video. It will require work on front-end and maybe some fixes to backend.

== Multiple qualities of video ==

Now MediaGoblin supports only a single quality of video files. We want to fix that and support multiple qualities: 360p, 480p, 720p, 1080p, 4k. This requires changes to frontend and to backend. To implement it, one must have some experience in JavaScript and Python.

'''Possible mentors''': Boris Bobrov