Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

[meta issue] track down & close stalled/obsolete issues to clean up the issue tracker #1750

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

Closed
ia opened this issue Jul 21, 2023 · 1 comment

Comments

@ia
Copy link
Collaborator

ia commented Jul 21, 2023

Hello. Just go to TL;DR if you don't want to read my rant :)

Otherwise... I'm kinda relatively new here. Unfortunately I'm not as good in low-level hardware microelectronics as others. But this project is so awesome that I try to help it in every way possible - with docs, scripts, build system, tiny improves in code where I'm capable.

Recently I had some time for the issue tracker itself. I looked through every comment in every opened issue (some of the comments were super-interesting by the way, so many interesting people in the community there), I kid you not! So you wouldn't have to. Because I'm fully aware that the crew is very busy with more important & useful things. However I noticed that there are a lot of opened issues where there is no any update, even from the reporters, even when @discip or @River-Mochi very kindly & very politely asked the reporters to update the info on the report.

Key take-aways from some issues if I would have been asked to summarize:

  • unfortunately, implementing in software/firmware some things which can be done only by hardware - is just impossible (me myself from time to time not fully realize and/or forget that);
  • software/firmware can't implement every single nuance of every QC/PD device, hence probably it should be added to somewhere into documentation maybe right in the middle of index.md in bold - if the iron works properly with one power source/cable but not with another one, it's a power source issue unfortunately, but not IronOS one; oh... and that using laptops' ports as high wattage power source for the irons with over ~300 *C temp. just not a good idea.

TL; DR:

Here is a brief list of the opened issues which, in my humble opinion, just should be closed forcefully by the project owners who have the permission to do that:

to close as solved/fixed/implemented:

to close as not relevant/out-of-dated:

to verify by extra pair of eyes before closing but very suitable candidates:


Consider this as the first brief run through opened issues - if/once these will be closed, I will double-sweep the rest of opened ones. The idea is to close this issue once at least the ones from the list above will be closed.

However, if this suggestion (just by a person from the side) is wrong in any way and it's too much (i.e. telling the crew what to do to close other issues) then just let me know and I will close this issue in no time myself and won't bother you with that. But if you agree that some old issues should be cleaned up, then here there the list and you would have to dedicate just ~15-20 minutes of your time to click, scroll through (to check after me whether I'm right or wrong) & close them.

As always, can't wait to hear what do you think.

@ia
Copy link
Collaborator Author

ia commented Jul 21, 2023

And I fully understand that people may be very-very busy with their lives & problems so not having time to update the report is ok but in such case if some issue turned out to be still valid it always can be re-opened easily.

Repository owner locked and limited conversation to collaborators Jul 21, 2023
@Ralim Ralim converted this issue into discussion #1751 Jul 21, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant