Email address: firstname.lastname@example.org
Preferred account name: gibrovacco
Created attachment 40512 [details]
gpg public key
Created attachment 40513 [details]
ssh rsa public key
Marco told me on IRC, that he would like especialy in the area of GStreamer rtp and rtsp, including improvements in the documentation and tests. +1 from my side.
Marco, I think you're definitely a good candidate for a git account (active in the community / on the mailing list, good understanding of some subsystems), but if I apply the criteria we usually apply to account requests, I'd come to the conclusion that it's maybe still a bit early. I haven't actually found a lot of code contributions or other contributed patches from you in git, but maybe I didn't look hard enough :-)
(In reply to comment #4)
> Marco, I think you're definitely a good candidate for a git account (active in
> the community / on the mailing list, good understanding of some subsystems),
> but if I apply the criteria we usually apply to account requests, I'd come to
> the conclusion that it's maybe still a bit early. I haven't actually found a
> lot of code contributions or other contributed patches from you in git, but
> maybe I didn't look hard enough :-)
Actually, they're not too many. Here's the list of bugs I've contributed to fix with my patches:
You might also find something from me (especially h264 parsing) in gst-dsp.
For at least a couple of them (628214, 630046), even if I submitted and revised the patches many times the versions ending up to the git repo were slightly modified versions authored by other people (I'd say 4-5 patches if I remember well).
My dual identity (gibrovacco / Marco Ballesio ad Nokia) does not definitely help in identifying all of my contributions.
FWIW, I'm also the maintainer of the Gladstone project (g729 reference code based elements), never submitted for inclusion in gst-plugins-bad for issues related to reference code distribution (the same for which it is not provided together with my sources):
As mentioned before, if I apply the same criteria we usually apply to all other account requests, I have to conclude that there just isn't enough patch flow at the moment, and the patches supplied that aren't trivial often still need work or review. There also doesn't seem to be a sign of increasing activity or any other reason for a developer account such as maintainership of a module or plugin, at least not at the moment.
So let's just close this for the time being.
Marco, feel free to re-open the bug at a later date when you think the situation has changed.