apac June 2017

apac@lists.stg.fedoraproject.org

2 participants
8 discussions

[ambassadors-apac] Issue #266: Active Fedoraproject Weibo account by mobile number
by Ziqian SUN (Zamir) 30 Aug '17

30 Aug '17

zsun reported a new issue against the project: `ambassadors-apac` that you are following: `` # Background In China, Fedoraproject weibo account is the only social network account we can use in China for promotion. It was registered with ```legal # fedoraproject.org``` in the early days as organization account. Since it has not been verified for a long time, the weibo account is now dropped back to personal account earlier (maybe since 2015). Now due to legal changes in China, in order to use network services, we need to authenticate the network service with either our ID, or a mobile number. So we've been not able to use it since last December. # Proposed solutioins ## Primary : Google Voice US mobile number is allowed by weibo. So we want to try if Google Voice works. In this way, we will ask some Fedora contributor to help us active a Google Voice number, and then we authenticate the Weibo account with the Google Voice number. Pro: This costs nothing at the moment. And easy to transfer if weibo account will be maintained by someone else. And it do not need a ID. Con: If we lost the Google Voice number, it would be an issue. ## Fallback: Buy a Chinese SIM for the community in China In this way, I need to buy a SIM with my own identity. And all related legal issue should be dealt myself. Pro: No risk of loss to the number Con: Takes quiet some paper work to transfer if I am no longer maintaining the weibo account. And I have to take sole legal responsibility for everything happened on the account. Besides, it will take about CNY120 (a little less than USD 20 ) per year. We prefer Google Voice way first and Chine SIM card way is a fallback. We need your ideas/approvals before raise this to council. `` To reply, visit the link below or just reply to this email https://pagure.io/ambassadors-apac/issue/266

4 8

[ambassadors-apac] Issue #267: Funding request for community card during LinuxCon Beijing
by Ziqian SUN (Zamir) 14 Aug '17

14 Aug '17

zsun reported a new issue against the project: `ambassadors-apac` that you are following: `` In planning for LinuxCon Beijing, we decide to make a community card for general using of leaving community contact, like the following. https://github.com/FZUG/linuxcon2017/blob/master/generic_contact_card_back.… https://github.com/FZUG/linuxcon2017/blob/master/generic_contactcard.svg It serves like, when people asking about development, we will write devel@lists before the fedoraproject.org, and when asking about generally thing to Fedora, we will write chinese@lists etc. It is not a big amount of money so I paid from my pocket. But today Bex suggested that we should file a reimbursement for this. So I am here writing this request. community card for 1000 pcs costs in total: CNY 22.5 ~ USD 3.38 as of today. Paypal: sztsian #AT# gmail.com `` To reply, visit the link below or just reply to this email https://pagure.io/ambassadors-apac/issue/267

4 11

F26 DVDs
by P J P 30 Jun '17

30 Jun '17

Hello, F26 release is just around the corner now. If you need F26 Workstation DVDs for release parties or other events you are planning, please update the sheet below -> https://ethercalc.org/f26-dvd-apac Thank you. --- -P J P http://feedmug.com

1 0

[ambassadors-apac] Issue #264: Travel Subsidy for tenchokden for Nullcon 2017.
by Brian Exelbierd (bex) 29 Jun '17

29 Jun '17

bex added a new comment to an issue you are following: `` I've moved this charge to FY18. The full explanation is in the commit message below. As APAC has spent no money so far this year, I don't believe this will cause a problem. If APAC runs out of money, we can discuss finding a way to fix this. commit 85213b6ccc74284a3ba6a5b642ad7ba02cca6b73 Author: Brian (bex) Exelbierd <bex(a)pobox.com> Date: Thu Jun 29 12:19:08 2017 +0200 Moving nullcon txn from FY17 to FY18 This expense was paid with FY18 money Even though the event occurred in FY17, FY17 closed on 28 Feb 2018 ANY CHARGES occuring after that time are FY18 costs. In the future, please work with the FCAIC in these situations as we may be able to get the costs to land in the correct year. `` To reply, visit the link below or just reply to this email https://pagure.io/ambassadors-apac/issue/264

1 0

[ambassadors-apac] Issue #264: Travel Subsidy for tenchokden for Nullcon 2017.
by Ziqian SUN (Zamir) 01 Jun '17

01 Jun '17

The issue: `Travel Subsidy for tenchokden for Nullcon 2017.` of project: `ambassadors-apac` has been reset by zsun. https://pagure.io/ambassadors-apac/issue/264

1 0

[ambassadors-apac] Issue #264: Travel Subsidy for tenchokden for Nullcon 2017.
by Ziqian SUN (Zamir) 01 Jun '17

01 Jun '17

The status of the issue: `Travel Subsidy for tenchokden for Nullcon 2017.` of project: `ambassadors-apac` has been updated to: Closed as Fixed by zsun. https://pagure.io/ambassadors-apac/issue/264

1 0

[ambassadors-apac] Issue #264: Travel Subsidy for tenchokden for Nullcon 2017.
by Ziqian SUN (Zamir) 01 Jun '17

01 Jun '17

zsun added a new comment to an issue you are following: `` I'm closing this ticket since it's done and not handled by APAC. `` To reply, visit the link below or just reply to this email https://pagure.io/ambassadors-apac/issue/264

1 0

[ambassadors-apac] Issue #264: Travel Subsidy for tenchokden for Nullcon 2017.
by Ziqian SUN (Zamir) 31 May '17

31 May '17

zsun added a new comment to an issue you are following: `` I have a lot of complaints for this ticket. Firstly, as mentioned in APAC process, > $300-1000 USD = The request requires approval from the appropriate regional community (APAC, EMEA, LATAM, or NA) > At least five (5) individual FAm votes required at APAC FAm Bi-Weekly meeting I don't see any meeting results for this, neither anyone voting on this ticket. I also even don't see izhar officially approve the ticket. I checked the air ticket provided in this request, as well as NullCon website, it shows that it happens in FY2018 instead of FY 2017. > Conference: 3rd - 4th Mar 2017 So based on the time, I see Izhar and kushal's comment invalid since they are commenting for FY2017 not for FY2018. And how come a request get reimbursed without a approved tag? Are we still following APAC guideline? `` To reply, visit the link below or just reply to this email https://pagure.io/ambassadors-apac/issue/264

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

apac June 2017