> From: Florian Weimer <[email protected]> > Cc: Eli Zaretskii <[email protected]>, [email protected], [email protected] > Date: Fri, 24 Apr 2026 12:41:04 +0200 > > * Eli Zaretskii via Gcc: > > >> Cc: Christopher Albert <[email protected]>, Jonathan Wakely > >> <[email protected]> > >> Date: Fri, 24 Apr 2026 11:00:08 +0200 > >> From: Florian Weimer via Gcc <[email protected]> > >> > >> It's already common practice to submit code on behalf of others. > >> When doing that, we don't know for certain if the code was not > >> copied from somewhere else. Yet that practice has not been called > >> into question. > > > > It should be, though, at least IMO. > > Why? Some organizations have designated employees who are the only ones > authorized to submit open-source contributions. (This applies to > contributions under DCO and under copyright assignment.) If GNU > development procedures cannot accommodate this contribution process, > it's potentially a significant loss to the GNU project.
My comment was a general one. Your counter-argument, OTOH, brings up a very specific example, in which perhaps a close scrutiny of the situation would conclude that there's no problem in such cases. But my point is that such a practice _in_general_ cannot be accepted IMO without seriously questioning it. A close scrutiny of each case of such submissions basically means that the policy in general is invalid.
