#4125 [RFE] Expand the README to include "How to provide feedback"
Opened 10 months ago by blaise. Modified 9 months ago

It would be nice to know how to provide feedback. For example:
Begin the subject line with [Bug] if something that isn't working as expected.
Begin the subject line with [RFE] if you have a suggestion or request.
* Begin the subject line with [Doc] if you have a problem with the descriptions or instructions.

etc...


The pagure project uses tags for this so I'm :thumbsdown: on adding this on the README, sorry.

I'll leave this ticket open for a few days so we can discuss it more if people disagree with me :)

I think @blaise is asking for is contributing guidelines / expectations for new contributors in Pagure. Are there steps a first-time reporter can follow for delivering feedback? What info makes life easier for Pagure maintainers to process a new ticket or feature request?

What info makes life easier for Pagure maintainers to process a new ticket or feature request?

I actually use the tags to as a mechanism to acknowledge that I have seen and categorized the ticket.

I would be glad to add something in the doc explaining this, suggestion on how/where to do it is welcome :)

I would be glad to add something in the doc explaining this, suggestion on how/where to do it is welcome :)

This isn't specific to Pagure development workflow, but I opened #4131 just now. I think it's related.

The pagure project uses tags for this so I'm 👎 on adding this on the README, sorry.
I'll leave this ticket open for a few days so we can discuss it more if people disagree with me :)

@jflory7 , It's possible that @pingou is not aware that the current access model does not allow users (ie consumers of the artifact) to assign tags. It seems that Pagure uses tags to describe the content of the issue and also to indicate the status.

Someone who is not a project member and wants to provide feedback or suggestions:

  • Doesn't know what info you would like them to provide.
  • Doesn't know where they can review the history of similar issues.
  • Has no way of knowing which tags to use
  • Doesn't know how to interpret the tags
  • Can't add any tags anyway, because they don't have the privs.

I would be glad to add something in the doc explaining this, suggestion on how/where to do it is welcome :)

OK, I'm reluctant to provide an example because I spent 40 minutes composing the previous example and you missed the point because you didn't like the implementation.
I would suggest instead that you consider what answers you would provide to these questions:

  • If someone outside the developer team uses Pagure, do I care?
  • If someone has a suggestion, do I care?
  • If someone outside the team wants to help, where should they start?
  • If someone is using Pagure and finds a problem, what info would I like them to provide?

-Blaise

@jflory7 , @pingou I think this topic is being addressed in:
https://pagure.io/pagure/issue/4131
so feel free to close this as a duplicate (or however you do things). -Blaise

Login to comment on this ticket.

Metadata