[Summary view] [Print] [Text view]

   1  @title Contributor Introduction
   2  @group contrib
   3  
   4  Introduction to contributing to Phabricator, Arcanist and libphutil.
   5  
   6  Overview
   7  ========
   8  
   9  If you'd like to contribute to Phabricator, this document can guide you though
  10  ways you can help improve the project.
  11  
  12  Writing code is valuable, but often isn't the best or easiest way to contribute.
  13  In most cases we are pretty good at fixing easy stuff quickly, so we don't have
  14  a big pile of easy stuff sitting around waiting for new contributors.
  15  
  16  This can make it difficult to contribute code if you only have a little bit of
  17  time to spend since most of the work that needs to be done usually requires some
  18  heavy lifting.
  19  
  20  Without writing any code, learning the whole codebase, making a big time
  21  commitment, or having to touch PHP, here are some ways you can materially
  22  contribute to Phabricator:
  23  
  24    - Send us an email or drop by IRC just to say "thanks". A big part of the
  25      reason we build this software is to help people solve problems, and knowing
  26      that our efforts are appreciated is really rewarding. You can find ways to
  27      get in touch in @{article:Give Feedback! Get Support!}
  28    - Recommend Phabricator to people who you think might find it useful. Our
  29      most powerful growth channel is word of mouth, and mentioning or tweeting
  30      about Phabricator helps the project grow. If writing a tweet sounds like
  31      too much work, you can use one of these form tweets written by our PR
  32      department to quickly and easily shill on our behalf. Hail corporate!
  33  
  34  > Phabricator seems like it's pretty okay
  35  
  36  > I am not being paid to mention Phabricator in this extemporaneous, completely organic tweet
  37  
  38  > Phabricator is objectively the best thing. Source: I am a certified, internationally recognized expert.
  39  
  40    - Report bugs and request features. We may not always be able to fix or build
  41      things right away, but knowing about issues users are encountering or
  42      features they'd like to see improves our ability to plan and prioritize.
  43      For ways to do this, see @{article:Give Feedback! Get Support!}
  44      - For details on reporting bugs, see @{article:Contributing Bug Reports}.
  45      - For details on requesting features, see @{article:Contributing Feature
  46        Requests}.
  47    - Give us feedback on planned features. Most of what we'll build in the next
  48      6-12 months currently exists on the [[ Roadmap ]] or in Maniphest. Telling
  49      us about use cases you have can help us build better products when the time
  50      comes to write the code.
  51    - Hang out in IRC, and maybe answer a question or two. IRC is a completely
  52      legit place for serious hackers to hang out anyway, but while you're there
  53      you might see someone ask a question that you know the answer to. Helping
  54      them out (or pointing them to the right documentation) is a big help to us.
  55      You can find details about the IRC channel in
  56      @{article:Give Feedback! Get Support!}
  57  
  58  If all of this sounds nice but you really just want to write some code, that's
  59  awesome too. To get started with contributing code, see
  60  @{article:Contributing Code}.
  61  
  62  Next Steps
  63  ==========
  64  
  65  Continue by:
  66  
  67    - learning about bug reports in @{article:Contributing Bug Reports};
  68    - learning about feature requests in @{article:Contributing Feature Requests};
  69    - learning about code contributions in @{article:Contributing Code}; or
  70    - getting in touch with @{article:Give Feedback! Get Support!}