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.

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

Quantifying the new browser criteria #194

Open
will-stone opened this issue Jan 4, 2021 · 4 comments
Open

Quantifying the new browser criteria #194

will-stone opened this issue Jan 4, 2021 · 4 comments

Comments

@will-stone
Copy link

Hi @alrra,

Browserosaurus maintainer here 👋 I've recently put Browserosaurus into what I'm calling Public Feature Complete where I'm no longer taking feature requests including adding new browsers. I realised that I probably shouldn't cut off all new browser requests as there may be some big ones that I miss. I was reading your contributing guidelines and really like your criteria (I'll paste them here for others reading this):

  1. Browser must have distinct feature(s) that separate it from the rest. For instance, many Chromium based browsers are very similar in functionality.
  2. The browser's overall usage and download count is relatively high.
  3. The browser has a proven track record of being maintained. This includes and is not limited to major updates, patches, community activity, etc.

I have been wondering if we could join forces to quantify these criteria and synchronise our projects?

With quantifiers, I don't think the the first point would be required. As for point 2, I think we could stipulate something from https://gs.statcounter.com/ maybe? And for point 3, maybe the browser must be of a certain age, not be declared deprecated or archived, have received an update in the last couple of months, etc. etc.

What do you reckon?

Thanks,

Will.

@alrra
Copy link
Owner

alrra commented Feb 17, 2021

@will-stone I do apologize for the delayed answer, I was and am currently busy in my day-to-day life.


I have been wondering if we could join forces to quantify these criteria and synchronise our projects?

Sure!

With quantifiers, I don't think the the first point would be required. As for point 2, I think we could stipulate something from https://gs.statcounter.com/ maybe? And for point 3, maybe the browser must be of a certain age, not be declared deprecated or archived, have received an update in the last couple of months, etc. etc.

For this repository I think it all boils down to the following question: Will a significant amount of people actually need/use this logo now and in the future (be it for a presentation, show browser support, etc.)?

From the data I've seen over the years and to no surprise, people are usually looking for and use the logos of browsers that had or have considerable market share, or have some kind of historical significance. In all other cases, the usage seems to be close to none.

When I have time I'll look more into this and improve the contributing guidelines. In the meantime, feel free to submit a pull request with your suggestions!

@will-stone
Copy link
Author

Thanks for the reply @alrra. No worries, I’m also rather busy: we got a puppy and so I’m basically tired 100% of the time now 😆 Hopefully I can put some time aside for this soon but maybe a kind volunteer will see this and offer to help out 🥺

@alrra
Copy link
Owner

alrra commented Feb 17, 2021

we got a puppy

@will-stone Cute!

...and since the internet always needs more puppy pictures, care to share some? :D

@will-stone
Copy link
Author

will-stone commented Feb 17, 2021

He's a 10 week old Cocker Spaniel called Pasty. He's very cute when he's sleeping or playing nicely. The rest of the time he's an auburn whirlwind with piranha's teeth. He's halfway through his vaccinations, and until they're complete he can't go out <he says rocking in the corner> 😅

I can certainly say that I am not currently at peak coding ability. I'm hoping once we can go out for walks, he'll be calmer, I'll get fitter, and the world will be a better place 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants