GITHUB . COM {}

Matching Content Categories {📚}

• Video & Online Content
• Events
• Books & Literature

Content Management System {📝}

What CMS is github.com built with?

Github.com utilizes WORDPRESS.

Traffic Estimate {📈}

What is the average monthly size of github.com audience?

🚀🌠 Tremendous Traffic: 10M - 20M visitors per month


Based on our best estimate, this website will receive around 10,000,019 visitors per month in the current month.
However, some sources were not loaded, we suggest to reload the page to get complete results.

check SE Ranking
check Ahrefs
check Similarweb
check Ubersuggest
check Semrush

How Does Github.com Make Money? {💸}

Subscription Packages {💳}

How Much Does Github.com Make? {💰}

Subscription Packages {💳}

Prices on github.com are in US Dollars ($). They range from $4.00/month to $21.00/month.
We estimate that the site has approximately 4,989,889 paying customers.
The estimated monthly recurring revenue (MRR) is $20,957,532.
The estimated annual recurring revenues (ARR) are $251,490,385.

Wordpress Themes and Plugins {🎨}

What WordPress theme does this site use?

It is strange but we were not able to detect any theme on the page.

What WordPress plugins does this website use?

It is strange but we were not able to detect any plugins on the page.

Keywords {🔍}

maintainer, author, field, metadata, pganssle, sign, generates, issue, projects, pkginfo, implementation, behavior, add, change, mentioned, navigation, source, pull, requests, actions, security, line, closed, choice, suspect, pep, pypi, warehouse, handle, side, jaraco, github, labels, milestone, footer, skip, content, menu, product, solutions, resources, open, enterprise, pricing, search, jump, pypa, setuptools, public, notifications,

Topics {✒️}

activity pganssle mentioned author= generates ascii decode error maintainer= generates author/maintainer field metadata consumer side metadata producer side comment metadata assignees labels projects projects milestone backwards-incompatible change author field warehouse handle prioritizes maintainer backwards compatible maintainer field issue license metadata pulled preferentially fallback logic installing package assigned labels milestone relationships author author= simply add add support deliberate choice github warehouse implementation question current behavior pypi maintainer= maintainer metadata field change add choice handle implementation behavior sign skip jump line moment generated get_contact

Payment Methods {📊}

• Braintree

Questions {❓}

• Already have an account?
• I suspect that this is an artifact of the fact that PEP 314 does not provide a Maintainer field, and that was a later addition in PEP 345?

Schema {🗺️}

