What to do about certain design decisions?

What to do about certain design decisions?

by Tim Hunt -
Number of replies: 0
Picture of Core developers Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers

I have had two bugs in the last few months (MDL-31519 and MDL-35111) where I submitted a bug fix for integration, and it got pushed back with a comment like

"We are not sure if this is the right general approach, there needs to a general policy on how to do this sort of thing, and then we will know whether to accept or reject your patch. In the mean time, we are going to take it out of integration."

The problem is, nothing happens after that. The patches just sit there bit-rotting.

Who should make those policy decision? What is the process for doing so?

This is not quite the same as coding style, where we have a policy that works. If you don't know, the policy is

  1. Create a MDLSITE issue saying what needs to be defined (e.g. MDLSITE-2008 or MDLSITE-2039).
  2. The integrators make a decision, and document it.

 I started MDLSITE-2042 for how we sort out these general policy questions. There is a suggestion there.

Average of ratings: Useful (3)