Why doesn't the repo have issues?

[huaracheguarache]

Why does the repo not have issues in addition to discussions? I think it would be easier to keep track of bugs if they could be submitted as issues.

[huaracheguarache]

@conorpp Could you please consider enabling issues in the repo to keep bug reports a bit more organised?

[nickray]

This repository mostly assembles other libraries into a running firmware bundle.

• technical bug reports should go into issues of the corresponding library
• higher-level questions about using the device should go into a discussion in this repository
• customer service problems like "key seems broken" (or anything else if you feel you're not being heard on GitHub) should be directed to [email protected]

We ask that users please check if related issues and discussions exist before filing new ones, to reduce discussion/issue fatigue. SoloKeys is still an unprofitable open source side business of its creators.

[KizzyCode]

Well, now we have the situation that the discussions are heavily used as issue replacement, which is just chaotic and confusing.

E.g. at least these discussions are completely valid issues and should have been treated as such:

• Release notes unclear which credentials are erased, and in the future, there should be a mechanism to repair credentials rather than wiping them. #126
• "resident" OpenSSH-sk keys not working (yet?) #108
• Flakey Presence Detection in Windows Sign-In #116
• Unable to add keys to Microsoft account #113
• Unable to Reset (Not allowed) #115
• Solokey 2 NFC #90
• Key not recognised on Windows 10 #111
• Solo2 with Bitwarden extension crashes Safari #106

I also want to state that it is of course completely fine to close/move issues that affect foreign repos or have a Q/A-character; however the current approach is highly uncommon for github and feels unsatisfying/opaque.

[needs-coffee]

There is a place for both issues and for discussions in a modern GitHub repo.
Discussions have really become prevalent as the issues were getting filled with non-issues/help/feature requests and obscuring actual issues but they are not a replacement.
The main problem with discussions is that they cant be 'closed'.
Ideally I think there should be issues open on this repo for issues global to the solo2, as some of the posts mentioned by @KizzyCode are. An example of a 'closed' discussion about this would be the first issue above (#126) about the release notes unclear - this has now been solved so should be marked as such, but cant be done so when it is in the form of a discussion.

An issue template could be used to direct users to the libraries where the issue should be filed if it pertains to one of the libraries not the key as a whole?