GNOME Bugzilla – Bug 639148
Request to host new project: frogr
Last modified: 2011-01-11 09:57:04 UTC
Hi, As suggested by Claudio Saavedra, I'm formally asking for the possibility of hosting my project 'frogr: flickr remote organizer for GNOME' in the GNOME infrastructure, so here you have the needed info about it: Name: 'frogr' ----- Description (as it was described at the request to package it for Debian [1]): ------------------------------------------------------------------------------ "Frogr is a small application for the GNOME desktop that allows users to manage their accounts in the Flickr image hosting website. It supports all the basic Flickr features, including uploading pictures, adding descriptions, setting tags and managing sets." Links: ------ * Website: http://code.google.com/p/frogr * Tarballs for the last release (0.3): http://frogr.googlecode.com/files/frogr-0.3.tar.gz http://frogr.googlecode.com/files/frogr-0.3.tar.bz2 * Upstream code (currently at gitorious): http://gitorious.org/frogr * Some distro-specific packages: http://code.google.com/p/frogr/downloads/list Why to include it? ------------------ After checking the ProjectPrerequisites wiki page [2], I think this project would match the prerequisites because: * It's Free Software, licensed under the terms of the GPLv3 (for the application itself) and the LGPLv3 (for the bundled-in library developed along with it, not released separately yet) licenses. * It entirely uses GNOME/GTK+ technologies, strictly depending on Glib, GTK+, libsoup2.4 and libxml2 only. * Even if it's being developed mainly in my spare time only (which is not a lot lately), the project started back in April 2009 and already has 3 releases out ([2], [4] and [5]), the last one just some weeks ago [4] * "To the best of my knowledge, it doesn't infringe any patent" :-) Current last version of frogr is just an flickr uploader with some nice features (such as adding to albums) that were not present in prior releases (due to using another dependency, no longer present in 0.3: libflickcurl), but I'm planning to release in the following weeks the 0.4 version [6] (as soon as I have properly tested and stabilized it), which I've been working hard on during Christmas holidays to make it a really complete app for interacting with flickr from the GNOME desktop. And that's yet another reason why I'm asking for this right now: I'd love to be able to have frogr hosted in GNOME by then, as simple as that :-) [IMPORTANT] About my (not existent yet) gnome.org account: --------------------------------------------------------- Back in March, I went through the NewAccounts section [7] and filled in the Mango form [8] to request a .gnome.org git account to commit changes directly to epiphany, as I started to work on WebKitGTK on a daily basis and would find handy to be able to directly commit to ephy whenever a patch was created because of my work there in WK world. Back then, I asked for 'msanchez' as the username and filled the rest of the fields accordingly, sent the form and confirmed the request when received a mail in my INBOX, right after that. However, I never got any feedback about my request, so I asked ephy maintainer (Xan Lopez) after reading the FAQ [9], but he said that there was no mail from the Mango system at his INBOX and the process got stuck there. Fortunately, at the end I did not need the git account as much as I thought for epiphany, but I'm afraid the process remains stuck (and I dare not to fill the form again, since it's very clearly stated I shouldn't do that) and perhaps you could find any trouble while creating now an account, in case this request got approved, for me to move my project to GNOME. So that's why I mention it. So, that's all. Thanks in advance and sorry for the long report. Don't hesitate to contact me in case of having any doubt [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607889 [2] http://live.gnome.org/ProjectPrerequisites [3] http://mail.gnome.org/archives/gnome-announce-list/2009-August/msg00068.html [4] http://mail.gnome.org/archives/gnome-announce-list/2009-October/msg00023.html [5] http://mail.gnome.org/archives/gnome-announce-list/2010-December/msg00045.html [6] http://gitorious.org/frogr/mainline/blobs/master/NEWS [7] http://live.gnome.org/NewAccounts [8] https://mango.gnome.org/new_account.php [9] http://live.gnome.org/MangoFAQ
Mario - In order to fulfill this request we will need to get your account application confirmed and created. Could you please go through the application process again (despite the warning you mentioned) and follow up until it is completed? We'll be happy to host your project, we just need to get that formality out of the way first. Thank you, Christer
I've tried that, but whenever I fill the Mango form and try to submit it, I get an error highlighting (in red color) the username and e-mail fields, and stating the following error: This email address has already been used. So it looks like the previous (failed process) is still blocking this... Should I pick then another nickname/email address (I'd prefer not), or is there any possibility to keep doing this process in a manual way? (something like stated at the end of the NewAccounts page [1], I guess) Mario [1] http://live.gnome.org/NewAccounts
Mario - We did a little bit of digging and pulled the account request out of the pending queue (looks like it got overlooked and just got stuck in limbo). In any case, your account has been approved and created. You should see your git access active within an hour.
To begin hosting your project on the GNOME servers, please see this link regarding creating a new Git repository. http://live.gnome.org/Git/NewRepository Also, please let us know (in a new ticket) if you require a mailing list and if you have archives that you would like migrated. Thank you, Christer
(In reply to comment #3) > Mario - > > We did a little bit of digging and pulled the account request out of the > pending queue (looks like it got overlooked and just got stuck in limbo). In > any case, your account has been approved and created. You should see your git > access active within an hour. Wow.. That was fast! Thanks a lot for your help, and please accept my apologies in case the cause my previous attempt fell in limbo was my fault :-) I'll re-read the documentation once again and will try the account as soon as possible. About the mailing list, to be honest the two Google groups I set up in the past have never had much traffic but perhaps this is the right moment to create a single frogr-list mailing list under gnome.org (instead of two -users and -devel ML's, as I have in GG) and get rid as well of Google code in that regard (unless you tell me that there's no point on such a thing and that it would be better to keep it as it is now, in GG, of course). What I'd be really interested in, however, would be in having a component in bugzilla for frogr, because I do use GC "issues" and do not like it that much. I'll file a new bug for that as soon as I finish the other steps. Thanks again, Mario
Don't forget to email gnome-i18n@gnome.org once you create your repository, so that they add frogr to extras in damned-lies.
(In reply to comment #6) > Don't forget to email gnome-i18n@gnome.org once you create your repository, so > that they add frogr to extras in damned-lies. Thanks for the tip, but I must say the .po files are not very updated atm since I've been changing things like mad the last weeks, and I still have some more changes planned involving l10n strings, so I guess it will be better that I mail them once the l10n strings are more settle down. I don't want nobody devoting time now to translate things that are likely to change in the short term :-)
(In reply to comment #4) > To begin hosting your project on the GNOME servers, please see this link > regarding creating a new Git repository. > http://live.gnome.org/Git/NewRepository Done. The project is now listed with the [PENDING] tag. I understand I must do nothing while it doesn't change to another state. Btw, I have a doubt: by reading the "Maintainers' corner: Making a release" [1] and the AccountPolicy [2], among other pages, it seems that I'd need also a shell account to log into master.gnome.org and make the releases through the 'install-module' command. Thing is that after reading so many pages it's not clear to me how I should ask for that, probably mailing to accounts@gnome.org or support@gnome.org, but I'm not sure. Could somebody confirm this? Thanks in advance. > Also, please let us know (in a new ticket) if you require a mailing list and if > you have archives that you would like migrated. > Done: https://bugzilla.gnome.org/show_bug.cgi?id=639183 Thanks! (off to bed now) Mario [1] http://live.gnome.org/MaintainersCorner/Releasing [2] http://live.gnome.org/AccountPolicy
(In reply to comment #8) > Btw, I have a doubt: by reading the "Maintainers' corner: Making a release" [1] > and the AccountPolicy [2], among other pages, it seems that I'd need also a > shell account to log into master.gnome.org and make the releases through the > 'install-module' command. Thing is that after reading so many pages it's not > clear to me how I should ask for that, probably mailing to accounts@gnome.org > or support@gnome.org, but I'm not sure. > > Could somebody confirm this? Thanks in advance. I believe the info you're looking for is here: http://live.gnome.org/NewAccounts
You need a doap file in the root of your project that identifies you as the maintainer. An example would be: http://git.gnome.org/browse/snowy/tree/snowy.doap
(In reply to comment #10) > You need a doap file in the root of your project that identifies you as the > maintainer. An example would be: > http://git.gnome.org/browse/snowy/tree/snowy.doap I already have that in my former repo at gitorious [1], not pushing because I read I shouldn't push while on [PENDING] state, as reading the docs it seems like if someone else needed to change that first: "Once you've done that, your repository is in a special "pending" mode indicating that the import is not complete, and will show up on http://git.gnome.org/browse/ prepending with [PENDING]. Normal pushes to you repository are not allowed as long as it is pending." ...but perhaps that just means that the I should just go ahead with the initial import, containing that doap file. Could you confirm? Thanks! [1] gitorious.org/frogr/mainline/blobs/master/frogr.doap
I misread sorry, I realized after reading through the Archives of some GNOME mailing lists and asking some people here. Now it's everything up and running. Sorry for the hassle