Public contributions
Contribute
Choose one route. Each route states what becomes public, who reviews it, and where a reply appears.
Issue forms
Issue forms and their replies are public. Accepted content becomes part of the public repository after review.
GitHub contributions
Issues and pull requests are public when you submit them. Review and replies happen in their public threads.
Reply timing
No response time is promised. Website publication always follows maintainer review.
-
Add your profile
Open a public GitHub issue with public-ready facts. A maintainer prepares the listing, and you review the final public text before publication.
Reply route: The maintainer replies in the public issue.
Add your profile → -
List an offer
Open a public GitHub issue with the offer facts. A maintainer checks its fit and facts before a listing can become public.
Reply route: The maintainer replies in the public issue.
List an offer → -
Propose a guide
Open a public pull request with the guide and its sources. A maintainer reviews the text before merge and publication.
Reply route: The maintainer replies in the public pull-request thread.
Read the guide instructions → -
Propose a case study
Open a public GitHub issue with low-risk facts. A proposal is not publication approval, and named people approve the final case.
Reply route: The maintainer replies in the public issue.
Propose a case study → -
Correct a profile
Open a public GitHub issue with the exact public correction and a public source. Do not include sensitive information.
Reply route: The maintainer replies in the public issue.
Request a correction → -
Remove a profile or portrait
Open a public GitHub issue for a public-safe removal request. The maintainer reviews the requested scope.
Reply route: The maintainer replies in the public issue.
Request removal →
For a security problem or sensitive personal data, do not use a public GitHub issue. Use the private security route.