Update "Disallowed minor code changes" doc
Update contributor docs to reflect the discussion of oslo library usage at the 10 January 2019 Glance weekly meeting. Change-Id: Ibb75ce0cbc2b906838a5149dc75bfb27383178a7
This commit is contained in:
parent
fb2c2e7de1
commit
cf2b3f25aa
@ -94,3 +94,15 @@ Python 3. While the deprecation is real, Glance uses oslo_log that provides
|
|||||||
alias warn and solves the issue in single place for all projects using it.
|
alias warn and solves the issue in single place for all projects using it.
|
||||||
These changes are not accepted due to the huge amount of refactoring they
|
These changes are not accepted due to the huge amount of refactoring they
|
||||||
cause for no reason.
|
cause for no reason.
|
||||||
|
|
||||||
|
Gratuitious use of oslo libraries
|
||||||
|
---------------------------------
|
||||||
|
|
||||||
|
We are big fans of the oslo libraries and all the hard work the Oslo team does
|
||||||
|
to keep common code reusable and easily consumable. But that doesn't mean that
|
||||||
|
it's a bug if Glance isn't using an oslo library everywhere you could possibly
|
||||||
|
use one. We are all for using oslo if it provides any level of benefit for us
|
||||||
|
and makes sense, but please let's not have these bugs/patches of "Let's use
|
||||||
|
oslo because it exists".
|
||||||
|
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user