Apache Mesos Community Working Group, 4 Dec 2017

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GMT 2017-12-04 Community WG

Description

Agenda and Notes:
https://docs.google.com/a/mesosphere.io/document/d/1vgi434dYkkZHs49EK4F4eMmM-3JG4f3qg-N5En-4ubg/edit?usp=drive_web

A

B

If we're recording.

C

So I see a few items on the agenda here. Should we start with those a review stuff from last time? First.

C

Well, the first thing I see is the jacket on, and so that's on our agenda for today. So I can talk about that. Today's agenda, oh the review meeting I haven't so we we dug up these tools for getting review board stats and I have not had a chance to make use of those. Yet so maybe I'll have that as an action item for myself this week,.

C

I'll, add an action item for myself to do that. This coming.

D

C

B

That was it there. Lastly, and enjoy you so the Dhaka thon is scheduled, search and wearing 11th I created a meet-up in the Bay Area in the mesosphere group, but I was wondering if there and I wrote a series of tweets about it from the bases account. But I was wondering if there were other ways we wanted to promote it, and if we wanted to make it a little bit.

D

More structured, this time.

B

We could um we could give a review about how to contribute to the docks at the beginning. In case we get new users.

C

Make? Oh just like a little document or something yeah.

B

Or like just give a little presentation, that's like here's, where the docs lives: here's how to contribute to them. If we have new people who joined the pocket on who have never contributed to the docs before.

C

Yeah I think that's a great idea.

C

A

You mind hopping on your.

B

Sari nice I didn't get a ring for this one. No.

C

That's that's. Alright. It's totally fine.

B

C

I think it's actually I kind of liked doing it just with people on their computers, because it kind of evens the playing field for folks who aren't in the same location do.

B

C

What I mean yeah I think having a little review of how to contribute yeah, it seems like a good idea and maybe we could send out yeah I don't know. Is there? Is there a way we could try to get some new folks in beyond just emailing the mailing lists.

B

Yeah I'm, not sure I mean I've, been posting Twitter posts about it, but one thing that might be good was if we wanted to have a like a seeded list of really easy little tweaks. You know we could say, join us and do one of these and get your first contribution, and that way people wouldn't have to be familiar enough to know what needs improving yeah, yeah.

C

That's a good idea. We could maybe just do that during this meeting. Try to come up with a couple little things.

C

We could also one thing that just occurred to me on our end. We could reach out to the DCOs community and see if anyone there is interested in corn, ASOS and kind of starting to contribute a little bit yeah.

B

That would be great I know we have people who are getting sophisticated enough. That they're like starting to wonder what happens under the could have be CLS and reading into pieces, so questions so yeah. We can definitely.

C

So I wonder: let's try to come up with a couple. Little easy duck improvement.

D

C

Let's I'll pull up the docs. Maybe I could share my screen and pull up the docs and we can just browse him for a second and see if anything jumps out. Yeah.

B

And I did put into this is the.

B

This is the brainstorming document where the doctor thought, so that might be a good place to add.

C

B

So if you guys just joined, we are.

B

C

Right, can you guys see my screen? Okay? Yes, if you guys have any ideas on small documentation, improvements that we could just have ready for new folks to work on and the next docket.

C

We thought we just browse for a second see if anything jumps out I.

C

Feel like well I guess that stuff might require a deeper I mean one thing: I see I think maybe this fundamental stuff hasn't been updated in a while, but that probably requires some deeper knowledge, so not great for a newbie.

C

Oh, but it says agent, so it has been updated sometime in the not-too-distant past.

E

C

Work so we're having a doc Athan on January 11th, so we were just saying we're hoping to get some new people. There I was saying we could reach out to the DCOs community.

C

We can put out some emails on the mailing list, so it might be cool if we have just a couple a couple, simple improvements that folks could work on if they are new.

C

Yeah I guess, if there's any like reorganization or copy-editing.

E

Some newbie could work on is in tour new binaries, you know getting started page instead of having people compiled from source and actually link in your downloads. Page I think that's kind of a valuable experience for people coming into the project. For the first time.

F

B

Actually, we think I'm writing them down in this write itself so that they.

G

Don't get lost.

G

B

If you have any leaks.

C

Okay, did you write that last one or should I.

B

Getting started and down those babies, cool.

B

But if there are any links that it.

A

Should be associated with that, to make it easier.

C

Okay, yeah I'm, not sure I have any ideas immediately. To be honest, so maybe we can try to think of some between now and the docket on.

E

One thing you want to do for a while that errand unnoticed moving the roadmap from the key in tour document.

E

So that it's probably easier to edit and for people to sand it appears and stuff to update roadmap thing is still linking to the wiki page, which doesn't get up better at all and I think should probably use this meeting a part of admitting going forward to kind of make sure the roadmap is up-to-date.

C

Yes, if we link to the JIRA roadmap.

E

Ritchie, what is it like to.

C

Get exists. This is our up day. Maybe it's just.

C

Yeah I'm not sure.

E

B

Are three roadmap links? Look at the website. It says, like here's, one version of the roadmap and here's the epics and here's the roadmap on the wiki, but I think the way people understand you're right enough. Yeah.

E

C

I think just revamping this roadmap page in general might be a good idea.

E

C

We can probably.

E

Roadmap things like a topic.

C

Anything else regarding the jacket.

E

B

I guess the other thing was Greg already answered this a little bit, but if you can think of any other sets of people, we should reach out to you to participate or get new users or any other channels to reach out on.

C

Shooteth, how should we reach out to the dcs community? Is there a mailing list that would be best for that or slack.

B

Yeah there's a mailing list. It's at.

C

B

C

And who do you think is a good person for that email to come from I would be happy to do it or, if you are kind of in the community and want to do it.

B

I'm happy to send out an email about it: okay,.

C

Well up there an action item for you.

B

And Aurora and marathon, maybe somebody who's a little more involved with those communities I'm a little involved with Marathon, but not very much and nothing with Aurora. So.

C

Yeah are: are you on those lists.

E

Of people, the.

C

Marathon, Channel and slow yeah in what? What about Aurora? How do they? They have a mailing list as I have.

E

Meaningless but they do have a channel in our mrs. black okay.

C

Cool, so we could reach out there.

C

I can do that.

C

Okay, any other docket on stuff.

E

Okay, I guess: we need a bunch of new documentation for new features and genderless all this, so that would probably be a good time to hack.

C

On those or are we really are we lacking docs for new features that are going in right now, yeah.

E

I mean not I, think we're just adding some like API changes and stuff like that, but not really, like top-level documentation, little fall domains. What does that mean? How do you.

D

E

For example, for example, the CSI stuff is there any documentation, I, don't think that is any documentation there. There's only all tuple discs and persistent volumes so stuff, like that, like I, think we don't have to upload documentation of features, it's more about just tacking on stuff to existing documentation like api's and stuff.

C

Okay, I mean yeah. We can use the darker thoughtful. That would be great if that stuff happens without the jackets well.

E

Yeah yeah, ideally as part of the project of the future yeah.

C

Well, that's clear: we got some good stuff listed for the jacket. I think we'll have plenty to work.

C

Okay, anything else should we move on to the next.

H

C

The next item on the list is release blog Judith yeah.

B

So currently, the release blog looks a little bit like a change log. It looks like it just has high level changes and not very blog II and so I was wondering if maybe because, when there's a new Apache or meses release, maybe new users want to try it out. It might be better to make the release Lodge a little more approachable and, like blog ish, yeah,.

C

Yeah, that's a good idea. I was.

B

Wondering who writes the release prog and if I could help get some more background with it and stuff like hey.

C

Gilbert is that you waving yeah.

I

I'll be right right, there really spot and.

I

You have to like be facing.

I

You can come to different channels, so.

C

