#939 lbazan: requesting provenpackager
Closed None Opened 11 years ago by lbazan.

Always in my spare time I contribute to the fedora community 100% in everything I can, Now I have much more free time and I can support as provenpackager is something I like I feel ready just wait in expectation of positive votes to enter this new line of action.

FAS: lbazan
IRC: LoKoMurdoK
Best Regards!!


Sent to list for feedback.

Unfortunately we're no longer allowed to give our feedback privately. Here's my on-list commentary; I'll try to format it a bit to keep trac from destroying it.

Appears to maintain (or co-maintain) 21 packages:

  • Perlbal -- Reverse-proxy load balancer and webserver
  • archmage -- Extensible reader/decompiler of files in CHM format
  • bmake -- The NetBSD make(1) tool
  • django-flash -- A Django extension to provide support for Rails-like flash
  • django-recaptcha -- A Django application for adding ReCAPTCHA to a form
  • django-typepad -- A helper Django app for making TypePad applications
  • eg -- Git for mere mortals
  • eruby -- An interpreter of embedded Ruby language
  • fbterm -- A frame buffer terminal emulator
  • flpsed -- WYSIWYG pseudo PostScript editor
  • gnome-rdp -- Remote Desktop Protocol client for the GNOME desktop environment
  • innotop -- A MySQL and InnoDB monitor program
  • koverartist -- Create CD/DVD covers
  • mk-files -- Support files for bmake, the NetBSD make(1) tool
  • perl-SVN-Simple -- A simple interface for writing a delta editor
  • perl-Term-Animation -- ASCII sprite animation framework
  • python-django-setuptest -- Simple module enabling Django app testing
  • python-typepad -- Connectivity to the TypePad API through remote objects
  • sonata -- An elegant GTK+ client for the Music Player Daemon (MPD)
  • svn2cl -- Create a ChangeLog from a Subversion log
  • xrdp -- Open source remote desktop protocol (RDP) server

Submitted ten review tickets, though to me it looks as if only a single
one was completed (with a few in progress):

https://bugzilla.redhat.com/buglist.cgi?email1=%20bazanluis20%40gmail.com&emailreporter1=1&emailtype1=substring&component=Package%20Review&qu\
ery_format=advanced

Reviewed no packages at all that I can find. (There are no package
review tickets assigned to him.)

There doesn't appear to be any compelling reason stated here and not a
whole lot of track record to go on. -1 from me.

Since a proven packager should be fit in every dimension of packaging, I think, a proven packager should have done a significant number of non-trivial reviews.

Luis, you should do some more reviews yourself. If you have got some spare time now, you could start immediately. As a proven packager, you should support packagers e.g. through diffs to their packages. I'm sure, you'll get commit acls, when it seems necessary.

-1 from me.

I agree with tibbs and mrunge. Proven packagers need extensive knowledge of Fedora policies and how rpm works, and you have to demonstrate that you are up to the task.

The best way to help improving Fedora at the moment is to perform reviews and thus shorten the huge list of packages waiting for a reviewer. I can tell by my own experience that by doing it you will also learn a lot of the skills necessary to become provenpackager.

Hi Luis,

One of my concerns is that I saw a flurry of commits on the EPEL 5/6 branches of perl-Danga-Socket and perl-Sys-Syscall. The commits were quite hard to follow, and then both packages were orphaned soon after perl-Sys-Syscall hit stable in Bodhi.

I can understand the occasional mistake during a commit+push - I have done quite a few myself! The thing is that we're working as a big team here, and it's important to communicate well with others when you change packages. One way to do that is to be very explicit in commit messages. To take the perl-Danga-Socket package as an example, you bumped the release version from 1 to 7 with no explanation as to why we would see such a big bump, and then in the next commit you bumped it back down, again with no explanation in the git log. If you make a mistake, it's a good idea to write a sentence or two in the next commit log, saying something like "The previous commit (abcdef0123) was an error, because such-and-such. I'm fixing it by doing so-and-so." When you clearly explain your reasoning, then we can all understand that yes, you know what you're doing, and it was an honest mistake.

There were also other commits with release bumps, and the log message was "rebuild again to check log". It's best to do mock builds on your local computer instead of using Fedora's build system for experimentation.

The last issue is that you orphaned perl-Danga-Socket without reverting your commits, so it is FTBFS on el6 now. In the future, please just revert your commits (and re-upload the older tarball), so that others don't have to clean up the mess.

-1 from me, for the reasons stated above.

I recall you revived two packages I orphaned (gnome-applet-remmina and xfce4-remmina-plugin) without looking at the dead.package files or contacting me. When I told you that these packages were replaced by a generic trayicon, you never replied.

You also applied for commit privileges to two other packages (menu-cache and lxpanel) and again I contacted you, asking for your plans with these. Again, I received no reply.

Communication is a key to becoming a good contributor. I am afraid that if become a proven packager and can touch any package you want, things will become worse. Please try to work with the package maintainers, not behind their back.

I also agree you still need to learn some more things, so for now I am -1. Keep up the good work, try to improve your communication and cooperation and then apply again. Thanks!

I apologize in advance for these annoying problems will not happen again, I will improve in all aspects and will apply again when ready.

Best Regards!!

Closing then; thanks for the feedback and help; lbazan, great attitude and we appreciate your enthusiasm for Fedora and willingness to improve.

Login to comment on this ticket.

Metadata