Where are OpenG Product Pages for packages?

[wildcatherder]

I'm reviewing the latest (2019) VI Package Manager listings for OpenG packages.  All the Product Pages link to http://wiki.openg.org/, which is a dead site.  I found a reference that one should look in https://lavag.org/forum/45-openg/ but I still have not found anything like individual product pages and examples.  Would someone please direct me to this information?

[Tim_S]

What you are looking for exists, but not in the way you are looking for it. The documentation is in the context help for the the VIs installed. Some of the libraries do install examples with them, though most do not need examples as the information in the context help is rather good and any confusion can be resolved by looking the block diagram.

One thing that I'm not sure is clear is that VIPM is a software package written by JKI that is used by many groups (including NI) to create easily installable packages, all of which is versioned and controlled separately so the VIPM version has no impact on the information the OpenG library provides for VIPM to display.

[Michael Aivaliotis]

@Tim_S, the OP makes a valid point. All you say is true, however, the link remains broken and the person packaging the OpenG tools should either fix the link and provide the documentation, or remove the link from the package build.

[Tim_S]

@Michael Aivaliotis, rereading my reply today that's a very fair criticism.

[Fab]

Semi related issue with OpenG URLs

One of my customers has added to his application's About page that the app uses OpenG code. He was including the old url http://openg.org, what URL should he include now?

Thanks,

Fab

[Michael Aivaliotis]

46 minutes ago, Fab said:

Semi related issue with OpenG URLs

One of my customers has added to his application's About page that the app uses OpenG code. He was including the old url http://openg.org, what URL should he include now?

Thanks,

Fab

It seems like OpenG needs a landing page. Perhaps if we use GitHub Pages for the GitHub repos, as proposed here. This could be the new URL to include in licensing.

[Jim Kring]

Hi All.

The OpenG wiki had several technical problems, so we dropped it -- I agree that we need a new landing page for OpenG with information and docs (and we can redirect old links).

I've been working with others over the past several years maintaining the OpenG packages on GitHub (e.g. OpenG-Variant-Configuration-File-Library), providing bug-fixes and upgrading the OpenG libraries to NXG (despite the fact nobody was really using NXG for real work -- that'll be changing the the next couple years).

I'm aware that people are becoming very interested in collaborating more on OpenG, especially with the enthusiasm around the upcoming LabVIEW Community Edition release (I am super excited about LV Community Edition, too). I'm really happy to see this renewed interest in LabVIEW and OpenG, since I've been doing a lot of the maintenance work, myself, and would love more participation in both development/testing and documentation/examples.

LAVA isn't generally the best way to reach me, but I'm available at jim.kring@jki.net or @jimkring.

[Michael Aivaliotis]

5 minutes ago, Jim Kring said:

I'm really happy to see this renewed interest in LabVIEW and OpenG, since I've been doing a lot of the maintenance work, myself, and would love more participation in both development/testing and documentation/examples.

I'm glad to hear that you are welcoming to this. I think this initiative and the positive response shows that the community is willing to take on some of these tasks and responsibilities as long as there's an open and inclusive process in place.

As a starter, it would be great to revive the openg.org domain which has been dead for many years and at least point it to the LAVA OpenG root forums,. That's where it was pointing to before as indicated by this post. In the future, it could point to a GitHub landing page.

[Jim Kring]

4 hours ago, Michael Aivaliotis said:

I'm glad to hear that you are welcoming to this. I think this initiative and the positive response shows that the community is willing to take on some of these tasks and responsibilities as long as there's an open and inclusive process in place.

As a starter, it would be great to revive the openg.org domain which has been dead for many years and at least point it to the LAVA OpenG root forums,. That's where it was pointing to before as indicated by this post. In the future, it could point to a GitHub landing page.

I'll try not to repeat myself too much here, since I've already posted a response here. I do welcome participation in making OpenG better and the current repositories are open to issues/pull-requests/etc. I'm not in favor of a new GitHub repository at this moment, since there are several things I've had on the roadmap, including fixing the website issues.

[Fab]

On 10/8/2019 at 5:18 PM, Fab said:

Semi related issue with OpenG URLs

One of my customers has added to his application's About page that the app uses OpenG code. He was including the old url http://openg.org, what URL should he include now?

Thanks,

Fab

@Jim Kring

What should my customer include in their about page since http://openg.org doesn't work anymore?

Thanks,

Fab

[Fab]

On 12/3/2019 at 9:45 AM, Fab said:

@Jim Kring

What should my customer include in their about page since http://openg.org doesn't work anymore?

Thanks,

Fab

Hi @Jim Kring,

My customer is back asking what he should be including in their about page since http://openg.org doesn't work anymore?

He wants to make sure he is respecting what the license says and giving a link to people to openg.org.

Thanks,

Fab

[Jim Kring]

On 7/23/2020 at 2:30 PM, Fab said:

Hi @Jim Kring,

My customer is back asking what he should be including in their about page since http://openg.org doesn't work anymore?

He wants to make sure he is respecting what the license says and giving a link to people to openg.org.

Thanks,

Fab

Thanks for the head-up fab. I'm working to fix that