4 ms·

Read into this more, here http://www.cpaptalk.com/viewtopic/t174687/SleepyHead-Project-Takeover-Attempt-by-AB.html http://www.cpaptalk.com/viewtopic/t174687/Sle

Read into this more, here http://www.cpaptalk.com/viewtopic/t174687/SleepyHead-Project-Takeover-Attempt-by-AB.html http://www.cpaptalk.com/viewtopic/t174687/SleepyHead-Project... and here http://www.apneaboard.com/forums/Thread-SleepyHead-version-1-1-Release-plus-odd-posts-by-JediMark?pid=284578#pid284578 http://www.apneaboard.com/forums/Thread-SleepyHead-version-1... Its not as black and white as it seems

Scaevolus 8y ago
It doesn't look like the project was ever that collaborative, so I'm filing this under the classic "primary developer dislikes the overhead of accepting patches, occasionally loses interest": https://gitlab.com/sleepyhead/sleepyhead-code/graphs/master https://gitlab.com/sleepyhead/sleepyhead-code/graphs/master I've fallen into that pattern myself, and seen my code forked and extended by those that were still interested. The thing that stung was them erasing all the commit history giving me attribution!
lima 8y ago
Well, they should've called their fork something other than "SleepyHead". From what I could gather from these threads: - Maintainer disappeared for a while, people wanted their fixes merged. - ApneaBoard community made a "1.1.0" release of "SleepyHead" without the author's approval, rather than forking it and calling it something else. - Maintainer unhappy about them using his trademark without his permission.
- treis 8y ago
  >ApneaBoard community made a "1.1.0" release of "SleepyHead" without the author's approval, rather than forking it and calling it something else So Mark says. The ApneaBoard folks say that it was released by Mark's chosen right hand man. As far as I can tell the ApneaBoard folks have yet to release their own version or fork the code. They seem to be organizing to do just that which is what set Mark off.
- Tomte 8y ago
  As far as I read so far, AB did not fork the program. They mirrored the original binary. With the original donation links to the original owner. It's a mess.
_coveredInBees 8y ago
Yup, this was an interesting read as well - http://www.apneaboard.com/forums/Thread-SleepyHead-version-1-1-Release-plus-odd-posts-by-JediMark?pid=284578#pid284578 http://www.apneaboard.com/forums/Thread-SleepyHead-version-1... I respect all the work and dedication it took him to build what he did, but from the reading I've done on the forums, it does appear that he is the primary source of all this drama. There really isn't any competing interests, and no big corporate takeover.
FussyZeus 8y ago
Seems like this dude has made himself in his mind the one and only last-word in the entire project, which is fine, but then if you're going to vanish for months at a time, you need to have someone else available to watch over things. He doesn't seem to be willing to cede ANY control to someone, but also needs to take several months off the project at a time. Neither of these are inherently bad but you can't have it both ways.
deleted 8y ago
[deleted]

Scaevolus 8y ago

It doesn't look like the project was ever that collaborative, so I'm filing this under the classic "primary developer dislikes the overhead of accepting patches, occasionally loses interest": https://gitlab.com/sleepyhead/sleepyhead-code/graphs/master https://gitlab.com/sleepyhead/sleepyhead-code/graphs/master I've fallen into that pattern myself, and seen my code forked and extended by those that were still interested. The thing that stung was them erasing all the commit history giving me attribution!

lima 8y ago

Well, they should've called their fork something other than "SleepyHead". From what I could gather from these threads: - Maintainer disappeared for a while, people wanted their fixes merged. - ApneaBoard community made a "1.1.0" release of "SleepyHead" without the author's approval, rather than forking it and calling it something else. - Maintainer unhappy about them using his trademark without his permission.

treis 8y ago
>ApneaBoard community made a "1.1.0" release of "SleepyHead" without the author's approval, rather than forking it and calling it something else So Mark says. The ApneaBoard folks say that it was released by Mark's chosen right hand man. As far as I can tell the ApneaBoard folks have yet to release their own version or fork the code. They seem to be organizing to do just that which is what set Mark off.
Tomte 8y ago
As far as I read so far, AB did not fork the program. They mirrored the original binary. With the original donation links to the original owner. It's a mess.

_coveredInBees 8y ago

Yup, this was an interesting read as well - http://www.apneaboard.com/forums/Thread-SleepyHead-version-1-1-Release-plus-odd-posts-by-JediMark?pid=284578#pid284578 http://www.apneaboard.com/forums/Thread-SleepyHead-version-1... I respect all the work and dedication it took him to build what he did, but from the reading I've done on the forums, it does appear that he is the primary source of all this drama. There really isn't any competing interests, and no big corporate takeover.

FussyZeus 8y ago

Seems like this dude has made himself in his mind the one and only last-word in the entire project, which is fine, but then if you're going to vanish for months at a time, you need to have someone else available to watch over things. He doesn't seem to be willing to cede ANY control to someone, but also needs to take several months off the project at a time. Neither of these are inherently bad but you can't have it both ways.

deleted 8y ago

[deleted]