3 ms·
This is the third time in a week an uninformative link has been posted to HN, without any comment from the forking community. Can we consider this a dupe? Pre
by doublerebel 12y ago
This is the third time in a week an uninformative link has been posted to HN, without any comment from the forking community. Can we consider this a dupe?
Previous:
https://news.ycombinator.com/item?id=8694953 https://news.ycombinator.com/item?id=8694953 (Link to the repo)
https://news.ycombinator.com/item?id=8669557 https://news.ycombinator.com/item?id=8669557 (Another link to the repo)
At this point I'm just getting frustrated because I should be able to learn about important open-source issues from the community, not from a Wired article and not hidden in some secretive organization and private repo. Airing frustrations through Wired is only bad for the community -- the headline is nothing but FUD:
"Future of Popular Coding Tool In Doubt After Public Split" -- Can you imagine selling your CEO on Node when articles like this are being written?? Someone on HN posted this [1] recently, and I think it's very appropriate -- I believe this confusion could have been avoided:
> If, after careful consideration, you still conclude that you must fork, line up support privately first, then announce the fork in a non-hostile tone. Even if you are angry at, or disappointed with, the current maintainers, don't say that in the message. Just dispassionately state what led you to the decision to fork, and that you mean no ill will toward the project from which you're forking. Assuming that you do consider it a fork (as opposed to an emergency preservation of the original project), emphasize that you're forking the code and not the name, and choose a name that does not conflict with the project's name. You can use a name that contains or refers to the original name, as long as it does not open the door to identity confusion. Of course it's fine to explain prominently on the fork's home page that it descends from the original program, and even that it hopes to supplant it. Just don't make users' lives harder by forcing them to untangle an identity dispute.
[1] http://producingoss.com/en/forks.html http://producingoss.com/en/forks.html