[QST] Anyone opposed to adding some new labels?

dask-contrib / dask-sql

Distributed SQL Engine in Python using Dask

https://dask-sql.readthedocs.io/

MIT License

392 stars 72 forks source link

[QST] Anyone opposed to adding some new labels? #259

Open randerzander opened 3 years ago

randerzander commented 3 years ago

It'd be useful to have some more labels for classifying issues and PRs.

For example, as more users adopt Dask-SQL for diverse workloads, we see a lot of SQL syntax specific feature requests:

substr vs substring distribute by

It'd be nice to have a "SQL Grammar" label for these.

Another major class could be "Performance": cost-based optimization sorting enhancements

charlesbluca commented 3 years ago

Agreed - I think it could also be useful to have some labels that given an idea of what layer of the codebase an issue resides in (i.e. python, java), and maybe even some labels for where the issue is in the codebase (for example, dask has labels like dataframe, delayed, core, etc.).

You need specific permissions to add labels, right? If that's the case then probably also a needs triage label that we could automatically add to certain issue templates.

charlesbluca commented 3 years ago

Ended up adding the discussed labels plus:

meta for maintenance issues like this
hive for some of the issues we've been getting specific to Hive support

I'm sure there are more that make sense to add, so we can leave this issue up for a while to keep that discussion going.