Hi Nyall,
We (at Oslandia) heard your call for more volunteers in reviewing the backports and PRs. We are very well aware that our contribution effort for this task is not enough. I see mainly two reasons: - Lack of time and human ressources to fullfill this task. This is a bad reason, and a well known situation that we need to take care of internally, to free our schedule. - A very partial knowledge of the code base in which we feel relevant to review. I try myself to review all Oracle related PRs, or take a look in some part of the code I know enough to make a good review, but it's very little compared to the QGIS code base. I hesitated answering your first email, saying basically that we will try to improve the situation, but it would have been just a promise, and I'm not sure that we would have been able to keep it, regarding the points I described above. Kind regard, Julien > On Tue, 23 Mar 2021 at 09:06, Nyall Dawson <[email protected]> wrote: >> >> Hi list, >> >> This is a public plea for more developers who are very familiar with >> different parts of the QGIS codebase to become actively involved in >> backport PR management. >> >> We NEED more people to be actively (i.e. daily) monitoring for >> backport PRs and then reviewing them if the backport affects code >> areas which they're knowledgeable about. >> > > Well my earlier plea seems like it fell on deaf ears, and we've seen > only minimal assistance coming to maintain the PR queue since I posted > this. > > I'll ask nicely once more. If you're an organisation involved in QGIS > development, you NEED to donate time to maintaining this list. It's > not enough to just ensure your own PRs get through the queue, you HAVE > to help with the shared burden of getting others PRs reviewed and > merged. > > This callout applies to ALL organisations who are making money from > core QGIS development. You know who you are, and you can ALL afford to > donate 30 minutes of a staff member's time each week to helping with > this shared burden. If your boss is blocking this then you NEED to let > them know how big a risk they are running here. It's not fair to leave > this responsibility on the already burdened shoulders of a few > overworked individuals. > > Nyall > _______________________________________________ > QGIS-Developer mailing list > [email protected] > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer _______________________________________________ QGIS-Developer mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
