I am one of the maintainers of the original Owl Carousel module: https://www.drupal.org/project/owlcarousel
We already use V2 of the library there is no need for another module.
If you want to modify the admin interface or something like that why not do it in a new branch for the original module.
This will create a lot of confusion I already saw people on Slack asking about this.
The Drupal policy is to collaborate.
Comments
Comment #2
dqdWhile I agree here that collaboration should always be considered and I do hope maintainers will merge efforts with the other project or at least colaborate on differences and overlaps to help both projects, what both would embrace the community at its best on eather way, I would -on the other hand - like to ask you (the issue reporter @ipwa or any other maintainer of the other owl-carousel module) to also embrace Drupal policies and community efforts by being kind and respectful to each other and each contribution. The original report does not sound very friendly and I would kindly ask you to change the "tone" of your request. Every contribution to the community is appreciated and so is this project here too, which had partly different features in the time of its initiation.
Apart from that, the Drupal license of D.O. hosted projects allows each of you to fork and merge, so, anybody who wants can merge efforts made here to another project or vis versa (with kindly asking and credits of course).
And: please do not misuse the issue priority for your needs. Descriptions of the Priority and Status values can be found in the Drupal project issues documentation. "Critical" should not be used for such belongings.
Comment #3
dqdApart from what I suggested above, there needs also new response from the original reporter here, since I have seen that his claim isn't actually up-to-date no more, because the project page of the owlcarousel module he refers to states:
So in fact there is actually -NO- actively maintained OwlCarousel module - at least not on his side - here on Drupal.org
An example of colaboration: It would be great if both groups of maintainers could agree on one library path/version and not 2 different paths and library versions. It would speed up time on testing and contributing ot both projects.
Comment #4
dqdComment #5
dqd