ambassadors April 2017

ambassadors@lists.fedoraproject.org

28 participants
40 discussions

Motorola Lapdock Donation
by Mike DePaulo 15 Aug '17

15 Aug '17

Hi everyone, I have a new spare Motorola Atrix Lapdock that I could donate. You can hook it up to a raspberry pi with a few adapters/cables: http://www.instructables.com/id/The-Raspberry-Pi-Lapdock-Connection/ "The lapdock incorporates a razor-sharp 11" HDMI display, an almost-adequate keyboard-with-trackpad, twin speakers, and a high-capacity battery -- all in a thin two-pound package." (Note: "razor-sharp" == 1366x768.) Are any regions interested in receiving it? -Mike

4 7

EMEA Trac migrated to Pagure
by Zacharias Mitzelos 04 Jul '17

04 Jul '17

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

7 12

Re: Rootconf + DevConf India
by Zamir Sun 28 Apr '17

28 Apr '17

(Involve ambassador list.) Hi PJP, As we talked before, apac@lists is mainly used for easy subscription to tickets on apac trac (now pagure) and not for discussion. So please keep send emails to Ambassador list. Thanks. On Fri, Apr 28, 2017 at 1:01 PM, P J P <pjp(a)fedoraproject.org> wrote: > Hello, > > Ever wondered what Site Reliability Engineering(SRE) is all about? > > Come participate at Rootconf! Learn about monitoring tools; Securing your > infrastructure > with Vault and SELinux; Building reliable monitoring systems using anomaly > detection and NLP; > Capacity planning; and MySQL + PostgreSQL. > > Dates: 11 - 12 May 2017 > Venue: MLR Convention Centre, J P Nagar, Bengaluru, Karnataka, India. > > Red Hat and Linux Foundation are co-hosting DevConf at Rootconf on 11-12 > May. > You can get training on Ansible and SELinux on 11 May, and listen to talks > on platform technologies > such as - OpenStack, Docker and Kubernetes – on 12 May. > > Rootconf has offered *10% discount to Fedora community* members. Click > link below to avail the discounts: > > -> https://rootconf.in/2017/?code=BWPMVO-Fedora > > For more details about training workshops, Icinga Camp, disaster stories > flash talk session, > volunteering and other activities around Rootconf > > See -> https://rootconf.in/2017 > > If you have questions, call HasGeek on 7676332020 or shoot an email to > info(a)hasgeek.com. > > Thank you. > --- > -P J P > http://feedmug.com > > _______________________________________________ > apac mailing list -- apac(a)lists.fedoraproject.org > To unsubscribe send an email to apac-leave(a)lists.fedoraproject.org > >

1 0

FAmNA meeting minutes 4/27/2017
by Andrew Ward 27 Apr '17

27 Apr '17

All, Please review our meeting minutes from 27 Apr 2017 ********************Special Note to North America Ambassadors****************************** There will be no meeting until 18 May 2017. If there is an urgent matter that needs attention please email me and your regional leader, Ben Williams/Nick Bebout/Brian Monroe. Again there will be no meeting until 18 May 2017. ****************************end of Note************************************************** Minutes: https://meetbot.fedoraproject.org/fedora-meeting/2017-04-28/famna.2017-04-2… Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting/2017-04-28/famna.2017-04-2… Log: https://meetbot.fedoraproject.org/fedora-meeting/2017-04-28/famna.2017-04-2… -- V/R Andrew Ward award3535(a)fedoraproject.org award3535(a)tds.net award3535(a)gmail.com

1 0

[FAmSCo] Ambassador's inactivity: policy change proposal
by Robert Mayr 27 Apr '17

27 Apr '17

Dear all, we have just finished our regular ambassador's activity check and set the ambassador's accounts which were not active for the last 18 months to "inactive". See our policy if you are not comfortable with this: https://fedoraproject.org/wiki/Ambassadors/MembershipService#Inactive_Ambas… However, the Infrastructure team raised some concerns about this rule, as we are setting accounts globally as inactive/disabled, and they asked the Council for a project wide decision to make that happen. The Council will discuss if we will have this policy or not, but also advised FAmSCo to handle this issue in the meanwhile by removing those accounts from the FAS group, instead of setting them to inactive. I have written down a proposal, where you will find more informations about the process and about how we would like to reactivate people if they like to come back. Please read it carefully and look also into the discussions on Infra and Council pagure before making your own opinion. FAmSCo is going to follow the Council's advise, but for openness and transparency we would like to get community feedback, as we did when this rule has been put in place. We also want to get this discussed during your next regional meeting, so if we miss to reach out to your chairs and anyone of you is attending the next meeting, please add it to your agenda. Please use this discussion if you like to give us feedback. Thank you. Kind regards. -- Robert Mayr (robyduck)

3 3

[Fedocal] Reminder meeting : APAC Ambassador's bi-weekly meeting
by pjp＠fedoraproject.org 27 Apr '17

27 Apr '17

Dear all, You are kindly invited to the meeting: APAC Ambassador's bi-weekly meeting on 2017-04-28 from 05:00:00 to 06:00:00 UTC At fedora-meeting(a)irc.freenode.net The meeting will be about: Hello, This is a friendly reminder to APAC Fedora Ambassadors, about our bi-weekly IRC meeting tomorrow. Please join in: #fedora-meeting on irc.freenode.net at 05:00 hrs. UTC. Thank you. Source: https://apps.fedoraproject.org/calendar/meeting/3844/

1 0

EMEA Ambassadors Meeting Minutes 2016-04-26
by Nemanja Milosevic 26 Apr '17

26 Apr '17

Hey Ambassadors, We had our regular EMEA meeting, it lasted about 35 minutes and 7 people attended. See below for more information regarding the meeting: Minutes: https://meetbot.fedoraproject.org/fedora-meeting/2017-04-26/emea_ambassador… Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting/2017-04-26/emea_ambassador… Log: https://meetbot.fedoraproject.org/fedora-meeting/2017-04-26/emea_ambassador… See you again in two weeks. Nemanja

1 0

[FAmSCo] New mentor nomination and removal process
by Robert Mayr 26 Apr '17

26 Apr '17

Dear all, One of the main missions of the current FAmSCo is to retool the ambassadors processes. The mentor’s nomination process is one of the topics we discussed during these first weeks. We already agreed unanimously on a new process, but for openness and transparency, we would like to get some feedback, if there are some points which need to be improved or clarified. Currently, the mentor nominating process says that only FAmSCo members or other mentors can nominate a new mentor and that FAmSCo will vote for approval. There is no rule for removing mentors. While this worked fine for many years, it seems the process is now stuck. FAmSCo wants to make this process more dynamic and one where people can more easily become an ambassador-mentor, but not for life. Mentoring is a rather hard job and sometimes very time-consuming. After some years of doing this job you grow personally and it is very rewarding, but there is also a high chance you could burn out. By adding a removal process we are making it easier for people to step back and realize they don’t have to do this forever. We are also creating a structure to have this conversation in. == Nomination Process == 1) Who can nominate a new mentor? * A mentor or a FAmSCo member * A Region* *NOTE: Regions need at least 5 +1s to nominate new mentors. 2) Where do they file a ticket? Instead of filing the request about a new mentor in the FAmSCo pagure, we want people to file these tickets in the FAmA pagure, because we prefer if mentors vote about other mentors. The new process will look like this: a) After nomination by a FAmSCo member, a mentor or a Region, the process starts with a ticket in the FAmA pagure, where mentors will be asked to give their +1/0/-1 to the nomination. As per lazy consensus, all votes with 0 or -1 have to be explained with a reason. Once the nominee gets at least 3 +1s, his nomination counts as “mentor-approved”. b) At this point, the person who nominated the new mentor, should file a ticket in the FAmSCo pagure, adding the FAmA in CC for any notification. c) Final approval is still done by FAmSCo, but there will be no extra voting session. Instead, in the ticket, FAmSCo will ask if anyone has any concerns about the new (and already approved) mentor. If nobody has concerns the new mentor gets appointed and FAmA will make all administrative actions required to give the new mentor the correct permissions. d) If FAmSCo has a concern, FAmSCo will discuss the reason and do a final vote. A valid quorum (50% +1) is needed to make this decision, even on pagure. == Availability == FAmA will check every mentor’s availability and/or activity once a year and update the wiki page accordingly. This can be done with a simple survey, where mentors can just flag their actual state. Mentors can also respond by telling FAmA they are not available. == Removal Process == Similarly to nomination, FAmSCo is introducing a removal process, which we want as dynamic as the nomination process. * Asking for the removal of a mentor can be done by a mentor, a FAmSCo member or by the region. The region must have at least 5 +1s. * Tickets have to be opened in the FAmSCo pagure and very clear reasons for the removal need to be provided!!! * Mentors are asked to provide feedback. Local regional specific feedback is critical and feedback from a local mentor will help FAmSCo make a decision. * FAmSCo votes on the proposal after at least 2 weeks, to give mentors time to provide feedback. If approved, FAmSCo asks FAmA to take action to process the removal. Also, a mentor can be removed by: * Asking to step down, by filing a ticket in the FAmA pagure (this is just to track his decision, FAmA can take immediate action) * Being set as not available for more than 12 months. At this point the mentor will automatically be removed by FAmA Kind regards. -- Robert Mayr (robyduck)

3 3

[FAmSCo] FAmSCo meeting minutes 2017-04-26
by Robert Mayr 26 Apr '17

26 Apr '17

Hi all, we had a regular FAmSCo meeting today (6 members of 7 showed up) and discussed mainly these topics: * Mentor's activity: we still need to update the wiki page, but want some feedback for the new mentor nomination and removal process (as per email of friday 21st) https://lists.fedoraproject.org/archives/list/ambassadors@lists.fedoraproje… * Ambassador's activity: inactive ambassadors have been set to "inactive", but due to Infra concerns and Council advise, we want to change the policy slightly and remove them immediately from the FAS group (next time we run the script). I'll come up with a separate email, for which we are asking for community feedback again. https://pagure.io/famsco/issue/424 * Swags: possible replacements of DVDs, a specific ticket will follow. If you'd like to read more, go to the minutes: https://meetbot.fedoraproject.org/fedora-meeting-2/2017-04-26/famsco.2017-0… Kind regards. -- Robert Mayr (robyduck)

1 0

[FAmSCo] Meeting tomorrow 2017-04-26 15UTC
by Robert Mayr 25 Apr '17

25 Apr '17

Hi all, we'll have another meeting tomorrow, agenda will look like this: * Finalize mentor's status (giannisk, please give us an update on pagure if you cannot attend the meeting) * Change of the ambassadors inactivity rule, see ticket #424 https://pagure.io/famsco/issue/424 * Check past actions and Open Floor If you have anything to add, please do. See you tomorrow. Regards. -- Robert Mayr (robyduck)

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

ambassadors April 2017