On Tue, Mar 7, 2017, at 10:40 AM, Christoph Wickert wrote:
2017-02-27 12:18 GMT+01:00 Zacharias Mitzelos
> Hello EMEA Ambassadors,
> I completed the trac migration from fedorahosted to pagure.
Great! Thanks a lot for your efforts!
> I have created another issue tracker for funding requests, that is
> set to public for the time being. This will be our primary issue tracker
> for funding requests or other expenses that will be reimbursed from the
> EMEA Budget. In the next meeting we have to make a decision weather or
> not we want to move forward with bex's idea to have 2 issue trackers for
> funding requests (one public under the EMEA group, and one private were
> receipts will be uploaded at, under the fedora-budget group).
The problem is that funding requests on the one hand need to be public
(for FAmSCo or the regional IRC meeting to make decisions) but on the
other contain sensitive information (invoices, bank accounts for
reimbursements). I'm not sure if splitting this up into two separate
trackers will help. Often the sensitive information is necessary for
decision making. If someone asks for approving 500 € in one tracker,
but for reimbursement of 1000 € in the other, we have a problem.
Two trackers only make sense from Bex's or the treasurers'
perspective. But it also means more work for them, as they have to
watch twice as many tickets and make sure the numbers in one ticket
match the ones in the other.
I believe that it is reasonable to ask the treasurers, card holders, and
me to click through and look for the final approved amount in the public
ticket as a matter of due diligence. The public ticket should be
included in the reimbursement ticket request.
Also, I (and the others) don't actually have to watch any tickets we
only have to respond to the reimbursement tickets when they get assigned
to us. The deliberations may be interesting, but as long as the ticket
contains the confirmation of approval it is all good. I believe the
group as a whole should feel responsible for ensuring that public
tickets don't contain false confirmations (and we do have to trust at
To make things more complicated, we have the same problem with swag
tracking. In the past, ambassadors had concerns sharing information
like shipping addresses,
I believe a split ticket here, while painful can work. I'd definitely
like to see some kind of public approval that hte swag can be used
before the shipping is just requested.
I think the easiest solution is to change the visibility of all 3
trackers to authenticated users only. swag_requests and trac_obsolete
already are, only funding_requests is completely public.
> All of the repositories/issue trackers I mentioned can be found under
> the EMEA Ambassadors group in pagure. Members of this group can see
> the private issue trackers, add comments to private tickets, change the
> status of tickets, and many more.
Beware, everybody in the group has full admin privileges! They can not
only change all tickets but also the trackers, e.g. delete
*everything*. I think admin privileges should be reserved for certain
people, not groups. IIRC not even FAmSCo had full admin on all trac
> I added some EMEA Ambassadors to the group.
It would be nice if we could manage that group directly in FAS.
> By default people that are in the EMEA Ambassadors group in pagure
> receive email notifications for ticket creation, new comments, status
> updates in tickets, etc.
I don't think people should watch by default but to the
trackers/tickets they are interested in. The only people to watch by
* funding_requests: @famsco, regional treasurer, credit card holders
and IRC meeting chair
* swag_requests: Some person in Brno who is in charge of shipping swag.
This person does not exist. We need to talk about this process. We
cannot expect that Kveta will just ship because we have told her too.
She is a volunteer just like the rest of us :)
Let's think this through in a future meeting. For now, feel free to
ping me on shipping tickets and I will work with Kveta.
> * trac_obsolete: Nobody, it's obsolete
> > I'm still exploring the capabilities of pagure, so please correct me if
> > I did something wrong.
> I think you did a great job, but we should tighten privileges and privacy
> a bit.
> Thanks again for your hard work!
> Best regards,
> ambassadors mailing list -- ambassadors(a)lists.fedoraproject.org
> To unsubscribe send an email to ambassadors-leave(a)lists.fedoraproject.org