Re: Make clear, when contributions will be ignored

[Joseph Myers <joseph@codesourcery.com>]

[-- Attachment #1: Type: text/plain, Size: 1611 bytes --]

On Tue, 5 Feb 2019, Дилян Палаузов wrote:

> Will it help, if bugzilla is tweaked to send reminders every two weeks 
> for ready-patches?  This also has the advantage, that people will not 
> have to once update a patch in BZ and then send it over gcc-patches.

For any proposed changes to patch submission / review processes to be 
helpful, they need to work with the existing development community, which 
means they need to be designed based on a deep understanding of what works 
for developers and reviewers, and of the issues likely to lead to lack of 
response on a submission (which can be that it doesn't fall clearly into 
any one maintainer's area, but can also be that the submission has 
deficiencies meaning it would take much longer to review than a 
well-formed submission, such as inadequate explanation, lack of testcases, 
lack of documentation, poor or missing comments, failure to follow the GNU 
Coding Standards, lack of ChangeLog entries, etc., and so is likely to be 
dropped unless a reviewer has more time than usual at the time the patch 
is posted).  A discussion at a future GNU Tools Cauldron would be better 
than on the gcc-patches list (which is for concrete discussion of 
individual patches, not meta-discussion of patch review processes).  I 
think an ongoing commitment from someone with sufficient experience with 
the community to maintain and develop any new tool used would also be 
required, as any existing tool in this area is unlikely to do well without 
significant customization.

-- 
Joseph S. Myers
joseph@codesourcery.com