Notices by phryk 🏴 (phryk@mastodon.social), page 3

@alcinnz

I think* for smaller projects it's totally fine to have a custom CoC that grows with the actual needs of the community – just make it clear that you're open to proposals for new extensions from prospective contributors.

*: personal view, not evaluated in practice

@alcinnz

Another thing is what I always brought up when the hackerspace was discussing CoCs:

No matter what CoC you adopt, it's worthless if you don't have an awareness team – potentially even worse, because people will *think* the space is safe for them when it's not.

You *have* to have some sort of contact point and procedure for when the CoC is violated and I think it's this rather than just the bare fact of having a CoC where most projects fail.

@alcinnz Do you already have contributors?

If so, I think an in-depth discussion with them might be in order. Maybe with some candidates to refer to.

I've thought about this a bit over the years, too – but I never came to a satisfactory conclusion.

Most of the commonly used CoCs feel like they're more about corporate ass-covery than about fostering a healthy community.

I was playing with the thought of using only prepared statements in order to forego using a full ORM, but I really, really want the easy query composability I get with ORMs like peewee.

Being able to pass around a query object where you can easily add extra pieces to the WHERE clause, add JOINs and things like that is just so damn handy. :F

Currently writing an object-oriented SQL query constructor because apparently I've opted to write everything myself.

But I also opted to use #PostGIS to make it easy to build in powerful spatial analysis tools.