See #69556: move "cvs access" tab into project, make it generic for background. Once that lands, we need a patch to rip out the "CVS access" code entirely, and convert this stuff to use the new project maintainers form and related code (e.g. hook_project_permission_info()).

Comments

dww’s picture

Assigned: Unassigned » dww
Status: Active » Needs review
StatusFileSize
new12.53 KB

This 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.

dww’s picture

Over 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

sun’s picture

Comparing 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.

dww’s picture

Bojhan agrees with "Write to CVS", too. Here's the patch and interdiff.

dww’s picture

Status: Needs review » Fixed

Committed, merged into bzr, deployed on d.o. DB updates ran without error. Hurray!

Automatically closed -- issue fixed for 2 weeks with no activity.