My guess: 1. Ping the people involved in the review, privately. 2. If you get no answer from them in a week, ping someone else that you think might have to do with the project you are modifying. 3. If you known of no one else, or you get no answer for a week, ping the mailing list of the project you are submitting the patch for. 4. If there is no such mailing list, or you get no answer for a week, ping the mailing list of a parent of the project you are submitting the patch for. 5. Repeat the previous step (4) for the mailing lists of as many parent groups as there are for the target project, until you reach kde-devel. (e.g. first try kde-proj...@kde.org, then kde-mod...@kde.org, then kde-devel@kde.org).
Nothing wrong with going directly to kde-devel, though, if you feel like you need to :) O Luns, 11 de Marzo de 2013 23:12:22 Alexey Shmalko escribiu: Hi, I am new to OpenSource development, so I need some help. I've wrote a patch that fixes this bug. https://bugs.kde.org/show_bug.cgi?id=217560[1] The patch is on reviewboard. https://git.reviewboard.kde.org/r/106110/[2] It seems that acceptance process is running for too long, because I've sent patch six months ago. And it isn't accepted yet. What should I do? -------- [1] https://bugs.kde.org/show_bug.cgi?id=217560 [2] https://git.reviewboard.kde.org/r/106110/
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
