Mendz.Library on GitHub - The Experience
Publishing source codes to GitHub is not that difficult. It took me a while to get the gist of it. In the end, the real saving grace is the decision to NOT use Visual Studio Team Services tools and to use GitHub Desktop instead.
Now, don't get me wrong. Visual Studio 2017 can be configured to work with GitHub. The confusing part though is that Visual Studio also tries to put Visual Studio Team Services front and center. One of the first mistakes I had was to actually use Visual Studio Team Services in the first place. Migrating out of it to switch to GitHub is not a smooth experience. In the end, I had to recreate my local repository to clean away any trace of Visual Studio Team Services in my projects.
Basically, if you plan to use GitHub, don't start by using Visual Studio Team Services first and then plan to migrate later. The experience is smoother if you just target GitHub itself from day 1.
GitHub Desktop provides a very simple experience to publishing codes to GitHub. It shows your change history and you can easily commit them to GitHub.
GitHub Desktop is so easy to use that it may be easy to overlook licensing. I think that it is one of the first things that you need to decide on before publishing to GitHub. For open source projects, the popular licenses with minimal restrictions are MIT and Apache. There are other licenses available to choose from as well. IMHO, reading and researching about them is important. Note that licensing is not required, though it doesn't hurt to have one even if you think you don't need it.
After publishing, GitHub online can be used to add files like LICENSE and README. GitHub can also be used to tag release versions.
Access the latest Mendz.Library codes at GitHub. The latest Mendz.Library binary can be downloaded from NuGet.
Now, don't get me wrong. Visual Studio 2017 can be configured to work with GitHub. The confusing part though is that Visual Studio also tries to put Visual Studio Team Services front and center. One of the first mistakes I had was to actually use Visual Studio Team Services in the first place. Migrating out of it to switch to GitHub is not a smooth experience. In the end, I had to recreate my local repository to clean away any trace of Visual Studio Team Services in my projects.
Basically, if you plan to use GitHub, don't start by using Visual Studio Team Services first and then plan to migrate later. The experience is smoother if you just target GitHub itself from day 1.
GitHub Desktop provides a very simple experience to publishing codes to GitHub. It shows your change history and you can easily commit them to GitHub.
GitHub Desktop is so easy to use that it may be easy to overlook licensing. I think that it is one of the first things that you need to decide on before publishing to GitHub. For open source projects, the popular licenses with minimal restrictions are MIT and Apache. There are other licenses available to choose from as well. IMHO, reading and researching about them is important. Note that licensing is not required, though it doesn't hurt to have one even if you think you don't need it.
After publishing, GitHub online can be used to add files like LICENSE and README. GitHub can also be used to tag release versions.
Access the latest Mendz.Library codes at GitHub. The latest Mendz.Library binary can be downloaded from NuGet.
Comments
Post a Comment