├── CONTRIBUTING.md ├── LICENSE └── README.md /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # TLTR: Create a Pull Request 2 | 1. Fork this repository. 3 | 2. Clone your new repository to your system. 4 | 3. Create a new branch (i.e. `add/your-name`). 5 | 4. Add your new site. Remember to add **alphabetically to the list.** 6 | 5. Commit changes and push the new branch. 7 | 6. Open and submit a PR. 8 | 9 | If you have never opened a PR and need direction, read more below. 10 | 11 | # Contributor's Guide 12 | Feedback, bug reports, and pull requests are welcome. Feel free to ask for [help](https://github.com/open-sauced/awesome-github-sponsor-profiles/issues). 13 | 14 | Working on your first Pull Request? You can learn how from this _free_ series [How to Contribute to an Open Source Project on GitHub](https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github) 15 | 16 | This guide has been modified from [freeCodeCamp's Contributors Guide](https://github.com/freeCodeCamp/freeCodeCamp/blob/master/CONTRIBUTING.md) 17 | 18 | ## Forking the Project 19 | 20 | ### Setting Up Your System 21 | 22 | 1. Install [Git](https://git-scm.com/) or your favorite Git client. 23 | 2. (Optional) [Setup an SSH Key](https://help.github.com/articles/generating-an-ssh-key/) for GitHub. 24 | 25 | ### Forking Developer Portfolios 26 | 27 | 1. Go to the top-level page of this [repository](https://github.com/open-sauced/awesome-github-sponsor-profiles) 28 | 2. Click the "Fork" button in the upper right-hand corner of the interface ([More Details Here](https://help.github.com/articles/fork-a-repo/)) 29 | 3. After the repository (repo) has been forked, you will be taken to your copy of the Developer Portfolios repo at 30 | 31 | ### Cloning Your Fork 32 | 33 | 1. Open a Terminal / Command Line / Bash Shell in your project's directory (_i.e.: `/yourprojectdirectory/`_) 34 | 2. Clone your fork of `Developer Portfolios` 35 | 36 | ```shell 37 | $ git clone https://github.com/yourUsername/developer-portfolios.git 38 | ``` 39 | 40 | **(make sure to replace `yourUsername` with your GitHub username)** 41 | 42 | This will download the entire `Developer Portfolios` repo to your project's directory. 43 | 44 | ### Setup Your Upstream 45 | 46 | 1. Change directory to the new directory (`cd ./developer-portfolios`) 47 | 2. Add a remote to the original `Developer Portfolios` repo: 48 | 49 | ```shell 50 | $ git remote add upstream https://github.com/emmawedekind/developer-portfolios.git 51 | ``` 52 | 53 | Congratulations, you now have a local copy of the `Developer Portfolios` repo! 54 | 55 | ### Maintaining Your Fork 56 | 57 | Now that you have a copy of your fork, there is work you will need to do to keep it current. 58 | 59 | #### Rebasing from Upstream 60 | 61 | Do this prior to every time you create a branch for a PR: 62 | 63 | 1. Make sure you are on the `main` branch 64 | 65 | ```shell 66 | $ git status 67 | On branch main 68 | Your branch is up to date with 'origin/main'. 69 | ``` 70 | 71 | If you aren't on `main`, resolve outstanding files/commits and checkout the `main` branch 72 | 73 | ```shell 74 | $ git checkout main 75 | ``` 76 | 77 | 2. Do a pull with rebase against `main` 78 | 79 | ```shell 80 | $ git pull --rebase upstream main 81 | ``` 82 | 83 | This will pull down all of the changes to the official main branch, without making additional commits in your local repo. 84 | 85 | 3. Merge remote changes to your local main fork: 86 | 87 | ```shell 88 | $ git merge upstream/main 89 | ``` 90 | 91 | ### Create a Branch 92 | 93 | Before you start working, you will need to create a separate branch specific to the issue/feature you're working on. You will push your work to this branch. 94 | 95 | #### Naming Your Branch 96 | 97 | There are several strategies for naming branches. 98 | 99 | You could name the branch something like `fix/xxx` or `feature/xxx` where `xxx` is a short description of the changes or feature you are attempting to add. For example `fix/email-login` would be a branch where you fix something specific to email login. 100 | 101 | We'd recommend naming it something that is relevant to your new site (i.e. `add/your-name` 102 | 103 | #### Adding Your Branch 104 | 105 | To create a branch on your local machine (and switch to this branch): 106 | 107 | ```shell 108 | $ git checkout -b [add/your-name] 109 | ``` 110 | 111 | and to push to GitHub: 112 | 113 | ```shell 114 | $ git push origin [add/your-name] 115 | ``` 116 | 117 | **If you need more help with branching, take a look at [this](https://github.com/Kunena/Kunena-Forum/wiki/Create-a-new-branch-with-git-and-manage-branches).** 118 | 119 | ### Creating a Pull Request 120 | 121 | #### What is a Pull Request? 122 | 123 | A pull request (PR) is a method of submitting your new site to the `Developer Portfolios` (or any repo, for that matter). You will make changes to copies of the files in a personal fork, then apply to have them accepted by the original repo. 124 | 125 | #### Need Help? 126 | 127 | Feel free to ask for [help](https://github.com/open-sauced/awesome-github-sponsor-profiles/issues), we are here to help. 128 | 129 | #### Important: ALWAYS EDIT ON A BRANCH 130 | 131 | Take away only one thing from this document: Never, **EVER** make edits to the `staging` branch. ALWAYS make a new branch BEFORE you edit files. This is critical, because if your PR is not accepted, your copy of staging will be forever sullied and the only way to fix it is to delete your fork and re-fork. 132 | 133 | #### Methods 134 | 135 | There are two methods of creating a pull request for 'Developer Portfolios': 136 | 137 | * Editing files on a local clone (recommended) 138 | * Editing files via the GitHub Interface 139 | 140 | ##### Method 1: Editing via your Local Fork _(Recommended)_ 141 | 142 | This is the recommended method. Read about [How to Setup and Maintain a Local Instance](#maintaining-your-fork). 143 | 144 | 1. Perform the maintenance step of rebasing `main`. 145 | 2. Ensure you are on the `main` branch using `git status`: 146 | 147 | $ git status 148 | On branch main 149 | Your branch is up-to-date with 'origin/main'. 150 | 151 | nothing to commit, working directory clean 152 | 153 | 3. If you are not on `main` or your working directory is not clean, resolve any outstanding files/commits and checkout `git checkout main` 154 | 155 | 4. Create a branch off of `develop` with git: `git checkout -b add/your-name` 156 | 157 | 5. Edit your file(s) locally with the editor of your choice. 158 | 159 | 6. Check your `git status` to see unstaged files. 160 | 161 | 7. Add your edited files: `git add path/to/filename.ext` You can also do: `git add .` to add all unstaged files. Take care, though, because you can accidentally add files you don't want to be added. Review your `git status` first. 162 | 163 | 8. Make sure your new site is added **alphabetically** to the existing list. 164 | 165 | 9. Commit your edits. `git commit -m "your-commit-message"` 166 | 167 | Please make sure to write a commit message that summarizes the changes. If you find yourself in the need to use `and` it might be better to do two separate commits. 168 | 169 | See [Useful Tips for writing better Git commit messages](https://code.likeagirl.io/useful-tips-for-writing-better-git-commit-messages-808770609503) for inspiration. 170 | 171 | As a note, use the present tense for your commit messages (i.e. `Add` instead of `Added`). 172 | 173 | 10. If you would want to add/remove changes to the previous commit, add the files as in Step 5 earlier, and use `git commit --amend` or `git commit --amend --no-edit` (for keeping the same commit message). 174 | 175 | 11. Push your commits to your GitHub Fork: `git push origin add/your-name` 176 | 177 | 12. Once the edits have been committed, you will be prompted to create a pull request on your fork's GitHub Page. 178 | 179 | 13. By default, all pull requests should be against the `Developer Portfolios` main repo, `main` branch. 180 | **Make sure that your Base Fork is set to developer-portfolios/main when raising a Pull Request.** 181 | 182 | 14. Submit a pull request from your branch to the `Developer Portfolios` `main` branch. 183 | 184 | 15. The title (also called the subject) of your PR should be descriptive of your changes and succinctly indicate what is being fixed. 185 | 186 | * **Do not add the issue number in the PR title or commit message.** 187 | 188 | * Examples: `Add site NAME` 189 | 190 | ### Next Steps 191 | 192 | #### If your PR is accepted 193 | 194 | Once your PR is accepted, you may delete the branch you created to submit it. This keeps your working fork clean. 195 | 196 | You can do this with a press of a button on the GitHub PR interface. You can delete the local copy of the branch with: `git branch -D branch/to-delete-name` 197 | 198 | #### If your PR comes back 199 | 200 | Don't despair! You are probably being asked to make a formatting change. If you have a local copy of the repo, you can make the requested changes, commit them and push them to your fork. 201 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Creative Commons Legal Code 2 | 3 | CC0 1.0 Universal 4 | 5 | CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE 6 | LEGAL SERVICES. DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN 7 | ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS 8 | INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES 9 | REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS 10 | PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM 11 | THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED 12 | HEREUNDER. 13 | 14 | Statement of Purpose 15 | 16 | The laws of most jurisdictions throughout the world automatically confer 17 | exclusive Copyright and Related Rights (defined below) upon the creator 18 | and subsequent owner(s) (each and all, an "owner") of an original work of 19 | authorship and/or a database (each, a "Work"). 20 | 21 | Certain owners wish to permanently relinquish those rights to a Work for 22 | the purpose of contributing to a commons of creative, cultural and 23 | scientific works ("Commons") that the public can reliably and without fear 24 | of later claims of infringement build upon, modify, incorporate in other 25 | works, reuse and redistribute as freely as possible in any form whatsoever 26 | and for any purposes, including without limitation commercial purposes. 27 | These owners may contribute to the Commons to promote the ideal of a free 28 | culture and the further production of creative, cultural and scientific 29 | works, or to gain reputation or greater distribution for their Work in 30 | part through the use and efforts of others. 31 | 32 | For these and/or other purposes and motivations, and without any 33 | expectation of additional consideration or compensation, the person 34 | associating CC0 with a Work (the "Affirmer"), to the extent that he or she 35 | is an owner of Copyright and Related Rights in the Work, voluntarily 36 | elects to apply CC0 to the Work and publicly distribute the Work under its 37 | terms, with knowledge of his or her Copyright and Related Rights in the 38 | Work and the meaning and intended legal effect of CC0 on those rights. 39 | 40 | 1. Copyright and Related Rights. A Work made available under CC0 may be 41 | protected by copyright and related or neighboring rights ("Copyright and 42 | Related Rights"). Copyright and Related Rights include, but are not 43 | limited to, the following: 44 | 45 | i. the right to reproduce, adapt, distribute, perform, display, 46 | communicate, and translate a Work; 47 | ii. moral rights retained by the original author(s) and/or performer(s); 48 | iii. publicity and privacy rights pertaining to a person's image or 49 | likeness depicted in a Work; 50 | iv. rights protecting against unfair competition in regards to a Work, 51 | subject to the limitations in paragraph 4(a), below; 52 | v. rights protecting the extraction, dissemination, use and reuse of data 53 | in a Work; 54 | vi. database rights (such as those arising under Directive 96/9/EC of the 55 | European Parliament and of the Council of 11 March 1996 on the legal 56 | protection of databases, and under any national implementation 57 | thereof, including any amended or successor version of such 58 | directive); and 59 | vii. other similar, equivalent or corresponding rights throughout the 60 | world based on applicable law or treaty, and any national 61 | implementations thereof. 62 | 63 | 2. Waiver. To the greatest extent permitted by, but not in contravention 64 | of, applicable law, Affirmer hereby overtly, fully, permanently, 65 | irrevocably and unconditionally waives, abandons, and surrenders all of 66 | Affirmer's Copyright and Related Rights and associated claims and causes 67 | of action, whether now known or unknown (including existing as well as 68 | future claims and causes of action), in the Work (i) in all territories 69 | worldwide, (ii) for the maximum duration provided by applicable law or 70 | treaty (including future time extensions), (iii) in any current or future 71 | medium and for any number of copies, and (iv) for any purpose whatsoever, 72 | including without limitation commercial, advertising or promotional 73 | purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each 74 | member of the public at large and to the detriment of Affirmer's heirs and 75 | successors, fully intending that such Waiver shall not be subject to 76 | revocation, rescission, cancellation, termination, or any other legal or 77 | equitable action to disrupt the quiet enjoyment of the Work by the public 78 | as contemplated by Affirmer's express Statement of Purpose. 79 | 80 | 3. Public License Fallback. Should any part of the Waiver for any reason 81 | be judged legally invalid or ineffective under applicable law, then the 82 | Waiver shall be preserved to the maximum extent permitted taking into 83 | account Affirmer's express Statement of Purpose. In addition, to the 84 | extent the Waiver is so judged Affirmer hereby grants to each affected 85 | person a royalty-free, non transferable, non sublicensable, non exclusive, 86 | irrevocable and unconditional license to exercise Affirmer's Copyright and 87 | Related Rights in the Work (i) in all territories worldwide, (ii) for the 88 | maximum duration provided by applicable law or treaty (including future 89 | time extensions), (iii) in any current or future medium and for any number 90 | of copies, and (iv) for any purpose whatsoever, including without 91 | limitation commercial, advertising or promotional purposes (the 92 | "License"). The License shall be deemed effective as of the date CC0 was 93 | applied by Affirmer to the Work. Should any part of the License for any 94 | reason be judged legally invalid or ineffective under applicable law, such 95 | partial invalidity or ineffectiveness shall not invalidate the remainder 96 | of the License, and in such case Affirmer hereby affirms that he or she 97 | will not (i) exercise any of his or her remaining Copyright and Related 98 | Rights in the Work or (ii) assert any associated claims and causes of 99 | action with respect to the Work, in either case contrary to Affirmer's 100 | express Statement of Purpose. 101 | 102 | 4. Limitations and Disclaimers. 103 | 104 | a. No trademark or patent rights held by Affirmer are waived, abandoned, 105 | surrendered, licensed or otherwise affected by this document. 106 | b. Affirmer offers the Work as-is and makes no representations or 107 | warranties of any kind concerning the Work, express, implied, 108 | statutory or otherwise, including without limitation warranties of 109 | title, merchantability, fitness for a particular purpose, non 110 | infringement, or the absence of latent or other defects, accuracy, or 111 | the present or absence of errors, whether or not discoverable, all to 112 | the greatest extent permissible under applicable law. 113 | c. Affirmer disclaims responsibility for clearing rights of other persons 114 | that may apply to the Work or any use thereof, including without 115 | limitation any person's Copyright and Related Rights in the Work. 116 | Further, Affirmer disclaims responsibility for obtaining any necessary 117 | consents, permissions or other rights required for any use of the 118 | Work. 119 | d. Affirmer understands and acknowledges that Creative Commons is not a 120 | party to this document and has no duty or obligation with respect to 121 | this CC0 or use of the Work. 122 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # awesome-github-sponsor-profiles 2 | A curated list of awesome GitHub Sponsor Profiles 💖 3 | 4 | Knowing what to put in a blank GitHub Sponsor Profile is a challenge. This list is meant to inspire others to create a profile and add context. 5 | 6 | This repository was ~inspired~ copied from [Developer Portfolios](https://github.com/emmabostian/developer-portfolios) github repository. 7 | 8 | Contribute to this repository by opening a [PR](./CONTRIBUTING.md) to this repository. Refer to the [CONTRIBUTING](./CONTRIBUTING.md) file for direction. 9 | 10 | **Jump to:** | [A](#a) | [B](#b) | [C](#c) | [D](#d) | [E](#e) | [F](#f) | [G](#g) | [H](#h) | [I](#i) | [J](#j) | [K](#k) | [L](#l) | [M](#m) | [N](#n) | [O](#o) | [P](#p) | [R](#r) | [S](#s) | [T](#t) | [U](#u) | [V](#v) | [W](#w) | [Y](#y) | [Z](#z) 11 | 12 | ## A 13 | - [aprilspeight](https://github.com/sponsors/aprilspeight) 14 | 15 | ## B 16 | ## C 17 | ## D 18 | - [dayhaysoos](https://github.com/sponsors/dayhaysoos) 19 | 20 | ## E 21 | ## F 22 | ## G 23 | ## H 24 | ## I 25 | ## J 26 | ## K 27 | - [kjaymiller](https://github.com/sponsors/kjaymiller) 28 | 29 | ## L 30 | ## M 31 | - [M0nica](https://github.com/sponsors/M0nica) 32 | 33 | ## N 34 | ## O 35 | - [Open Sauced](https://github.com/sponsors/open-sauced) 36 | ## P 37 | - [prophen](https://github.com/sponsors/prophen) 38 | 39 | ## Q 40 | ## R 41 | ## S 42 | ## T 43 | ## U 44 | ## V 45 | ## W 46 | ## X 47 | ## Y 48 | ## Z 49 | 50 | 51 | 52 | --------------------------------------------------------------------------------