Summary of merge requests for opencraft/documentation/public from 2026-07-07
Merge request: docs: update information about GitLab and GitHub
Description: ## Description
- clarify that we still prefer GitLab for new projects wherever possible
- clarify reasons to use GitHub
- update instructions for adding teams to GitHub repos
- general rewording for readability
Supporting information
See discussion on Migrate to GitHub?
Private-ref: Log in - OpenCraft
Testing instructions
- verify this doesn’t change any policy, but just restates it for better clarity
- verify the changes render as expected
- verify everything is readable and accurate
Author: Samuel Allan
For more details visit: #670.
Merge request: docs: remove review timeline from task template
Description: ## Description
We almost never use this section, so it just adds noise to tickets.
If a specific timeline is really needed, then this should be mentioned
in the ticket and/or the “Due Date” field used.
Supporting information
Private-ref: Log in - OpenCraft
Previously raised at Feedback: following processes - #5 by paulo
Testing instructions
- verify the changes render as expected
- verify that it’s fine to remove this field
Author: Samuel Allan
For more details visit: #669.
Merge request: feat: add internal AI policy
Description: ## Description
This is a proposed AI policy for us to adopt at OpenCraft,
applying to OpenCraft members.
This is based on the new Open edX AI Contribution Policy
( .github/AI_POLICY.md at master · openedx/.github · GitHub ),
but with the following tweaks:
- Clarify that we don’t directly put limitations on allowed AI tools, but that we must respect the upstream limitations for any Open edX related code, in case we want to upstream anything later.
- Add a requirement to not use cloud AI models with private repos,
since this could leak private information. - Adjust guidelines around what to do when you suspect the policy hasn’t
been followed. We can’t just close a colleague’s PR and move on. ;)
We need to account for colleague’s contributions as well as external
contributions.
Also integrate this into the rest of the handbook, by linking to it
from the coding standards and security pages.
Note that the target audience is OpenCraft members; we may still want
a separate policy for external contributors to follow when contributing
to our projects.
Supporting information
See Adopt the Open edX AI policy?
for discussion.
Private-ref: Log in - OpenCraft (ticket) NOTE: this the ticket where the work began, but we may need a different ticket for logging time for reviews on this and further work.
Private-ref: Log in - OpenCraft (the ticket to discuss and review)
Testing instructions
- verify the document renders correctly
- verify the accuracy of the content
- verify this is what we want
Author: Samuel Allan
For more details visit: #663.