For me Forem is a less intimidating place to post. I always feel like everyone judges my github contributions and my first instinct with a bug in Forem is I did something wrong.
This is my instinct as well, and generally the culture we'd want to cultivate. There is no "wrong" forem post, though if we discover that something is, in fact, an issue through discussion here, we can instruct folks to spin up GH issues.
One distinction we could potentially draw on is the existing "bug" and "feature request" labels.
Bugs should definitely be opened on GH.
Feature requests can probably start out here, have some discussion around them, then find their way into our regular workflow (shaping, etc.) and eventually end up on some product board.
I'm a bit unsure about where I prefer to see things that might be bugs. My gut feeling says GH, because even if something turns out to not be an issue after all, it's easy to close and move on. But I also understand the desire for a more "neutral" place to post first. In an ideal world, people would feel just as welcome on our GH as they do here, if that's not the case I'd like to start fixing that first.
I always feel like everyone judges my github contributions
@rcarlson
If you ever feel this on the Forem repo, please let us know!
In an ideal world, people would feel just as welcome on our GH as they do here, if that's not the case I'd like to start fixing that first.
I think this is what Forem should always strive for.
For example, I've read issues in other projects where maintainers tell people to not use the issue tracker for X or Y. Maybe people do it because they don't know what's the right place.
With that experience in mind, someone might refrain from posting an issue in Forem because they'd be giving some more work for maintainers (for "silly" stuff). But also they wouldn't know what is be the right place.
Edited for clarity on who'd need confidence to post issues
I might refrain from posting an issue because I'd be giving some more work for maintainers (for "silly" stuff)
As someone who contributed to our codebase you hopefully know we're a friendly bunch. The worst that could happen is that the issue gets closed with an explanation. Also it literally is our work, unlike many open-source maintainers, we get paid for it.
This is my instinct as well, and generally the culture we'd want to cultivate. There is no "wrong" forem post, though if we discover that something is, in fact, an issue through discussion here, we can instruct folks to spin up GH issues.
One distinction we could potentially draw on is the existing "bug" and "feature request" labels.
I'm a bit unsure about where I prefer to see things that might be bugs. My gut feeling says GH, because even if something turns out to not be an issue after all, it's easy to close and move on. But I also understand the desire for a more "neutral" place to post first. In an ideal world, people would feel just as welcome on our GH as they do here, if that's not the case I'd like to start fixing that first.
@rcarlson If you ever feel this on the Forem repo, please let us know!
I think this is what Forem should always strive for.
For example, I've read issues in other projects where maintainers tell people to not use the issue tracker for X or Y. Maybe people do it because they don't know what's the right place.
With that experience in mind, someone might refrain from posting an issue in Forem because they'd be giving some more work for maintainers (for "silly" stuff). But also they wouldn't know what is be the right place.
Edited for clarity on who'd need confidence to post issues
As someone who contributed to our codebase you hopefully know we're a friendly bunch. The worst that could happen is that the issue gets closed with an explanation. Also it literally is our work, unlike many open-source maintainers, we get paid for it.
Ah yeah. I wasn't telling this because of me but for other people 😅
Sorry not making that clear
Anyone feeling unsure about posting issues on GitHub should see my issue list 😂😍