how to upload scripts

[extioStorm]

i have a few scripts i made that would be useful to people,

but i dont have them packaged in installers or anything. can someone upload them for me?
these files may not stay forever where i have them uploaded so it would be great if someone posted them. they could even take credit for sharing them.

also, github confuses me or i would figure it out myself.
the nicktracker is highly effecient brilliant work. texteffects are just for fun, and nicktools are just some aliases and auto-ghost and auto-away, auto identify type things.

scripts are as follows with instructions in post:

http://www.jroisocial.com/file/view/18558/extios-texteffects-92-script

http://www.jroisocial.com/file/view/24120/extios-nicktracker-for-kvirc-version-56

http://www.jroisocial.com/file/view/24587/extios-nicktools-32-for-kvirc

(menu add on if you have other scripts http://www.jroisocial.com/file/view/48389/extios-exscripts-menu-v11 )

( incomplete script http://www.jroisocial.com/file/view/46168/extios-soundscript-version-08 )

[un1versal]

First of all, thank you, I haven't looked at your work but the fact youre sharing them is good news.

You dont upload them per say, you make pull requests for that you need to fork the repo and start from there.

I suggest you start at https://github.com/kvirc/KVIrc/wiki/Contributing-code-to-KVIrc's-repository

If you know how to use a web-browser you can do a great deal via that, There is some learning curve but nothing huge.

As for your scripts where they are, you could make gists -> https://gist.github.com/ the files are hosted in plain text in your GitHub account again this is fully via web-browser and you can then sahre those links.

When I have some time Ill look not today or maybe not even tomorrow,, but if youre worried about scripts being lost, I suggest Gist..

As for credits, not a problem theres ways around that too.

[un1versal]

@extioStorm I had a look at your scripts, and that seems to me like its intended to be a whole rather than separate scripts, seems that you still have a bit to do here.
Im not sure someone who doesnt fully understand how these things go together (as they are very complex) would be the ideal person to just wack them in repo without any instructions readme to the users etc.. we wouldnt be doing anyone any favors by just committing them in as is.

You have a good opportunity here to clean them up and organize them add some documentation and learn how to make a pull request (I see you already forked the repository) and submit these yourself.

For assistance with anything (git related etc.), just pop into #KvIrc on freenode and dont hesitate to ask any questions you may have.
on

[extioStorm]

wow i didnt even know that i created a fork! that was not intended.

[un1versal]

Its absolutely fine to fork the project its encouraged even as outlined in https://github.com/kvirc/KVIrc/wiki/Contributing-code-to-KVIrc's-repository.

Without it you wont be able to make a pull request for your scripts/addon whatever.

[extioStorm]

i polished and tried to request the new version be merged. hopefully its in better shape and should be now.

[extioStorm]

I intend to upload my other scripts, but im trying to decide if i should do them all as one multi-file commit, pick and choose script in the commit, or as separate commits. My other scripts are more useful, powerful, and helpful than the first game i put up. also, should i close this issue?

[un1versal]

You can close issue if you like, but keep it until youre done it doesnt hurt.

To make things easier to review, please make one commit per script (each pull request only for one script)

Please make sure it has readmes (its nicer for users that dont know or want to go dig in source to read what it is or what it does.

also the other you contributed should at least hold some uninstaller, since your scripts are massive, asking anyone to keep tabs on what you installed is not quite the way to go about these things.

Thx

[un1versal]

If you look at https://github.com/kvirc/kvirc-scripts/tree/master/BelovedInDistress you will see the README.md

I fixed a couple of typos and took the liberty to make it GitHub Markdown friendly