No, you are saying that you are entitled to an developers code if they leave a project just because they let you test it. You are acting/being entitled as fuck.
Engywuck ( @Engywuck@lemm.ee ) True… It amazes me when people become so entitled online, especially in the FOSS community. It looks like they think devs owe them something.
jarfil ( @jarfil@beehaw.org ) They got free testing for the promise of releasing the source, then failed to fulfill that promise, so… yeah, they do owe those people something.
@Scary_le_Poo and @jarfil: if the two of you have a disagreement on another thread, please work it out between the two of you like adults there; don’t spill it over into other, unrelated threads.
@Scary_le_Poo, these types of personal attacks are not acceptable on beehaw. It is possible to disagree while still being kind and without resorting to angry or abusive language. Please try to remember beehaw’s guiding principal when interacting with others in the future.
You are saying that getting people to do work for you by promising them something in return, means nothing, that you can break that promise whenever you want.
No, I’m a foss dev, and I speak for all of us when I ask you to please not join any of our communities.
Also I’m calling you out. You need to put up or shut up evidence of where that developer said that he would release his code as open source. And that he would do it in return for you testing it.
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.
I’ve nothing to say more on topic. Off topic, people may be quite different and even if objectively there should be nothing bad in releasing pre-production, they may find it sensitive + there might be someone to actively offend for that. I only encountered the former, luckily
No, you are saying that you are entitled to an developers code if they leave a project just because they let you test it. You are acting/being entitled as fuck.
Yeah, that’s not how any of this works.
@Scary_le_Poo and @jarfil: if the two of you have a disagreement on another thread, please work it out between the two of you like adults there; don’t spill it over into other, unrelated threads.
@Scary_le_Poo, these types of personal attacks are not acceptable on beehaw. It is possible to disagree while still being kind and without resorting to angry or abusive language. Please try to remember beehaw’s guiding principal when interacting with others in the future.
We didn’t have any interaction in the other thread, I only mentioned it because I saw a similarity between the topics. Guess I struck a nerve.
How is me calling him entitled as fuck a personal attack? Would you rather I said “you are being/acting entitled as fuck”? I can do that…
You are saying that getting people to do work for you by promising them something in return, means nothing, that you can break that promise whenever you want.
That’s what a scammer would say.
No, I’m a foss dev, and I speak for all of us when I ask you to please not join any of our communities.
Also I’m calling you out. You need to put up or shut up evidence of where that developer said that he would release his code as open source. And that he would do it in return for you testing it.
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.
I’ve nothing to say more on topic. Off topic, people may be quite different and even if objectively there should be nothing bad in releasing pre-production, they may find it sensitive + there might be someone to actively offend for that. I only encountered the former, luckily