Create "learn" label so we can keep track of all the learning-related issues in dwyl?

[nelsonic]

We do a lot of learning in @dwyl projects! (in fact knowledge is one of the main outputs of our work!)

When someone asks a question in an issue in a project and the issue leads to new knowledge,
we are currently only "OK" at capturing that knowledge generated in our projects ...

(not everyone has the habit of capturing and sharing knowledge as evidenced by the fact that we have people working with us who have made zero contributions to learn-... repos/tutorials in the 3 months...! this is going to change very soon BTW, but that's for another issue!)

In the interest of being able to signal to other people (e.g: people who join a project half-way-through) that we have learned something (e.g: how to deploy the app on a specific infrastructure) I propose having a learn label we can use in projects!

This will allow people to filter for all the issues where learning was acquired in the project. 💡

I already have this for my personal learning: https://github.com/nelsonic/nelsonic.github.io/issues?q=is%3Aissue+is%3Aopen+label%3Alearn
But I think it's worth having for our projects.

Thoughts?
relates to: dwyl/hq#314

[Cleop]

I like the idea @nelsonic, I suppose we'd just need to make sure that we gave a good definition of what a new learning is considered to be. Ie. what's new for some people won't be new for others and therefore what should qualify? In theory everything is new for someone?

[nelsonic]

@Cleop indeed. "everything is new for someone" 😉
The more we capture the easier we make the lives of people who follow after us. 👍

[iteles]

Also, we need to define it tightly enough so that we don't cause unnecessary tension on client projects where we need to add context to things we are 'learning' during a project 👍