What do you guys think about the release blog versus the newsletter that we're starting so I have a draft newsletter um that we can look over today and I would hope to send that out? You know over the next week, or so so I could imagine either having a separate blog post for the release or rolling it into the newsletter for January. What do you guys think?

C

What's the news netic? So this is something we've been talking about for a while and trying to get off the ground and I finally have a draft of one to share today, and our hope is that we can start releasing a monthly newsletter that just kind of briefly goes over progress in the project so that people can stay up to date. Try to like keep people talking about what we're working on.

I

Okay, so I think I think they, for this is like different purpose to me because like but for the newsletter is, it is used for the for report. The progress that for the release bra, it is for one specific release and then, despite your couple specific features and about fix so I think you should have both and keep them separately. Yeah.

B

C

That sounds good to me.

I

Yes, sir, so for the photo release but I think I can see like the prop canopy starting like after we cut the Asti one which I not be likely happened in one.

D

Not so big, so it mean I still have a lot.

I

Of issues fun doing, for example, the CSI support the end or effective 90, so Microsoft have the business health check, things which you, which is blending these two weeks and yes have a lot of some other feature like the image GC. So the cut could be happening and around the middle of the sample and because I, just our the purpose.

J

For Windows support I could help write up a snippet, so this is gonna, probably be the first release. We actually try to like, say yeah this stuff in Windows actually landed cuz right now. It's just been experimental and it's still kind of experimental, but um about writing a paragraph or two taken, for you know, Windows support and what's there what's not for the one by though it sounds great yeah.

I

This is good, so I cannot speak. That's Friday about that. To.

I

Five minutes so so I work with nd for that. In those specific part in the post.

I

Okay, so do you guys have any other concern for the.

E

I

I did not create a test for you guys once I created a beautiful female in the Select I said: that's why they do it this week. Yes,.

C

D

C

So anything else about the release blog or should we move on to the next okay?

C

So next the newsletter I'll share my screen, real, quick and actually first I'll, put a share link to the Google Doc in the chat here. So you guys can take a look if you like there, you go.

C

So that's the wrong link. Sorry, one second.

E

What are you sure.

C

I'm sharing the the draft newsletter just grabbing a link, real quick.

C

C

There you go and I'll share my screen.

C

So I was just short on time and really wanting to get something out, so I thought an easy way to get some content on storage, which is what I was hoping to do. This first newsletter on was to do a little interview with G since he's been leading that effort. So we just sat down for a few minutes, asked him some questions and I put put it together in a little interview form.

C

So there's just some text at the beginning and end, and then most of it is me asking G about what they've been working on kind of like so yeah, maybe I'll just go through the questions. I asked them about his background.

C

First, so people kind of know, you know where he's coming from people who aren't familiar with them got a summary at a high level of kind of what direction we're going with we're going in for the storage support and asked him what use cases he was excited about and when the features would be available and how people can get involved.

C

And then, what's coming up next after this stuff is done, and then he had a couple other things just share, just kind of like long-term vision, kind of stuff for global resource support in Mesa, and then we can put a couple links in it to design docked to JIRA and just a little blurb about the upcome release and a little blurb kind of explaining what we're trying to do at the newsletter. Just that we're hoping to do these monthly, so I would aim for you know, like maybe mid-january, for the next.

C

So do you guys think this, like interview, type format, seems okay,.

B

Yeah, it seems like a good like kind of blog II or not. Okay,.

C

Yeah I, don't know no good I. Think.

B

Part of what we talked about was just kind of giving like little updates from all of the like people who are leading projects.

B

C

B

Looks great okay.

C

Yeah, if it seems like reasonable at a high level, then I guess I would just encourage you guys to take a look and tear it apart. Give me comments like feel free to mark it up as much as you want, and we can get it into a finished form, maybe in the next week or so, and if it, if there's something kind of higher level, that it seems like, doesn't look right or you think we should change in a more drastic way, I'm, definitely open to that too. So you can feel free to.

