Yes, correct. Jeremy

Check it out: "You acknowledge and agree that other users of the Service may create a restricted membership group requiring acknowledgement of additional terms to participate in such restricted

In other words, it's not an advantage because every change made to any one of those features would have to take the GG requirements into account, over and over again. And there are going to be

Not yet, as far as I can see. I think we're going to have to agree to disagree on this. I think they are a special, but not unique, case (with groups potentially having a similar case, for things that

I disagree, because every change would still have to bend itself to fit the unique requirements of the Group Guidelines, namely: always visible on the home page; mailed out periodically to members

If I'm understanding correctly, you'd like to have a page similar to https://groups.io/topics, but at the messages level rather than topics level? I can see where that could be handy in saving some

That's a change desirable on its own merits. Jeremy

A case of your mileage varying... If that's the way you want it, not for me to criticise Yes, I agree up to a point. The big miss is lack of an overview messages page. Also that it can take multiple

Thanks, no trouble. I think we all want a better service... This about a logical concept - how things are perceived - rather than things are: the advantage provided is what to my mind is a better way

Also don't forget that the (possible) existence of group guidelines to which group members must adhere is now legally embedded in the TOU. I really think they're unique. They're not a wiki page.

And then you, or someone, would have another desirable change for the "member notice" feature. And then yet another desirable change for yet another feature of your design...it could go on and on for

Haha. I thought you were going to say my approach was a *smaller* number - namely, ONE - single-purpose thing and yours a *larger* number of multi-purpose things. I also don't think my approach will

Something else which occurred to me, another change desirable for individual wiki pages is the ability to suppress or individualize footer and sidebar (even if there is no standard one), as well as

Yes, all could be done (and controlled) that way. But that doesn't seem to be the way we're proceeding, for better or worse. All three are desirable, separately: (2) is what this topic started with,

I'm pretty sure all of these are handled by my idea to create a separate Group Guidelines entity that's entered and maintained in the Settings page. The rest of this sounds overly complicated. --

This crossed with my previous message (slow typing!) My thoughts on member notices: They should be able to be sent automatically (triggered by some event), on schedule (driven by calendar or

This would be possible with my idea that they be entered as a separate entity in the settings page. It would be visible to owners/mods there (I doubt you'll get granularity between owners and mods,

Mark Thanks. My preference would still be for a second wiki (set of pages) for this sort of purpose, but yes, having a designated one is a good approach (but will there be the possibility of multiple

I'm thinking in spurts. Another checkbox could be "send to direct-add members", per Shal's request that only a separate, direct-add message (entered through the member notices page) be sent to those

It could be entered in the Settings page, with yes/no checkbox options ("send to all new members", "include in tab", "include as member notice") but there would be only one place to enter and maintain