mirror
/
writefreely
mirror of https://github.com/writeas/writefreely
2
0
Fork 0
Code Issues Releases Wiki Activity

Merge pull request #1023 from writefreely/update-phabricator

Browse Source 
Update Phabricator URL in docs and PR template
pull/1024/head
Matt Baer 3 months ago committed by GitHub
parent 038a80c25e 5cc89b6795
commit 68d43f7af9
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 5 additions and 5 deletions
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Show Stats Download Patch File Download Diff File
  1. 2
      .github/pull_request_template.md
  2. 8
      CONTRIBUTING.md

2
.github/pull_request_template.md
Unescape View File

@ -2,4 +2,4 @@
--- ---
- [ ] I have signed the [CLA](https://phabricator.write.as/L1) - [ ] I have signed the [CLA](https://todo.musing.studio/L1)

8
CONTRIBUTING.md
Unescape View File

@ -18,11 +18,11 @@ First, you'll want to clone the WriteFreely repo, install development dependenci
### Starting development ### Starting development
Next, [join our forum](https://discuss.write.as) so you can discuss development with the team. Then take a look at [our roadmap on Phabricator](https://phabricator.write.as/tag/write_freely/) to see where the project is today and where it's headed. Next, [join our forum](https://discuss.write.as) so you can discuss development with the team. Then take a look at [our roadmap on Phabricator](https://todo.musing.studio/tag/writefreely/) to see where the project is today and where it's headed.
When you find something you want to work on, start a new topic on the forum or jump into an existing discussion, if there is one. The team will respond and continue the conversation there. When you find something you want to work on, start a new topic on the forum or jump into an existing discussion, if there is one. The team will respond and continue the conversation there.
Lastly, **before submitting any code**, please sign our [contributor's agreement](https://phabricator.write.as/L1) so we can accept your contributions. It is substantially similar to the _Apache Individual Contributor License Agreement_. If you'd like to know about the rationale behind this requirement, you can [read more about that here](https://phabricator.write.as/w/writefreely/cla/). Lastly, **before submitting any code**, please sign our [contributor's agreement](https://todo.musing.studio/L1) so we can accept your contributions. It is substantially similar to the _Apache Individual Contributor License Agreement_. If you'd like to know about the rationale behind this requirement, you can [read more about that here](https://todo.musing.studio/w/writefreely/cla/).
### Branching ### Branching
@ -49,7 +49,7 @@ We value reliable, readable, and maintainable code over all else in our work. To
* Write code for other humans, not computers. * Write code for other humans, not computers.
* The less complexity, the better. The more someone can understand code just by looking at it, the better. * The less complexity, the better. The more someone can understand code just by looking at it, the better.
* Functionality, readability, and maintainability over senseless elegance. * Functionality, readability, and maintainability over senseless elegance.
* Only abstract when necessary. * Only abstract when necessary.
* Keep an eye to the future, but don't pre-optimize at the expense of today's simplicity. * Keep an eye to the future, but don't pre-optimize at the expense of today's simplicity.
#### Code guidelines #### Code guidelines
@ -96,4 +96,4 @@ Beyond that, we prioritize pull requests in this order:
2. Superficial changes and improvements that don't adversely impact users 2. Superficial changes and improvements that don't adversely impact users
3. New features and changes that have been discussed before with the team 3. New features and changes that have been discussed before with the team
Any pull requests that haven't previously been discussed with the team may be extensively delayed or closed, especially if they require a wider consideration before integrating into the project. When in doubt, please reach out [on the forum](https://discuss.write.as) before submitting a pull request. Any pull requests that haven't previously been discussed with the team may be extensively delayed or closed, especially if they require a wider consideration before integrating into the project. When in doubt, please reach out [on the forum](https://discuss.write.as) before submitting a pull request.

Write Preview
Loading…
Cancel
Save