Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(10)

Side by Side Diff: third_party/gsutil/gslib/addlhelp/dev.py

Issue 10199002: Upgrade gsutil to 3.4 (Closed) Base URL: https://dart.googlecode.com/svn/branches/bleeding_edge/dart
Patch Set: Addressed comments Created 8 years, 7 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch | Annotate | Revision Log
OLDNEW
(Empty)
1 # Copyright 2012 Google Inc.
2 #
3 # Licensed under the Apache License, Version 2.0 (the "License");
4 # you may not use this file except in compliance with the License.
5 # You may obtain a copy of the License at
6 #
7 # http://www.apache.org/licenses/LICENSE-2.0
8 #
9 # Unless required by applicable law or agreed to in writing, software
10 # distributed under the License is distributed on an "AS IS" BASIS,
11 # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
12 # See the License for the specific language governing permissions and
13 # limitations under the License.
14
15 from gslib.help_provider import HELP_NAME
16 from gslib.help_provider import HELP_NAME_ALIASES
17 from gslib.help_provider import HELP_ONE_LINE_SUMMARY
18 from gslib.help_provider import HelpProvider
19 from gslib.help_provider import HELP_TEXT
20 from gslib.help_provider import HelpType
21 from gslib.help_provider import HELP_TYPE
22
23 _detailed_help_text = ("""
24 <B>OVERVIEW</B>
25 We're open to incorporating gsutil code changes authored by users. Here
26 are some guidelines:
27
28 1. If you found a bug or have an idea for a feature enhancement, we suggest
29 you check http://code.google.com/p/gsutil/issues/list to see if it has
30 already been reported by another user. From there you can also add yourself
31 to the Cc list for an issue, so you will find out about any developments.
32
33 2. It's usually worthwhile to send email to gs-team@google.com about your
34 idea before sending actual code. Often we can discuss the idea and help
35 propose things that could save you later revision work.
36
37 3. We tend to avoid adding command line options that are of use to only
38 a very small fraction of users, especially if there's some other way
39 to accommodate such needs. Adding such options complicates the code and
40 also adds overhead to users having to read through an "alphabet soup"
41 list of option documentation.
42
43 4. While gsutil has a number of features specific to Google Cloud Storage,
44 it can also be used with other cloud storage providers. We're open to
45 including changes for making gsutil support features specific to other
46 providers, as long as those changes don't make gsutil work worse for Google
47 Cloud Storage. If you do make such changes we recommend including someone
48 with knowledge of the specific provider as a code reviewer (see below).
49
50 5. Please make sure to run all tests against your modified code. To
51 do this, change directories into the gsutil top-level directory and run:
52
53 export PYTHONPATH=./boto:$PYTHONPATH
54 ./gslib/test_commands.py
55 ./gslib/test_thread_pool.py
56 ./gslib/test_wildcard_iterator.py
57
58 The above tests run quickly, as they run against an in-memory mock
59 storage service implementation. We have an additional set of tests
60 that take longer because they send requests to the production service;
61 please also run these tests:
62
63 ./gsutil test
64
65 6. Please consider contributing test code for your change, especially if the
66 change impacts any of the core gsutil code (like the gsutil cp command).
67
68 7. When it's time to send us code, please use the Rietveld code review tool
69 rather than simply sending us a code patch. Do this as follows:
70 - check out the gsutil code from at
71 http://code.google.com/p/gsutil/source/checkout and apply your changes
72 in the checked out directory.
73 - download the "upload.py" script from
74 http://code.google.com/p/rietveld/wiki/UploadPyUsage
75 - run upload.py from the above gsutil svn directory.
76 - click the codereview.appspot.com link it generates, click "Edit Issue",
77 and add mfschwartz@google.com as a reviewer, and Cc gs-team@google.com.
78 - click Publish+Mail Comments.
79 """)
80
81
82
83 class CommandOptions(HelpProvider):
84 """Additional help about Access Control Lists."""
85
86 help_spec = {
87 # Name of command or auxiliary help info for which this help applies.
88 HELP_NAME : 'dev',
89 # List of help name aliases.
90 HELP_NAME_ALIASES : ['development', 'developer', 'code', 'mods',
91 'software'],
92 # Type of help:
93 HELP_TYPE : HelpType.ADDITIONAL_HELP,
94 # One line summary of this help.
95 HELP_ONE_LINE_SUMMARY : 'Making modifications to gsutil',
96 # The full help text.
97 HELP_TEXT : _detailed_help_text,
98 }
OLDNEW
« no previous file with comments | « third_party/gsutil/gslib/addlhelp/command_opts.py ('k') | third_party/gsutil/gslib/addlhelp/metadata.py » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698