You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Left over items in 'xblocks-extra` consolidation #16
Dropping points pop up into my mind while reviewing the PR's so we don't miss them.
License should be created/moved at the root
License should be bundled in the packaging
How the python upgrade will work
How the common constraints for edx repos will be applied -c https://raw.githubusercontent.com/edx/edx-lint/master/edx_lint/files/common_constraints.txt
PACKAGE DATA should be revised for all the xblocks as we are not shifting the packaging strategies for example
i18n should be supported, translations commands in make file is pending to add
Testing of docs is pending
Make sure all the readme content of the xblocks has been moved to the xblocks-extra repository. We should create different read-me files for different blocks in their directories for isolation and easy maintenance.
We should reference the inter block readmes to the main readme file and list the xblocks repo will contain.
We should also make sure all the migrated XBlocks have been marked deprecated and archived before closing this epic.
What about the issues created in the main repositories, should we move them all, I think so.
What about the un-merged PR's, I think as soon as we make xblocks-extra ready, publish it on pypi, we can drop message on the PR's to shift their PR's.
We should make sure:
Existing sites will be able to uninstall the old packages and install xblocks-extra seamlessly.
There will be documentation explaining that to them.
Both the old repos and xblocks-extra work in Verawood, so that they have a full release to transition.
Write transition/migration notes for the Verawood open edx release
Update xblocks-extra readme to add a transition section [doc for the community; how to shift to xblocks-extra]
Add the archiving xblocks [that are not merged] to the verawood release notes as well.
We need to add make upgrade targets that will use uv to keep dependencies in sync and locked. See openedx/xqueue-watcher#122 for an example of how to do this.
4. How the common constraints for edx repos will be applied `-c https://raw.githubusercontent.com/edx/edx-lint/master/edx_lint/files/common_constraints.txt`
I think we'll be continuing to move away from that so let's try to keep it out of this repo for now and see if that causes any issues.
5. `catalog-info.yaml` should be created at the root
Yes, the owner should be axim-engineering for this.
6. Are we going to move `openedx.yaml` For [example](https://github.com/openedx/xblock-qualtrics-survey/blob/master/openedx.yaml)
No, openedx.yaml is no longer used and should be removed so no need to be ported to this new repo.
7. `PACKAGE DATA` should be revised for all the xblocks as we are not shifting the packaging strategies for [example](https://github.com/openedx/FeedbackXBlock/blob/master/MANIFEST.in)
You'll have to port this info into the pyproject.toml format but it should translate pretty easily.
8. i18n should be supported, translations commands in `make` file is pending to add
Agreed, we should add these as we move over packages that provide translations. We'll also need to add this repo to the openedx-translations repo so that translations are regularly built.
9. Testing of docs is pending
👍🏾
10. Make sure all the readme content of the xblocks has been moved to the `xblocks-extra` repository. We should create different read-me files for different blocks in their directories for isolation and easy maintenance.
Activity
feanil commentedon Apr 10, 2026
Agreed, this should be AGPL-3
Agreed
We need to add
make upgradetargets that will useuvto keep dependencies in sync and locked. See openedx/xqueue-watcher#122 for an example of how to do this.I think we'll be continuing to move away from that so let's try to keep it out of this repo for now and see if that causes any issues.
Yes, the owner should be
axim-engineeringfor this.No,
openedx.yamlis no longer used and should be removed so no need to be ported to this new repo.You'll have to port this info into the pyproject.toml format but it should translate pretty easily.
Agreed, we should add these as we move over packages that provide translations. We'll also need to add this repo to the
openedx-translationsrepo so that translations are regularly built.👍🏾
Agreed.