DiscussionForumPosting:
      context:https://schema.org
      headline:maintainer= generates AUTHOR: line in PKG-INFO
      articleBody:This seems like a deliberate choice, but it seems that at the moment the `Author:` metadata is pulled preferentially from `maintainer=`, and `Maintainer:` is never actually generated. The implementation is [here](https://github.com/pypa/setuptools/blob/d10a1bb476db25dc888b5b4aad9d81ffa245ea30/setuptools/dist.py#L55), and the implementation of `get_contact` that prioritizes `maintainer` is [here](https://github.com/python/cpython/blob/8837dd092fe5ad5184889104e8036811ed839f98/Lib/distutils/dist.py#L1119). I suspect that this is an artifact of the fact that [PEP 314](https://www.python.org/dev/peps/pep-0314/#author-optional) does not provide a `Maintainer` field, and that was a later addition in [PEP 345](https://www.python.org/dev/peps/pep-0345/#maintainer-email-optional)? I can make a PR for this, but there is an implementation question. The options I see right now are: 1. Maintain the current behavior and simply *add* a "Maintainer" field. This is the most "backwards compatible" way to do things. 2. Change the behavior so that `author=` is given preference over `maintainer=` when generating the `AUTHOR` field, but still use `maintainer` if no `author` is specified. Additionally always add the `Maintainer` field if `maintainer=` is present. 3. Change the behavior so that *only* `author=` generates the `Author` field and *only* `maintainer=` generates the `Maintainer:` field. This is the least backwards-incompatible change. I suspect that the choice of these probably should come down to how PyPI and Warehouse handle the metadata. If both PyPI and Warehouse are able to handle an either/or Author/Maintainer field, then I suggest that the best option is 3. Basically the fallback logic should be on the metadata consumer side, not on the metadata *producer* side.
      author:
         url:https://github.com/pganssle
         type:Person
         name:pganssle
      datePublished:2018-03-13T13:32:32.000Z
      interactionStatistic:
         type:InteractionCounter
         interactionType:https://schema.org/CommentAction
         userInteractionCount:1
      url:https://github.com/1288/setuptools/issues/1288
      context:https://schema.org
      headline:maintainer= generates AUTHOR: line in PKG-INFO
      articleBody:This seems like a deliberate choice, but it seems that at the moment the `Author:` metadata is pulled preferentially from `maintainer=`, and `Maintainer:` is never actually generated. The implementation is [here](https://github.com/pypa/setuptools/blob/d10a1bb476db25dc888b5b4aad9d81ffa245ea30/setuptools/dist.py#L55), and the implementation of `get_contact` that prioritizes `maintainer` is [here](https://github.com/python/cpython/blob/8837dd092fe5ad5184889104e8036811ed839f98/Lib/distutils/dist.py#L1119). I suspect that this is an artifact of the fact that [PEP 314](https://www.python.org/dev/peps/pep-0314/#author-optional) does not provide a `Maintainer` field, and that was a later addition in [PEP 345](https://www.python.org/dev/peps/pep-0345/#maintainer-email-optional)? I can make a PR for this, but there is an implementation question. The options I see right now are: 1. Maintain the current behavior and simply *add* a "Maintainer" field. This is the most "backwards compatible" way to do things. 2. Change the behavior so that `author=` is given preference over `maintainer=` when generating the `AUTHOR` field, but still use `maintainer` if no `author` is specified. Additionally always add the `Maintainer` field if `maintainer=` is present. 3. Change the behavior so that *only* `author=` generates the `Author` field and *only* `maintainer=` generates the `Maintainer:` field. This is the least backwards-incompatible change. I suspect that the choice of these probably should come down to how PyPI and Warehouse handle the metadata. If both PyPI and Warehouse are able to handle an either/or Author/Maintainer field, then I suggest that the best option is 3. Basically the fallback logic should be on the metadata consumer side, not on the metadata *producer* side.
      author:
         url:https://github.com/pganssle
         type:Person
         name:pganssle
      datePublished:2018-03-13T13:32:32.000Z
      interactionStatistic:
         type:InteractionCounter
         interactionType:https://schema.org/CommentAction
         userInteractionCount:1
      url:https://github.com/1288/setuptools/issues/1288
Person:
      url:https://github.com/pganssle
      name:pganssle
      url:https://github.com/pganssle
      name:pganssle
InteractionCounter:
      interactionType:https://schema.org/CommentAction
      userInteractionCount:1
      interactionType:https://schema.org/CommentAction
      userInteractionCount:1

External Links {🔗}(5)

• Profit of https://github.blog
• Financial intake of https://www.python.org/dev/peps/pep-0314/#author-optional
• Financial intake of https://www.python.org/dev/peps/pep-0345/#maintainer-email-optional
• Check the income stats for https://bugs.python.org/issue33069
• Check the income stats for https://www.githubstatus.com/

Analytics and Tracking {📊}

• Site Verification - Google

Libraries {📚}

• Clipboard.js
• D3.js
• Lodash

Emails and Hosting {✉️}

Mail Servers:

• aspmx.l.google.com
• alt1.aspmx.l.google.com
• alt2.aspmx.l.google.com
• alt3.aspmx.l.google.com
• alt4.aspmx.l.google.com

Name Servers:

• dns1.p08.nsone.net
• dns2.p08.nsone.net
• dns3.p08.nsone.net
• dns4.p08.nsone.net
• ns-1283.awsdns-32.org
• ns-1707.awsdns-21.co.uk
• ns-421.awsdns-52.com
• ns-520.awsdns-01.net