intrigeri:
> hi,
> Woo! \o/
>
> Sorry for the delay…
>
Well... I took my time too!
So, I agree with most of what you suggested, and made changes based on
your input. Some doubts/questions below:
>> and would benefit for some more insight on
>
> Regarding "Debian": the current description makes it sound anything
> that has to be done upstream should have Type of work = Debian, which
> is not the case. Some work has to be done upstream _elsewhere_, and
> then we generally use Communicate (e.g. when the action is to report
> a bug upstream), or Code (e.g. when the action is to do the needed
> tech work upstream), or Wait (when we're waiting for upstream to do
> it themselves).
>
>
> * Dev Needed: "Choose this when you think a developer will have enough
> information to start working on this ticket" ← I'm not aware of such
> usage; do we really use it this way?
How would you define it?
>
> * Generally: in a few places it's written "code", while the text is
> valid for any kind of contribution that lives in Git; I would love
> to see the language be a bit more inclusive wrt. these other kinds
> of contributions. If you don't feel like working on this yourself,
> I'll be happy to give it a try once you see the branch as ready
> for QA.
>
I understand your reasoning, but I didn't acted much upon that... please
change what you find misleading..
> * "If you create a ticket you become automatically
> a watcher" ← really?
>
Yes
