mirror of
https://we.phorge.it/source/phorge.git
synced 2025-02-26 21:49:08 +01:00
4cb2ec1120
Summary: Basically similar to D13941 but a little more extreme: - Really strongly emphasize reproducibility for bug reports, and set users up for rejection if they don't satisfy this. - Really strongly emphasize problem descriptions for feature requests, and set users up for rejection. - Get rid of various "please give us feedback"; we get plenty of feedback these days. - Some modernization tweaks. - Split the support document into: - Stuff we actually support for free (security / good bug reports / feature requests). - Stuff you can pay us for (hosting / consulting / prioritization). - A nebulous "community" section, with appropriate (low) expectations that better reflects reality. My overall goals here are: - Set expectations better, so users don't show up in IRC expecting it to be a "great place to get amazing support" or whatever the docs said in 2011. - Possibly move the needle slightly on bug reports / feature request quality, maybe. Test Plan: Read changes carefully. Reviewers: chad Reviewed By: chad Differential Revision: https://secure.phabricator.com/D14305
63 lines
2.8 KiB
Text
63 lines
2.8 KiB
Text
@title Contributor Introduction
|
|
@group contrib
|
|
|
|
Introduction to contributing to Phabricator, Arcanist and libphutil.
|
|
|
|
Overview
|
|
========
|
|
|
|
If you'd like to contribute to Phabricator, this document can guide you though
|
|
ways you can help improve the project.
|
|
|
|
Writing code is valuable, but often isn't the best or easiest way to contribute.
|
|
In most cases we are pretty good at fixing easy stuff quickly, so we don't have
|
|
a big pile of easy stuff sitting around waiting for new contributors.
|
|
|
|
This can make it difficult to contribute code if you only have a little bit of
|
|
time to spend since most of the work that needs to be done usually requires some
|
|
heavy lifting.
|
|
|
|
Without writing any code, learning the whole codebase, making a big time
|
|
commitment, or having to touch PHP, here are some ways you can materially
|
|
contribute to Phabricator:
|
|
|
|
- Send us an email or drop by IRC just to say "thanks". A big part of the
|
|
reason we build this software is to help people solve problems, and knowing
|
|
that our efforts are appreciated is really rewarding.
|
|
- Recommend Phabricator to people who you think might find it useful. Our
|
|
most powerful growth channel is word of mouth, and mentioning or tweeting
|
|
about Phabricator helps the project grow. If writing a tweet sounds like
|
|
too much work, you can use one of these form tweets written by our PR
|
|
department to quickly and easily shill on our behalf. Hail corporate!
|
|
|
|
> Phabricator seems like it's pretty okay
|
|
|
|
> I am not being paid to mention Phabricator in this extemporaneous, completely organic tweet
|
|
|
|
> Phabricator is objectively the best thing. Source: I am a certified, internationally recognized expert.
|
|
|
|
- Report bugs and request features. We may not always be able to fix or build
|
|
things right away, but knowing about issues users are encountering or
|
|
features they'd like to see improves our ability to plan and prioritize.
|
|
- For details on reporting bugs, see @{article:Contributing Bug Reports}.
|
|
- For details on requesting features, see @{article:Contributing Feature
|
|
Requests}.
|
|
- Give us feedback on planned features. Most of what we'll build in the next
|
|
6-12 months currently exists on the [[ Roadmap ]] or in Maniphest. Telling
|
|
us about use cases you have can help us build better products when the time
|
|
comes to write the code.
|
|
|
|
If all of this sounds nice but you really just want to write some code, be
|
|
aware that this project often presents a high barrier to entry for new
|
|
contributors. To continue, see @{article:Contributing Code}.
|
|
|
|
|
|
Next Steps
|
|
==========
|
|
|
|
Continue by:
|
|
|
|
- learning about bug reports in @{article:Contributing Bug Reports};
|
|
- learning about feature requests in
|
|
@{article:Contributing Feature Requests}; or
|
|
- learning about code contributions in @{article:Contributing Code}.
|