Greate news for the community

[MikaelH]

NI is uploading projects to GitHUB, so the LV community can help out in development.
The GOOP Development Suite will be one of the first projects they will try out.

Check out the vishots live video:

<a href="https://www.youtube.com/watch?v=abXD7M7-Y1Q#action=share">https://www.youtube.com/watch?v=abXD7M7-Y1Q#action=share</a>

[AristosQueue (NI)]

I have promised the community we'll have this up within two weeks from yesterday. Those who know my history know I do not make promises about future functionality lightly. I'm pushing as hard as I can to make sure all the moving parts within NI are lined up to make this happen in short order.

[David_Staab]

I'm morbidly curious to see how the pull request model will work out on this project. Who's going to be the Benevolent Dictator?

[AristosQueue (NI)]

You'll be able to publish any changes you want to the repository and they'll be automatically available to the other enrolled users or publish your changes as a package and publish them in other forums as long as you have put those changes onto the repository. So the pull request model doesn't get involved there.

The pull request comes into play when you have changes well enough polished that you think they should become part of the main "golden" distribution that NI maintains. At that point you would put in the pull request for a pull from the dev branch (which users have read/write access for) to the trunk branch (which users only have read access for). Someone from NI will be evaluating the pull request and either accepting or denying it. Who exactly that is will vary based on time we have available in our schedules. Think Oligarchy not Dictatorship. 😉

[David_Staab]

Yeah, I'm specifically talking about the difficulty of merging LV code, especially LV classes and libraries. Anyone reviewing a PR is going to have a heck of a time merging conflicts, and I expect that some PRs will be entirely rejected because the master branch got too far ahead of the one they forked.

[AristosQueue (NI)]

We'll see. I deal with merging LV code on a somewhat regular basis. Yes, there are times when there are issues, but it isn't necessarily common. Some open source projects catagorically reject any pull request that isn't already sync'd to the master, making it an issue for the person making the pull request instead of the person evaluating the pull request. And in ANY branched development (speaking as someone who works on a team of N where N is larger than any alliance partner I've ever seen), you need to be sync'ing regularly -- once a week at least.