action #37811
closed[functional][y] Move okurz/openqa_review to os-autoinst/openqa_review
0%
Description
Motivation¶
QSF would be more willing to work on openqa_review if it's not a "okurz-private-pet-project" :)
Suggestions¶
- Ask nsinger/rbrown how to bring an existing project into openSUSE
- Update references to old project path, e.g.
- OBS projects
- wiki pages
- Communicate on mailing lists, e.g. openqa@suse.de
- Make sure openSUSE/openqa_review is the main project, okurz/openqa_review secondary
Updated by okurz over 5 years ago
should work when I do this myself: https://github.com/okurz/openqa_review/settings
Updated by okurz over 5 years ago
I excepted https://github.com/okurz/openqa_review/settings/transfer to work, transferring to os-autoinst but "You don’t have the permission to create repositories on os-autoinst". I understood the github docs as the os-autoinst owners would be asked to accept. https://help.github.com/articles/about-repository-transfers/ says "When the current owner initiates the transfer, the new owner will receive an email giving the option to accept or reject the transfer. If the new owner doesn't accept the transfer within one day, it won't complete.". I assume despite the red error popup I get someone got an email. But coolo reports he did not get any email.
Updated by okurz over 5 years ago
I am "Owner" of the organisation "os-autoinst" now. Member of a team does apparently only have an influence on the included repos, not the organisation where I need to create a new repo in.
Updated by okurz over 5 years ago
- Status changed from Workable to In Progress
- Assignee set to okurz
Updated by okurz over 5 years ago
- Moved using the "Transfer Ownership" option in https://github.com/okurz/openqa_review/settings
- Updated package setting of https://build.opensuse.org/package/show/home:okurz/python-openqa_review
- Same for https://build.opensuse.org/package/show/devel:languages:python/python-openqa_review
- Updated description of https://github.com/os-autoinst/openqa_review to point to http://os-autoinst.github.io/openqa_review/
- Created https://github.com/os-autoinst/openqa_review/pull/112 to check whole PR review and testing workflow. This did not seem to trigger any tests on travis CI though, I understand the integration of travis-ci.org is deprecated and instead we need to use travis-ci.com as a github marketplace plugin or something? On https://travis-ci.org/os-autoinst/openqa_review/requests I find "Build config file is required via repository settings, but config is empty." which google wants to point me to https://github.com/travis-ci/travis-ci/issues/9825 but of course our path to .travis.yml is correct, see https://github.com/os-autoinst/openqa_review/blob/master/.travis.yml . https://travis-ci.org/os-autoinst/openqa_review/builds/466014654 seems to work now, probably because I untoggled the project https://travis-ci.org/organizations/os-autoinst/repositories and toggled it again.
- Checked that https://build.opensuse.org/package/show/home:okurz/python-openqa_review triggers a new build -> https://build.opensuse.org/package/rdiff/home:okurz/python-openqa_review?linkrev=base&rev=104
To be done later after the next commit to the project fixing the python style as reported by more recent flake8:
- Check that https://pypi.org/project/openqa-review/ is updated by travis jobs , currently not working because updated flake8 checks fail, see https://travis-ci.org/os-autoinst/openqa_review/jobs/466015756
Updated by okurz over 5 years ago
- python style checks are in
- https://travis-ci.org/os-autoinst/openqa_review/jobs/466531207 should have deployed to pypi but it has not. I guess I need a new tag? -> solved with new version 1.14.1: https://travis-ci.org/os-autoinst/openqa_review/jobs/469423749 uploaded new version to https://pypi.org/project/openqa-review/
- Tried to update https://bestpractices.coreinfrastructure.org/en/projects/699 but could not replace all the URLS, "You may only change your repo_url from http to https".
- Updated http://os-autoinst.github.io/openqa_review/
Updated by okurz over 5 years ago
- Due date set to 2019-01-01
- Status changed from In Progress to Resolved
- Target version changed from future to Milestone 21