On Saturday, 2015-09-19, 20:32:43, Eike Hein wrote: > On 09/19/2015 08:25 PM, Kevin Krammer wrote: > > Saying "I don't look at the KDE review tool" would be like saying "I am > > not > > interested in your patch". > > Saying "My personal productivity and efficiency matters more > to me in the long-run than your patch, so please use the tool > I prefer to reach me" happens all the time, and is a respect- > able stance. > > In fact, it's come up in this thread because that's what "I > don't want to use two review sites even if having two means > more patches than I would get otherwise" means. > > It also comes up when someone says "please put this in BKO > instead of telling me on IRC because not having all my data > in one central location is a problem for me". > > Simplicity and centralization matter. If there are two code > review sites, some people will be willing to work with both > of them, others will prefer one over the other. Some of the > latter may pick GitHub.
Right. If a maintainer wants all patches via email, that is how they work. Even using a review tool in the first place is something that the maintainer asks people to do. If you don't want to you don't override the maintainer's decision and push directly, do you? So the hypothetical situation is that there is a KDE project who's maintainer does not want the contribution of any other KDE developer. Their loss, no? Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
