There will be two types of tags: generic tags and managed tags. Generic tags would make it easier to find packages by category such as "Networking", "Logging", or "Charting". Managed tags can only be applied by a specific developer group though there should be a feature for maintainers of a package to request a managed tag be applied which would then show up for the tag managing group to approve or deny.
Developer groups can be created for privileged people such as LabVIEW Champions, CLAs, NI staff, etc. It would then be possible for managed tags to be created for each of these groups so that a group such as the champions can review a package and apply a special "Champion Reviewed" tag. If NI were to start using this package system they'd be able to identify officially endorsed packages with their own managed tag regardless of which individual / group uploaded the package.
Managed tags could be used to identify specific ecosystems of packages to make it trivial to create 3rd party package management software that leverages GCentral repositories. For instance, an idea is to leverage GCentral for hosting Linx toolkit related packages so that a small package manager could be built into the Linx tools that make it trivial for newcomers to LabVIEW / makers to gain additional device feature support as part of their Linx projects. The open nature of the GCentral repositories also makes it easy for community members to contribute packages to expand the ecosystem.
There will be two types of tags: generic tags and managed tags. Generic tags would make it easier to find packages by category such as "Networking", "Logging", or "Charting". Managed tags can only be applied by a specific developer group though there should be a feature for maintainers of a package to request a managed tag be applied which would then show up for the tag managing group to approve or deny.
Developer groups can be created for privileged people such as LabVIEW Champions, CLAs, NI staff, etc. It would then be possible for managed tags to be created for each of these groups so that a group such as the champions can review a package and apply a special "Champion Reviewed" tag. If NI were to start using this package system they'd be able to identify officially endorsed packages with their own managed tag regardless of which individual / group uploaded the package.
Managed tags could be used to identify specific ecosystems of packages to make it trivial to create 3rd party package management software that leverages GCentral repositories. For instance, an idea is to leverage GCentral for hosting Linx toolkit related packages so that a small package manager could be built into the Linx tools that make it trivial for newcomers to LabVIEW / makers to gain additional device feature support as part of their Linx projects. The open nature of the GCentral repositories also makes it easy for community members to contribute packages to expand the ecosystem.