Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

******** General Announcement ******** #740

Open
carl-hostrander opened this issue Jul 24, 2024 · 1 comment
Open

******** General Announcement ******** #740

carl-hostrander opened this issue Jul 24, 2024 · 1 comment

Comments

@carl-hostrander
Copy link
Contributor

carl-hostrander commented Jul 24, 2024

Hello community!

I am Carl and would like to announce that I am the tech lead overseeing the Turnitin Moodle Plugins. My goal is to address the issues and submitted pull requests in a timely manner when they are submitted. We are planning to have plugin releases twice a year, in June and in October where needed.

Unfortunately, I have inherited a lot of unresolved pull requests and issues. The action plan for resolving these will be to work from the latest to the oldest. There is a caveat to the term oldest. Currently we support versions 4.1+ up to and including 4.4+. Moodle 4.1 originally was release in November, 2022. Any issue that has been tagged with version before that will have a comment and then closed. If the issue is still pertinent to you, please retest in supported version of Moodle and either create a new issue or comment on the current issue, denoting version tested on and re-open the ticket. The reasoning behind this is that fixes have gone out that may have already resolved the issue or a fix has been implemented but the issue has not been closed in repo. Also, I don't have the resources right now to investigate every single issue that is not pertinent to a supported release.

Lastly, I would like to say, if you believe an issue or pull request needs immediate action please tag me to let me know. Also, here are a few notes on this repo:

  • Please always submit Pull Requests to the Develop branch. Any other Branch the PR will be denied.
  • We will be implementing 2 labels that show our progress:
    • investigating : This means we have taken this issue or PR and activately working on it
    • scheduled for next release : This means we have accepted the PR, fixed the issue and merged to develop. Once merged to develop it automatically gets added to next release.
@aspark21
Copy link
Contributor

aspark21 commented Jul 25, 2024

Welcome @carl-hostrander

I've now reviewed all of our hotfixes and hacks.

These are the maintenance fixes worth looking at for mod_turnitintooltwo

We don't have fixes for these:

plagiarism_turnitin - all fixes now merged :) Thank you!

These are nice to haves, we do need to keep maintaining a fork with some of our more bespoke hacks so no big deal if not merged :

Really appreciating the effort in reviewing all these long standing fixes.
Thanks
Alistair

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants