On 06/11/2014 01:39 AM, Andrew Savchenko wrote: > On Sat, 7 Jun 2014 23:08:15 +0200 Jeroen Roovers wrote: >> On Sat, 07 Jun 2014 15:35:04 -0500 >> Daniel Campbell <cont...@sporkbox.us> wrote: >> >>>> [2]: Overview of bugs that involve OpenRC, most for the package >>>> itself. https://bugs.gentoo.org/buglist.cgi?quicksearch=openrc >> >>> I think working on OpenRC would be a great learning experience for me >>> and would be a great opportunity to contribute to Gentoo. >> >> You can start fixing bugs immediately. You can check out the sources, >> write patches and attach the patches to the bug reports. Then all it >> takes is someone else to review/commit the patches. > > And who will review patches made? There are already six push > requests pending on OpenRC github for a long time: > https://github.com/OpenRC/openrc/pulls > And some of them are fixing long-standing severe bugs such as > https://bugs.gentoo.org/show_bug.cgi?id=391945 is fixed by: > https://github.com/OpenRC/openrc/pull/12 > https://github.com/OpenRC/openrc/pull/13 > We tested these patches on our infra and they work fine. Though > without upstream accepting/reviewing these changes for a long time > all enthusiasm dies slowly...
Some people like me don't github, so if it's not a bugreport on bugs.g.o it'll just be ignored. Duplicating stuff like that is still a bad idea ... (I have no idea why some people are so eager to have multiple writable clones of repositories) > > I understand that all devs have issues of their own to handle and I > don't want to blame anyone due to a lack of time. I just want to > point out that lack of contributions is only one side of a problem. > Another one is that someone with proper authority should take care > of such contributions. As long as they are in the right place
