On Wed, May 30, 2007 at 01:02:08PM -0400, Sandy wrote: > Patrick R. Michaud wrote: > > Option 3: Introduce a new SiteAdmin group that contains pages > > specifically intended for the site administrator. This group could > > have a read password that limits viewing to the admin by default, and > > the pages listed in option 2 would move to this new group. > > > > The downside of this approach is that it complicates upgrading a bit > > in terms of moving existing Site.* pages to the new Site group, as > > well as introducing a new group to the distribution. > > I vote for 3, for reasons already expressed by others. No more listing > which pages to unlock/lock, just say "the entire group". Most of the > teething pains would be undoing existing work-arounds.
I think I'm pretty well convinced that option 3 is the way to go, and that we should go ahead and make the switch as part of 2.2.0-beta and not wait for another major revision. I'll outline the details of my proposal in a followup message. > Create two new groups rather than one new and one existing. Add checking > code so page cannot exist in both. Old Site Group keeps existing > permissions, and admins will be able to move pages out one at a time. > [...] While this is a good idea, I think there are too many Site.* pages (provided by recipes and the like) to make it work. And Site.* seems like the right name for the group, so I think we should keep it. I'm guessing that we'll just say that the migrating pages (there are only six of them) all have to be in the Site-Admin.* group, or if the wiki administrator wants to keep them in Site they set the value of $SiteAdmin to 'Site'. More in a bit, and thanks! Pm _______________________________________________ pmwiki-users mailing list [email protected] http://www.pmichaud.com/mailman/listinfo/pmwiki-users
