Improve code contribution guidelines for patch authors
Closed, ResolvedPublic


This task item was mentioned as one topic in the Developer Summit session T114419 and hence is a subtask of T101686. See also T207.

Task summary to be improved - please edit.

Improve initial quality of contributed patchsets and communicate expectations.


Intention: Improve the situation described in (and to some extend )

Related Objects

Aklapper updated the task description. (Show Details)Mar 7 2016, 7:14 PM
Aklapper claimed this task.Mar 14 2016, 8:50 PM
Aklapper triaged this task as Low priority.

I'm tentatively assigning this task to myself for the next quarter (April-June 2016) but if someone wants to work on this task earlier, please go ahead!

Aklapper raised the priority of this task from Low to Normal.Apr 25 2016, 3:18 PM
greg awarded a token.May 13 2016, 6:06 PM

Note to myself: Make sure that only covers technical, Gerrit specific, review aspects and is different from "generic"

Aklapper raised the priority of this task from Normal to High.May 30 2016, 8:16 AM

Planning to resolve this task this week.
Watch for changes.

Aklapper closed this task as Resolved.EditedJun 26 2016, 1:27 PM

Things take longer (sigh) but now lists prerequisite expectations; expectations about the patch (scope, testing, docs); and dealing with obstacles (no timely review and further reasons for rework or rejection).

28 edits later:

I'm closing this task as it seems sufficient.

Further improvements encouraged. Dropped an email on wikitech-l about this.

Qgil awarded a token.Jun 28 2016, 8:34 PM