Hi,
I created a new contrib called Views UI permissions. It lets you restrict access to users with the restricted views permissions to edit certain fields in the views interface. It creates a new views admin page (this was the easiest way to get rid of all other views operations) where people can edit existing views (not default views!). Administrators choose which fields(ets) are editable.
Simple use case: Sometimes I don't want my (mostly non-technical) clients to have full control over views. However, editing the title, or header text or other simple operations can be interesting to give them access to. This is why I built this module.
Currently, it supports views 1 (Drupal 5) and is stable enough. Before I roll out an official release and start working on views 2, I would like to hear your opinions and/or patches - use the issue queue please for bugs and patches.
Some feedback I'm looking for:
- Security: Did I cover everything in making sure fields are not accessable or other acces control issues
- Minor problem: I'm having troubles getting 2 local tasks at the top when editing a view from admin/build/views_ui_perm so at this point I left them out. They work great when you are looking at the view directly. I don't consider it as a major block for an official release but it would be nice if I could find it though.
- Code quality (besides coder, it passes now heh).
- Anything else
The project page can be found at http://drupal.org/project/views_ui_perm. I made some commits today (3 september), so a cvs checkout from the DRUPAL-5 branch is the best option if you want to test the latest version.
Note: permission to create a new view is out of the scope of this module, so I happily will mark that won't fix :)

Comments
Drupal 6 development started
Hi,
development for a drupal 6 version supporting views 2 has started. It's in a real early state, so do not expect wonders from it right now. Anyone willing to help along, test and or submit patches, feel free to go nuts!