GNOME Bugzilla – Bug 651796
media-explorer-list@gnome.org
Last modified: 2011-06-16 13:15:20 UTC
Hi, I'd like to create a mailing list for media-explorer on the GNOME infrastructure. Media explorer is a media center type of application with strong bounds to GNOME. It is using GNOME-related technologies as Clutter, Grilo, Tracker, Mx, rest, soup, dbus-glib, ... * Mailing list name: media-explorer-list@gnome.org * Mail address of the primary administrator: damien.lespiau@gmail.com Thanks.
I forgot to put a link to the actual project code source. We are hosting it on github. https://github.com/media-explorer/media-explorer
Why not have the project on git.gnome.org?
As a group of people developing media-explorer we decided to use github. While I was reticent at first, I have to admit that github is quite nice, offers useful features and seems to lower the barrier for contributors and advanced users (reporting issues, branching and asking for pulls, follow a project, project wiki (Vs the more general live.gnome.org), a way to have public static pages on http://media-explorer.github.com/ by pushing them into a git repo, ...) Don't get me wrong the GNOME infrastructure as an exceptional integration level when it comes to accounts, bugzilla, tarballs but the "project-centric" nature of github is quite appealing. You also have to add the fact that having it on github does not strongly link the project with GNOME (despite using *a lot* of the GNOME stack) which, depending on who you talk to is a good or a bad thing. Now, why ask for a @gnome.org ml? I got the feeling that the project needed one, say to be a better citizen, and we (through a small Friday afternoon vote :p) would rather use a @gnome.org one to start showing our links to the GNOME project (to be completely transparent, 1/3 of the people answered that they'd rather not have another potentially low-traffic mailing-list to watch and try to find something else). If you feel like hosting the source code on gnome.org should be part of the prerequisite to get a mailing list on gnome.org, that would be totally understandable (and needs to be mentioned on the wiki page :p) and FWIW, the backup plan is clutter-project.org or bite the bullet and administrate it myself.
ping? Note that if is bug is stalled because people don't know if they should allow a project not hosting the source code on gnome.org to get a @gnome.org mailing list, it's really fine to say no. It is in fact much better then saying nothing :p We have a @clutter-project.org back up plan. Thanks for your time!
1. There was a bug in our mailman package which I wanted to fix (and did) 2. I cannot make up my mind -- I want everything on GNOME infrastructure.. and only using it partly seems.. lacking
Thanks for your quick answer. I think it's reasonable to expect that a project has to be a "better" GNOME project to get a @gnome.org ml. This may happen in the future but, for now, we'd like to stay on github. We'll have a @clutter-project.org ml then,. Thanks for you time, choosing a somewhat funny resolution :p