Comment 148 for bug 44082

No, because i'm not familiar with gnome-panel code, it would take me a few hours to get acquainted with how it works. (if i'm correct on how much code there is in the gnome panel) 10/15 minutes of comment writing is a much smaller amount of time. Now if I was familiar with the code, I probably would've worked on that. However, I don't have a few hours to spend just to understand the layout of the code, let alone to fix the problem... I've got too much school work. However, the team of people intimately familiar with the gnome-panel code should either be able to write that code in well under a weekend's worth of work or the gnome-panel should be trashed in favor of a cleaner code base. I know from personal experience that if I am a lazy programmer, code will become unmanageable, making functionality changes nearly impossible. But, if I wrote code in a clean, structured way; development would proceed faster with less bugs, and future revisions to the functionality would be relatively painless.

So unless I spend the whole night writing 5 minute comments, I would not have even been able to come close to fixing this bug. Someone who is familiar with the code base should be able to fix the code in a few hours work tops, assuming the code is complicated. If this is not possible, than I think it must be time to reconsider the value of this panel. Perhaps I'm missing some key fact, but I don't think it should take four years of procrastination to fix such a bug as this. Let me know the next time your firefox bookmarks bar rearranges itself.