License

[Tomo Krajina]

Nodir, I think you should decide about the license of git-tf -- add a LICENSE.txt and mention it in the documentation.

I suppose it is open source now, but don't know exactly the license it uses. I know of people who don't want to contribute to projects if they don't know the license. Also, there are companies with strict rules for application they can use in development -- depending on the license.

It is better if you do it now than later because -- if you have contributions from many people -- you will have to ask them all if they are OK with the chosen license. 

Cheers,

tk

PS. My choice for my opensource projects if the Apache2.0 license. It is a widely used business-friendly liberal open source license. 

[Nodir Turakulov]

Licensing was always obscure to me, that's why I didn't license git-tf
and I didn't want to spend time learning the difference among
licenses.

I read about Apache 2.0 license here
http://www.apache.org/foundation/license-faq.html#License
Seems the right license to use. Thanks for the advice.

Another thing that I procrastinate is versioning...

-Nodir