Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Newer
Older
100644 347 lines (221 sloc) 10.26 kb
8ee1ad7 @allisonrandal [cage] Updating copyright in whole repository to Parrot Foundation.
allisonrandal authored
1 # Copyright (C) 2004-2008, Parrot Foundation.
b103d20 @bschmalhofer Update 'docs' WRT to the switch to subversion.
bschmalhofer authored
2
6501e21 [perl #24103] updated
Michael Scott authored
3 =head1 NAME
4
5 docs/submissions.pod - Parrot Submission Instructions
6
7 =head1 ABSTRACT
8
9 How to submit bug reports, patches and new files to Parrot.
10
11 =head1 How To Submit A Bug Report
12
cc8cb90 @jkeenan Applying, with small modifications, patches to documentation re submi…
jkeenan authored
13 If you encounter an error while working with Parrot and don't understand what
14 is causing it, create a bug report using the F<parrotbug> utility. The
ea0630c @jhoblitt reformat all Pod files under docs with podtidy (modified to also remo…
jhoblitt authored
15 simplest way to use it is to run
6501e21 [perl #24103] updated
Michael Scott authored
16
17 % ./parrotbug
edb1fb0 @coke spelling, urls, email addresses...
coke authored
18
6501e21 [perl #24103] updated
Michael Scott authored
19 in the distribution's root directory, and follow the prompts.
20
9ba6ab1 @pmichaud [docs] Update submissions.pod with ticket@parrot.org address.
pmichaud authored
21 If you just want to use email to create the bug report, send an email to
22 L<tickets@parrot.org>.
23
24 If you know how to fix the problem you encountered, then think about
25 submitting a patch, or (see below) getting commit privileges.
6501e21 [perl #24103] updated
Michael Scott authored
26
ffb0b0f @plobsing add notes on reporting/debugging random failures
plobsing authored
27 =head1 A Note on Random Failures
28
29 If you encounter errors that appear intermittently, it may be difficult or
30 impossible for Parrot developers to diagnose and solve the problem. It is
31 therefore recommended to control the sources of randomness in Parrot in an
32 attempt to eliminate the intermittency of the bug. There are three common
33 sources of randomness that should be considered.
34
35 =over
36
37 =item Pseudo-Random Number Generator
38
39 Direct use of a PRNG from within Parrot programs will lead to inconsistent
40 results. If possible, isolate the bug from PRNG use, for example, by logging
41 the random values which trigger the error and then hard coding them.
42
43 =item Address Space Layout Randomization
44
45 Several operating systems provide a security measure known as address space
46 layout randomization. In bugs involving stray pointers, this can cause
47 corruption in random Parrot subsystems. Temporarily disabling this feature may
48 make this problem consistent and therefore debugable.
49
50 =item Hash Seed
51
52 Parrot's hash implementation uses randomization of its seed as a precaution
53 against attacks based on hash collisions. The seed used can be directly
54 controlled using C<parrot>'s C<--hash-seed> parameter. To determine what seeds
55 are causing the error, Parrot can be rebuilt with C<DEBUG_HASH_SEED> set to
56 C<1>, which will cause C<parrot> to output the hash seed being used on every
57 invocation.
58
59 =back
60
cc8cb90 @jkeenan Applying, with small modifications, patches to documentation re submi…
jkeenan authored
61 =head1 How To Create A Patch
6501e21 [perl #24103] updated
Michael Scott authored
62
05a7e7b @bschmalhofer This patch is huge because of all the whitespace reformatting. This was
bschmalhofer authored
63 Try to keep your patches specific to a single change, and ensure that your
4bc4302 @chromatic [docs] Clarified how a contributor becomes a committer, except for th…
chromatic authored
64 change does not break any tests. Do this by running C<make test>. If there is
65 no test for the fixed bug, please provide one.
6501e21 [perl #24103] updated
Michael Scott authored
66
05a7e7b @bschmalhofer This patch is huge because of all the whitespace reformatting. This was
bschmalhofer authored
67 In the following examples, F<parrot> contains the Parrot distribution, and
58c06d7 @jhoblitt fix error in the use of parrot vs. parrotdev in the patch examples, p…
jhoblitt authored
68 F<workingdir> contains F<parrot>. The name F<workingdir> is just a placeholder
05a7e7b @bschmalhofer This patch is huge because of all the whitespace reformatting. This was
bschmalhofer authored
69 for whatever the distribution's parent directory is called on your machine.
6501e21 [perl #24103] updated
Michael Scott authored
70
58c06d7 @jhoblitt fix error in the use of parrot vs. parrotdev in the patch examples, p…
jhoblitt authored
71 workingdir
72 |
73 +--> parrot
74 |
5ce0abd @coke [docs]
coke authored
75 +--> LICENSE
58c06d7 @jhoblitt fix error in the use of parrot vs. parrotdev in the patch examples, p…
jhoblitt authored
76 |
5c37a49 @particle [docs] trailing space cleanup
particle authored
77 +--> src
58c06d7 @jhoblitt fix error in the use of parrot vs. parrotdev in the patch examples, p…
jhoblitt authored
78 |
a9a4b2c @coke [devel]doc
coke authored
79 +--> tools
58c06d7 @jhoblitt fix error in the use of parrot vs. parrotdev in the patch examples, p…
jhoblitt authored
80 |
81 +--> ...
82
6501e21 [perl #24103] updated
Michael Scott authored
83 =over
84
45c0ea1 @leto [docs] Update docs/submissions.pod
leto authored
85 =item C<git>
51781a5 @bschmalhofer [submissions.pod]
bschmalhofer authored
86
45c0ea1 @leto [docs] Update docs/submissions.pod
leto authored
87 If you are working with a git repository of parrot then please generate
88 your patch with C<git diff>.
51781a5 @bschmalhofer [submissions.pod]
bschmalhofer authored
89
90 cd parrot
45c0ea1 @leto [docs] Update docs/submissions.pod
leto authored
91 git diff > my_contribution.patch
51781a5 @bschmalhofer [submissions.pod]
bschmalhofer authored
92
6501e21 [perl #24103] updated
Michael Scott authored
93 =item Single C<diff>
94
4bc4302 @chromatic [docs] Clarified how a contributor becomes a committer, except for th…
chromatic authored
95 If you are working from a released distribution of Parrot and the change you
96 wish to make affects only one or two files, then you can supply a C<diff> for
97 each file. The C<diff> should be created in F<parrot>. Please be sure to
98 create a unified diff, with C<diff -u>.
c8e0dac revised the patch section to incorporate suggestions made by Leo Toetsch
Michael Scott authored
99
100 cd parrot
101 diff -u docs/submissions.pod docs/submissions.new > submissions.patch
6501e21 [perl #24103] updated
Michael Scott authored
102
4bc4302 @chromatic [docs] Clarified how a contributor becomes a committer, except for th…
chromatic authored
103 Win32 users will probably need to specify C<-ub>.
6501e21 [perl #24103] updated
Michael Scott authored
104
105 =item Recursive C<diff>
106
05a7e7b @bschmalhofer This patch is huge because of all the whitespace reformatting. This was
bschmalhofer authored
107 If the change is more wide-ranging, then create an identical copy of F<parrot>
58c06d7 @jhoblitt fix error in the use of parrot vs. parrotdev in the patch examples, p…
jhoblitt authored
108 in F<workingdir> and rename it F<parrot.new>. Modify F<parrot.new> and run a
05a7e7b @bschmalhofer This patch is huge because of all the whitespace reformatting. This was
bschmalhofer authored
109 recursive C<diff> on the two directories to create your patch. The C<diff>
58c06d7 @jhoblitt fix error in the use of parrot vs. parrotdev in the patch examples, p…
jhoblitt authored
110 should be created in F<workingdir>.
c8e0dac revised the patch section to incorporate suggestions made by Leo Toetsch
Michael Scott authored
111
58c06d7 @jhoblitt fix error in the use of parrot vs. parrotdev in the patch examples, p…
jhoblitt authored
112 cd workingdir
45c0ea1 @leto [docs] Update docs/submissions.pod
leto authored
113 diff -ur --exclude='.git' parrot parrot.new > docs.patch
6501e21 [perl #24103] updated
Michael Scott authored
114
4bc4302 @chromatic [docs] Clarified how a contributor becomes a committer, except for th…
chromatic authored
115 Mac OS X users should also specify C<--exclude=.DS_Store>.
6501e21 [perl #24103] updated
Michael Scott authored
116
a815702 @jhoblitt add a blurb about CREDITS
jhoblitt authored
117 =item C<CREDITS>
118
119 Each and every patch is an important contribution to Parrot and it's important
120 that these efforts are recognized. To that end, the F<CREDITS> file contains
121 an informal list of contributors and their contributions made to Parrot. Patch
122 submitters are encouraged to include a new or updated entry for themselves in
123 F<CREDITS> as part of their patch.
124
125 The format for entries in F<CREDITS> is defined at the top of the file.
126
6501e21 [perl #24103] updated
Michael Scott authored
127 =back
128
cc8cb90 @jkeenan Applying, with small modifications, patches to documentation re submi…
jkeenan authored
129 =head1 How To Submit A Patch
130
131 =over 4
132
133 =item 1
6501e21 [perl #24103] updated
Michael Scott authored
134
4d1c65b @allisonrandal [doc] Update submissions.pod for Trac ticket web form.
allisonrandal authored
135 Go to Parrot's ticket tracking system at
136 L<https://trac.parrot.org/parrot/>. Log in, or create an account if you
137 don't have one yet.
6501e21 [perl #24103] updated
Michael Scott authored
138
cc8cb90 @jkeenan Applying, with small modifications, patches to documentation re submi…
jkeenan authored
139 =item 2
140
141 If there is already a ticket for the bug or feature that your patch relates
142 to, just attach the patch directly to the ticket.
143
6501e21 [perl #24103] updated
Michael Scott authored
144 =item 3
145
cc8cb90 @jkeenan Applying, with small modifications, patches to documentation re submi…
jkeenan authored
146 Otherwise select "New Ticket" at the top of the site.
147 L<https://trac.parrot.org/parrot/newticket>
6501e21 [perl #24103] updated
Michael Scott authored
148
149 =item 4
150
209a94e @jkeenan Inspired by Aninhumer++ submission in
jkeenan authored
151 Give a clear and concise Summary. You do B<NOT> need to prefix the Summary
152 with a C<[PATCH]> identifier. Instead, in the lower-right corner of the
153 F<newticket> page, select status C<new> in the F<Patch status> drop-down box.
6501e21 [perl #24103] updated
Michael Scott authored
154
155 =item 5
156
4d1c65b @allisonrandal [doc] Update submissions.pod for Trac ticket web form.
allisonrandal authored
157 The Description should contain an explanation of the purpose of the patch, and
05a7e7b @bschmalhofer This patch is huge because of all the whitespace reformatting. This was
bschmalhofer authored
158 a list of all files affected with summary of the changes made in each file.
159 Optionally, the output of the C<diffstat(1)> utility when run on your patch(s)
160 may be included at the bottom of the message body.
6501e21 [perl #24103] updated
Michael Scott authored
161
162 =item 6
163
4d1c65b @allisonrandal [doc] Update submissions.pod for Trac ticket web form.
allisonrandal authored
164 Set the Type of the ticket to "patch". Set other relevant drop-down
165 menus, such as Version (the version of Parrot where you encountered the
209a94e @jkeenan Inspired by Aninhumer++ submission in
jkeenan authored
166 problem), Platform, or Severity. As mentioned above, select status C<new> in
167 the F<Patch status> drop-down box.
4d1c65b @allisonrandal [doc] Update submissions.pod for Trac ticket web form.
allisonrandal authored
168
169 =item 7
170
cc8cb90 @jkeenan Applying, with small modifications, patches to documentation re submi…
jkeenan authored
171 Check the box for "I have files to attach to this ticket". Double-check
172 that you've actually done this, because it's easy to forget.
6501e21 [perl #24103] updated
Michael Scott authored
173
4d1c65b @allisonrandal [doc] Update submissions.pod for Trac ticket web form.
allisonrandal authored
174 B<DO NOT> paste the patch file content into the Description.
6501e21 [perl #24103] updated
Michael Scott authored
175
49a1fb1 @Util [codingstd] Re-sequenced =item numbers to pass pod_syntax.t
Util authored
176 =item 8
6501e21 [perl #24103] updated
Michael Scott authored
177
4d1c65b @allisonrandal [doc] Update submissions.pod for Trac ticket web form.
allisonrandal authored
178 Click the "Create ticket" button. On the next page attach your patch
179 file(s).
6501e21 [perl #24103] updated
Michael Scott authored
180
181 =back
182
070739d @bschmalhofer Mention how to make patch for www.parrotcode.org.
bschmalhofer authored
183 =head1 Applying Patches
c8e0dac revised the patch section to incorporate suggestions made by Leo Toetsch
Michael Scott authored
184
05a7e7b @bschmalhofer This patch is huge because of all the whitespace reformatting. This was
bschmalhofer authored
185 You may wish to apply a patch submitted by someone else before the patch is
45c0ea1 @leto [docs] Update docs/submissions.pod
leto authored
186 incorporated into git
c8e0dac revised the patch section to incorporate suggestions made by Leo Toetsch
Michael Scott authored
187
45c0ea1 @leto [docs] Update docs/submissions.pod
leto authored
188 For single C<diff> patches or C<git> patches, copy the patch file to
58c06d7 @jhoblitt fix error in the use of parrot vs. parrotdev in the patch examples, p…
jhoblitt authored
189 F<parrot>, and run:
c8e0dac revised the patch section to incorporate suggestions made by Leo Toetsch
Michael Scott authored
190
191 cd parrot
45c0ea1 @leto [docs] Update docs/submissions.pod
leto authored
192 git apply some.patch
c8e0dac revised the patch section to incorporate suggestions made by Leo Toetsch
Michael Scott authored
193
58c06d7 @jhoblitt fix error in the use of parrot vs. parrotdev in the patch examples, p…
jhoblitt authored
194 For recursive C<diff> patches, copy the patch file to F<workingdir>, and run:
c8e0dac revised the patch section to incorporate suggestions made by Leo Toetsch
Michael Scott authored
195
58c06d7 @jhoblitt fix error in the use of parrot vs. parrotdev in the patch examples, p…
jhoblitt authored
196 cd workingdir
45c0ea1 @leto [docs] Update docs/submissions.pod
leto authored
197 git apply some.patch
c8e0dac revised the patch section to incorporate suggestions made by Leo Toetsch
Michael Scott authored
198
e024cdd @bschmalhofer Tweaking docs/submissions.pod
bschmalhofer authored
199 In order to be on the safe side run 'make test' before actually committing
5c37a49 @particle [docs] trailing space cleanup
particle authored
200 the changes.
e024cdd @bschmalhofer Tweaking docs/submissions.pod
bschmalhofer authored
201
4bc4302 @chromatic [docs] Clarified how a contributor becomes a committer, except for th…
chromatic authored
202 =head2 Configuration of files to ignore
3e4b92a @bschmalhofer Regenerate MANIFEST.SKIP because new ignore files have been added
bschmalhofer authored
203
05a7e7b @bschmalhofer This patch is huge because of all the whitespace reformatting. This was
bschmalhofer authored
204 Sometimes new files will be created in the configuration and build process of
205 Parrot. These files should not show up when checking the distribution with
3e4b92a @bschmalhofer Regenerate MANIFEST.SKIP because new ignore files have been added
bschmalhofer authored
206
45c0ea1 @leto [docs] Update docs/submissions.pod
leto authored
207 git status
3e4b92a @bschmalhofer Regenerate MANIFEST.SKIP because new ignore files have been added
bschmalhofer authored
208
209 or
210
211 perl tools/dev/manicheck.pl
212
5c37a49 @particle [docs] trailing space cleanup
particle authored
213 In order to keep the two different checks synchronized,
69e07c0 @bschmalhofer Use indirekt file handles.
bschmalhofer authored
214 the MANIFEST and MANIFEST.SKIP file should be regenerated with:
215
216 perl tools/dev/mk_manifest_and_skip.pl
3e4b92a @bschmalhofer Regenerate MANIFEST.SKIP because new ignore files have been added
bschmalhofer authored
217
218
6501e21 [perl #24103] updated
Michael Scott authored
219 =head1 How To Submit Something New
220
221 If you have a new feature to add to Parrot, such as a new test.
222
223 =over
224
225 =item 1
226
05a7e7b @bschmalhofer This patch is huge because of all the whitespace reformatting. This was
bschmalhofer authored
227 Add your new file path(s), relative to F<parrot>, to the file MANIFEST. Create
4bc4302 @chromatic [docs] Clarified how a contributor becomes a committer, except for th…
chromatic authored
228 a patch for the MANIFEST file according to the instructions in B<How To Submit
229 A Patch>.
6501e21 [perl #24103] updated
Michael Scott authored
230
231 =item 2
232
a9a4b2c @coke [devel]doc
coke authored
233 If you have a new test script ending in C<.t>, some mailers may become confused
05a7e7b @bschmalhofer This patch is huge because of all the whitespace reformatting. This was
bschmalhofer authored
234 and consider it an application/x-troff. One way around this (for *nix users) is
235 to diff the file against /dev/null like this:
acd1598 [perl #35892] [PATCH] Updated submissions.pod
Leopold Toetsch authored
236
237 cd parrot
238 diff -u /dev/null newfile.t > newfile.patch
6501e21 [perl #24103] updated
Michael Scott authored
239
240 =item 3
241
4d1c65b @allisonrandal [doc] Update submissions.pod for Trac ticket web form.
allisonrandal authored
242 Go to Parrot's ticket tracking system at
243 L<https://trac.parrot.org/parrot/>. Log in, or create an account if you
244 don't have one yet.
acd1598 [perl #35892] [PATCH] Updated submissions.pod
Leopold Toetsch authored
245
246 =item 4
247
4d1c65b @allisonrandal [doc] Update submissions.pod for Trac ticket web form.
allisonrandal authored
248 Select "New Ticket" L<https://trac.parrot.org/parrot/newticket>.
acd1598 [perl #35892] [PATCH] Updated submissions.pod
Leopold Toetsch authored
249
250 =item 5
251
4d1c65b @allisonrandal [doc] Update submissions.pod for Trac ticket web form.
allisonrandal authored
252 Give a clear and concise Summary.
6501e21 [perl #24103] updated
Michael Scott authored
253
254 Prefix it with a C<[NEW]> identifier.
255
acd1598 [perl #35892] [PATCH] Updated submissions.pod
Leopold Toetsch authored
256 =item 6
6501e21 [perl #24103] updated
Michael Scott authored
257
4d1c65b @allisonrandal [doc] Update submissions.pod for Trac ticket web form.
allisonrandal authored
258 The Description should contain an explanation of the purpose of the feature
4bc4302 @chromatic [docs] Clarified how a contributor becomes a committer, except for th…
chromatic authored
259 you are adding. Optionally, include the output of the C<diffstat(1)> utility
260 when run on your patch(es).
6501e21 [perl #24103] updated
Michael Scott authored
261
acd1598 [perl #35892] [PATCH] Updated submissions.pod
Leopold Toetsch authored
262 =item 7
6501e21 [perl #24103] updated
Michael Scott authored
263
4d1c65b @allisonrandal [doc] Update submissions.pod for Trac ticket web form.
allisonrandal authored
264 Set the Type of the ticket to "patch". Set other relevant drop-down
265 menus, such as Version, Platform, or Severity.
266
267 =item 8
268
269 Check the box for "I have files to attach to this ticket"
6501e21 [perl #24103] updated
Michael Scott authored
270
05a7e7b @bschmalhofer This patch is huge because of all the whitespace reformatting. This was
bschmalhofer authored
271 Double-check that you've actually done this, because it's easy to forget.
6501e21 [perl #24103] updated
Michael Scott authored
272
1772034 @jhoblitt reformat all Pod files under docs with podtidy except for docs/pdds
jhoblitt authored
273 B<DO NOT> paste the content of the new file or files into the body of the
274 message.
6501e21 [perl #24103] updated
Michael Scott authored
275
49a1fb1 @Util [codingstd] Re-sequenced =item numbers to pass pod_syntax.t
Util authored
276 =item 9
6501e21 [perl #24103] updated
Michael Scott authored
277
4d1c65b @allisonrandal [doc] Update submissions.pod for Trac ticket web form.
allisonrandal authored
278 Click the "Create ticket" button. On the next page attach the patch for
279 MANIFEST and your new file(s).
6501e21 [perl #24103] updated
Michael Scott authored
280
281 =back
282
283 =head1 What Happens Next?
284
cc8cb90 @jkeenan Applying, with small modifications, patches to documentation re submi…
jkeenan authored
285 If you created a new ticket for the submission, you will be taken to the page
286 for the new ticket and can check on the progress of your submission there.
287 This identifier should be used in all correspondence concerning the submission.
6501e21 [perl #24103] updated
Michael Scott authored
288
cc8cb90 @jkeenan Applying, with small modifications, patches to documentation re submi…
jkeenan authored
289 Everyone on Trac sees the submission and can comment on it. A developer with
04120ec @jkeenan Spelling corrections per TT #2016. mstevens++.
jkeenan authored
290 git commit privileges can commit it to git once it is clear that it is the
1772034 @jhoblitt reformat all Pod files under docs with podtidy except for docs/pdds
jhoblitt authored
291 right thing to do.
6501e21 [perl #24103] updated
Michael Scott authored
292
04120ec @jkeenan Spelling corrections per TT #2016. mstevens++.
jkeenan authored
293 However developers with commit privileges may not commit your changes
cc8cb90 @jkeenan Applying, with small modifications, patches to documentation re submi…
jkeenan authored
294 immediately if they are large or complex, as we need time for peer review.
6501e21 [perl #24103] updated
Michael Scott authored
295
cc8cb90 @jkeenan Applying, with small modifications, patches to documentation re submi…
jkeenan authored
296 A list of active tickets can be found here:
297 L<http://trac.parrot.org/parrot/report/1>
acd1598 [perl #35892] [PATCH] Updated submissions.pod
Leopold Toetsch authored
298
cc8cb90 @jkeenan Applying, with small modifications, patches to documentation re submi…
jkeenan authored
299 A list of all the unresolved patches is at:
300 L<http://trac.parrot.org/parrot/report/15>
6501e21 [perl #24103] updated
Michael Scott authored
301
070739d @bschmalhofer Mention how to make patch for www.parrotcode.org.
bschmalhofer authored
302 =head1 Patches for the Parrot website
303
4d1c65b @allisonrandal [doc] Update submissions.pod for Trac ticket web form.
allisonrandal authored
304 The L<http://www.parrot.org> website is hosted in a Drupal CMS. Submit
305 changes through the usual ticket interface in Trac.
070739d @bschmalhofer Mention how to make patch for www.parrotcode.org.
bschmalhofer authored
306
a9a4b2c @coke [devel]doc
coke authored
307 =head1 Getting Commit Privileges
308
4bc4302 @chromatic [docs] Clarified how a contributor becomes a committer, except for th…
chromatic authored
309 If you are interested in getting commit privileges to Parrot, here is
a9a4b2c @coke [devel]doc
coke authored
310 the procedure:
311
312 =over 4
313
314 =item 1
315
4bc4302 @chromatic [docs] Clarified how a contributor becomes a committer, except for th…
chromatic authored
316 Submit several high quality patches (and have them committed) via the process
317 described in this document. This process may take weeks or months.
a9a4b2c @coke [devel]doc
coke authored
318
319 =item 2
320
4d1c65b @allisonrandal [doc] Update submissions.pod for Trac ticket web form.
allisonrandal authored
321 Obtain a Trac account at L<https://trac.parrot.org/parrot>
a9a4b2c @coke [devel]doc
coke authored
322
323 =item 3
324
ec0a376 @allisonrandal [cage] Caught a reference to "Perl Contributor License Agreement".
allisonrandal authored
325 Submit a Parrot Contributor License Agreement; this document signifies that you
8ee1ad7 @allisonrandal [cage] Updating copyright in whole repository to Parrot Foundation.
allisonrandal authored
326 have the authority to license your work to Parrot Foundation for inclusion in
4bc4302 @chromatic [docs] Clarified how a contributor becomes a committer, except for th…
chromatic authored
327 their projects. You may need to discuss this with your employer if you
328 contribute to Parrot on work time or with work resources, or depending on your
329 employment agreement.
330
ec0a376 @allisonrandal [cage] Caught a reference to "Perl Contributor License Agreement".
allisonrandal authored
331 L<http://www.parrot.org/files/parrot_cla.pdf>
4bc4302 @chromatic [docs] Clarified how a contributor becomes a committer, except for th…
chromatic authored
332
333 =item 4
334
66ddda2 @Infinoid [docs] Fix up old references to submitting/subscribing/archives for t…
Infinoid authored
335 Request commit access via the C<parrot-dev> mailing list, or via IRC
cc8cb90 @jkeenan Applying, with small modifications, patches to documentation re submi…
jkeenan authored
336 (#parrot on irc.parrot.org). The existing committers will discuss your
337 request in the next couple of weeks.
4bc4302 @chromatic [docs] Clarified how a contributor becomes a committer, except for th…
chromatic authored
338
cdc0d84 @Util [docs] Typos - s/navitate/navigate/; Committer has 2 "m"s and 2 "t"s
Util authored
339 If approved, a metacommitter will update the permissions to allow you to commit
4bc4302 @chromatic [docs] Clarified how a contributor becomes a committer, except for th…
chromatic authored
340 to Parrot; see C<RESPONSIBLE_PARTIES> for the current list. Welcome aboard!
a9a4b2c @coke [devel]doc
coke authored
341
342 =back
343
9f76dea + Point to "metacommitters" in C<RESPONSIBLE_PARTIES> for SVN
Bob Rogers authored
344 Thanks for your help!
345
b103d20 @bschmalhofer Update 'docs' WRT to the switch to subversion.
bschmalhofer authored
346 =cut
Something went wrong with that request. Please try again.