It is okay to release a F/OSS project where the expected set of users is you.

It is okay to declare that a F/OSS project that you maintain is feature complete and stop.

It is okay to stop writing new code in a F/OSS project and just review patches from other people.

It is okay to stop reviewing patches once other people are familiar enough with the codebase to do so.

It is okay to admit that a F/OSS project that you created has so much technical debt that people would be better off reimplementing it than depending on it (especially if you write down the lessons that they should learn).

It is okay if your F/OSS project doesn't meet the requirements of some potential group of users, as long as no one applies pressure to force them to adopt it.

It is okay to tell a company that depends on your F/OSS project that it's unsupported and they can pay developers to contribute if they really need it.

It's okay to say 'I created this F/OSS project to meet my personal needs, but someone else made something that meets those needs better and so I'll use theirs instead'.

It's okay to say 'I made this F/OSS project as an experiment, and the result was that I learned that this approach is a bad idea'.

Submissions are still open!

If you've been sitting on a bug, technique, war story, weird research rabbit hole, or beautifully cursed idea: now is the time.

Write something worth archiving.

Phrack CFP closes June 30.

More details on how to submit at https://phrack.org/news

By Alariko

#Art #DigitalArt

Childhood Computing: https://susam.net/childhood-computing.html

#blog #post #programming #technology

Remember when we used to dial into the internet, and the machines would scream at us?

That was a warning right?