Hello everyone, stemming from the discussions that we had back in the gathering, I make a proposal having two things in mind:
- We won’t never track it all and there’s little value on trying to do so
- We need to know the main areas of work and how they relate to our budget so we can take more informed decisitions
For that, I’d go with a first simple step of tidying up the projects and start tracking the basics. Here is the list and what I understand by them, please share your ideas/additions:
Sysadmin: anything related to ofn-install plus server management such as provisioning, deployment or dealing with incidents (what we called operations). For now, I don’t think we’ll need to differentiate between them.
Bugs: I didn’t know this one existed until the gathering. I started using it when I’m dealing with a bug either fixing or investigating its issue, or even when discussing it with product. I propose we keep it that way. It’ll shed some light on how much time we spend on them.
Dev: obviously programming hours but also any other task that requires dev know-how like answering questions on Slack, debating on community, etc. But those that are not included in the categories above. This leaves us with features and general tech discussions.
Testing: pretty clear I think. Any time we spend testing.
Release: I heard some people suggesting this. It makes sense since it is one of the areas we want to improve.
In any case, it’s important we state the id of the PR or issue always. AFAIK most of us have been doing it so far.
These are the tech ones (and we could start creating/cleaning these) but I’d like others to share their ideas on ATAP stuff. I can think of: funding, communication, instances support, but I’m sure there are others.
What I don’t find an easy solution for is tracking specific features like PI or subscriptions. Tags? Do we need it at all?
So, I’d say we start with an agreed list for tech stuff and iterate from there. Then, I will document them.