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.

Sign up for GitHub

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

Jump to bottom

Coordination #29

Open
walter opened this issue Feb 17, 2018 · 3 comments
Open

Coordination #29

walter opened this issue Feb 17, 2018 · 3 comments
Assignees
@Br3nda

Comments

@walter
Copy link
Member

walter commented Feb 17, 2018

@Br3nda,

As far as I'm aware the legacy project I've been maintaining is the only user of this gem. As the gem maintainer and main user, I would appreciate some coordination before turning on outside services to change the codebase.

Can you give me a rundown of what you are up to, please?
@walter
Copy link
Member Author

walter commented Feb 17, 2018

I've updated the description to make clear this software is no longer maintained.

@walter
Copy link
Member Author

walter commented Feb 17, 2018

I've also turned off hound, etc.

@Br3nda
Copy link
Member

Br3nda commented Feb 17, 2018

Kia ora Walter.

The code has several vulns to the point that github is sending me notifications about it. I started to chip away at the vulns in kete, and yesterday looked at the gems.

There have been no commits for nearly 6 years, and I understood it to be abandoned by maintainers.

If you need this to not be modified I can leave it alone. Git hub does let you archive a repos if it no longer active but want to maintain a record.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Br3nda Br3nda

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@walter @Br3nda