Closed (fixed)
Project:
CVS integration
Version:
6.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
12 Aug 2010 at 02:22 UTC
Updated:
3 Jan 2014 at 01:42 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
dwwThis should be everything we need. Might be worth adding some tests for this, too, but cvs.module is a dying beast, so I'm not sure it's worth the effort.
Comment #2
dwwOver at #69556-7: move "cvs access" tab into project, make it generic I originally proposed this permission should be called "Write to CVS". Then at #69556-9: move "cvs access" tab into project, make it generic I switched it to "Administer CVS" as I wrote "for consistency". Now that's considered a UI bug. ;) Heh.
So, should we just move it back to "Write to CVS"? I think that's better than "Access CVS" since anyone still has read-only access. This is specifically about controlling write access, so "write" should be in the name. "CVS write access" also works (although it's a bit longer).
Thoughts?
Thanks,
-Derek
Comment #3
sunComparing both, then
- "Write to CVS" works as "action label"
- "CVS write access" works as noun
So, yes, either of both. But which of both ultimately depends on the other permission titles.
Comment #4
dwwBojhan agrees with "Write to CVS", too. Here's the patch and interdiff.
Comment #5
dwwCommitted, merged into bzr, deployed on d.o. DB updates ran without error. Hurray!