General cleanup/organization of open issues

[hboyd2003]

Currently there are 266 open issues. Many of them have not been touched in years.
In terms of bug issues many have little info and many have not been validated or checked.
In terms of feature request issues there is no organization in terms of priority and there is no set way to determine which feature requests should be implemented or not.

I believe an overall of the issues needs to be completed.
To this end I have mapped out new labels to help re-organization the existing issues. Each issue should have a "core label" which dictates which type of issue it is, these are "Bug", "Feature Request" and "Other". Other labels on the issue would further categorize it (E.g. A feature request could have the tag "tweak") or relate to how it should be handled (E.g. priority).
Below I have listed the "core labels" and the labels that would accompany each.

Not specific to a core label
Bugs

• Chrome Specific: A Bug that it specific to Google Chrome
• Edge Specific: A Bug that is specific to Microsoft Edge
• Firefox Specific: A Bug that is specific to Firefox
• Other Browser Specific: A Bug that is not specific to Firefox, Chrome or Edge
• All Browsers: A Bug that exists on at least Firefox, Chrome and Edge
• Experimental YouTube: Bug exists only on a experimental version of YouTube (In many cases before YouTube roles out a new update it tests it on a small subset of users to gather feedback and iterate on the update)
• Low Priority: The issue is a rare case and needs a rare configuration to occur.
• Medium Priority: The issue is a happens occasionally or the issue only partially breaks the feature in some scenarios.
• High Priority: The issue fully or partially breaks the feature in many scenarios.

Feature Requests

• Existing: The feature already exists as another extension or in some other form.
• Tweak: An edit to an existing feature
• UI/UX: Requests centered around the extensions UI
• Complex: Could take major rework to implement or very difficult to
• Easy: Quick to implement

Other

In terms of the plan labels and Q/A they should both be moved to the discussion section.
I want to hear feedback on this (@ImprovedTube @victor-savinov)

[ImprovedTube]

yay! we can work on the top ~20 bugs and then top 20 plans / feature requests. As linked in the readme.md todo

• any label that occures repeatedly can be helpful to tidy.
  (VS. now they are orded by relevance/frequency despite of the forced alphabetic order 😎)

• Duplicates are usually linked & closed (latest ones might not have been read by the team...)

• Everything not labeled "not Goo. Chrome" applies to the main Version in Webstore (& probably all browser)

• Plan = good implementation/solution steps layed out. Plan = good implementation/solution steps layed out.

Existing
👍 Just added & these: UX / UI (Few requests about it yet.) & Experimental Youtube (hope fully the author would say so too)

Important = (high) Priority

(just a) tweak ∼= rare / low priority (Unless im wrong. Or it is easy. Posted by a humans != "low priority" )

---

Question = there is an open question.
(If this is the only label it will be converted to discussion, but people will post such questions in issue)

• Difficulty/complexity labels will be nice to know (yet hard to guess maybe / personal).
  Easy & Hard // Beginner & Expert // Quick/Few Character & big weekend Project

• Other Browsers: Firefox is catching up & is featured there. Can have some unique bugs.
  Besides that the main task yet can be building & uploading all browser versions at once https://github.com/code-for-charity/YouTube-Extension/blob/master/py/Extension%20builder%20and%20Browser%20Stores%20Updater
  Chrome based browser might not need attention. We might not identify Edge-only bugs /Opera /Whale /Brave /Vivaldi, (if we identify a bug only appearing in a rare browser then we might tell the browser developer instead) (aand Safari version is already relevant before it is published. it might need some fixes like the Firefox Version, but it can raise funds(/bounties) for more work than it takes.)

[ImprovedTube]

#unique & #structural can be motivational.

#Structure is to keep a complete perspective. The structure can be most important. Only 1 in 1000s of longterm users studies the project on github yet. Those who do, might be ready to think of it as whole. (
-We shoudnt collect the next 100 features the same way:

• Can fix search & greately improve it.
• Should add the improvedtube icon on youtube back soon as it is part of xx xxx people's memory (why is it gone in v3.945? 🤨) #bug #important
• Should have a fullpage menu / dashboard making use of the full screen, including a play (embedded youtube and / or <video>)
• Should reduce clicks in the small, existing menu too (minimap on front page?) and add Tooltips. Potentially / sometimes including a links to github wiki or a small screenshot / .gif (screen video / illustration)
  )

---

#unique is for special thought / out of the box.
(mosty likely unique despite big / not rare. )

While #Feature exist is often predictable.
Any big #Feature Request that has neither label should start with researching

• Userscripts: 1. greasyfork 2. tampermonkey 3. userscript.zone (a search combining multiple sources) 4. ( 5. )

