Hello EMEA Ambassadors,
I completed the trac migration from fedorahosted to pagure. The visibility has been set to private, since there is sensitive information like home addresses, receipts, phone numbers, etc attached to the tickets. There are a couple of active tickets in the trac, that I will transfer to the new issue trackers soon. You can find the migrated trac here[1]. Please do not open new tickets there, use the other issue trackers to request funding or swag.
I have created another issue tracker for funding requests[2], 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). There is also an issue tracker for swag requests[3] that is set to private (because it contains private information like addresses and phone numbers).
All of the repositories/issue trackers I mentioned can be found under the EMEA Ambassadors group in pagure[4]. Members of this group can see the private issue trackers, add comments to private tickets, change the status of tickets, and many more. I added some EMEA Ambassadors to the group. If you have not been added, you can ping me(off-list or in Telegram) or someone else that is in the group to add you. Please don't add people to the group that are not EMEA Ambassadors.
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. You can stop receiving notifications by visiting the specific project and click the stop watching button. For example, you might want to unsubscribe from the swag_requests tracker.
I'm still exploring the capabilities of pagure, so please correct me if I did something wrong.
Many thanks to jflory7 and nmilosev for their help during the migration!
Cheers, Zach
[1] https://pagure.io/ambassadors-emea/trac_obsolete [2] https://pagure.io/ambassadors-emea/funding_requests [3] https://pagure.io/ambassadors-emea/swag_requests [4] https://pagure.io/group/ambassadors-emea
-- Zacharias Mitzelos <mitzie at mitzelos dot com> mitzie on freenode http://zacharias.mitzelos.com
Am 27.02.2017 um 12:18 schrieb Zacharias Mitzelos:
Hello EMEA Ambassadors, I completed the trac migration from fedorahosted to pagure. The
thank you!
Thanks for the migration!
On 27.2.2017 12:18, Zacharias Mitzelos wrote:
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. You can stop receiving notifications by visiting the specific project and click the stop watching button. For example, you might want to unsubscribe from the swag_requests tracker.
I've just got e-mail with this link:
https://pagure.io/ambassadors-emea/trac_obsolete/issue/653
But that page says 403 Forbidden (even when I'm logged in).
On 27.2.2017 21:28, Miro Hrončok wrote:
Thanks for the migration!
On 27.2.2017 12:18, Zacharias Mitzelos wrote:
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. You can stop receiving notifications by visiting the specific project and click the stop watching button. For example, you might want to unsubscribe from the swag_requests tracker.
I've just got e-mail with this link:
https://pagure.io/ambassadors-emea/trac_obsolete/issue/653
But that page says 403 Forbidden (even when I'm logged in).
Oh, maybe because I'm not yet in the group, sorry about the noise.
This is awesome work, thank you so much mitzie! :)
Kind regards, Nemanja
2017-02-27 12:18 GMT+01:00 Zacharias Mitzelos mitzie@mitzelos.com:
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[2], 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.
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 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[4]. 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 instances.
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 default are * 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. * 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, Christoph
On Tue, Mar 7, 2017, at 10:40 AM, Christoph Wickert wrote:
2017-02-27 12:18 GMT+01:00 Zacharias Mitzelos mitzie@mitzelos.com:
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[2], 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 some point).
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[4]. 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 instances.
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 default are
- 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.
regards,
bex
- 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, Christoph _______________________________________________ ambassadors mailing list -- ambassadors@lists.fedoraproject.org To unsubscribe send an email to ambassadors-leave@lists.fedoraproject.org
Hello everyone,
For a strange reason I never saw Christoph's response in the first place, sorry for the late reply. Kudos to tyll for the reminder
About the admin privileges the whole ambassadors-emea[1] group has over the 4 issue trackers we have for EMEA Ambassadors in pagure, this is mainly for visibility purposes. The problem is that if the ambassadors-emea group is not an admin in the repos, the repositories will not be visible in the ambassadors-emea page[1], and people will have to manually search and find the repos (since they won't be displayed in the group). Even if we give commit access to the group, the repos still wouldn't be displayed in the main group page. During setup, I noticed how other projects deal with this, and many of them had given to the whole group admin privileges for exactly this reason (see Design, Commops, Marketing, etc). Unfortunately this is how pagure is configured.
On the other hand, I realize how dangerous this is, as everyone could delete/edit tickets or even delete the whole tracker.
What are your thoughts on this?
By the way, a few days ago I changed the funding_requests tracker from public to private, because it now contains sensitive information (receipts and paypal addresses).
Cheers, Zach
[1] https://pagure.io/group/ambassadors-emea
--- Zacharias Mitzelos <mitzie at mitzelos dot com> mitzie on freenode http://zacharias.mitzelos.com
2017-02-27 12:18 GMT+01:00 Zacharias Mitzelos mitzie@mitzelos.com:
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. You can stop receiving notifications by visiting the specific project and click the stop watching button. For example, you might want to unsubscribe from the swag_requests tracker.
Hi Zach,
I'm afraid this still does not work correctly, I still get mail for new tickets, e,.g. https://pagure.io/ambassadors-emea/funding_requests/issue/23 which was just opened yesterday.
I even get mails for old tickets that I unsubscribed from.
I checked I'm not watching any of https://pagure.io/ambassadors-emea/trac_obsolete https://pagure.io/ambassadors-emea/funding_requests https://pagure.io/ambassadors-emea/swag_requests
Can you tell me why I'm still getting mail?
Best regards, Christoph
On Mon, Jul 03, 2017 at 12:29:57PM +0200, Christoph Wickert wrote:
2017-02-27 12:18 GMT+01:00 Zacharias Mitzelos mitzie@mitzelos.com:
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. You can stop receiving notifications by visiting the specific project and click the stop watching button. For example, you might want to unsubscribe from the swag_requests tracker.
Hi Zach,
I'm afraid this still does not work correctly, I still get mail for new tickets, e,.g. https://pagure.io/ambassadors-emea/funding_requests/issue/23 which was just opened yesterday.
It looks like the entire https://pagure.io/group/ambassadors-emea groups has commit access to the project, so everyone in that group will receive notifications about (private) tickets.
Pierre
2017-07-03 12:42 GMT+02:00 Pierre-Yves Chibon pingou@pingoured.fr:
On Mon, Jul 03, 2017 at 12:29:57PM +0200, Christoph Wickert wrote:
I'm afraid this still does not work correctly, I still get mail for new tickets, e,.g. https://pagure.io/ambassadors-emea/funding_requests/issue/23 which was just opened yesterday.
It looks like the entire https://pagure.io/group/ambassadors-emea groups has commit access to the project, so everyone in that group will receive notifications about (private) tickets.
What is the easiest way to solve this? Client-side to delete unwanted mails would delete relevant ones as well.
I've filed a feature request at https://pagure.io/pagure/issue/2396 but I wonder if there is something we can change in the configuration. I really don't think all ambassadors want every ticket by default.
Best regards, Christoph
Just checked the team and repo configuration and I couldn't find something to turn off the email notifications.
Pingou, any ideas?
Cheers, Zach
-- Zacharias Mitzelos <mitzie at mitzelos dot com> mitzie on freenode http://zacharias.mitzelos.com
On Tue, Jul 4, 2017, at 13:14, Christoph Wickert wrote:
2017-07-03 12:42 GMT+02:00 Pierre-Yves Chibon pingou@pingoured.fr:
On Mon, Jul 03, 2017 at 12:29:57PM +0200, Christoph Wickert wrote:
I'm afraid this still does not work correctly, I still get mail for new tickets, e,.g. https://pagure.io/ambassadors-emea/funding_requests/issue/23 which was just opened yesterday.
It looks like the entire https://pagure.io/group/ambassadors-emea groups has commit access to the project, so everyone in that group will receive notifications about (private) tickets.
What is the easiest way to solve this? Client-side to delete unwanted mails would delete relevant ones as well.
I've filed a feature request at https://pagure.io/pagure/issue/2396 but I wonder if there is something we can change in the configuration. I really don't think all ambassadors want every ticket by default.
Best regards, Christoph
On Tue, Jul 04, 2017 at 12:14:25PM +0200, Christoph Wickert wrote:
2017-07-03 12:42 GMT+02:00 Pierre-Yves Chibon pingou@pingoured.fr:
On Mon, Jul 03, 2017 at 12:29:57PM +0200, Christoph Wickert wrote:
I'm afraid this still does not work correctly, I still get mail for new tickets, e,.g. https://pagure.io/ambassadors-emea/funding_requests/issue/23 which was just opened yesterday.
It looks like the entire https://pagure.io/group/ambassadors-emea groups has commit access to the project, so everyone in that group will receive notifications about (private) tickets.
What is the easiest way to solve this? Client-side to delete unwanted mails would delete relevant ones as well.
I've filed a feature request at https://pagure.io/pagure/issue/2396 but I wonder if there is something we can change in the configuration. I really don't think all ambassadors want every ticket by default.
There are two changes that can be done atm: - Drop the ambassadors-emea group in favor of just who wants the access - Give the group a "ticket" level (instead of commit) so at least private tickets aren't sent to everyone.
We'll be re-working the notification settings in a bit (the drop-down menu on the top right) so that you can disable all notifs but the ones about your tickets and when you are explicitly mentioned.
Hope this helps, Pierre
ambassadors@lists.fedoraproject.org
-
Brian Exelbierd -
Christoph Wickert -
Joerg Simon -
Miro Hrončok -
Nemanja Milosevic -
Pierre-Yves Chibon -
Zacharias Mitzelos