Can we tweak the reimbursement work flow slightly?
I think it is a good idea. It is also helpful for other APAC CC holder in the future.
+1 from me.
However, I think we should take it to vote in the next APAC meeting (for people to know that new way as well).
This is what I've come up with:
An additional report shows all approved tickets: 11. This is to differentiate event reports from others that we have on the trac (discussion/admin tasks).
I hope that's streamlined enough Tuan? If you think it's OK, I'll send out a short mail to the list and update the reimbursement page with these minor changes? I can also update the trac front page so people see it when they log in?
I was also thinking if we should use "milestones" instead of reports like "FY2014 Q1". If we keep creating reports for each quarter, we'll have too many of them. I think milestones are supposed to be used for this purpose (not sure, but I remember seeing marketing use milestones like Fedora 20 beta, Fedora 20 release, Fedora 20 follow up etc.).
We can either have milestones based on Fedora releases or based on quarters. Considering that the Fedora release cycle isn't the most regular, I think 4 quarters would be better.
It's fine to me.
Replying to [comment:4 tuanta]:
It's fine to me.
I've added 2 milestones for the time being:
I haven't assigned any tickets to them yet. I wasn't sure if tickets are assigned to quarters by their filing date or by their date of reimbursement..
Seems fixed for now, so closing it. If need be, we could re-open.
Metadata Update from @sarupbanskota:
- Issue assigned to bckurera
to comment on this ticket.