-
Notifications
You must be signed in to change notification settings - Fork 70
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
add npm package.json #23
base: master
Are you sure you want to change the base?
Conversation
Hi, @glensc |
you can do all that yourself!
|
and instead of forking, did you try to reach @drewwilson and ask to transfer ownership to you? |
I prefer the first option of the first reply. Good idea, I wasn't thinked about. |
I'm thinking now, get ownership is an good idea for pull requests come direct to me for approve. I will contribute more with and think about. Thanks ;) "ps: once merged, please tag v1.3 in github!" |
seems you're new to this, it's not really about "preference" or "not preferring" thing. well. the original author does not go anywhere, he's still in copyright blocks and readme. please talk to him, then don't need to transfer tickets, have several forks around and nobody knows which one is the right one! also, there's second option too, he can add you as collabrator (multiple developers) so the url stays as is. altho if original author is absolutely not interested anymore of this product, the transfer is better option, he'll get free of the burden as well :) and if you go with "transfer" option, then the old urls keep working (github will redirect) and internet will not be broken because old links used elsewhere will keep working, including git remote urls! as for github release, it's just git tag which you push (google here!) |
used by cdnjs cdnjs/cdnjs#6418
but could be useful otherwise as well.
ps: once merged, please tag v1.3 in github!