-
Notifications
You must be signed in to change notification settings - Fork 29.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
may be it's good idea go tell something about this fork? #74
Comments
iojs.org has them, we should probably add this to readme. cc @Fishrock123 |
It is mentioned inital release will be on Jan 13. What is the version? 1.0 or 0.12 or others like 1.0.0-beta? thanks |
Indeed. I'll add some bits to the site, and make a PR for the readme. |
I saw Mikeal mentioned such things via #28 |
Why nobody use GitHub fork button? |
Because there is a bunch of things that GitHub disables on a fork, I presume they don't want that to happen. |
I think you can (re)enable a lot. Just using "Settings". |
"However, to ensure better relevancy, repository forks will not be searchable unless the fork has more stars than the parent repository." (link) It's not the reason, but github treats forks like second-class citizens, like they are used for PR only. And because of that, they indeed are. |
Can we close it? |
I think so. If it's still an issue, move it to the website repo. |
A colleague just pointed me to this fork saying
Node v0.12
but I can't find any information about it. Would be great to know more details.The text was updated successfully, but these errors were encountered: