Project

General

Profile

Actions

action #37811

closed

[functional][y] Move okurz/openqa_review to os-autoinst/openqa_review

Added by okurz almost 6 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Enhancement to existing tests
Target version:
SUSE QA - Milestone 21
Start date:
2018-06-26
Due date:
2019-01-01
% Done:

0%

Estimated time:
Difficulty:

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
Actions #1

Updated by okurz over 5 years ago

should work when I do this myself: https://github.com/okurz/openqa_review/settings

Actions #2

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.

Actions #3

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.

Actions #4

Updated by okurz over 5 years ago

  • Status changed from Workable to In Progress
  • Assignee set to okurz
Actions #5

Updated by okurz over 5 years ago

To be done later after the next commit to the project fixing the python style as reported by more recent flake8:

Actions #6

Updated by okurz over 5 years ago

Actions #7

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
Actions

Also available in: Atom PDF