• Chrome Webstore: Cisco CRXcavator (archives all versions - matters as of the upcoming 'Manifest2 apocalypse' (where xx xxx extensions i will go unlisted next June ( ArchiveTeam/chrome webstore )

• https://github.com/JustOff/ca-archive the 20000 "Firefox extensions" offline after "XUL/XPCOM apocalypse" (often unnecessarily) - the palemoon browser also comes with the old store afaik

#shoud be crowdsourced will be rare but a good point if true (crowdsourced like for example SponsorBlock, UserStyles.org, Return Dislikes, Userstyles or LyricsTranslate)

[ImprovedTube]

If you want a more polite description: "Not enough information or abstruse"

#Unclear - seems we didnt understand it all ?

#Not-google-chrome

Not sure which ones to replaced it with. Recently next to the closed ones (now 18) there were proportionally many open ones)

"Major Browsers"

Google Chrome means ~70%. Edge & other chrome browsers >20%. Taking years to change.
Firefox still < 5% (catching up through their recommentation "top 100" and being the original extentable open source non profit browser, so a firefox user might be more likely to try extensions or report bugs. The users count there is daily (DAU) not weekly (WAU) like Chrome Webstore). Safari < 1% until we offer it in the App Store since we already have overproportionally many Mac users (Chrome ond Mac.)

Major Browsers

Makes sense. (Besides not currently helping to know if it is >80% or >95%)
(while when we disover a bug only in one (Chromium based-)Browser, we could maybe report it in that browser's repo)

#unResolved:
yes, oh, i dont think you closed any. sorry!
is:closed -reason:complete? yes! could be both / can't harm yet alphabetically.
(yet invaluablely more important for our whole project will be that it feels good working on it generally - and to you especially )

[hboyd2003]

#unique is for special thought / out of the box.

I understand now! Thank You! A better description might be "Does not exist in any extension, webapp or app. (Written in JS or not)"

Google Chrome means ~70%. Edge & other chrome browsers >20%. Taking years to change.

I see what you mean, that it what "Chromium Specific" tag is supposed to be for. I still think that having a label to indicate that the bug exists irrespective of browsers should exist. Maybe a "Browser Non-specific" or "Browser Agnostic" label?

is:closed -reason:complete? yes! could be both / can't harm yet alphabetically.

What do you mean? Do you mean having both that and a label?

#Structure is to keep a complete perspective. The structure can be most important. Only 1 in 1000s of longterm users studies the project on github yet. Those who do, might be ready to think of it as whole. (

I'm sorry but I still don't quite grasp what your trying so say. What do you mean by structure?

Not sure which ones to replaced it with. Recently next to the closed ones (now 18) there were proportionally many open ones)

Ah! I forget you have to remove all labels even from closed ones to delete a label. I will work on it.

Completion / Revision - Improves one of our features

I think that the description should indicate that it can be more than just and improvement. So how about "A tweak or improvement to an existing feature" for the description?

Niche(Rare use-case?/fun?) - Rare or just for fun?. Alternatively: used currently but predicted/scheduled to be replaced)

I don't think there is much reason to having "rare use-case" and "fun" in the actual label name. All of that can be construed in the description (I just don't want the labels to be to long). So how about the label being named "Niche" and the description being "Rare use-case or a feature just for fun"

Unclear (seems we didn't understand all) - Not enough information or unclear wording?

"Not enough information or unclear wording" works perfectly, IDK why I couldn't think of a good description. Like above I would like the labels to be shorter and since "seems we didn't understand all" is what the description is saying, I don't think it is necessary in the label name.

[ImprovedTube]

Ah! I forget you have to remove all labels even from closed ones to delete a label. I will work on it.

noo, dont have to @hboyd2003 (on the contrary removing one by one just fills all the threads unnecessarily / permanently ,
while we can just remove(delete) a useless label all together with 1 click. (but if it has any use, then rather first rename it to appear at end on page2 and / or one letter only, because removing can't be undone) - i just wondered if the open ones werent useful

structure ... don't grasp

Yes uncommon 😳. Great to have you trying! Not adding specification but just an appeal to also zoom out and see the whole project. The underlying surrounding structure, thats determining if our work is discovered and how efficiently. (For example, as said, obviously a rare feature should not be moved above a broad and established one that many people would be able to click on blindly already. However some pull requests might do that. So i could always adjust that. Or it could be ordered automatically. Or we could make everyone think about it too maybe😀 )

I just don't want the labels to be to long

yes still, planning to polish. (And or give you permission.) (and maybe having several Labels starting with letter Z still before deleting or achieving perfection. - Guess i wanted the authors to see without tooltips. Yet this should be about dev productivity

• aand checking other candidates since this tread was all about labels:
  "Bounty" (Issuehunt, GitCoin, or any)
  "m.youtube" "Youtube Premium" ( "music.youtube" "gaming.youtube" "Youtube Creator Studio" "YouTube TV" )
  "Subsequent Error" "Youtube implemented this"

• looking at other popular / serious browser extension Repo Labels:
  "Please ♥︎ - everyone would love" https://github.com/refined-github/refined-github/labels (also "oldest bug🦖" "ajax")
  "Browser Bug" https://github.com/darkreader/darkreader/labels ( also "Broken website", "dependencies", "Firefox CSS filter bug" )
  "regression" https://github.com/vuejs/devtools/labels

[hboyd2003]

renamed: out of the box

I know you just renamed it but I think unique works better. At least for me I didn't immediately catch on that you mean "thinking outside the box"