walt posted on Sun, 28 Feb 2016 15:14:59 -0800 as excerpted: > Works For Me too :) Guys, thank you for your excellent detective > work. That's such a simple bug but very hard to find. Now, how to get > someone to commit the fix to the git repo? The pan bug reports aren't > getting much love lately from the gnome.org devs.
I think Petr Kovar still does what he can as pan's official gnome face, but he's a l10n (localization, aka translation) specialist, not really a code-writing dev, so he needs patches that can be simply applied, not code descriptions of what's wrong and how to fix it. And of course given a patch, he needs some idea of whether it's correct or not as well, so particularly for patches from people who don't have a trusted history of supplying good patches, either to gnome in general or to pan, having on- list people saying "yes, this looks correct" or even simply "yes, this corrects the problem for me, tho I don't know enough code to say for sure it's correct", helps. Of course without a real dev (gnome affiliated or not) to actively feed him patches (KHaley wasn't gnome affiliated and wasn't interested in becoming gnome affiliated, so he and PKovar complimented each other nicely, Heinrich wasn't gnome affiliated at first, but AFAIK, PKovar gave him perms for pan, which Heinrich could have used to more easily get perms for other gnome projects, tho I'm not sure he ever did), PKover can't do too much on his own, and Heinrich has graduated and moved on to a real life job and likely family, so pan is basically stagnated, once again. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman _______________________________________________ Pan-users mailing list Pan-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/pan-users
