Rust Programming Language Core Team, 11 Jun 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Core Team Meeting 2020-06-11

Description

Core Team Meeting 2020-06-11

A

Okay, welcome to the July, no June 11th meeting core team meeting. Wow.

A

Okay. First item is licensing copyright, clarity for him. The.

B

Meetings, the initial meetings: tomorrow we have a mass issue ticket and a master document yeah. First, the person is going to be dr., Felix and me and we're going to report on our findings or on our initial plans. Next week,.

A

Awesome, mmm non-commercial for forum terms, Nico I,.

C

Sent out requests about this or anything I think I didn't well, but I think I'll check.

B

Back then, there's a thread on the licensing.

B

On the licensing Zula.

B

What let us thread on the licensing so that mentioning that just trip that has actually opened it a.

C

Thread about licensing of the internals and users yeah exactly exactly.

B

C

You can send that to you know in see that good right, yeah, okay, let's continue the meeting, but it looks like I sent a mail about the code. Snippet and I didn't get it direct I didn't get I didn't get a refined legal language paragraph, but it's not bit like they did get a response to suggestion. That would be fine, so I'll just request again and we get like or I'll send a sample paragraph and then change it. Maybe or something.

A

Okay sounds good white papers, Florian.

B

A

Anything with the target tear policy RFC.

C

I, first of all, we created I've started the towards the process of having actual groups around each of our targets.

C

Right now, a little notification groups they're just like lists of people that get pings when you see something around windows and would like some help and like Ryan Levesque found a bunch of names for that particular one and- and we also made one for arm which had that's the names for the word came from down through arm, and so that's that seems pretty good and we might start doing a few more of those like maybe awaaz m1 was proposed. I eventually I'd like to have them for kind of everything.

C

Useful and there's already been a little discussion, which is cool like I, see some tomato T, compiler / windows screen in the lift and I see people talking.

C

Just kinda nice, so that's happening and I think that would tie into the target tier RFC like basically when, when you want to move up past a certain point of support and maybe even I think initially at all times. If we support that target, we should have some people we can gain when stuff happens around that target, that's the main thing I wanted to see in the RFC. Actually the language is already there, but it just needs to be like very big I think Josh about it. He acknowledged not having done anything.

A

Okay and next is rethinking working groups anything there. Last.

C

A

Okay, anything else for the public part of the meeting and.

D

I quickly ask what the rethinking working groups points to there's, not a lot of detail here, so I'm a little confused, yeah.

A

I kind of forget why we this.

C

Discussing and taking on we've in the last week or two, this was kind of a question of domain working groups, whether we want an application procedure, how we wanted to manage them and that's something that's been under discussion for a while. That's what it's referring to I don't have at the top of my head, the the latest thing we said, but I remember. We posted an update somewhere, maybe just in meeting.

C

But the general consensus we've been moving choices that we sort of. If we're gonna have them, they want a few and they should be well purposed and not like an open-ended set of groups. I think there was some discussion around the idea of. Maybe we can make some mechanisms like link to community groups that are outside of the rest or they have their own presence and you know, meets the minimum criteria.

C

Saying yeah hey if you're interested in like I, don't know mail handling, there's like a group of people who come and mail handling over there, and maybe you want to jump in.

A

Okay, anything else for the public part of the meeting.

A