Blog: Why Does FusionAuth Open Source Their Issues?

[mark-robustelli]

---

• To see the specific tasks where the Asana app for GitHub is being used, see below:
  • https://app.asana.com/0/0/1205789265049339

[alex-fusionauth]

Overall I think it is a good start. I would add some images inline to grab people
Maybe

or

[alex-fusionauth]

Suggested change

Many open source projects generate revenue through professional services. They make their source code public and then charge money to implement it and update it. FusionAuth also does not have a professional services group and does not operate this way. FusionAuth is [free to use](https://fusionauth.io/download) and you can use it with an unlimited number of users. However, we believe the source code that makes our product run is our secret sauce. As such, the code is not publicly available. However, several ancillary projects are. As a matter of fact, there are over 200 [FusionAuth organization](https://github.com/FusionAuth) repositories available to the public on GitHub. Projects like the various [client libraries](https://fusionauth.io/docs/v1/tech/client-libraries/), [Quickstarts](https://fusionauth.io/docs/quickstarts/) and even the [FusionAuth website](https://github.com/FusionAuth/fusionauth-site) are available as open source. Afterall, FusionAuth is built by developers for developers. This is a chance to give back to the community and share some of the knowledge.

Many open-source projects generate revenue through professional services. They make their source code public and then charge money to implement it and update it. FusionAuth also does not have a professional services group and does not operate this way. FusionAuth is [free to use](https://fusionauth.io/download) and you can use it with an unlimited number of users. However, we believe the source code that makes our product run is our secret sauce. As such, the code is not publicly available. However, several ancillary projects are. There are over 200 [FusionAuth organization](https://github.com/FusionAuth) repositories available to the public on GitHub. Projects like the various [client libraries](https://fusionauth.io/docs/v1/tech/client-libraries/), [Quickstarts](https://fusionauth.io/docs/quickstarts/), and even the [FusionAuth website](https://github.com/FusionAuth/fusionauth-site) are available as open source. After all, FusionAuth is built by developers for developers. This is a chance to give back to the community and share some of the knowledge.

[alex-fusionauth]

Suggested change

In addition to the open source projects just mentioned, there is an [issues]( https://github.com/FusionAuth/fusionauth-issues) open source project for the core product as well. It also allows customers and those interested to have an open and transparent conversation about any issues they may experience with FusionAuth and give the community an opportunity to vote on how important the issue is to them. It also allows another avenue of support for those on the [Community Plan](https://fusionauth.io/pricing?step=plan&hosting=self-hosting). The Community Plan is free and support is available through the community. Github is one of those community support vehicles. If you are experiencing an issue with your instance, in addition to searching the [Forum](https://fusionauth.io/community/forum/) and [Slack](https://join.slack.com/t/fusionauth/shared_invite/zt-6ykfov9u-MTwA1A6ptv0Gr6KcFBVG4w) channels, you can search the [issues](https://github.com/FusionAuth/fusionauth-issues/issues). You can search both the open and closed issues. If the issue is closed, you can find the reason for your issue and hopefully a fix. If there is an existing issue, you can upvote\downvote an issue by giving the thumbs up or thumbs down as a reaction to help FusionAuth prioritize the issue. If the issue does not exist, you can create a new issue. The best part about this is the FusionAuth developers monitor this project. Not only do they monitor, they create issues in this project when they uncover issues during their development. By simply reporting issues, you are able to actively participate in the development of the product.

In addition to the open source projects just mentioned, there is an [issues]( https://github.com/FusionAuth/fusionauth-issues) open source project for the core product as well. It also allows customers and those interested to have an open and transparent conversation about any issues they may experience with FusionAuth and allows the community to vote on how important the issue is to them. It also allows another avenue of support for those on the [Community Plan](https://fusionauth.io/pricing?step=plan&hosting=self-hosting). The Community Plan is free and support is available through the community. GitHub is one of those community support vehicles. If you are experiencing an issue with your instance, in addition to searching the [Forum](https://fusionauth.io/community/forum/) and [Slack](https://join.slack.com/t/fusionauth/shared_invite/zt-6ykfov9u-MTwA1A6ptv0Gr6KcFBVG4w) channels, you can search the [issues](https://github.com/FusionAuth/fusionauth-issues/issues). You can search both the open and closed issues. If the issue is closed, you can find the reason for your issue and hopefully a fix. If there is an existing issue, you can upvote/downvote an issue by giving a thumbs up or thumbs down as a reaction to help FusionAuth prioritize the issue. If the issue does not exist, you can create a new issue. The best part about this is the FusionAuth developers monitor this project. Not only do they monitor, but they also create issues in this project when they uncover issues during their development. By simply reporting issues, you can actively participate in the development of the product.

[alex-fusionauth]

Suggested change

Not every issue is a bug. In addition to bugs there are multiple types of issues such as documentation, performance, enhancement and others. However, once an issue has been triaged by the development team, it is addressed accordingly. Just because the software does not behave as you would expect, does not mean it is a defect. There can be multiple ways to implement a feature and at times, the community will submit what they see as an issue to be later told that the software is working as expected. This may not be the desired outcome for the reporter, but they now have the information they need to move forward. If they need more information, the reporter can also see any discussion and reasoning that has taken place in the comments of the issue because they are open source.

Not every issue is a bug. In addition to bugs, there are multiple types of issues such as documentation, performance, enhancement, and others. However, once an issue has been triaged by the development team, it is addressed accordingly. Just because the software does not behave as you would expect, does not mean it is a defect. There can be multiple ways to implement a feature and at times, the community will submit what they see as an issue to be later told that the software is working as expected. This may not be the desired outcome for the reporter, but they now have the information they need to move forward. If they need more information, the reporter can also see any discussion and reasoning that has taken place in the comments of the issue because they are open source.

[alex-fusionauth]

Suggested change

	Another benefit of the open issues on github is that it allows the users of the software to interact directly with the developers. This is part of the way a community is created. Instead of the development team in a room somewhere trying to guess what the community wants, the open issues allow the users a direct path to the developers for their concerns.
	Another benefit of the open issues on GitHub is that it allows the users of the software to interact directly with the developers. This is part of the way a community is created. Instead of the development team in a room somewhere trying to guess what the community wants, the open issues allow the users a direct path to the developers for their concerns.

[alex-fusionauth]

Could we add more to this section? Do we have a contributing guide? I asked dan we shall see.
https://inversoft.slack.com/archives/C02CR2M6SRK/p1698339876870129