Skip to content
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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

glensc
Copy link

@glensc glensc commented Dec 7, 2015

used by cdnjs cdnjs/cdnjs#6418
but could be useful otherwise as well.

ps: once merged, please tag v1.3 in github!

@danimesq
Copy link

Hi, @glensc
I've forked TipTip to maintain it and use in all web projects of my community.
Please clone your pull request to: https://github.com/Software-js/TipTip
Thanks!

@glensc
Copy link
Author

glensc commented Apr 11, 2016

you can do all that yourself!

    1. you can merge this from commandline:
git remote add glensc https://github.com/glensc/jquery.tiptip.git
git fetch glensc
git merge glensc/package.json --no-ff

@glensc
Copy link
Author

glensc commented Apr 11, 2016

and instead of forking, did you try to reach @drewwilson and ask to transfer ownership to you?

@danimesq
Copy link

I prefer the first option of the first reply. Good idea, I wasn't thinked about.
About second reply, I prefer forking instead of get ownership of a thing I isn't created, then I prefer forking.
Thanks to contributions and ideas!

@danimesq
Copy link

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!"
Can be more clear about how do this?

@glensc
Copy link
Author

glensc commented Apr 12, 2016

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!)

@danimesq
Copy link

@glensc
Merged in: Floflis#3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants