Check-in [d9ca0cb590]
Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Add note about Code of Conduct Huge thanks to everyone involved in contributor-covenant.org for providing this framework. <3 |
---|---|
Downloads: | Tarball | ZIP archive | SQL archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
d9ca0cb590489953ec58d429f2aa4ab9 |
User & Date: | jls@semicomplete.com 2014-11-21 17:43:45 |
Context
2014-12-10
| ||
22:37 | Merge pull request #824 from dlanderson/patch-2 Remove errant space in debian postinst_upgrade.sh check-in: f464393ebb user: jls@semicomplete.com tags: trunk | |
21:37 | Remove errant space in debian postinst_upgrade.sh This space was preventing postinst scripts to run on initial install of the .deb package check-in: d94f8d5b37 user: dave@dubkat.com tags: trunk | |
2014-11-21
| ||
17:43 | Add note about Code of Conduct Huge thanks to everyone involved in contributor-covenant.org for providing this framework. <3 check-in: d9ca0cb590 user: jls@semicomplete.com tags: trunk | |
17:43 | Add a Code of Conduct from http://contributor-covenant.org/ check-in: 374c5fa262 user: jls@semicomplete.com tags: trunk | |
Changes
Changes to README.md.
︙ | ︙ | |||
148 149 150 151 152 153 154 155 156 157 158 159 160 161 | request. If you don't know git, I also accept diff(1) formatted patches - whatever is most comfortable for you. * Want to lurk about and see what others are doing? IRC (#fpm on irc.freenode.org) is a good place for this as is the [mailing list](http://groups.google.com/group/fpm-users) ### Contributing by forking from GitHub First, create a github account if you do not already have one. Log in to github and go to [the main fpm github page](https://github.com/jordansissel/fpm). At the top right, click on the button labeled "Fork". This will put a forked copy of the main fpm repo into your account. Next, clone your account's github repo of fpm. For example: | > > > > | 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 | request. If you don't know git, I also accept diff(1) formatted patches - whatever is most comfortable for you. * Want to lurk about and see what others are doing? IRC (#fpm on irc.freenode.org) is a good place for this as is the [mailing list](http://groups.google.com/group/fpm-users) ### Contributing by forking from GitHub Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms. See the [CODE\_OF\_CONDUCT.md](CODE_OF_CONDUCT.md). First, create a github account if you do not already have one. Log in to github and go to [the main fpm github page](https://github.com/jordansissel/fpm). At the top right, click on the button labeled "Fork". This will put a forked copy of the main fpm repo into your account. Next, clone your account's github repo of fpm. For example: |
︙ | ︙ | |||
186 187 188 189 190 191 192 | At this point, the fpm command should run directly from the code in your cloned repo. Now simply make whatever changes you want, commit the code, and push your commit back to master. If you think your changes are ready to be merged back to the main fpm repo, you can generate a pull request on the github website for your repo and send it in for review. | < | 190 191 192 193 194 195 196 197 198 199 200 201 202 203 | At this point, the fpm command should run directly from the code in your cloned repo. Now simply make whatever changes you want, commit the code, and push your commit back to master. If you think your changes are ready to be merged back to the main fpm repo, you can generate a pull request on the github website for your repo and send it in for review. ##Problems running bundle install? If you are installing on Mac OS 10.9 (Mavericks) you will need to make sure that you have the standalone command line tools seperate from Xcode: $ xcode-select --install |
︙ | ︙ |