Stream: t-compiler/wg-learning

Topic: Meeting 2020.03.03


mark-i-m (Mar 03 2020 at 18:40, on Zulip):

@WG-learning Meeting in 20 minutes

mark-i-m (Mar 03 2020 at 18:40, on Zulip):

:wave:

Santiago Pastorino (Mar 03 2020 at 19:00, on Zulip):

@WG-learning meeting time! :wave: everyone, please add your :wave: so we know who is participating

Santiago Pastorino (Mar 03 2020 at 19:01, on Zulip):

so the goal of this meeting is to decide what is going to be our focus for the next 2 months, so March and April

Santiago Pastorino (Mar 03 2020 at 19:01, on Zulip):

in this document https://hackmd.io/75x4U2e1Qp2f-lg7V09nGA?both

Santiago Pastorino (Mar 03 2020 at 19:01, on Zulip):

going to paste what's relevant here

Santiago Pastorino (Mar 03 2020 at 19:01, on Zulip):

we have a set of ideas that we may want to accomplish

Santiago Pastorino (Mar 03 2020 at 19:01, on Zulip):
Santiago Pastorino (Mar 03 2020 at 19:02, on Zulip):

my proposal for the meeting is:

Santiago Pastorino (Mar 03 2020 at 19:03, on Zulip):
  1. discuss if we want to accomplish those tasks and define them a bit better
Santiago Pastorino (Mar 03 2020 at 19:03, on Zulip):
  1. prioritize the ones we pick to go after
Santiago Pastorino (Mar 03 2020 at 19:04, on Zulip):
  1. decide what's doable to accomplish in the next 2 months
Santiago Pastorino (Mar 03 2020 at 19:04, on Zulip):

does this plan sound good?

Santiago Pastorino (Mar 03 2020 at 19:04, on Zulip):

ok, let's proceed then

Santiago Pastorino (Mar 03 2020 at 19:04, on Zulip):

1. discuss if we want to accomplish those tasks and define them a bit better

Santiago Pastorino (Mar 03 2020 at 19:05, on Zulip):

we have these tasks

Santiago Pastorino (Mar 03 2020 at 19:05, on Zulip):
Santiago Pastorino (Mar 03 2020 at 19:05, on Zulip):

removed sub-bulleting for brevity

Santiago Pastorino (Mar 03 2020 at 19:06, on Zulip):

those are all things I'd like to accomplish at some point

LeSeulArtichaut (Mar 03 2020 at 19:06, on Zulip):

Overview is already WIP, I'd guess it has already recieved enough feedback to push it in the next 2 months

Santiago Pastorino (Mar 03 2020 at 19:06, on Zulip):

but that's obvious because I was the one that wrote the most polemic ones :joy:

Chris Simpkins (Mar 03 2020 at 19:07, on Zulip):

Can you elaborate on what "how we want to structure the Guide" means?

Santiago Pastorino (Mar 03 2020 at 19:08, on Zulip):

ok yeah I can elaborate that instead of wasting time trying to make checkboxes on the list :P

mark-i-m (Mar 03 2020 at 19:08, on Zulip):

Zulip...

Santiago Pastorino (Mar 03 2020 at 19:09, on Zulip):

so what I meant is ... I have the feeling that the order of the chapters could be improved

Santiago Pastorino (Mar 03 2020 at 19:09, on Zulip):

some things could be moved to forge

Santiago Pastorino (Mar 03 2020 at 19:09, on Zulip):

like for instance ...

Santiago Pastorino (Mar 03 2020 at 19:09, on Zulip):

https://rust-lang.github.io/rustc-guide/stability.html

Santiago Pastorino (Mar 03 2020 at 19:09, on Zulip):

and things like that

Santiago Pastorino (Mar 03 2020 at 19:09, on Zulip):

not saying that that's not important

Santiago Pastorino (Mar 03 2020 at 19:10, on Zulip):

my feeling is ... as @nikomatsakis once said, we need to make the guide more focused on understanding how the Rust compiler works

LeSeulArtichaut (Mar 03 2020 at 19:10, on Zulip):

But it's not required to understand the compiler

LeSeulArtichaut (Mar 03 2020 at 19:10, on Zulip):

That's what you mean?

mark-i-m (Mar 03 2020 at 19:10, on Zulip):

Personally, I'm against moving things to the forge. I feel that the forge is really more for things that only compiler/lang team members would do

Santiago Pastorino (Mar 03 2020 at 19:11, on Zulip):

so ... I'd try to avoid to discuss two things at the same time :)

mark-i-m (Mar 03 2020 at 19:11, on Zulip):

whereas stabilization etc are things that anyone can do...

Chris Simpkins (Mar 03 2020 at 19:11, on Zulip):

Personally, I'm against moving things to the forge. I feel that the forge is really more for things that only compiler/lang team members would do

Maybe an appendix then?

Santiago Pastorino (Mar 03 2020 at 19:11, on Zulip):

I mean, I'm not sure where to move that, maybe to an appendix

Santiago Pastorino (Mar 03 2020 at 19:11, on Zulip):

but the first thing would be ... wouldn't be better if the guide just try to explain how the compiler works?

Santiago Pastorino (Mar 03 2020 at 19:11, on Zulip):

recently I've started reading the guide since the beginning and trying to read it as if it was a book

Santiago Pastorino (Mar 03 2020 at 19:11, on Zulip):

from cover to cover

Santiago Pastorino (Mar 03 2020 at 19:12, on Zulip):

to be honest it's a bit boring :joy:

LeSeulArtichaut (Mar 03 2020 at 19:12, on Zulip):

Imo it's lacking examples

Santiago Pastorino (Mar 03 2020 at 19:12, on Zulip):

I wanted to go to the meat of the thing

LeSeulArtichaut (Mar 03 2020 at 19:12, on Zulip):

It makes the book quite difficult to follow sometimes

Santiago Pastorino (Mar 03 2020 at 19:12, on Zulip):

LeSeulArtichaut said:

Imo it's lacking examples

yeah, also that

Santiago Pastorino (Mar 03 2020 at 19:12, on Zulip):

so ... I'm not trying to say what we should do, all I'm trying to say is that there's a lot of room for improvement

Santiago Pastorino (Mar 03 2020 at 19:13, on Zulip):

in the readability

Santiago Pastorino (Mar 03 2020 at 19:13, on Zulip):

in what's the focus of the guide

Santiago Pastorino (Mar 03 2020 at 19:13, on Zulip):

in what one should be getting out of it

Santiago Pastorino (Mar 03 2020 at 19:13, on Zulip):

and so on

mark-i-m (Mar 03 2020 at 19:13, on Zulip):

Perhaps one question is this:

Santiago Pastorino (Mar 03 2020 at 19:15, on Zulip):

Santiago Pastorino said:

to be honest it's a bit boring :joy:

to be a bit more clear, because I don't want to diminish the effort a lot of people put in the guide ... what I meant is ... I want to learn how the compiler works, reading from cover to cover you end reading a lot of things that do not go in that direction

mark-i-m (Mar 03 2020 at 19:15, on Zulip):

currently, the guide is more of documentation about a bunch of the compiler's parts, rather than a book per se. That is, it's currently written so that one would learn about a particular part of the compiler that they want to work on. Do we want it to be more of a book that one would actually read from beginning to end?

Santiago Pastorino (Mar 03 2020 at 19:15, on Zulip):

all the content is great, it's just that's not exactly what I've expected to read

mark-i-m (Mar 03 2020 at 19:16, on Zulip):

@Santiago Pastorino Yep, I can definitely sympathize. I don't think I've ever tried to read it beginning to end, though I have read all of it at various points in time

Santiago Pastorino (Mar 03 2020 at 19:16, on Zulip):

mark-i-m said:

currently, the guide is more of documentation about a bunch of the compiler's parts, rather than a book per se. That is, it's currently written so that one would learn about a particular part of the compiler that they want to work on. Do we want it to be more of a book that one would actually read from beginning to end?

I think it depends on the time and effort we can put on

Santiago Pastorino (Mar 03 2020 at 19:16, on Zulip):

I meant, it's easier to just add content and will always probably have more priority and easier costs to do that

mark-i-m (Mar 03 2020 at 19:16, on Zulip):

I think it also depends a bit on the audience... do we expect people to try to read it from cover to cover or just certain parts?

amanjeev (Mar 03 2020 at 19:16, on Zulip):

I think someone once said here that we do not want it to be a "how to build a compiler" course. Not sure if that still stands.

Santiago Pastorino (Mar 03 2020 at 19:16, on Zulip):

but I guess it's something that we can plausibly do, going for a modality that is more like a book

Iñaki Garay (Mar 03 2020 at 19:17, on Zulip):

I seem to recall that the overview chapter was the first step in providing a more comprehensible structure from which each part could be explored i more detail.

Chris Simpkins (Mar 03 2020 at 19:17, on Zulip):

^^

The Overview might be an opportunity to collect thoughts about cohesion as an end-to-end textbook on the compiler.

Santiago Pastorino (Mar 03 2020 at 19:17, on Zulip):

exactly what @Iñaki Garay and @Chris Simpkins just said

Santiago Pastorino (Mar 03 2020 at 19:17, on Zulip):

we are making some efforts in that same direction in my opinion

Santiago Pastorino (Mar 03 2020 at 19:18, on Zulip):

it's not that we want to sprinkle parts of content into the guide

Iñaki Garay (Mar 03 2020 at 19:18, on Zulip):

in addition to that, perhaps some attention could be paid to how one chapter connects to the next?

Santiago Pastorino (Mar 03 2020 at 19:18, on Zulip):

with examples, overview and other parts we seem to want something that gives more like a structure

Santiago Pastorino (Mar 03 2020 at 19:19, on Zulip):

Iñaki Garay said:

in addition to that, perhaps some attention could be paid to how one chapter connects to the next?

totally, I think it's hard to do all this but something that would be better for the guide

mark-i-m (Mar 03 2020 at 19:19, on Zulip):

@Iñaki Garay I think that is a bit hard because the chapters are often written by domain experts who don't have time/interest in the literary aspects of the guide and just want to document there subcomponent of the compiler

mark-i-m (Mar 03 2020 at 19:19, on Zulip):

but I agree it would be good

Santiago Pastorino (Mar 03 2020 at 19:19, on Zulip):

:+1:

Iñaki Garay (Mar 03 2020 at 19:19, on Zulip):

then our efforts would be best put into other tasks.

Santiago Pastorino (Mar 03 2020 at 19:19, on Zulip):

as everything, we need to lay out what can we do in that direction if we wanted to accomplish something

Santiago Pastorino (Mar 03 2020 at 19:20, on Zulip):

there are zillions of things we could do, there may be some easy wins there

mark-i-m (Mar 03 2020 at 19:20, on Zulip):

do we expect people to try to read it from cover to cover or just certain parts?

Sorry, I want to come back to this. Which direction do we want to go?

LeSeulArtichaut (Mar 03 2020 at 19:20, on Zulip):

What should be mentioned, is where one particular bit of code will be used. That, along with the Overview, could give the book cohesion

mark-i-m (Mar 03 2020 at 19:20, on Zulip):

I'm fine with either

Santiago Pastorino (Mar 03 2020 at 19:21, on Zulip):

LeSeulArtichaut said:

What should be mentioned, is where one particular bit of code will be used. That, along with the Overview, could give the book cohesion

maybe the first steps are just this ones

Santiago Pastorino (Mar 03 2020 at 19:21, on Zulip):

well maybe now I'm starting to think that this may be a good idea, but we first have the Overview and other things that would serve for those purposes

Santiago Pastorino (Mar 03 2020 at 19:21, on Zulip):

so in any case, it seems that that objective is better to have it around and look in a next sprint and not in this one

Santiago Pastorino (Mar 03 2020 at 19:22, on Zulip):

maybe after having the Overview up we can re-discuss

Santiago Pastorino (Mar 03 2020 at 19:22, on Zulip):

?

Santiago Pastorino (Mar 03 2020 at 19:22, on Zulip):

ok, let's move on then

LeSeulArtichaut (Mar 03 2020 at 19:23, on Zulip):

mark-i-m said:

do we expect people to try to read it from cover to cover or just certain parts?

Sorry, I want to come back to this. Which direction do we want to go?

What if the compiler expends further? It will basically be impossible to have everything in mind, right? Even as of today, I don't think there is a single person that is familiar with the whole codebase

LeSeulArtichaut (Mar 03 2020 at 19:24, on Zulip):

Sorry, you said to move on, nevermind me ^^

Santiago Pastorino (Mar 03 2020 at 19:24, on Zulip):

:+1:

Santiago Pastorino (Mar 03 2020 at 19:24, on Zulip):

one other thing from the list that I'd like to do is

Santiago Pastorino (Mar 03 2020 at 19:24, on Zulip):

Collect a set of PRs that help understanding some parts of the compiler

Santiago Pastorino (Mar 03 2020 at 19:24, on Zulip):

that's something that's kind of easy to do

Santiago Pastorino (Mar 03 2020 at 19:24, on Zulip):

and we can start with something if we want that and then improve or shape it better

mark-i-m (Mar 03 2020 at 19:25, on Zulip):

I know Niko and others expressed support for this, but I'm still a bit skeptical

mark-i-m (Mar 03 2020 at 19:25, on Zulip):

Can you give an example of what sort of PR you are thinking of

mark-i-m (Mar 03 2020 at 19:25, on Zulip):

?

LeSeulArtichaut (Mar 03 2020 at 19:25, on Zulip):

It's not something that I can do. If I ever see a low hanging fruit, I'm just going to take it :sweat_smile:

Santiago Pastorino (Mar 03 2020 at 19:25, on Zulip):

ouch, I was not prepared for that question

Santiago Pastorino (Mar 03 2020 at 19:25, on Zulip):

let me see

LeSeulArtichaut (Mar 03 2020 at 19:26, on Zulip):

Maybe I can help answer

Santiago Pastorino (Mar 03 2020 at 19:26, on Zulip):

maybe this one https://github.com/rust-lang/rust/pull/47954

Santiago Pastorino (Mar 03 2020 at 19:26, on Zulip):

also https://github.com/rust-lang/rust/pull/48300

Santiago Pastorino (Mar 03 2020 at 19:27, on Zulip):

there was a PR that in the mir-opt-wg we were using as an example of adding a pass

Santiago Pastorino (Mar 03 2020 at 19:27, on Zulip):

but I think there are a lot of PRs that may help to understand certain parts of the code without all the hassle of writing a chapter

Chris Simpkins (Mar 03 2020 at 19:27, on Zulip):

I suppose that one concern about that approach is how evergreen the PR's are and whether anyone will revisit this information to update it in a way that they would (?) with text content as things change in the codebase.

Santiago Pastorino (Mar 03 2020 at 19:28, on Zulip):

yeah, if done should have a huge warn about that

mark-i-m (Mar 03 2020 at 19:28, on Zulip):

@Chris Simpkins That's a good question. I suspect that they will bitrot a bit, but generally, I've found that things are often "similar enough" that a reasonable guess can be made

Santiago Pastorino (Mar 03 2020 at 19:28, on Zulip):

Chris Simpkins said:

I suppose that one concern about that approach is how evergreen the PR's are and whether anyone will revisit this information to update it in a way that they would (?) with text content as things change in the codebase.

but at the same time everything needs to be updated

mark-i-m (Mar 03 2020 at 19:29, on Zulip):

We could try to make a cookbook appendix or something like that

Santiago Pastorino (Mar 03 2020 at 19:29, on Zulip):

yep

mark-i-m (Mar 03 2020 at 19:29, on Zulip):

where we make a big table "how to xxx" -> "see PR YYY"

Santiago Pastorino (Mar 03 2020 at 19:30, on Zulip):

exactly

Chris Simpkins (Mar 03 2020 at 19:30, on Zulip):

Love the idea of a cookbook style approach

Santiago Pastorino (Mar 03 2020 at 19:30, on Zulip):

maybe we can start with an appendix and then if some things make sense we can move some parts into the sections

Santiago Pastorino (Mar 03 2020 at 19:30, on Zulip):

ok

Santiago Pastorino (Mar 03 2020 at 19:30, on Zulip):

should we continue with the discussion of next tasks?

Santiago Pastorino (Mar 03 2020 at 19:31, on Zulip):

actually the other two are ...

Santiago Pastorino (Mar 03 2020 at 19:31, on Zulip):
[ ] Write a walkthrough section about what the compiler does to your code
[ ]Write a walkthrough about how a full feature is implemented
mark-i-m (Mar 03 2020 at 19:31, on Zulip):

I expect these to take some time if we do them

Santiago Pastorino (Mar 03 2020 at 19:31, on Zulip):

which given that may be debatable, .... exactly

Santiago Pastorino (Mar 03 2020 at 19:31, on Zulip):

I was going to say, let's leave these out of this next sprint

Santiago Pastorino (Mar 03 2020 at 19:32, on Zulip):

in that sense we have ...

Santiago Pastorino (Mar 03 2020 at 19:33, on Zulip):
Santiago Pastorino (Mar 03 2020 at 19:33, on Zulip):

just these two, right?

Chris Simpkins (Mar 03 2020 at 19:33, on Zulip):

There was discussion at the last meeting about expert interviews/screencasts or something along those lines. Is content expansion in the Guide still on the roadmap?

mark-i-m (Mar 03 2020 at 19:33, on Zulip):

Yes

mark-i-m (Mar 03 2020 at 19:33, on Zulip):

There was some discussion about filling out the backend stuff

mark-i-m (Mar 03 2020 at 19:34, on Zulip):

but I think we are short on experts who have time atm, and I still need to go through the doc that nagisa made last time

Santiago Pastorino (Mar 03 2020 at 19:36, on Zulip):

so we ended saying that this Define how would we want to structure the guide is better tackled by doing first the Overview section and then we can come back to it, right?

mark-i-m (Mar 03 2020 at 19:36, on Zulip):

just to make sure I understand, our decisions so far have been:

Santiago Pastorino (Mar 03 2020 at 19:36, on Zulip):

that's what I was trying to do, you made it perfect :+1:

Santiago Pastorino (Mar 03 2020 at 19:36, on Zulip):

on top of that ... what we already had in the form of tasks was ...

Santiago Pastorino (Mar 03 2020 at 19:37, on Zulip):
Santiago Pastorino (Mar 03 2020 at 19:38, on Zulip):

have updated to reflect which ones are done

Santiago Pastorino (Mar 03 2020 at 19:38, on Zulip):

but basically we wanted to coordinate 4 lectures or from the list as many as we can and we wanted to rename the guide

Santiago Pastorino (Mar 03 2020 at 19:38, on Zulip):

right?

mark-i-m (Mar 03 2020 at 19:39, on Zulip):

yeah

mark-i-m (Mar 03 2020 at 19:39, on Zulip):

that's a lot

mark-i-m (Mar 03 2020 at 19:39, on Zulip):

should we focus on the overview and not new chapters this sprint?

Santiago Pastorino (Mar 03 2020 at 19:39, on Zulip):

from the ones I have I doubt it's possible to get more than 2 :)

LeSeulArtichaut (Mar 03 2020 at 19:40, on Zulip):

Maybe we can work on both the Overview and the Walkthough (what the compiler does to your code)

Santiago Pastorino (Mar 03 2020 at 19:40, on Zulip):

mark-i-m said:

should we focus on the overview and not new chapters this sprint?

yes that would be the focus, but remember that scheduling a lecture and maybe even having the lecture means maybe 2hs of effort for us in this sprint

LeSeulArtichaut (Mar 03 2020 at 19:40, on Zulip):

Those two seem very close to one another

Santiago Pastorino (Mar 03 2020 at 19:41, on Zulip):

agree on that @LeSeulArtichaut

mark-i-m (Mar 03 2020 at 19:41, on Zulip):

Hmm... I see

Santiago Pastorino (Mar 03 2020 at 19:41, on Zulip):

Santiago Pastorino said:

mark-i-m said:

should we focus on the overview and not new chapters this sprint?

yes that would be the focus, but remember that scheduling a lecture and maybe even having the lecture means maybe 2hs of effort for us in this sprint

we can summarize that lecture on a different sprint, my idea with this is that it takes time to schedule and have a lecture. I wouldn't wait until we are done with chapters

Santiago Pastorino (Mar 03 2020 at 19:42, on Zulip):

otherwise, we may be blocked by not having what to summarize

mark-i-m (Mar 03 2020 at 19:42, on Zulip):

Ok, I guess that can work

Santiago Pastorino (Mar 03 2020 at 19:42, on Zulip):

to sum up then ...

Santiago Pastorino (Mar 03 2020 at 19:43, on Zulip):

well was writing a summary but first ...

Santiago Pastorino (Mar 03 2020 at 19:44, on Zulip):

do we want an overview and a walkthrough of what the compiler does to your code?

Santiago Pastorino (Mar 03 2020 at 19:44, on Zulip):

or is it just one chapter?

mark-i-m (Mar 03 2020 at 19:44, on Zulip):

I would say one chapter

Santiago Pastorino (Mar 03 2020 at 19:45, on Zulip):

seems good

Santiago Pastorino (Mar 03 2020 at 19:45, on Zulip):

anyway, once we have something we are going to see that more clearly so I'm kind of fine with either

Santiago Pastorino (Mar 03 2020 at 19:45, on Zulip):

that could be defined before landing the stuff

Santiago Pastorino (Mar 03 2020 at 19:45, on Zulip):

so now yeah, to sum up ...

Santiago Pastorino (Mar 03 2020 at 19:47, on Zulip):
Santiago Pastorino (Mar 03 2020 at 19:47, on Zulip):

