When I login as a student the css messes up, not sure why, it does not do this when I view as student role. It seems to not like alignment.
Logged in as student:
Logged in as user:
Chad Parmentier
Posts made by Chad Parmentier
We are using Moodle 4.1, and Nexsis automatically enrolls students into Moodle. However, when students drop courses, they are marked as "suspended" in Moodle. I believe this might be causing our issue. My concern is with the "Full Delete User" option in the Moodle admin settings for Nexsis. Does this delete the user from just the course, or from the entire system? If anyone uses Nexsis with Moodle, please let me know.
How is it that Moodle Partners can disable the plugin feature to elicit a profit from their clients by forcing them to pay for a simple plugin addition? It's not like 20 years ago when some rogue plugin could wipe your whole installation out. What the hell? And how is this not a breach of GNU for the people who wrote the plugin module and fought to standardize it so that it doesn't happen? We finally solved the issue, and Moodle partners monetized it. Sorry, I have been on an island for a long time, and I haven't been paying attention. Tim Hunt Thoughts? Are they charging for quiz issues now, Too? I'm smelling a lot of Blackboard. I'm just saying...Sorry, I have been promoting and installing LAMP and Moodle for 20 years. I looked away for 10 years, and Moodle partners smell a lot like WebCT.
(Edited by Mary Cooch - original submission Thursday, 22 August 2024, 5:07 AM)
Yeah, well, if that were the case, a hosting company would be better off allowing clients to install their own plug-ins and, when they fail, charge to repair the installation. However, this would probably not be profitable because Moodle moved to certified, verified Moodle plugins, which require adherence to the verification process in order to offer the plugin via moodle.org. I'm not against charging for hosted services. By the way, which hosting company do you work for?
Well I guess I was wrong about hosting companies violating GPL, however even Legal AI knows its ethically sketch and goes against the spirit of open source. Source:
Moodle and the GNU General Public License (GPL):
Moodle is licensed under the GNU General Public License (GPL), which allows anyone to use, modify, and distribute the software freely, provided that any modifications or derivative works are also distributed under the same license.
The GPL ensures that the code remains free and open, meaning that anyone can access the source code, modify it, and share those modifications under the same terms.
Hosting Companies and GPL:
A hosting company offering Moodle as a service does not necessarily need to distribute the software; they are providing access to the software running on their servers. This practice is commonly referred to as Software as a Service (SaaS).
The GPL covers distribution, not the service itself. Therefore, hosting companies can technically modify the code on their servers and charge for the services they provide, including the activation or use of certain features.
However, if the hosting company distributes the modified Moodle software (e.g., offers it for download or shares the modified code), they are required under the GPL to also provide access to the modified source code under the same GPL terms.
Disabling Features and Charging for Them:
If the hosting company disables certain features within their hosted version of Moodle and charges for enabling them, this might be seen as a business practice rather than a direct violation of the GPL. Since they are not distributing the modified code (but merely running it on their servers), they are within their rights to charge for the service, even if that involves enabling or disabling features.
From a legal perspective, they are not violating the GPL by charging for the service of hosting and managing the software. The GPL does not prohibit charging for services related to the software, such as hosting, support, or additional features.
Ethical Considerations:
While this practice may not violate the letter of the GPL, it could be considered contrary to the spirit of open-source software, depending on your perspective. The open-source community often emphasizes freedom and access, so restricting features behind a paywall might be seen as going against these principles.
In conclusion, while the hosting company's practice of disabling features and charging for them may not violate the GNU GPL, it could be viewed as ethically questionable by some in the open-source community. If you are concerned about this, you might consider looking for a different hosting provider that offers a more open and transparent service model, or even hosting Moodle yourself to retain full control over the software.
Moodle and the GNU General Public License (GPL):
Moodle is licensed under the GNU General Public License (GPL), which allows anyone to use, modify, and distribute the software freely, provided that any modifications or derivative works are also distributed under the same license.
The GPL ensures that the code remains free and open, meaning that anyone can access the source code, modify it, and share those modifications under the same terms.
Hosting Companies and GPL:
A hosting company offering Moodle as a service does not necessarily need to distribute the software; they are providing access to the software running on their servers. This practice is commonly referred to as Software as a Service (SaaS).
The GPL covers distribution, not the service itself. Therefore, hosting companies can technically modify the code on their servers and charge for the services they provide, including the activation or use of certain features.
However, if the hosting company distributes the modified Moodle software (e.g., offers it for download or shares the modified code), they are required under the GPL to also provide access to the modified source code under the same GPL terms.
Disabling Features and Charging for Them:
If the hosting company disables certain features within their hosted version of Moodle and charges for enabling them, this might be seen as a business practice rather than a direct violation of the GPL. Since they are not distributing the modified code (but merely running it on their servers), they are within their rights to charge for the service, even if that involves enabling or disabling features.
From a legal perspective, they are not violating the GPL by charging for the service of hosting and managing the software. The GPL does not prohibit charging for services related to the software, such as hosting, support, or additional features.
Ethical Considerations:
While this practice may not violate the letter of the GPL, it could be considered contrary to the spirit of open-source software, depending on your perspective. The open-source community often emphasizes freedom and access, so restricting features behind a paywall might be seen as going against these principles.
In conclusion, while the hosting company's practice of disabling features and charging for them may not violate the GNU GPL, it could be viewed as ethically questionable by some in the open-source community. If you are concerned about this, you might consider looking for a different hosting provider that offers a more open and transparent service model, or even hosting Moodle yourself to retain full control over the software.