On Tue, Sep 12, 2017 at 8:31 AM, Matthias Bläsing wrote: I was able to push the fix, because there is/was no RTC system in place > and so I could override the "process". > > There are many areas in netbeans that are just plain not interesting > and were maybe one person will look into. How should he/she get one > reviewer, let alone 3? >
You've explained the difference between a company-driven project and an Apache-driven project. NetBeans under Oracle had very different aims to NetBeans in Apache. There are not going to be any areas that are "just plain not interesting" in Apache NetBeans. And there'll be a lot more engineers involved, i.e., there are currently already more committers to Apache NetBeans than there were under Oracle. Gj On Tue, Sep 12, 2017 at 8:31 AM, Matthias Bläsing <mblaes...@doppel-helix.eu > wrote: > Hey, > > Am Dienstag, den 12.09.2017, 07:58 +0200 schrieb Jaroslav Tulach: > > I vote for RTC all the time for all changes. It is easy with GitHub > > pull requests. > > nobody asked for votes. I added an argument to not change the modus of > operation for netbeans commits. I'll add another one: > > https://netbeans.org/bugzilla/show_bug.cgi?id=270672 > > There is a solution for a problem. The solution stands 3 months without > any reaction from netbeans engineers and after that time I was fed up > enough to just push the fix directly. > > I was able to push the fix, because there is/was no RTC system in place > and so I could override the "process". > > There are many areas in netbeans that are just plain not interesting > and were maybe one person will look into. How should he/she get one > reviewer, let alone 3? > > Greetings > > Matthias >
