In the following issue I am attempting to provide valuable information to the project maintainers and also attempting to organize other users to organize what is needed by a fork. If this is not approved or helpful please explain to me what part of my post is not a helpful or constructive contribution to the issue so that I may adjust the message. Additionally, if you do think this is a helpful or constructive contribution, please review my account to see if I have earned the rank of a confirmed account at this time:
Issue: https://www.drupal.org/project/opigno_lms/issues/3396566 →
I was attempting to post the following post:
For reference here are the users who have discussed helping maintain/support a fork thus far: #21 #22 #23 #29 #36 #37 #39
Also it is worth mentioning that many (if not all) would welcome a change to have a developmental release available as well.
I believe many have said what is on everyone's mind. This is a HUGE project. And if we are going to fork it, it is obviously with the intention of providing more than what Opigno is currently providing. If we as a community cannot provide more than Opigno is providing, then we should not fork it.
- What is needed exactly to maintain this project?
- What is needed exactly to provide more than the current project is providing?
- Do we communicate somewhere else publicly other than on this issue to progress this conversation of a fork?
- How do we proceed with this conversation?
I appreciate Opigno's communication here. Opigno is/was several months behind this major update with little to no insight to where Opigno is/was in their work to update this project. As mentioned several times in these comments, we have no idea if the maintainers of Opigno are making headway on this distribution or if they are working on other projects or clients. As our business (and clearly others) currently rely on Opigno, we cannot ignore this behavior. We are forced to make a risk/cost analysis of whether we can rely on Opigno's pattern of behavior or not. I assume that is why many others have advocated for a fork, development release, and alternative technologies on these issues. If there is no fork and there is no change from Opigno, these are the options we have identified for our business:
1. Trust in Opigno (*expecting this behavior/situation to continue and happen again in the future)
2. Pay Opigno to maintain our website(s) (*contractually agreeing to keep the site updated)
3. Pay other developers for updates of Opigno (*internally or external developers that are not Opigno)
4. Fund/Maintain a fork of Opigno
5. Find an alternative product and rebuild
I implore you to understand that if a fork doesn't happen or if Opigno doesn't change anything; We reason that the only users that would go with option 1 are the businesses that find the Opigno updates to be non-essential to their business. We reason that it would be difficult to pick options 2-4 as we see this as Opigno actively losing legitimate interest in their product.
Fixed
Other