FAQ

Are there any videos or presentations of GCentral online?

Yes. You can see GCentral present its vision and mission at the 2019 CLA Summit in Austin Tx.


What do people think about GCentral?

GCentral conducts a yearly survey. At the conclusion of the survey (closes/opens at NIWeek) we report out results to our community. Please share your thoughts by taking the 2020-21 survey here. In order to help ensure accuracy by preventing double voting, please sign in with your google account when prompted .


Where can I find results from previous surveys?

The survey summary is presented once you've completed a survey. In addition, summaries and trends will be presented on GCentral.org once enough data has been collected.


How is GCentral different than other companies in the LabVIEW Community?

GCentral is a non profit organization whose main purpose is enabling the G community to improve its own tools through collaboration. Whereas other companies may have a similar objective, GCentral is the only organization with this as its prime objective. Since GCentral is not driven by profit, the measure of our success is not financial, but in its positive effect on the G community.


How does GCentral enable collaboration?

By providing resources that

  1. Alleviate the pain of finding and using community code
  2. Teach and enable G programmers to give their code to others
  3. Teach and enable G programmers to develop each other’s code

Wait, is there really a problem?

Yes. Today G community members are often frustrated when trying to find tools and code others have posted on the web. There are too many places to look and most aren’t intuitive to find. Today code is stored on ni.com, lavag.org, the LabVIEW Tools Network, NI package manager, VI package manager, G package manager. These locations often don’t reference each other, so a new or even experienced G community member can easily miss code ALREADY WRITTEN that solves their problem, resulting in wasted time duplicating code.


So, specifically, how will GCentral solve this problem?

GCentral will create and maintain GCentral.org, the G community’s first package agnostic index exposed through a website. From a single website, a G community member will be able to search/find NI Packages, G Packages, and VI Packages. GCentral will create a repository where anyone can put a package, regardless of type (NI package, G Package, VI Package). This repository will be published through GCentral.org. Our intent is to also expose the GCentral repository through existing package managers.


What about the other repositories that already exist like GPackage.io, the LabVIEW tools Network, vipm.jki.net/packages?

GCentral will work with other repository owners to expose their packages through GCentral.org. GCentral will expose packages regardless of package type.

See the diagram below for a system level description.

Aren’t you just creating "yet another repository"?

No, GCentral isn’t just another repository. It will index and expose packages from other repositories as well as its own. GCentral will expose packages of all types (NI Packages, G Packages, VI Packages). GCentral is creating a repository that can hold all three package types. The quality/completeness of code will not gate GCentral from publishing the package.


Will GCentral expose more than packages?

No. GCentral will only expose code put in packages. However, a user may choose their packaging technology and the package's contents.


How is GCentral different from the NI Tools Network?

GCentral will not gate publishing packages to the community like the NI Tools Network does. Anyone can publish a package of any type to the GCentral repository. The community will be able to rate packages for quality, completeness, etc. GCentral will not rate the code's quality. GCentral will, however, enable the community to qualify packages submitted to the community.


So GCentral is just a website? Basically a packaging index?

While GCentral is a website and a packaging index, our set of objectives is larger. Specifically GCentral has three objectives:

  1. Ease finding and using code (accomplished through the global package index exposed through GCentral.org).
  2. Minimize the amount of work necessary to publish packages for others to consume.
  3. Enable members of the G community to co-develop.

GCentral will create a community build process and template LabVIEW projects designed to export code into any/all package types. GCentral will leverage collaboration tools (like Git) to create template repositories ready for forking.


Is GCentral.org yet another package manager?

No. GCentral.org is not a package manager, nor does GCentral recommend one package manager over another. GCentral provides an index of all packages, regardless of package type, exposed through a website as well as a set of tools that facilitate contribution and co-development. It is left to the community member to decide which package manager to use based on the characteristics of each.

For an objective comparison of package managers see the LabVIEW Wiki page comparing the package managers.


How will GCentral pay for its offerings?

GCentral will be funded through donations from individuals and corporations. GCentral believes its value allows the G community to save time and development costs by leveraging each other's solutions. GCentral will reduce developers wasting time recreating what already exists, but is hard to find . (See the donation page.)

We believe those most interested will be:

  1. Companies that have mission critical applications based on the National Instruments tool chain, including LabVIEW
  2. Companies that want to efficiently use the NI tool chain and rely on the availability of code
  3. Alliance partners who want to more quickly develop solutions for applications vs develop support code
  4. Individuals who want to develop code specific to an application vs write lower level code


How can I join GCentral's efforts?

Spread the word!

The easiest way to show your support of GCentral is to adding the GCentral logo to your ni.com profile using the following HTML.

<a href="https://www.gcentral.org"><img src="https://labviewwiki.org/w/images/a/a3/Gcentral_circle_logo.png"alt="GCentral" width="100" height="100" ></a>

See the video below on how to edit your ni.com profile signature:

Use the GCentral logo

The most current GCentral logo can always be found on the LabVIEW Wiki. Please redirect all clicks on the logo to https://www.gcentral.org where applicable.


Join the conversation on LavaG.org

LavaG has a new "GCentral" section with one of the forums dedicated to identifying personas and use cases. We're looking for input on use cases to make sure GCentral aligns with our community's needs. So please tell us your thoughts.


Help develop the GCentral website

The indexer proof of concept is open source and developed completely in LabVIEW NXG using Web VIs. The source is located in GitHub at GCentral/Website repository GCentral has Matthias Baudot of StudioBods and Siva Shankar of Soliton Technologies to thank for pioneering the prototype. Join us in developing our community's solution.


How can I financially support GCentral?

See the donation page. GCentral is a 501(c)3 organization. As a result, all donations are tax deductible.


What are GCentral's Terms of Use?

GCentral is not responsible for software or content accessed through GCentral or any repository or site referenced by GCentral. All software and content is subject to the terms and licenses specified by the package or website referenced by GCentral.