@team
Summary of merge requests for opencraft/documentation/public
from 2022-08-09
Merge request: fix: remove dat from handbook list
Description:
Author: Arunmozhi
For more details visit: #471.
Merge request: fix: set test environment prefix
Description: Set env prefix for test environment to avoid clashing with production env variables.
Author: Navin Karkera
For more details visit: #470.
Merge request: docs: fix markdown formatting
Description: ## Description
Fixes a few markdown formatting issues in handbook
Supporting information
Link to other information about the change, such as Jira issues, GitHub issues, or Discourse discussions.
Be sure to check they are publicly readable, or if not, repeat the information here.
Testing instructions
Please provide detailed step-by-step instructions for testing this change.
Deadline
āNoneā if thereās no rush, or provide a specific date or event (and reason) if there is one.
Other information
OpenCraft Internal: BB-6536
Author: Kaustav Banerjee
For more details visit: #469.
Merge request: feat: retrospective meeting migration
Description: Migrates sprint retrospective meeting from zoom to google drive and posts the link to respective cell forum.
Test instructions
You can find successful run of this new schedule here
To test locally:
- Launch any retrospective meeting from opencraft calendar. Let it start recording and then leave.
- export environment variables locally (ignore DISCOURSE_API_*, it is handle by
DISCOURSE_CONFIG
), ref
- Make sure to set
DEBUG=True
- run
make migrate_retro_meetings
- Inspect drive folder for uploaded video.
- Check forum post printed in console.
- Finally delete the retrospective meeting from zoom recordings either from zoom ui or run the above script with
DEBUG=False
and make sure to change discourse config to something random.
Other information
Private-ref
: BB-6586
Post merge checklist
- [ ] Update env variables
- [ ] create new schedule for retro migration
Author: Navin Karkera
For more details visit: #468.
Merge request: docs: minimize exposure of private links in public PRs and commits
Description: ## Description
It is important that all information which is valuable for context about changes from PRs/commits should be publicly available in those PRs and commits for all community members to access and not be behind private links.
As per this change to OEP-51 and this discussion, the Open edX community is trying to ensure that private links and references are not included in the subject lines of the PRs and commits. Further such private references should only be present at the footers of the commit messages with them being tagged as such.
This MR adds/tweaks revelant sections in our handbook, so that we follow the recommendations of the community for our upstream PRs and commits as well.
Supporting information
Link to other information about the change, such as Jira issues, GitHub issues, or Discourse discussions.
Be sure to check they are publicly readable, or if not, repeat the information here.
Testing instructions
Please provide detailed step-by-step instructions for testing this change.
Deadline
āNoneā if thereās no rush, or provide a specific date or event (and reason) if there is one.
Other information
OpenCraft internal ticket BB-6536
Author: Kaustav Banerjee
For more details visit: #465.