Side note: I traveled to Prague, Czech after the summit and took a connection flight Prague-Munich-Beijing. There was no price difference for the flight Munich-Beijing and Prague-Munich-Beijing when I bought the ticket. Reproducible: Always
Created attachment 594210 [details] flight_itinerary-invoice.pdf
FYI: Of the flight invoice, the amount of 6057CNY is 857.40USD according to today's google.
In line with previous GSOC reimbursements, can you please provide a capture of quoting from when you purchased your ticket showing that there was no price difference between the routings PEK-MUC,MUC-PEK vs PEK-MUC,PRG-MUC-PEK.
also, please provide the paypal-linked email address to send the reimbursement to.
Created attachment 594532 [details] LH-price.png Sorry this is my first GSoC Summit. I didn't know I needed to provide proof for flight ticket prices. I went to do an example search for flights from Nov. 23 to Nov. 30. It turned out that for the same flight PRG-MUC-PEK is cheaper than MUC-PEK along. So it could happen that they were the same. Do you think that's enough? Sorry for not preparing it ahead of time.
(In reply to Robin Johnson from comment #4) > also, please provide the paypal-linked email address to send the > reimbursement to. I am having trouble adding a bank account to Paypal. I am trying to figure it out. In the mean time, is there any other way of receiving the reimbursement?
(In reply to Benda Xu from comment #5) > Created attachment 594532 [details] > LH-price.png > > Sorry this is my first GSoC Summit. I didn't know I needed to provide proof > for flight ticket prices. > > I went to do an example search for flights from Nov. 23 to Nov. 30. It > turned out that for the same flight PRG-MUC-PEK is cheaper than MUC-PEK > along. So it could happen that they were the same. > > Do you think that's enough? Sorry for not preparing it ahead of time. Yes, thank you. I can take this as proof that it's enough. We should put together a small FAQ for Gentoo mentors travelling to the summit, so they know more of these details ahead of time (any travel arrangement that's not more expensive than reasonable flight routing is acceptable) (In reply to Benda Xu from comment #6) > (In reply to Robin Johnson from comment #4) > > also, please provide the paypal-linked email address to send the > > reimbursement to. > > I am having trouble adding a bank account to Paypal. I am trying to figure > it out. In the mean time, is there any other way of receiving the > reimbursement? Paypal & US bank cheques are the options available to us at this time. If you can't add it directly due to national limitations (e.g. I don't know if Paypal supports Chinese bank accounts for reasons of politics), then we can look for pass-through means to get you reimbursed.
(In reply to Robin Johnson from comment #7) > (In reply to Benda Xu from comment #5) > > Created attachment 594532 [details] > > LH-price.png > > > > Sorry this is my first GSoC Summit. I didn't know I needed to provide proof > > for flight ticket prices. > > > > I went to do an example search for flights from Nov. 23 to Nov. 30. It > > turned out that for the same flight PRG-MUC-PEK is cheaper than MUC-PEK > > along. So it could happen that they were the same. > > > > Do you think that's enough? Sorry for not preparing it ahead of time. > Yes, thank you. I can take this as proof that it's enough. Thank you, Robin! > We should put together a small FAQ for Gentoo mentors travelling to the > summit, so they know more of these details ahead of time (any travel > arrangement that's not more expensive than reasonable flight routing is > acceptable) Way to go. Now that I have went through the process, feel free to call me up for inputs for the FAQs. > (In reply to Benda Xu from comment #6) > > (In reply to Robin Johnson from comment #4) > > > also, please provide the paypal-linked email address to send the > > > reimbursement to. > > > > I am having trouble adding a bank account to Paypal. I am trying to figure > > it out. In the mean time, is there any other way of receiving the > > reimbursement? > > Paypal & US bank cheques are the options available to us at this time. If > you can't add it directly due to national limitations (e.g. I don't know if > Paypal supports Chinese bank accounts for reasons of politics), then we can > look for pass-through means to get you reimbursed. No worries. I have a US-based bank account and for what we have Paypal is the most convenient way for us. I will sort it through and get back to you ASAP. Thank you!
Dear Robin, (In reply to Robin Johnson from comment #4) > also, please provide the paypal-linked email address to send the > reimbursement to. My Paypal-linked email address is <heroxbd@hotmail.com>. I have finally resolved all the banking issues and am ready to go ;) Yours, Benda
857.40USD sent today. Please confirm that you have gotten it.
(In reply to Robin Johnson from comment #10) > 857.40USD sent today. Please confirm that you have gotten it. Thanks Robin. I have gotten the fund.
Shall we close this bug?
I have doubts whether posting your booking reference number publicly is a good idea. Knowing this number, it might be possible to log on into an airline travel itinerary portal and then learn your private data like passport number, frequent flyer card number, sometimes even home address. That's why it would probably be better if access to these bugs or at least attachments got restricted when they are being filled already. This comment applies also to other GSoC reimbursement bugs.
(In reply to Maciej S. Szmigiero from comment #13) > I have doubts whether posting your booking reference number publicly is a > good > idea. > > Knowing this number, it might be possible to log on into an airline travel > itinerary portal and then learn your private data like passport number, > frequent > flyer card number, sometimes even home address. > That's why it would probably be better if access to these bugs or at least > attachments got restricted when they are being filled already. > > This comment applies also to other GSoC reimbursement bugs. The airline portals at present permit looking at active & future reservations, but not historic ones. It's always been up to the person if they would like the attachments & specific comments restricted. However as a matter of principle, we do not restrict the entire bug, because of the intent of transparency in our finances. The great many of them have the sensitive details that the owners cared about already redacted.
heroxbd: Reimbursement bugs remain open until they are reconciled with the accounting process.
(In reply to Maciej S. Szmigiero from comment #13) > I have doubts whether posting your booking reference number publicly is a > good > idea. > > Knowing this number, it might be possible to log on into an airline travel > itinerary portal and then learn your private data like passport number, > frequent > flyer card number, sometimes even home address. > That's why it would probably be better if access to these bugs or at least > attachments got restricted when they are being filled already. > > This comment applies also to other GSoC reimbursement bugs. Thank you Maciej for your reminder. I will be careful next time. For this case I am going to leave it as is. Benda
Reimbursement received. Thanks!
