Skip to content
This repository has been archived by the owner on Jun 3, 2024. It is now read-only.

Reporting issues to Qwant Maps #167

Open
remi-dupre opened this issue Jan 11, 2022 · 0 comments
Open

Reporting issues to Qwant Maps #167

remi-dupre opened this issue Jan 11, 2022 · 0 comments

Comments

@remi-dupre
Copy link
Contributor

This little documents aims at explaining how issues are handled in this repository.

Short version is that we are a little team and we are almost exclusively committed into completing our roadmap goals. However any suggestion will be read and taken into account, we may just not have time to process them in the short/middle term.

Were to report an issue?

You are at the right place, any issue can be submitted in this repository: https://github.com/Qwant/qwantmaps/issues/new

What kind of issues should I open?

Any suggestion is welcome but they may be treated differently, for example bugs will be treated as quickly as possible but big features may never be prioritized.

What does label XXX mean?

We'll try to be explicit on how we will handle your issue by labeling them,
here is the list of available labels and their meaning:

  • planified: this ticket has its own equivalent in our internal Jira board, which mean it has been specified and is planed to be implemented.
  • bug: a component is not working as desired, this is likely to be treated as soon as possible.
  • small-enhancement: this is a small enhancement that requires very little work to setup, it is likely that it will be implemented without requiring to fit it in the roadmap.
  • feature: this is a big enhancement or a whole new set of functionalities, which would require to find its own entry in our roadmap to be implemented.
  • question: this issue is not related to a change in the product itself, but stands to hold a discussion over a specific topic.
@remi-dupre remi-dupre pinned this issue Jan 11, 2022
@Qwant Qwant locked as off-topic and limited conversation to collaborators Jan 11, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant