The promise I’m referring to, is to “release the code”.
(long version)
I understand the thought process of people not wanting to show how messy their pre-production code is… but that’s why, following semver rules, you mark it as a version “0.x.y”. It’s not an exam, it’s nothing to be ashamed of, anyone who’s written code knows that’s how things work, and it’s on the community to be understanding of this, so the “initial dev” of an open source project should feel confident in releasing a tangled mess, no less no more.
Promising the code, then disappearing without giving a community that’s invested in the project a chance to take over, is what I find fishy.
Sure, I’ll write your name down in the black book. What’s your GitHub nick, or wherever you keep your stuff?
From the article:
https://wedistribute.org/2023/12/artemis-shuts-down/
Implying the code was supposed to get released. You may want to ask the article’s author about where they got that out.
I’m mostly with you but “didn’t want to release prematurely” is not a promise, as you can never know when one sees code as matured.
The promise I’m referring to, is to “release the code”.
(long version)
I understand the thought process of people not wanting to show how messy their pre-production code is… but that’s why, following semver rules, you mark it as a version “0.x.y”. It’s not an exam, it’s nothing to be ashamed of, anyone who’s written code knows that’s how things work, and it’s on the community to be understanding of this, so the “initial dev” of an open source project should feel confident in releasing a tangled mess, no less no more.
Promising the code, then disappearing without giving a community that’s invested in the project a chance to take over, is what I find fishy.