Skip to content

Open Issues #360

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
sven-7 opened this issue Oct 20, 2020 · 10 comments
Open

Open Issues #360

sven-7 opened this issue Oct 20, 2020 · 10 comments

Comments

@sven-7
Copy link
Contributor

sven-7 commented Oct 20, 2020

@ScudLee @sixtenbe @slohj --- I know you guys are active every once and a while to push things thru. If willing to give me write access, I'm happy to go thru and clean up all the open issues and push what pull requests are still relevant thru.

@sven-7
Copy link
Contributor Author

sven-7 commented Oct 23, 2020

Bump to @ScudLee @sixtenbe @slohj

@sven-7
Copy link
Contributor Author

sven-7 commented Nov 3, 2020

Just checking again...

@reconman
Copy link
Contributor

I think a switch to a fork is necessary, one owned by a Github organization. The main problem is that for personal repositories, only the owner can give you Collaborator status, which is ScudLee in this case. Other collaborators can't do anything.

In the case of organizations, multiple people can have a role similar to a repo owner. The Admin role can add new collaborators. That way, the repo will be future-proof as long as at least 1 admin is periodically available.

Organizations can be created under https://github.com/organizations/plan. Then fork with the organization, invite collaborators and assign them roles.

Afterwards we just need to convince people to use and update the fork.

@sven-7
Copy link
Contributor Author

sven-7 commented Nov 24, 2020

Okay. I think I'll take this to task. That way, it can get off @ScudLee's plate if he doesn't want to maintain anymore. Will look into this more today.

@sven-7
Copy link
Contributor Author

sven-7 commented Nov 24, 2020

@reconman yep - I've got something going. I'm going to try and close out the open issues and pull requests into the new one. Then maybe figure out how to pass it down.

@sven-7
Copy link
Contributor Author

sven-7 commented Nov 25, 2020

I'm talking about this here: ZeroQI/Absolute-Series-Scanner#315

I've also tried reach out to @ScudLee on Kodi.

Ultimately, I've set a new one up and if we work things out, it can just be merged into the master. Otherwise, we could move towards a new model.

Here is the temp: https://github.com/Anime-Lists/anime-lists

@reconman
Copy link
Contributor

@sven-7 Have you noticed my PR in the new repo?

@sven-7
Copy link
Contributor Author

sven-7 commented Nov 25, 2020

@reconman I had not set up notifications just yet, so thanks for the heads up. Committed.

@reconman
Copy link
Contributor

So, someone with write access copied over the commits from the new repository... Who was it?

@sven-7
Copy link
Contributor Author

sven-7 commented Dec 4, 2020

To follow up, that was @slohj

Also - for anyone else, myself and whomever else wants to help, is maintaining a more up-to-date version here: https://github.com/Anime-Lists/anime-lists

mikethecalamity pushed a commit to mikethecalamity/anime-lists that referenced this issue Jan 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants