-
Notifications
You must be signed in to change notification settings - Fork 38
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
Why does HA says that repo was archived? #348
Comments
You don't have to remove it, and it will be added again. So don't worry :) |
great, thanks :D |
@marcokreeft87: Thank you for developing and maintaining this card <3 |
According to hacs/integration#4136 (comment), the repo author must request to be re-added. |
I did that but they are very very slow |
If you link to the issue you filed we can 👍 it. I looked through the HACS issues and only found the ones filed by other users. |
Doesn't help unfortunately |
Did you open a bug to be reinstated? Can you point me to that bug? I understand that you don't think it can help, but if you never opened one they will just shrug and blame you. (And they will be right.) |
I made a pull request to re-add room card. But they are just slow |
Have you tried opening a bug? It is hard to justify blaming them when you didn't do the step they asked for. |
I did everything they need to add it to the repository again |
But nothing that they asked for. 🤷 They have a simple process. You refused to follow it. That is on you, not on them. (That said, I don't like how they run that project, I don't like how it is engineered, and given the chance I probably wouldn't like the people. But that doesn't make them wrong about this. The process isn't convoluted, it doesn't require special access or knowledge. It may be wildly unbalanced in favor of removals, but it is clear and documented.) |
They ask for a PR. Nothing more.. or am I missing something? |
They asked for an issue. I get that they interacted with the PR (and their attitude was terrible) but the docs for removals say issue. |
I don't want it removed. I want it re-added. They can see the issue in earlier comments I placed. So yeah I did everything they asked for. They are just terrible maintainers |
Two things can be true. I still agree that you did everything they should need. I do not agree that you have done everything reasonable to push it forward. According to their docs, the maintenance pipeline is driven by issues. Right now, you can feel superior to them for being bad maintainers, but they can justifiably claim you did not follow their process. |
I did follow their process. But I just gave up after months of waiting. This discussion is even not worth it anymore. Please go and complain at them for me because I just gave up. There is nothing I can do, they made that very clear |
You could open an issue. Then, when you say "I am out of actions", we will all agree. Unfortunately, their policy makes it explicitly clear that nobody else can open that issue for you. (Didn't someone up-thread already try anyway?) You have the opportunity to actually get the "win" on them, and to actually be ignored. Instead you are just insisting that they run their project the way you want. Think of someone going to a busy restaurant and waiting for a table. It doesn't matter how long they stand there if they do not follow the process to get on the waiting list. It is perfectly reasonable to ignore them in favor of people who did follow the process. It doesn't matter that the host "knows" you are waiting. It doesn't even matter if you are really really hungry. You didn't do your part, so they do not have to do theirs. Once you follow their process, and THEN get ignored, you will stop sounding petulant and we can all get back to helping push it forward. Until then, they will correctly say that we are not on the waiting list (or not authorized, because only you can get on that list.) |
got an error on the latest ha version saying that this repo needs to be removed from hacs because it was archived. is it no longer supported?
The text was updated successfully, but these errors were encountered: