Open ghost opened 8 years ago
:+1:
I must say I never understood what is the purpose for this repo. So :+1:
@dufresnedavid Maybe this is best discussed in the Contributors ML.
@dreispt I prefer having an issue to keep the trace of the arguments. Perhaps I should also mail to the contributor ML to make sure that concerned people get to know. Good point.
:-1:
More info on result-based management: https://en.wikipedia.org/wiki/Results-based_management
:+1: to move the repository under the Project and Services PSC.
Hi,
I must say I never had a look at those modules. But at a glance, it not a project & services generic modules, so I'm not in favor of adding them to this PSC.
But if really bind to a specific management strategy, why not renaming this repo to something like "vertical-result-based-mgmt" ?
My2cents,
Joël
As I understand it's not generic at all... So if it can't be reused why keep it in OCA?
From my point of view, those modules need refactoring to make them generic plus some explanations about how to use it. Otherwise they should go back on SFL repo
So if it can't be reused why keep it in OCA?
:+1:
Hi,
In this moment about moving this to Project and Services PSC I'm not agree :-1:
I prefer to renaming this repo to something like "vertical-result-based-mgmt" :+1:
Anywhy, we must ask to Savoir-faire Linux, are you going to migrate to v8/v9?
Is there any video or doc to know full use of all modules?
Thanks
These features are not related to Project nor Program management, so OCA/project is not a suitable place for them - so I agree with @rafaelbn.
I find the current repo name misleading: "program" makes me think of Program management (as in managing a portfolio of projects), but it's something completely different.
I see no harm on keeping it, by I would prefer for it to have a different name - it's not a vertical, but taking from Rafael's suggestion OCA/result-based-mgmt
could be a good name.
And it definitely would need a better README explaining what the repo is about.
program modules implement result-based management. The problem here is that this set of modules was developped for a specific company. It is very hard to understand how it works and the code is not reusable.
I do not see how these modules benefit from being published in OCA. No one except Savoir-faire Linux contributes to it and it is difficult to explain the choices we make in the pull requests.
I suggest that we remove completely this project from OCA. First, I would like to know if it is used by someone other than Savoir-faire Linux.