Hi, I wanted to request an fd.o account for use with GStreamer CVS. realname: Sebastian Dröge email: slomo@circular-chaos.org prefered account name: sdroege GPG key and SSH public key attached. Bye
Created attachment 7977 [details] gpg.key
Created attachment 7978 [details] ssh.key
Oh I thought I saw some rules for the account name... must've been somewhere else then ;) So my preferred account name would be "slomo" if still available, otherwise "sdroege" as before...
Sebastian, can you link to some bugs/patches/motivation you did on GStreamer ? Thanks, Thomas
The following Gnome bugs contain GStreamer patches by me that were already committed... I might've missed some though: 379918 343127 382982 383726 387866 327350 369627 377332 343122 344472 351663 369539 351495 351659 351557 343131 352476 347443 387076 The main motivation to file this bug was that thaytan and MikeS asked me on IRC whether I already have a CVS account and that I should get one. My main goals for GStreamer are random bugfixing to improve the overall quality, getting the wavpack plugin to plugins-good and improving it, create some new elements (maybe port the shorten element to 0.10 in the next time, create some audio effect plugins with the help of Stefan Kost, ...). In the past I've spent much of my free time with distribution specific stuff (I'm maintaining the GStreamer packages for Ubuntu and Debian and will continue to do so ;)) but wanted to spend more time with coding in the future. Bye
If you need some further information or have some more questions feel free to ask :)
Ok, added. Sorry for the delay, was on holiday. Reopen if there is any problem. Thanks Thomas
Thanks :) But although the mail said that the password would be attached GPG encrypted to the mail I got there was no attachment or anything else that looked like a password :/
Ok, should probably be closed again... as no password is required but everything works with the ssh key.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.