[GH-ISSUE #305] We need to find a new home #246

Closed
opened 2026-05-05 05:49:56 -06:00 by gitea-mirror · 10 comments
Owner

Originally created by @AdrianKoshka on GitHub (May 12, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/305

Originally assigned to: @p12tic, @walker0643, @AdrianKoshka on GitHub.

With the radio silence from @walker0643, I'm worrying we'll have to, in a way, find a new home for barrier. One where multiple people in an organization have elevated permissions, so that we don't end up in this situation again. I think we should still keep this repo as the home of barrier. I think things like issues, release, PRs will to some degree still have to come through here. Though, obviously if we want things like new CI pipelines, it'll have to be done under the new home.

@nelsonjchen has been making great strides in improving our CI situation, but alas, I couldn't integrate them here if I wanted to.

Originally created by @AdrianKoshka on GitHub (May 12, 2019). Original GitHub issue: https://github.com/debauchee/barrier/issues/305 Originally assigned to: @p12tic, @walker0643, @AdrianKoshka on GitHub. With the radio silence from @walker0643, I'm worrying we'll have to, in a way, find a new home for barrier. One where multiple people in an organization have elevated permissions, so that we don't end up in this situation again. I think we should still keep this repo as the home of barrier. I think things like issues, release, PRs will to some degree still have to come through here. Though, obviously if we want things like new CI pipelines, it'll have to be done under the new home. @nelsonjchen has been making great strides in improving our CI situation, but alas, I couldn't integrate them here if I wanted to.
gitea-mirror 2026-05-05 05:49:56 -06:00
Author
Owner

@AdrianKoshka commented on GitHub (May 12, 2019):

btw, @nelsonjchen and @noisyshape, if you want in the new organization, I'd be happy to add you as members.

<!-- gh-comment-id:491623077 --> @AdrianKoshka commented on GitHub (May 12, 2019): btw, @nelsonjchen and @noisyshape, if you want in the new organization, I'd be happy to add you as members.
Author
Owner

@nelsonjchen commented on GitHub (May 12, 2019):

It might just be radio silence for GitHub mentions. Have you emailed @walker0643 ?

<!-- gh-comment-id:491623107 --> @nelsonjchen commented on GitHub (May 12, 2019): It might just be radio silence for GitHub mentions. Have you emailed @walker0643 ?
Author
Owner

@AdrianKoshka commented on GitHub (May 12, 2019):

I don't have their email, and I've tried private messages on IRC.

<!-- gh-comment-id:491623187 --> @AdrianKoshka commented on GitHub (May 12, 2019): I don't have their email, and I've tried private messages on IRC.
Author
Owner

@nelsonjchen commented on GitHub (May 12, 2019):

https://marc.info/?l=aic7xxx&m=115246403330410&w=2

<!-- gh-comment-id:491623193 --> @nelsonjchen commented on GitHub (May 12, 2019): https://marc.info/?l=aic7xxx&m=115246403330410&w=2
Author
Owner

@AdrianKoshka commented on GitHub (May 12, 2019):

Oh, that was a quick find.

<!-- gh-comment-id:491623223 --> @AdrianKoshka commented on GitHub (May 12, 2019): Oh, that was a quick find.
Author
Owner

@AdrianKoshka commented on GitHub (May 12, 2019):

Email sent, hopefully it reaches them. If I don't hear from them w/in a week, I think we'll need to start deciding on what happens next.

<!-- gh-comment-id:491623489 --> @AdrianKoshka commented on GitHub (May 12, 2019): Email sent, hopefully it reaches them. If I don't hear from them w/in a week, I think we'll need to start deciding on what happens next.
Author
Owner

@p12tic commented on GitHub (May 14, 2019):

@AdrianKoshka: I hope that we eventually get the needed permissions to handle the project at its current home. If not, I think it's best to create a new organization, transfer as much of the project there as possible and leave the placeholders in this repository linking to the new home. Having half of the development process on one repository and half in another is very, very confusing for both users and potential contributors alike.

By the way, do you remember when was the last communication form @walker0643 and what level of permissions do you have?

<!-- gh-comment-id:492047613 --> @p12tic commented on GitHub (May 14, 2019): @AdrianKoshka: I hope that we eventually get the needed permissions to handle the project at its current home. If not, I think it's best to create a new organization, transfer as much of the project there as possible and leave the placeholders in this repository linking to the new home. Having half of the development process on one repository and half in another is very, very confusing for both users and potential contributors alike. By the way, do you remember when was the last communication form @walker0643 and what [level of permissions](https://help.github.com/en/articles/repository-permission-levels-for-an-organization) do you have?
Author
Owner

@AdrianKoshka commented on GitHub (May 14, 2019):

I only really have some read/write access to the repository. I heard from @walker0643 earlier today hopefully we can catch each-other tomorrow.

<!-- gh-comment-id:492048158 --> @AdrianKoshka commented on GitHub (May 14, 2019): I only really have some read/write access to the repository. I heard from @walker0643 earlier today hopefully we can catch each-other tomorrow.
Author
Owner

@p12tic commented on GitHub (May 14, 2019):

Great, that looks promising.

<!-- gh-comment-id:492048435 --> @p12tic commented on GitHub (May 14, 2019): Great, that looks promising.
Author
Owner

@AdrianKoshka commented on GitHub (May 15, 2019):

Hopefully we could get hold of them and perhaps get @AdrianKoshka bumped up the ranking to be able to do almost anything in this repo.

Yeah, this is what I'd rather do tbh, but it's not up to me to make that decision.

Originally posted by @AdrianKoshka in https://github.com/debauchee/barrier/pull/303#issuecomment-492677653

<!-- gh-comment-id:492678239 --> @AdrianKoshka commented on GitHub (May 15, 2019): > Hopefully we could get hold of them and perhaps get @AdrianKoshka bumped up the ranking to be able to do almost anything in this repo. Yeah, this is what I'd rather do tbh, but it's not up to me to make that decision. _Originally posted by @AdrianKoshka in https://github.com/debauchee/barrier/pull/303#issuecomment-492677653_
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/barrier#246
No description provided.