C

Let me know now or later.

E

C

Sounds good yeah, so please this week, maybe in the next couple days have a look. If you have a cycle and I'm gonna aim for sending this out, maybe by the end of the week so I guess we could put it on so we had talked about like putting it on the blog.

C

So do you think it's appropriate to put it on the maysa blog and just send links to the mailing lists? Yeah.

B

I think that's great okay,.

C

Well but an action item done for me to take care of.

E

E

C

Sorry, what was that last bit? I'm.

E

Saying it's probably also easier to write it that way, yeah.

K

C

J

Definitely interested in reading it just from seeing the drafts. Oh yeah I think this will go over well. Okay,.

C

Great thanks, Andy I'm.

B

C

Right, so that's the end of the agenda. Is there anything anybody else has on their mind, wants to chat about. Oh there.

J

Was one thing I think we brought up? We were throwing around the idea of like a weekly or every two weeks, sort of get together review community catches group for our maintained, errs and community members to join up. Did we get that onto the agenda?

J

C

Yes, so that was something we spoke about last time and I had a little chat offline with a couple of folks about it, and one thing we were curious about was what the current status of review board and the review situation is, and we were thinking that whether or not a meeting like that would be really beneficial perhaps depends on what types of reviews are sitting on addressed in review board and if, if most of the unaddressed stuff belongs to like chains of work, that that are part of a like a project where someone's already engaged with a committer on it.

C

And it's just like that. Committers having trouble getting time to look at that project, then a meeting might be less useful than just those people coordinating between themselves and I'm. I'm thinking a meeting like an open meeting like that would be more beneficial for kind of miscellaneous reviews that aren't part of a larger effort that are really not getting looked at because of a lack of visibility or a lack of knowledge on the part of committers that but they're even there.

C

What what do you think about that? Does that kind of match your perspective yeah.

J

That does match my perspective. At least wait like how you described it totally, which means we should probably take a look at what gets reviewed. I. Think mostly like the problem. I was seeing a lot of is, there are maintained, errs, but sometimes they just get busy like conversations get sort of can't dissipate, so I was kind of hoping.

J

You know just be able to get routine time for committers to get back to patch teams that they've, forgotten about or just kind of fell, fell to the wayside so yeah that kind of fits into both categories. Right like it is a they are changed where there's a conversation with a committer, but it's still kind of dropped in visibility.

J

So I'm not yeah,.

C

So and okay so you're talking about like like larger chains,.

J

Of work so yeah, there's, there's small things too that go through so like, for instance, and I'm not going to pick on anyone, but like we've, got a there's three patches up that are close to a month old that were for seaming stuff. um There is a another committee engaged on it right, there's Jo and it's just a matter of like running into getting time to actually go through and do it so I was hoping with like a routine meeting.

J

It would just make sure that committers have time to set aside and say: hey yeah I have this hour a week to go, look at actual changes and get it through. It's not necessarily lack of visibility. It seems more like a lack of time on the majority of committers parts, yeah.

B

Andy I think that was my original intention. Bring it up also was not so much for accountability as parlez. That.

J

Time, yes,.

B

Exactly like this is your time to work on this thing. You have time to dedicate to it, go for it. You know.

J

C

So yeah I, guess I I think it's I'm kind of I'm not sure how much of an impact it would make honestly but I think it's worth a shot personally and the impression I got from talking to a couple hooks is that we might not get, or at least from the folks I talked to they weren't as excited about it and I. Think for it to be useful, you really need to get buy-in from the committers yeah. It's.

D

C

Maybe one thing that we could do is start a thread amongst commits. You know maybe, like the committers, can kind of discuss this, because I just did a couple ad hoc discussions with people. We could have a more public open I mean a public discussion amongst committers about you know whether or not we think this would be beneficial like whether or not is something we wanted to vote. Regular time to so yeah I manage.

B

I might not spend that even not just for like whether or not this would be beneficial, but what way people could think of that they would want to work on it right, because if people don't want to review their patches, they're gonna be like I. Don't want to review in this way and I also don't want to review them. That way.

D

B

What way would be the most effective way.

B

C

So I guess the committers have like a mailing list on which we could discuss such a thing. I already have several action items for this session this next couple weeks. So I don't really want to add any more for myself. Is there a committer on on the call who would be interested in doing that? I could.

J

Send out an email, yeah, okay,.

C

That would be great, I'll, add an action item for you.

L

J

Reminds me that I need to get subscribed to that list. I thought I was but I think multiple mailing lesson like the Welcome getting started kind of cited.

C

All right, so we can kill a couple birds with one action item.

C

Cool yeah thanks for bringing that up, and we appreciate the momentum on that.

C

Well, anything else! Anybody you wanted to discuss.

F

I was planning to write up sort of a progress report for the performance working group. We can talk about some of the improvements that remain, and things like that. So I was probably just gonna write that and leverage some people to read it over and see if it's written well and stuff like that, it's not enough who would want to help review that, but.

C

F

C

To help, what's what what are your plans for that report?.

C

What do you mean like? What do you intend to do with it once it's ready like a blog post? Okay, what do you think about making that the topic of the next newsletter in January, oh.

F

Yeah, we can probably could do it, although I suspect that we probably just want to publish it before January.

B

F

B

Thing is that, if we're just sending out links to, if we're sending out to blogs in the newsletter, then we could send out a link to whatever blogs have been published since the last newsletter. And you know that would include this, even though they were concurrent yeah.

C

F

Yeah, that put that probably makes more sense.

F

The newsletter would be highlighting different things: yeah, yes,.

J

C

Yeah I feel free to reach out whenever you've got something for us to look at.

B

You doing technical edits, I'm glad to do writing. Yeah.

F

That's that's helpful too.

C

Cool any any other topics.

F

I mean along those lines, just curious if we wanted to do this kind of thing for other working groups or not I, think.

B

That would be awesome, yeah.

C

Yeah definitely I bet once once this big push on storage stuff is over I bet. She would be willing to work on something for the storage effort or I'm. Sorry about that containerization working group in general, because he's been leading that and maybe I don't yeah. Maybe you as well Gilbert would want to help us something together for containerization yep.

I

Ongoing features in our roadmap so and just each might have some items as well, so we can this.

C

I

C

What what other working groups do we have others right now that we might want to do that, for is that it.

C

C

E

C

True I mean we could yeah.

E

We just talked about we could we could talk about that too. I think.

E

K

B

I think we have a lot to show for it too. So we've got the doctor bond newsletters are going to come out, we're gonna have more blogs, so it sounds like it might be. Nice.

A

To advertise a little more yeah, yeah.

I

I think the doctor thought that that knit a birthday was a new listener day to announce that oh, we have a lot more documentation which we faced before.

C

And that's something: I can include in the newsletter this time. I'll add that about the docket Bob.

C

Okay, any other topics people want to discuss, got a little time left, I.

E

Think find out for next week or some other session I think we talked about our releases, how we can improve them in the process. You should follow. What is time-based release mean and how do you want to advocate for it and whether it works for the project or not stuff like that? I think is what well study that.

E

Using discs, the better forums are coming just meeting, but I think it's worth adding it whatever.

D

Who understand.

E

D

E

About this more important for the community and stuff like that, it comes up already.

C

Yeah I think that's a good call.

C

Well, any other topics for today or for I done this for discussion for next time that we could be thinking about.

C

Going once going twice, okay, I think we can call it thanks for a great meeting today. Everybody appreciate y'all coming and so are we are we still planning on I? Guess it'll be the twenty or no it'll be the 18th of December? Also it may be around so I.

J

Should probably.

E

J

Around on the 18th yeah yeah.

E

C

Okay, great so we can meet up in two weeks: cool thanks. Everybody well see you then bye E,.