- The Open Source LabVIEW Icon Editor
- Our Contributing Philosophy
- How to contribute
- Collaborate with the community and NI!
- Creating a discussion for a new feature
- Enhancements
- Reporting issues
Just recently, the LabVIEW Icon Editor has been made open source to encourage collaboration between NI and the LabVIEW Community. Every new build of LabVIEW will grab the icon editor that has been pushed into the main branch from this repo.
The direction of the LabVIEW Icon Editor and which new features are added, and which are left out, is decided by the steering committee, which includes NI staff and LabVIEW community volunteers (sometimes referred to as a “cathedral” style of development).
That being said, the Icon Editor is great because of the LabVIEW users who use it, share their code with the community, and discuss ways to make LabVIEW even better. Some of the most important and undervalued work in open source is from non-code contributions, and that is where we can use the most help from you.
This repo is managed via git, with the canonical upstream repository hosted on GitHub and it follows a pull-request model for development.
Feature requests are selected by NI in a joint effort with a group of members of the LabVIEW community called a "steering committee". A steering committee is a group of trusted individuals selected by the software community lead based on their background and contribution history to the NI ecosystem.
Steering committees are non-NI employees with triage roles to the repo that can vote on community driven features being part of the next LabVIEW release.
Ready to level up your game?. Collaborate with people from different backgrounds and proficiency levels.
See below the different ways to collaborate
| Contribution type | Effort level(1-10) |
|---|---|
| Comment on GitHub issues | 1 |
| Comment on GitHub discussions | 1 |
| Create a GitHub discussion | 2 |
| Report an issue | 2 |
| Develop a feature | 8 to 10 |
| Solve a bug | 5 to 10 |
Go to the issues section of the repo and voice your opinion on issues that other people are having. Did you find a workaround to any of the GitHub issues? We want to hear about it!
GitHub discussions are raw ideas in the process of gathering feedback from the community before converting them into a GitHub issue. Go to the GitHub discussions and voice your opinion on ideas that will eventually be a part of the next shipping version of the Icon Editor.
Want things done differently? or have an idea on a feature that is not ready yet to be considered as a GitHub issue?
Create a GitHub discussion so that other member of the LabVIEW community can weigh in on your dicsussion. Discussions are usually initial stage for GitHub issues.
Found an issue? raise a new GitHub issue and select "Bug Report"
You can do this by becoming a contributor.
Contributions for bug resolution and feature development have certain guidelines and processes not covered on this document. More information can be found here.
Try developing a new feature by going into the GitHub issues labeled as Workflow: Open to contribution. Go to the GitHub issue you want to work on, and let us know via a comment.
Go to the GitHub issues marked as bugs that are open for contribution here.
If you have an idea or suggestion for an enhancement to the LabVIEW Icon Editor library, please use the New Features discussion section. please make sure to start a discussion about your changes.
Talking to us first via the discussions section about the enhancement you want to build will be the most likely way to get your pull request into the library (see Our Contributing Philosophy above). We would hate to see you write code you’re proud of, just to learn that we’ve already been working on the same thing, or that we feel doesn’t fit into the core library.
Once your idea has been selected for the next release of LabVIEW, a branch will be created that you can submit your pull request to.
All interactions should be done with care following our Code of Conduct.