1
0
Fork 0
mirror of https://we.phorge.it/source/phorge.git synced 2024-11-10 08:52:39 +01:00
phorge-phorge/README.md
Bob Trahan dca27279cc README update - rely on bug reporting doc and add section about community chat
Summary: Saw D11693 and I thought these changes on top might make the README even better? Open for discussion. I like our bug reporting doc a lot so I don't mind funneling users through it and not mentioning the bug reporting link directly in the readme. This notably forces github users to read a bit before they report issues to us for the first time. That said, I think the community chat can be really helpful at no cost to us so why not upsell it? This could fail if people start asking for say epriestley directly and / or the overall chatter is time consuming, but seemed worth tossing out at least.

Test Plan: read the text, asking opinions of cohorts

Reviewers: chad, epriestley

Reviewed By: epriestley

Subscribers: Korvin, epriestley

Differential Revision: https://secure.phabricator.com/D11694
2015-02-05 09:48:11 -08:00

42 lines
1.9 KiB
Markdown

**Phabricator** is an open source collection of web applications which help software companies build better software.
Phabricator includes applications for:
- reviewing and auditing source code;
- hosting and browsing repositories;
- assembling a party to venture forth;
- tracking bugs;
- managing projects;
- writing stuff down and reading it later;
- hiding stuff from coworkers; and
- also some other things.
You can learn more about the project (and find links to documentation and resources) at [Phabricator.org](http://phabricator.org)
Phabricator is developed and maintained by [Phacility](http://phacility.com). The first version of Phabricator was originally built at Facebook.
----------
**BUG REPORTS**
Please update your install to **HEAD** before filing bug reports. Follow our [bug reporting guide](https://secure.phabricator.com/book/phabcontrib/article/bug_reports/) for complete instructions.
**FEATURE REQUESTS**
We're big fans of feature requests that state core problems, not just 'add this'. We've compiled a short guide to effective upstream requests [here](https://secure.phabricator.com/book/phabcontrib/article/feature_requests/).
**COMMUNITY CHAT**
Please visit our [IRC Channel (#phabricator on FreeNode)](irc://chat.freenode.net/phabricator) to talk with other members of the Phabricator community. There might be someone there who can help you with setup issues or what image to choose for a macro.
**SECURITY ISSUES**
Phabricator participates in HackerOne and may pay out for various issues reported there. You can find out more information on our [HackerOne page](https://hackerone.com/phabricator).
**PULL REQUESTS**
We do not accept pull requests through GitHub. If you would like to contribute code, please read our [Contributor's Guide](https://secure.phabricator.com/book/phabcontrib/article/contributing_code/) for more information.
**LICENSE**
Phabricator is released under the Apache 2.0 license except as otherwise noted.