id	summary	reporter	owner	description	type	status	priority	component	severity	resolution	keywords	cc	release
9058	Let `TAGS_MODIFY` inherited `TAGS_VIEW` for more intuitive permissions	hasienda	hasienda	Sure, Trac core, i.e. wiki permissions have no inheritance as well, and there are some good reasons for a high degree of privilege separation.\r\n\r\nBut it doesn't make any sense to give a modify permission without view, does it? In fact, you can hardly do one without the other, so there's no point to try, if not for diminishing the "joy" of hacking a ton of privileges per group/user for each Trac application you have to administrate.\r\n\r\nSo I speak up in favor of a sensible inheritance like so:\r\n TAGS_VIEW remains just that: TAGS_VIEW\r\n TAGS_MODIFY gets extended to: TAGS_MODIFY + TAGS_VIEW\r\n\r\nI'll happily provide the patch or the changeset to accomplish this, if it is acceptable and receives at least two more positive votes from fellow developers. Thanks for consideration.	enhancement	assigned	low	TagsPlugin	normal		permission inheritance	doki_pen, mitar, rjollos, robguttman, otaku42	0.11
