Create Issue templates for Bug reports and RFEs #2823
Conversation
|
Resolves: #2752 |
| If applicable, add copy of the output on the command line or a screenshots to help explain your problem. | ||
|
|
||
| **Environment** | ||
| - OS / Distribution: [e.g. Fedora 13] |
There was a problem hiding this comment.
Not that it really matters, but I'd use a bit newer Fedora version as an example 😄
|
|
||
| --- | ||
|
|
||
| If your feature need figuring out how to implement it or needs feedback from the wider comunity, please open a [Discussion](https://github.com/rpm-software-management/rpm/discussions) instead. If the discussion has solidified into a plan of action it is time to create an issue for actually implementing it. |
There was a problem hiding this comment.
I think we'll want a stronger emphasis on the discussions. Basically: always start a discussion first, using the template info below as the starter, and: "Once the discussion has solidifed into a plan of action, the rpm maintainers will open an RFE issue (or request you to do it) for actually implementing it.".
There was a problem hiding this comment.
I don't think that's necessary, since Issues can be converted into Discussions and back.
There was a problem hiding this comment.
It's manual work that, ahem, somebody gets to do. And the average pony request is better off starting as a discussion, to avoid the overhead that goes into ticket processing.
There was a problem hiding this comment.
Unless someone is committing to doing that same work in Discussions, we should not be telling people to go there. Discussions should not be treated like that.
There was a problem hiding this comment.
It's not the same work, otherwise there would be little point in all this. Discussions are better for discussions than tickets, and tickets are better for organizing work.
This is work we do so maybe we get to decide how to do it, no?
There was a problem hiding this comment.
Just FTR, I dislike the discussions, mainly because I read everything through rpm-maint ML and the discussions are not forwarded there AFAICT. And I don't know if there is any meaningful way to subscribe to discussions, but I don't see any on the first look. IOW they might look like the best tool for the team or project members, but IMHO, they prevent collaboration in wider community.
There was a problem hiding this comment.
Oh, we have a confirmed rpm-maint reader. I've suspected nobody looks at that anymore because volume and format...
There was a problem hiding this comment.
Just FTR, I dislike the discussions, mainly because I read everything through rpm-maint ML and the discussions are not forwarded there AFAICT.
Hm, checking the archives, I was wrong. I might change my mind, sorry for the noise.
There was a problem hiding this comment.
Ack, I thought they should be forwarded along with all the other traffic. And, if not then it should at least be possible.
There was a problem hiding this comment.
Oh, we have a confirmed rpm-maint reader. I've suspected nobody looks at that anymore because volume and format...
At least my rumbling was good for something 🙈 Yes, rpm-maint is the most consumable format allowing to follow what is going on with RPM.
|
urgs this was created as branch in the main repo by the GH UI (and though can't be force pushed...). Created an new PR from my private repo. Closing this here. |
No description provided.