Skip to content
This repository has been archived by the owner on Nov 18, 2021. It is now read-only.

Proposal: Archive this project #598

Closed
tetsuharuohzeki opened this issue Nov 10, 2021 · 5 comments
Closed

Proposal: Archive this project #598

tetsuharuohzeki opened this issue Nov 10, 2021 · 5 comments
Labels
A-repository AREA: nearly equals to governance I-question

Comments

@tetsuharuohzeki
Copy link
Contributor

After this announcement, the time has been passed.

I'm not sure about that how much "abema" core products still depends on this project, but I think it's time to archive this project. Because:

  1. Now, I don't have enough time to maintain this repository and I would not touch this project for the time being.
  2. I'm not a paid staff for this upstream product for a long time and I'm not a strong stakeholder of this project. I think it would not be a proper position to make a decision of this project.
  3. I heared that "abema" products decrease the strong dependency for this project in 2019 in The current status #247. After 2 years ago, I'm not sure about that how much "abema" core products still depends on this project, but I guess there is no dependency for this.
  4. There is no other active contributor/maintainer. This is a biggest reason which I propose this.

Therefore, for the aspect of branding, I think it's better that we should archive this inactive project. Archiving this repository does not mean that removals of all of codes. It continues to open-source codes. But it's nice to tell that this project is inactive obviously.

Of course, if some paid staffs retry to make this project active, then we can unarchive this. But it's not now.


@nodaguti @kubosho

How did you think about this?

answer deadline: 2021, Nov, 19th, 24:00 (UTC+9:00).
If there is no objection until this date, I'll archive this (Probably I have a permission to do it).

@tetsuharuohzeki tetsuharuohzeki added A-repository AREA: nearly equals to governance I-question labels Nov 10, 2021
@tetsuharuohzeki
Copy link
Contributor Author

Now, I don't have enough time to maintain this repository and I would not touch this project for the time being.

Even if I come back to maintain this kind of rule set when I got a time, I would fork this project and change it for my purpose. It does not make sense to continue to maintain this with this project name.

@nodaguti
Copy link

@tetsuharuohzeki
Sorry for taking some time to make a reply with your suggestion.

I'm for the proposal; As you noted, no repositories in our product use this configuration at this moment and there is no plan to re-introduce it as well. You have been virtually the only active maintainer of this project, so it's a good reason to cease the project when you are no longer motivated to maintain it.

Thank you so much for your incrediable efforts into this project for such a long time! The contributions you have made were undoutedly awesome!

@nodaguti
Copy link

It does not make sense to continue to maintain this with this project name.

I totally agree with this. Since this rule set is no longer used by any repositories within the AbemaTV organisation, the name "abema" is quite misleading.

@kubosho
Copy link

kubosho commented Nov 17, 2021

I agree with the proposal.

Currently in our project, we are configuring lint based on eslint:recommended. So we don't use eslint-config-abema.

Thanks for the long time maintenance!

@tetsuharuohzeki
Copy link
Contributor Author

Thank you for your feedback! I will proceed this proposal.

Thanks for the long time maintenance!

It’s a pleasure.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A-repository AREA: nearly equals to governance I-question
Projects
None yet
Development

No branches or pull requests

3 participants