odoylerules Posted July 4, 2014 Report Share Posted July 4, 2014 (edited) All, Recently I moved from SVN to GIT as my source control and revision manager. I'm still getting used to everything so i don't consider myself an expert yet, but i really missed the Project Provider options that I used for SVN source control within the project window. I'm releasing an open source beta project provider for TortoiseGit Integration. This addon is very similar to the current SVN options but was developed entirely from scratch. Currently this provider requires TortoiseGit to perform most of the Source Control Actions. I know a lot of you on here have recently switched to sourcetree, however, unlike TortoiseGit they do not currently offer a command line interface yet for windows that i could find. I've tried to make this project flexibile and if they offer a command line for windows eventually it should be fairly quick to re-factor for that. The project can be found here: https://bitbucket.org/jed_d/lv_tortoisegit Addon Features Tortoise Git Icon Overlays within Labview IDE Tortoise Git Commands from within Labview IDE Ability to directly reload a project from within the Project Window, as well as prompts to reload the project when performing actions that require a reload. Open Git Bash from project window I'm hoping some of you will have a chance to try this out and let me know of any issues. I would like to track issues on bitbucket if possible so that they are all in one place, but i will also be checking these post for issues as well. Feel free to fork the project and hack on it yourself. If you come up with something decent and don't mind sharing, send a pull request. One initial issues i'm hoping the community can help with is building the package for older versions of LV. Currently i only have access to 2013 so i am only able to build the package for this version. If anyone has a change to pull down the repo and build it for older versions please do. Another question i have for the community is the license i currently have on the project. This is my first open source project of any kind so i wasn't sure what license to put on it. I did not want to be too restrictive so i went with a BSD license. If any of you see an issue with this please let me know as I'm open to suggestions. Edited July 4, 2014 by odoylerules Quote Link to comment
happyarrow Posted July 5, 2014 Report Share Posted July 5, 2014 nice， ,It will be useful for people that use Tortoise git. Quote Link to comment
Rolf Kalbermatter Posted July 9, 2014 Report Share Posted July 9, 2014 Another question i have for the community is the license i currently have on the project. This is my first open source project of any kind so i wasn't sure what license to put on it. I did not want to be too restrictive so i went with a BSD license. If any of you see an issue with this please let me know as I'm open to suggestions. BSD is a very permissive license and as such should not pose any problems. In fact the Open Source license usually only really matters for reuse libraries. This being a tool it is of less concern, even GPL (with a small exclusion clause that the SW may also be used within the closed source LabVIEW application) would work as all it disallows is to use the SW library for derivative works without releasing the entire source code of said derivative work. As a plugin for LabVIEW with aformentioned exclusion clause there is not really much you would take away from potential tinkerers with your tool/plugin. That said I usually use nowadays BSD for anything I want to make available as Open Source since it is the most simple license IMO. GPL and LGPL are about umtien pages of text now, that even lawyers disagree about what it all means 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.