So let me be a little more specific about this project.
Without the availability of these projects I could not have achieved so much in so little time and it has convinced me that if we can foster a stronger open source approach in the LabVIEW community we can achieve better things and faster than we already do. This might be through additional libraries like openg or the JSON project on the LAVA code repository or additional tools like the LabVIEW Task Manager or VI package manager (I realise this isn't open source but it demonstrates that we don't have to depend on NI for tools if we take the initiative).
Out of this I want to start this project (tentatively "Open Source LabVIEW" but we will probably need to come up with a name that doesn't have a trademark!) to raise awareness of these projects and educate the LabVIEW community on the best approaches to collaborative development. This is where I need your help as I'm by no means an expert myself!
My initial ideas center around building a community of enthusiasts such as yourselves to help produce a web site and raise awareness of projects. I have a couple of key ideas of what I think will set off on a good start.
Educate: Practical tips on using sites like github effectively. Issue tracking, forking and pull requests. Github apparently have a good community team that we can try and reach out to and understand if they have materials we can use.
Raising Awareness: Having a directory of existing projects and highlighting them so people are aware of the libraries that already exist rather than reinventing the wheel.
So first questions for those of you that are keen enough to join already:
On the naming front one idea I had is that rather than LabVIEW we should use G.
Obviously Open G is taken though and Open Source G is too similar.
"FreeG" - I think this sounds too much like it is currently shackled though which isn't the point.
So I joined as I am interested in see where you are going with this. In truth at this stage I am not clear in the distinctive difference you are aiming for here against the already existing code repository of LAVA or the NI Tools network. Or even the new NI-DEV GitHub
Regarding your question 1) I suspect the start point needs to be pushing a GitHub or similar system (Mecurial).
How about OpenWires
In essence I want to help those networks grow. The LAVA CR is a great example, there is some great code on there but a) I think the awareness outsite of LAVA is low that it even exists and b) Too few projects on there are backed by an open repo which the community can contribute back to. It is still very much single developers sharing a build. I think by opening these to the community the library can be improved in ways that the original developer didn't invision or broaden beyond their use case to be useful to a much wider audience.
NI-DEV is a step in the right direction but I think that more is better! And I don't think it has to be driven by NI, I think the community is capable of helping push LabVIEW forward as well as NI.
Does that make more sense? Thanks for your comments though, I really want to get a feel for what the community opinion is on this subject as my goal isn't to force a split or a new community as much as enhance what is already there and I definately think part of the process is going to be working with LAVA, Tools Network, OpenG to understand how we can help.
I like OpenWires
I'm still fairly new to the whole open source concept so I'm going to be more of an observer than an actor for the beginning. But this does sound promising to me.
I am a daily user of LAVA, but I must admit that I'm still confused about what else is out there...
+1 for OpenWires
OpenWires sounds nice .
I wanted to quickly step in and mention my group's (ni systems engineering) efforts to move our work in this open-source direction. We've recently put up a few different sets of tools on a github organization (https://github.com/NISystemsEngineering). And I created this project (https://decibel.ni.com/content/projects/open-source-community-collaboration) on the reference design portal to help people get started with git. Admittedly neither effort has a ton of contributions yet, but I've gotten generally positive feedback internally and I am (slowly) trying to drive people towards posting the things they work on externally when its possible to do so.
tl;dr, I think this is a cool idea, but I'm having trouble gathering steam. Its nice to see someone else coming at this same issue.
Hmm that could be too similar. We could be the open wires project instead?