It's Allgood, Serra @jump_spider@qoto.org

@dsfgs
Wow, that sounds pretty amazing! Might have to track that down, see how it handles security

@dsfgs
Informatics, conlangs...tbh, right now my focus is on Elm and starting up a blog

@dsfgs @witchescauldron
If y'all aren't already using it, I recommend the gitch-soc fork of Mastodon; it includes easy to adjust environment variables for char limit of toots and bios, as well as the data fields users can add to their profiles. Plus, it allows for writing with Markdown or raw HTML

Learned from Sandi Metz, and the specific arrangement of letters from a former coworker;

HECL (pronounced like heckle) - A better version of SOLID

Highly Cohesive - An object's lifecycle, responsibilities, and API should all fit well together and make practical sense

Easily Composable - A complex organization of objects should be easily made from smaller, independent objects

Context Independent - An object should not be overly specialized and capable of being used in multiple contexts

Loosely Coupled - When an object depends on another, it should "know" as little as possible about the dependency, and ideally the dependency should be injected as an initializing attribute

@Shamar @khird
I think I've reached a final version, per the Discourse thread.

# Description of this document

This document outlines specific political goals and intentions for this project. This file is a living document and is expected and encouraged to change over time; changes will be included in the CHANGELOG.

## Social goals of react-useintersection

The `IntersectionObserver` api is a powerful JavaScript construct. The author of this package intends for it to help facilitate:

1. **Accessible UX design:** Programmatically determining the intersection of nodes with the screen gives powerful flexibility to control styling and layout.

2. **Wider understanding of advanced JavaScript apis:** The `IntersectionObserver` api is but one of several Observer apis in JavaScript, most of which are in the author's opinion relatively unknown to the average programmer because there is a lack of high level packages for them in frameworks such as React.

3. **Demonstrable testing practices for React outside of the Jest ecosystem:** Jest is a powerful testing framework; however, in the author's opinion, it is worthwhile to be familiar with more than one tool, as every tool is "more than a hammer." In specific, Jest is ideally suited for large projects, and is arguably overkill for small components such as `react-useintersection`.

@khird
Well, as @ Shamar clarified, users benefit from reading to understand what the current intent of the project is. For instance, I've been thinking about starting a toy project for Elm, involving generating a yaml for installing and configuring arbitrary tools, but I'm going to limit the scope to asdf and n for language managers. That will be something I include in POLITICS.txt, so users can know upfront that I don't currently intend to support rvm, for example

@khird @Shamar
Good point re: why it should matter to anyone else. I posted this in the Discourse thread, but how does this read?

# Description of this document

The creation and distribution of software do not exist in a vacuum. As such, this document outlines specific and quantifiable political goals for this project. This file is a living document and is expected and encouraged to change over time; changes will be included in the CHANGELOG, though are not suggested to trigger a version bump if using semantic versioning.

## Social goals of react-useintersection

The `IntersectionObserver` api is a powerful JavaScript construct. The author of this package intends for it to help facilitate:

1. **Accessible UX design:** Programmatically determing the intersection of nodes with the screen gives powerful flexibility to control styling and layout.

2. **Wider understanding of advanced JavaScript apis by helping them be more easily used in the React framework:** The `IntersectionObserver` api is but one of several Observer apis in JavaScript, most of which are in the author's opinion relatively unknown to the average programmer because there is a lack of high level packages for them in frameworks such as React.

@mngrif Big trans femme energy in this

@Shamar
Ahh, so I should save the *prescriptive* arguments for their own separate pieces, the point of POLITICS.txt is to be purely descriptive?
@freemo

@rodolpho I got contacted by an internal recruiter for a company in this space, and boy howdy, did I stand on my soap box for him

Soliciting feedback on a boilerplate template for a POLITICS file for free software projects

cc: @Shamar

https://discourse.qoto.org/t/boilerplate-template-for-politics-md/87?u=jump_spider

> From now on, all of my Free Software projects will contain a new file alongside with LICENSE.txt and README.txt: POLITICS.txt

~ http://www.tesio.it/2019/06/03/what-is-informatics.html

@Shamar really knocks out the quotables in this piece