After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 628206 - Git request for nautilus-sound-converter
Git request for nautilus-sound-converter
Status: RESOLVED FIXED
Product: sysadmin
Classification: Infrastructure
Component: Git
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GNOME Sysadmins
GNOME Sysadmins
Depends on:
Blocks:
 
 
Reported: 2010-08-28 18:09 UTC by Brian Pepple
Modified: 2010-08-30 14:10 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Brian Pepple 2010-08-28 18:09:37 UTC
I received an e-mail about my request being closed for lack of activity. What happened to my request that was made around August 1st? I've yet to hear anything about it, and frankly it's fairly frustrating just how many different times I've made this request to either be told to use a different form to request it, or hear absolutely nothing about it. If I hadn't been contributing to GNOME either through patches directly or through maintaining a number of GNOME projects (Empathy, Telepathy stack, Gossip,  Meld, XChat-GNOME, etc) for Fedora for the last 6 or so years I'd understand, but how many more hoops do I need to jump through to get an answer. Apologize if this is overly-emotional/critical but this has been going on for so long my frustration has gotten to the point that I really question if I should spend anymore of my free time contributing to GNOME at all. If I could get some sort of definitive answer it would really be appreciated.
Comment 1 Olav Vitters 2010-08-28 18:23:57 UTC
With Git, can't you just create a new repository using http://live.gnome.org/Git/NewRepository?
Comment 2 Brian Pepple 2010-08-28 18:28:23 UTC
(In reply to comment #1)
> With Git, can't you just create a new repository using
> http://live.gnome.org/Git/NewRepository?

Sorry, forgot to mention in my rant that my original request was for a gnome.org git account.
Comment 3 Olav Vitters 2010-08-28 18:34:33 UTC
What ticket number did your Git account request have?
Comment 4 Christer Edwards 2010-08-28 18:36:55 UTC
Brian - again, we apologize for letting your original ticket stall. We are in the process of refreshing our ticket queue, and part of that means finding out which tickets are still valid. I understand your frustration.

If you need a gnome.org git account, please see: http://live.gnome.org/NewAccounts

If you need additional help, please contact us in #sysadmin on irc.gnome.org, or email me at christer dot edwards at gmail dot com.

Christer
Comment 5 Brian Pepple 2010-08-28 19:06:24 UTC
@Olav: Not sure what the ticket number was since I can't locate the e-mail confirmation for my request. I'll go ahead and fill out a new request from link Christer gave.
Comment 6 Brian Pepple 2010-08-28 19:11:14 UTC
Hmm, attempting to fill out the form and I'm getting an error that my e-mail address and user name is already being used. So, apparently my request is somewhere within the system.

http://bpepple.fedorapeople.org/error.png
Comment 7 Olav Vitters 2010-08-28 19:30:56 UTC
Checking Mango manually I see you requested a voucher from the Empathy maintainers. They haven't vouched for you. Until that has happened, we (accounts team, though in this case the sysadmin team) cannot do anything, or are notified.

Could you check please with the Empathy maintainers. They should log in to Mango and approve your git request.
Comment 8 Christer Edwards 2010-08-30 12:37:26 UTC
@Brian - I have tried contacting the Empathy maintainers via IRC with no response. If you're still actively working with these people, a simple reminder to attend to their queue would move things along.
Comment 9 Guillaume Desmottes 2010-08-30 14:08:34 UTC
Sorry I missed the mail. I just approved the request in Mango.

Again, sorry for the delay.
Comment 10 Olav Vitters 2010-08-30 14:10:45 UTC
User created. It will activate at x:00 (meaning 15:00 UTC). After that you can follow the instructions given in comment 1.

Closing as resolved. Please reopen if something is wrong.