summaryrefslogtreecommitdiff
path: root/docs/internals/contributing/new-contributors.txt
diff options
context:
space:
mode:
authorAymeric Augustin <aymeric.augustin@m4x.org>2014-07-13 19:42:06 +0200
committerAymeric Augustin <aymeric.augustin@m4x.org>2014-08-01 14:41:25 +0200
commita4ead67ee9000a41f7bdca2978c5b2e309066220 (patch)
tree43e7cfc3ca22c016a27f742822a30d71832dbe32 /docs/internals/contributing/new-contributors.txt
parentdd9c8f9382d626b432902de6178fb70a7a04a8b0 (diff)
Adjusted 'internals' docs to the new organization.
Most of these changes are about using the correct vocabulary -- "core team member" vs "core developer/committer" and adding internal links.
Diffstat (limited to 'docs/internals/contributing/new-contributors.txt')
-rw-r--r--docs/internals/contributing/new-contributors.txt12
1 files changed, 6 insertions, 6 deletions
diff --git a/docs/internals/contributing/new-contributors.txt b/docs/internals/contributing/new-contributors.txt
index 80a87f1e8f..2e55114a66 100644
--- a/docs/internals/contributing/new-contributors.txt
+++ b/docs/internals/contributing/new-contributors.txt
@@ -102,8 +102,8 @@ some advice to make your work on Django more useful and rewarding.
Sometimes it can be scary to put your opinion out to the world and say "this
ticket is correct" or "this patch needs work", but it's the only way the
project moves forward. The contributions of the broad Django community
- ultimately have a much greater impact than that of the core developers. We
- can't do it without YOU!
+ ultimately have a much greater impact than that of the core team. We can't
+ do it without **you**!
* **Err on the side of caution when marking things Ready For Check-in**
@@ -138,10 +138,10 @@ FAQ
I do to get it committed?**
First off, it's not personal. Django is entirely developed by volunteers
- (even the core developers), and sometimes folks just don't have time. The
- best thing to do is to send a gentle reminder to the |django-developers|
- mailing list asking for review on the ticket, or to bring it up in the
- #django-dev IRC channel.
+ (even the core team), and sometimes folks just don't have time. The best
+ thing to do is to send a gentle reminder to the |django-developers| mailing
+ list asking for review on the ticket, or to bring it up in the #django-dev
+ IRC channel.
2. **I'm sure my ticket is absolutely 100% perfect, can I mark it as RFC
myself?**