Skip to content

Quantifying the new browser criteria #194

Description

@will-stone

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions