This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[RIPE Atlas Ambassadors] RIPE-Atlas-Ambassadors Digest, Vol 44, Issue 2
- Previous message (by thread): [RIPE Atlas Ambassadors] RIPE-Atlas-Ambassadors Digest, Vol 44, Issue 2
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Michal Krsek
michal at krsek.cz
Mon Jul 8 12:46:12 CEST 2024
Hello Lia, it would be quite good to share (and later update) the actual strategy. I think I can be close to 100% handing over probes in Prague (or Amsterdam) - with questionable service improvement, or more to 90% loss handing over probes in Burkina Faso, Cambodia - with huge service improvement in those countries. Countries (ASes) may be somehow added into ambassador scoring. With kind regards Michal On 08.07.2024 12:20, Lia Hestina wrote: > Hello Johan, > > I completely understand why you feel this way about your first batch > of probes. We're currently developing a strategy for deploying RIPE > Atlas probes to improve the network so we can better serve the > ambassador community and we'll be sharing this plan soon. > We're also working on the ambassador probe admin to allow you to write > off probes that are end-of-life, lost, or broken. This will help us > better understand the distribution and data too, as well as serve as a > basis for distributing new probes. > > Thank you for this feedback and continued support. > > Regards, > Lia > > > On Thu, 4 Jul 2024 at 15:15, Johan Bogg <johan at bogg.nu> wrote: > > Well I like the monthly report, it makes me feel inadequate and a > bit terrible seeing my first batch of probes all are dead now 10 > years later and I can't seem to get another batch to hand out... > > On Thu, 4 Jul 2024 at 14:47, Lia Hestina <lhestina at ripe.net> wrote: > > Dear Chris, > > Thanks for your email. The last report we sent out was on > March 1. Since then, we paused sending the monthly report as > we prepared to adhere with the new requirements for bulk email > senders. We posted a RIPE Labs article with information about > this topic: > https://labs.ripe.net/author/fergalc/enhancing-email-delivery-at-the-ripe-ncc/to > > We are also still looking for feedback from ambassadors on > whether the report is useful or should be discontinued. Once > we receive enough input, we will use it to help us form a more > effective and non-spammy report. > > Many thanks for your insightful input and for letting us know > you still want to receive the report. > > Kind regards, > Lia Hestina > RIPE NCC > > On Wed, 3 Jul 2024 at 13:41, Chris Carini > <chris at chriscarini.com> wrote: > > I, too, have not received a monthly Ambassador Report > email since January of this year - I had assumed it was > stopped for some reason. I'd like to receive them again, > if possible. Given there are a handful of folks chiming in > here stating they have not received emails, it makes me > wonder if there was some issue when migrating to "the new > system that activates the reports" you mentioned - perhaps > something for the RIPE team to investigate? I'd personally > like to start receiving these once again. > > Q1: 1. Do you find the monthly ambassador report useful in > its current format? > A1: (answering based on the last report I received, Jan of > this year) Yes, slightly. I wish the report was formatted > more nicely - I'm a visual person, and the report being > completely unformatted text makes it much more difficult > to process & digest. > > Q2: 2. Are there specific parts of the report you find > particularly helpful or relevant? > A2: I find the following helpful; (a) total number of > probes I've received, (b) connection rate, (c) newly > connected probes, if any, (d) total connected probes, (e) > historical ambassador credits, (f) which events were > attended, (g) which probes are disconnected. I find the > following unhelpful; (A) the length of the reminder to > tell probe hosts "You might want to remind your hosts who > have not plugged in their probes or whose probes are > disconnected and advise them on what steps to take to fix > each issue here: <link>" (suggestion: "You might want to > remind your hosts with disconnected probes what steps to > take: <link>"), (B) the troubleshooting link that follows > could have many more entries, IMO, (C) "You have no probes > with known USB issues" - great, but its not useful to me > then, so omit it. I'd only want to know if I have any that > do have known issues, but otherwise omit this please, (D) > no mention of what to do now that an ambassador has > distributed all the probes they were given (there used to > be a mention of what to do, but that seems to have gone > away; is that intentional because RIPE no longer wants the > Atlas network to grow? Is it because there is no longer > hardware available? Is it because RIPE would prefer hosts > use VMs instead? Is it just something that was > accidentally removed?) (E) a second reminder, just above > the 'probes that are disconnected', that states "You have > no ambassador probes that are experiencing USB stick issues". > > I also agree with Gavin, an "exception report" of sorts > would be handy to have, too, depending on what information > it provided, and how actionable it would be for > ambassadors. More specifically, I'd like to get an > "exception report" that contains (1) which probes were > disconnected for a longer period of time (once they have > been disconnected for longer than say 6 months), and (2) > what I can do about them. For (2), I'd want there to be > something actionable, and a way for me to 'dismiss / > ignore' this probe in future "exception reports". For > example, I gave a probe to a colleague years ago whose > house burnt down, they are ok, however their probe is long > gone - I don't want / need reminders about this probe ever > again, as it no longer exists. If this was the only probe > that would show up in the "exception report", I'd want a > way to acknowledge "yes, I'm aware or I know something is > wrong. please do not notify me of this probe being an > 'exception' again." > > Best, > Chris > > On Tue, Jul 2, 2024 at 3:00 AM > <ripe-atlas-ambassadors-request at ripe.net> wrote: > > Send RIPE-Atlas-Ambassadors mailing list submissions to > ripe-atlas-ambassadors at ripe.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://mailman.ripe.net/ > or, via email, send a message with subject or body > 'help' to > ripe-atlas-ambassadors-request at ripe.net > > You can reach the person managing the list at > ripe-atlas-ambassadors-owner at ripe.net > > When replying, please edit your Subject line so it is > more specific > than "Re: Contents of RIPE-Atlas-Ambassadors digest..." > > > Today's Topics: > > 1. Re: Ambassador Monthly Report (Gavin Tweedie) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 2 Jul 2024 17:48:56 +0800 > From: Gavin Tweedie <gav at narx.net> > To: ripe-atlas-ambassadors at ripe.net > Subject: Re: [RIPE Atlas Ambassadors] Ambassador > Monthly Report > Message-ID: > <1ebe91b0-8a20-4284-8dbd-e0f61e25bf2d at narx.net> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Hey Lia, > > I haven't had an ambassador report since March FYI. > I'll own up that I don't read them. I'd be happy to > swap it for an > exception report - what changed this week/month.. did > a probe go offline > and not come back? > > The ones that went dead years ago, are probably long > lost and not much > can be done about, but as soon as one goes offline for > a few days/week - > that'd be handy. A likely a lower aggregate email volume. > > > Gavin > > > On 2/7/2024 4:22 pm, Lia Hestina wrote: > > Hello Joe, > > > > The report was sent monthly to the email address > that the ambassador uses. > > It contains the following information: > > - News and update > > - Statistics about probe distribution > > - Connection rate of the distributed probes > > - Credits > > - Events you will be attending - when you tag > yourself here: > > > https://atlas.ripe.net/get-involved/community/#!conferences > > > > Regards, > > Lia Hestina > > p.s. It seems like your email was not connected to > the (then) new > > system that activates the report. > > > > On Tue, 2 Jul 2024 at 09:10, Joe Abley > <jabley at strandkip.nl> wrote: > > > > Hi Lia, > > > > I have never seen a monthly ambassador report. I > guess it's not > > sent to this list, since the archives don't > reveal any examples of > > it arriving here. Where is it sent? > > > > > > Joe > > > >> On 2 Jul 2024, at 08:15, Lia Hestina > <lhestina at ripe.net> wrote: > >> > >> ? > >> Dear all, > >> > >> You may have heard about the new requirements > for bulk email > >> senders based on changes made by large email > providers like > >> Google, Microsoft and Yahoo, which we wrote > about on RIPE Labs > >> [1]. Following these changes, we are reviewing > the emails that we > >> send out from RIPE Atlas. We want our emails to > be helpful and > >> contribute to your work. > >> > >> Our monthly ambassador report provides an > update on the status of > >> the probes in your account and other news. We > would like hear: > >> > >> 1. Do you find the monthly ambassador report > useful in its > >> current format? > >> 2. Are there specific parts of the report you > find particularly > >> helpful or relevant? > >> > >> > >> Your answers will help us work out how to best > share this > >> information with you, whether in a monthly > update or another > >> format. If you have any questions, please let > us know. > >> > >> Kind regards, > >> Lia Hestina > >> > >> [1] > >> > https://labs.ripe.net/author/fergalc/enhancing-email-delivery-at-the-ripe-ncc/ > >> _______________________________________________ > >> RIPE-Atlas-Ambassadors mailing list > >> RIPE-Atlas-Ambassadors at ripe.net > >> > https://mailman.ripe.net/ > > > > > > _______________________________________________ > > RIPE-Atlas-Ambassadors mailing list > > RIPE-Atlas-Ambassadors at ripe.net > > > https://mailman.ripe.net/ > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > </ripe/mail/archives/ripe-atlas-ambassadors/attachments/20240702/aed8cf2a/attachment-0001.html> > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > RIPE-Atlas-Ambassadors mailing list > RIPE-Atlas-Ambassadors at ripe.net > https://mailman.ripe.net/ > > > ------------------------------ > > End of RIPE-Atlas-Ambassadors Digest, Vol 44, Issue 2 > ***************************************************** > > _______________________________________________ > RIPE-Atlas-Ambassadors mailing list > RIPE-Atlas-Ambassadors at ripe.net > https://mailman.ripe.net/ > > _______________________________________________ > RIPE-Atlas-Ambassadors mailing list > RIPE-Atlas-Ambassadors at ripe.net > https://mailman.ripe.net/ > > > _______________________________________________ > RIPE-Atlas-Ambassadors mailing list > RIPE-Atlas-Ambassadors at ripe.net > https://mailman.ripe.net/ -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/ripe-atlas-ambassadors/attachments/20240708/b32b7acd/attachment-0001.html>
- Previous message (by thread): [RIPE Atlas Ambassadors] RIPE-Atlas-Ambassadors Digest, Vol 44, Issue 2
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]