Mark C. Miller

> I don't want to rehash a whole conversation, but what's the use case of this table in the context of _search_? I don't think it is so much about...

BTW...the upshot of the search discussion is that @bartlettroscoe and I (and @pagrubel if she is still interested) will research and create some example URLs of searching (and sorting results)...

> I'd really like to _discourage_ that approach. I feel entirely the opposite. I don't see value in expending my time or others in reinventing the wheel here. Who could...

> this is a stopgap against any issues with search. Ok, apologies...I think my remark above is misleading. I was thinking in the context of bssw-editorial activities and not users/site-visiters....

One advantage is separating these repos is that we separate content related dialog and development from site-admin related dialog and development. A downside could be breaking some of the kinds...

> 3\. Having multiple repos would allow different privacy settings. Right, I was thinking the *bssw-content-contributions* repo would be public but, in theory, the actual site repo could be private....

> Can't anyone submit issues and PR's now? Yes, and anything a *submitter* doesn't do precisely correctly we either have to catch as reviewers and force them to fix (or...

> It means we have a clear delineation of site-admin and publication relatd work and content development related work. As @bernhold indicates, we *can* probably achieve this same goal with...

I made the mistake of direct commits to main on a handful of occasions. So, I would welcome a branch protection here.

> We have wanted for some time to discourage direct commits, but I think the ability to bypass reviews is important too. I think you can set it up so...