Skip to content
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

Active Barrier maintainers have moved here #1414

Open
p12tic opened this issue Nov 10, 2021 · 2 comments
Open

Active Barrier maintainers have moved here #1414

p12tic opened this issue Nov 10, 2021 · 2 comments

Comments

@p12tic
Copy link
Contributor

p12tic commented Nov 10, 2021

The active maintainers of Barrier for the past 2 years, @p12tic and @shymega [1] have moved their efforts to this repository.

The reasons are the following:

  • All important parts of the project were controlled by walker0643. No one knows the real identity of that person.
  • walker0643 has not been active for at least 2 years and did not give enough administrative access to anyone else, which caused operational issues maintaining the project.
  • The name debauchee is not professional and should not be associated to a popular project.

Our attempts to achieve a compromise have failed, walker0643 did not think that a fork is bad and encouraged it himself so we are here.

We intend to maintain compatibility with older versions of Barrier.

Currently we think that InputLeap would be a good new name for the project. We will confirm this when we do the first release from this repository. Picking new names will need changes in the directory structure of the project, so we want to delay this for as long as possible.

[1]: During the past 2 years since v2.3.2 @p12tic and @shymega together authored 305 commits which is more than twice the number of commits by all the rest of contributors (150 commits). This can be checked by running git shortlog -ns v2.3.2..master on the Barrier repository.

@p12tic p12tic pinned this issue Nov 10, 2021
@shymega
Copy link
Member

shymega commented Nov 13, 2021

I can attest that what @p12tic put in this announcement is true, and I look forward to maintaining this fork.

@p12tic
Copy link
Contributor Author

p12tic commented Nov 13, 2021

I will lock the conversation to have a clean place for any fork-related announcements. We can discuss the topic here: #1427

@input-leap input-leap locked as too heated and limited conversation to collaborators Nov 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants