-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #45804 from Expensify/mallenexpensify-patch-1
Update CONTRIBUTING.md
- Loading branch information
Showing
1 changed file
with
0 additions
and
9 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -31,15 +31,6 @@ This project and everyone participating in it is governed by the Expensify [Code | |
## Restrictions | ||
At this time, we are not hiring contractors in Crimea, North Korea, Russia, Iran, Cuba, or Syria. | ||
|
||
## Slack channels | ||
All contributors should be a member of a shared Slack channel called [#expensify-open-source](https://expensify.slack.com/archives/C01GTK53T8Q) -- this channel is used to ask **general questions**, facilitate **discussions**, and make **feature requests**. | ||
|
||
Before requesting an invite to Slack, please ensure your Upwork account is active, since we only pay via Upwork (see [below](https://github.com/Expensify/App/blob/main/contributingGuides/CONTRIBUTING.md#payment-for-contributions)). To request an invite to Slack, email [email protected] with the subject `Slack Channel Invites`. We'll send you an invite! | ||
|
||
Note: Do not send direct messages to the Expensify team in Slack or Expensify Chat, they will not be able to respond. | ||
|
||
Note: if you are hired for an Upwork job and have any job-specific questions, please ask in the GitHub issue or pull request. This will ensure that the person addressing your question has as much context as possible. | ||
|
||
## Reporting Vulnerabilities | ||
If you've found a vulnerability, please email [email protected] with the subject `Vulnerability Report` instead of creating an issue. | ||
|
||
|