On Fri, Mar 4, 2016 at 4:04 AM, Aleksey Kuleshov <rndfax@xxxxxxxxx> wrote: > [quote] > To improve tracking of who did what, especially with patches that can > percolate to their final resting place in the kernel through several > layers of maintainers, we've introduced a "sign-off" procedure on > patches that are being emailed around. > [/quote] > > So Linux kernel had some problems due to their huge developers/maintainers list > and they solved them by using "sign-off" procedure. > Do Barebox have that burden of "patches that can > percolate to their final resting place in the kernel through several > layers of maintainers"? > > Also in chapter 11 there are rules which are pure bureaucratic. > Bureaucracy is a thing of a large projects. > Is Barebox such as big as Linux that it must have these rules too? > IANAL, but AFAIU those "rules which are pure bureaucratic" are a legal framework that originated in Linux kernel and was borrowed by many projects, Barebox among them. So to answer your question: it has nothing to do with the size of the project, copyright and associated laws in various shapes or forms applies to everyone. Can it be done in a better, less verbose, more convenient form by smaller projects? Maybe or maybe not, but I don't think the question can be answered without performing proper legal analysis(done by law professionals, of course) which is very costly, time consuming, etc. > Solving inexisting problems doesn't make life easier but complicates it. > That's very much a truism, so you won't find much opposition to that. The devil, as usual, is in the details of how you define what constitutes a non-existing problem. This may sound rude and I apologize for not coming up with a way of better delivery, but I, personally, think that even if we were to assume that the whole SOB mechanism is most egregious and ridiculous legal cargo-cult, necessity to type "git commit -s" as opposed "git commit -s" when you are commiting changes is a non-existing problem. Andrey _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
