Not overriding set models.

[willtp87]

No description provided.

[whikloj]

Wouldn't array_unique or the like be better to avoid duplicating content-models? Or is there a use case for having multiple of the same content-model in here?

[willtp87]

This is handled at a lower level.

[ruebot]

For clarity and posterity, where is it handled?

[willtp87]

https://github.com/Islandora/tuque/blob/99f602a8203354e8a9afb686c8ddf309e200fcff/Object.php#L430-L432

[ruebot]

I think it would have been extremely helpful to have not merged until @DiegoPino provided some input here since he is the component manager.

[DiegoPino]

@willtp87 and @jordandukart. It's time to discuss some open issues that require the whole community attention.

Most of us contribute to this community with the sole intention of making Islandora a better software. We all join each week in long discussions on what/how to fix problems detected in the stack and most of the time i see people getting their pulls and code reviewed and even sometimes rejected. This is good because it's a group decision. People act accordingly and always follow the group's suggestions and also your view on the stack because you have a deep knowledge on this. We all learn. We grow.

That said, a better software it's not only build on good code, also on strong community. And community stays working for us and for you, when there is respect and common rules that apply to everyone.
And you guys are not following the rules nor being respectful. I can't even imagine a situation where someone X and me (me friend of X) mutually review pulls to, e.g Tuque, and then merge without asking you or the rest. Even less closing an JIRA issue without giving the enough time to peer-review what was done, more if the reporter is someone else, who took the time to find, describe and identify a problem.

If you look closely, the whole reason for having this pull is because you have been doing this systematically before. Unit tests are good, but external human review is even better because interaction between modules requires real UI testing sometimes.

I don't know if you are aware of this, but every time you add new code to the stack without discussing, merge without asking at least the maintainer's opinion, you are sub-estimating the community, not only a particular person.

Your pull is correct in terms of code so i won't reject this merge. But the way you are acting is not right and the consequences are many, one of them is introducing bugs, this is not the first time, but the most important and dangerous one is making the community weak.

[whikloj]

👍 to @DiegoPino's comments. These type of changes make it much harder to work with the project and begs the question of how much hassle is Islandora worth.

[ruebot]

👍 to @DiegoPino and @whikloj's comments as well. This continued behavior that is antagonistic to community developers is alienating, and destructive to the project. This is an example of why I am not serving as release manager after this release. It just isn't worth the frustration anymore.