that seems to be our sprint

Santiago Pastorino (Mar 03 2020 at 19:50, on Zulip):

ok, is there something else we want to discuss?

Chris Simpkins (Mar 03 2020 at 19:50, on Zulip):

Timeframe for sprint?

mark-i-m (Mar 03 2020 at 19:50, on Zulip):

:scream: we finished early?

Santiago Pastorino (Mar 03 2020 at 19:50, on Zulip):

March + April?

Santiago Pastorino (Mar 03 2020 at 19:51, on Zulip):

another thing that it may be good is to have small sync meetings

mark-i-m (Mar 03 2020 at 19:51, on Zulip):

Perhaps one other thing is to decide on some milestones to keep us on track?

mark-i-m (Mar 03 2020 at 19:51, on Zulip):

yep

Santiago Pastorino (Mar 03 2020 at 19:51, on Zulip):

yeah and also that

Santiago Pastorino (Mar 03 2020 at 19:51, on Zulip):

meetings, should we have every two weeks?

Chris Simpkins (Mar 03 2020 at 19:52, on Zulip):

I can do another run through on the blog post and have this ready by next week. I would appreciate feedback from the team here if you have any thoughts about what is currently there. Don't be shy about editing it. And add your name to the author list if you do.

Santiago Pastorino (Mar 03 2020 at 19:52, on Zulip):

we should publish that too :smile:

Chris Simpkins (Mar 03 2020 at 19:52, on Zulip):

Specifically, the FAQ list could use better examples of what we are trying to prompt readers to weigh in on

Chris Simpkins (Mar 03 2020 at 19:54, on Zulip):

Santiago do you need help with the rustc-dev-guide transition? I took a look at the ripgrep dump of rustc-guide in the repo yesterday. There is quite a bit there

Santiago Pastorino (Mar 03 2020 at 19:54, on Zulip):

yeah so about those two things I'd say, let's create Zulip threads, discuss and move forward things async

mark-i-m (Mar 03 2020 at 19:54, on Zulip):

Also, fixing links in the rust-lang/rust repo and forge

Santiago Pastorino (Mar 03 2020 at 19:55, on Zulip):

yep

Santiago Pastorino (Mar 03 2020 at 19:55, on Zulip):

Santiago Pastorino said:

meetings, should we have every two weeks?

two weeks? weekly? other ideas?

mark-i-m (Mar 03 2020 at 19:55, on Zulip):

two weeks seems ok

Santiago Pastorino (Mar 03 2020 at 19:55, on Zulip):

I can create the events

Santiago Pastorino (Mar 03 2020 at 19:55, on Zulip):

mark-i-m said:

Perhaps one other thing is to decide on some milestones to keep us on track?

now this ^^^ :)

Santiago Pastorino (Mar 03 2020 at 19:56, on Zulip):

is it doable to do that in 3 mins? :P

Santiago Pastorino (Mar 03 2020 at 19:56, on Zulip):

another thing we could do is to try to come up with the milestones async

Chris Simpkins (Mar 03 2020 at 19:57, on Zulip):

rustc-dev-guide transition, blog post published, and outline for Overview for next every other week meeting?

Santiago Pastorino (Mar 03 2020 at 19:58, on Zulip):

yeah, that makes sense, let's define things until our next meeting

Santiago Pastorino (Mar 03 2020 at 19:58, on Zulip):

and what @Chris Simpkins have said makes sense

Santiago Pastorino (Mar 03 2020 at 19:58, on Zulip):

so ... I guess this is all?

mark-i-m (Mar 03 2020 at 19:59, on Zulip):

We finished on time :)

Santiago Pastorino (Mar 03 2020 at 19:59, on Zulip):

being 7.59pm UTC we have finished

Santiago Pastorino (Mar 03 2020 at 19:59, on Zulip):

congrats everyone!!!

Santiago Pastorino (Mar 03 2020 at 19:59, on Zulip):

:smiley:

Chris Simpkins (Mar 03 2020 at 19:59, on Zulip):

Thanks all! :wave:

mark-i-m (Mar 03 2020 at 19:59, on Zulip):

:wave:

Santiago Pastorino (Mar 03 2020 at 19:59, on Zulip):

thanks everyone!!!

Yuki Okushi (Mar 03 2020 at 19:59, on Zulip):

\o

Last update: Apr 03 2020 at 18:25UTC