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

Side by Side Diff: appengine/monorail/templates/project/project-admin-page.ezt

Issue 1868553004: Open Source Monorail (Closed) Base URL: https://chromium.googlesource.com/infra/infra.git@master
Patch Set: Rebase Created 4 years, 8 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
OLDNEW
(Empty)
1 [define category_css]css/ph_detail.css[end]
2 [include "../framework/master-header.ezt" "showtabs"]
3
4 [if-any read_only][include "../framework/read-only-rejection.ezt"]
5 [else]
6
7 <form action="admin.do" method="POST" autocomplete="off" enctype="multipart/for m-data">
8 <input type="hidden" name="token" value="[form_token]">
9
10 <h4>Project metadata</h4>
11
12 <div class="section">
13 [include "../framework/project-descriptive-fields.ezt"]
14 </div>
15
16
17 <h4>Project access</h4>
18
19 <div class="section">
20 [if-any offer_access_level initial_access]
21 <br>This project may be viewed by:
22 [include "../framework/project-access-part.ezt" "dontchecksubmit"]<br>
23 [end]
24
25 <div class="section">
26 <div class="closed">
27 <p>Restriction labels allow project members to restrict access to individual
28 issues.
29 <a class="ifClosed toggleHidden" href="#" style="font-size:90%; margin-left:.5 em">Learn more</a></p>
30 <div class="ifOpened help">
31 Normally, if a project member may edit the labels, then he or she may also
32 edit restriction labels. That allows project committers to adjust access
33 controls for the items that they are working on. However, some project
34 owners may prefer that once a restriction label is in place, only a projec t
35 owner may remove it.
36 </div>
37 </div>
38 <input type="checkbox" name="only_owners_remove_restrictions"
39 id="only_owners_remove_restrictions"
40 [if-any only_owners_remove_restrictions]checked="checked"[end] >
41 <label for="only_owners_remove_restrictions">Only project owners
42 may remove <tt>Restrict-*</tt> labels</label>
43 </div>
44
45 <div class="section">
46 <div class="closed">
47 <p>Collaboration style
48 <a class="ifClosed toggleHidden" href="#" style="font-size:90%; margin-left:.5 em">Learn more</a></p>
49 <div class="ifOpened help">
50 Project workspaces are usually intended to promote collaboration among
51 all project members. However, sometimes a compartmentalized collaboration
52 style is more appropriate. For example, one company might want to work
53 with several partners, but not let each partner know about the others.
54 Note: In such a project, all artifacts should have restriction labels.
55 </div>
56 </div>
57 <input type="checkbox" name="only_owners_see_contributors" id="only_owners_see_ contributors"
58 [if-any only_owners_see_contributors]checked="checked"[end] >
59 <label for="only_owners_see_contributors">Only project owners may see the list of contributors.</label>
60 </div>
61
62 </div>
63
64
65 <h4>Activity notifications</h4>
66
67 <div class="section">
68 <p>Email notifications of issue tracker activity will automatically be sent to
69 the following email address.</p>
70
71 <table cellpadding="2">
72 <tr><th>All issue changes:</th>
73 <td><input type="email" name="issue_notify" size="35" value="[issue_notify ]"><br>
74 [if-any errors.issue_notify]
75 <div class="fielderror">[errors.issue_notify]</div>
76 [end]
77 </td>
78 </tr>
79 </table>
80 [# TODO: validate as address is entered ]
81
82 [include "../framework/admin-email-sender-part.ezt"]
83 </div>
84
85
86 <h4>Email reply processing</h4>
87
88 <div class="section">
89 <div class="closed">
90 <p>Users may add comments and make updates by replying to
91 certain notification emails.
92 <a class="ifClosed toggleHidden" style="font-size:90%; margin-left:.5em">Learn more</a></p>
93 <div class="ifOpened help">
94 Users may add comments to an issue
95 by replying to a notification email:
96
97 <ul>
98 <li>Look for a note in the footer of the email indicating that
99 a reply will be processed by the server.</li>
100 <li>Comments must be in replies to notification emails sent directly
101 to the member, not through a mailing list.</li>
102 <li>The reply must be <tt>From:</tt> the same email address to which
103 the notification was sent.</li>
104 <li>Project members who have permission to edit issues may make
105 changes via email replies.</li>
106 </ul>
107 </div>
108 </div>
109 <input type="checkbox" name="process_inbound_email" id="process_inbound_email"
110 [if-any process_inbound_email]checked="checked"[end] >
111 <label for="process_inbound_email">Process email replies</label>
112 </div>
113
114 <br>
115
116 <input type="submit" id="savechanges" name="btn" value="Save changes" class="s ubmit">
117 </form>
118
119 [include "../framework/footer-script.ezt"]
120
121 <script type="text/javascript" nonce="[nonce]">
122 runOnLoad(function() {
123 _onload();
124 });
125 </script>
126
127 [end]
128
129 [include "../framework/master-footer.ezt"]
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698