YUI Library Open RoundTable, 2 May 2013

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: YUI Open RoundTable Thurs May 2 2013

Description

YUI Open RoundTable Thurs May 2 2013

A

um Noisy and visually messed up the way I open round table last week. We had some issues because of uh speakers and sounds so we're back back to normal today. Hopefully,.

B

A

um Today's thursday may 2nd 2013 and we don't have anything special on the agenda outside of bugs.

A

um If uh was there anything that either one of you guys wanted to bring up like, for instance, the performance stuff you're working.

B

On no, I haven't even had a chance to do much work on performance, yeah, eager.

A

To get back into.

C

B

But uh yeah it's working on cleaning up scrollvy's.

A

B

Testing at this point, cool anything special.

A

In your world right now,.

D

No well, I was looking at some of the like the way we do combo handling and uh there's.

C

D

I don't actually I shouldn't bring it up because I don't want to bring anybody's hopes up. You know, I remember.

A

Whenever you were you're just looking at highways,.

D

Yeah yeah so basically uh there's a possibility. We might be able to really shorten them, but it relies on other teams inside yeah, so cool and they have other high priority goals according to it. Right now,.

B

Eventually, hopefully, something figured out there because we've tried a number of projects in the past to to kind of do that stuff- and this is the latest attempt- and hopefully we won't run into any roadblocks like we have right past, but that would be pretty awesome. Yeah.

D

I saw you get some initial victories like just a few file names make them smaller, yeah.

A

I mean I have working.

B

D

And stuff, like.

B

That but we'll see so smaller file names would get us uh less urls to load in um when, because when the combo urls are generated, if they're too long, it'll chop it up into multiple requests, is there any aside from less requests? Is there any other performance.

D

Gains by well there's one performance concern that I was going to look into, which is um it might be better to have multiple files in some cases, because there's more parallelism. Oh.

A

Yeah yeah right, like it's waiting for this long stream, so like things don't render as they could, whereas.

D

They were coming in parallel yeah, so to kind of, I know, that's kind of really hard for me to figure out how to to test that. So I was thinking if we just gave full control over the number of requests that a developer wants like to.

C

Have them be able to specify.

D

That then, people can just kind of experiment, and then we can settle on it'd be cool too. If you could find out like.

A

What components load faster than others, so you could front load those so they'll come in. So if you got you know, instead of one big one and three small ones and the three small ones come in last and the big one, you know blocks them. If you could have the three small ones come in first, you know so: they'll start rendering you know modules or whatever yeah.

B

Well, yeah having a config option to configure that would be pretty helpful and then for anything loading in later on. In the page you can have those requests be bigger, um but anything that needs to be loaded up right away chop it up into multiple requests. Yeah.

D

B

Yeah, that would actually probably be the preferable route yeah, um at least from a developer perspective.

D

Yeah, that's all pretty much application specific, so yeah just to get everything configurable and.

A

Yeah, because it's not cut and try right you, you can tweak things like you can get.

D

One big long download that you know fast speeds work great, but.

A

Like you said, there's a threshold where that.

D

That becomes, it might not be. uh You know best for performance.

C

Right because I was able to load.

D

The whole library.

D

Wow wow: that's a.

A

That is impressive. What about like um uh sockets and stuff? Is there a way to take advantage of sockets at some point in the future, where you could just.

D

A

It always like an always-on channel that just pulls things down our our cdnos sure didn't support. Oh sorry, it's okay, because I.

D

Saw some demos at the.

A

Html5 dev uh that were really impressive on that regard, where you.

B

Just basically have an.

A

Open channel, instead of fetching it all like ahead of time, you just fetch it like right on demand or like right ahead, and it's just constantly adding new stuff so yeah. That would be great one.

D

Step out of time, yeah far future.

A

Well, um so I want to put in a bid if you go to the roundtable topics page on github.

A

It's basically there for everyone in the community and yy folks to post any kind of topic that they want to talk about in this forum. Typically, we'll have three to five at least um yy.

C

A

Folks, plus community folks, here all the time. So if there are topics you want to bring up, uh for instance, something that maybe is going on in the contributor mailing list, please feel free to add it here and.

C

If you have any demos for.

A

Things like gallery components you want to demo, or things like that. Please feel free to add them here. This is meant to be a showcase for the community.

C

A

Yahoo folks so feel free to drop it in um outside.

C

Of that we could jump into the.

A

Scale, request, reviews and we've had a lot of pinned up stuff because we had a delay on our release from last time. So a lot of stuff is coming through. um I'm going to jump down and see what items are new this time around.

A

A

Basically, the the criteria for something like this is someone. That's an external contributor who's not had a lot.

C

A

And who contributed something that looks like it's ready.

C

To go but hasn't.

A

Had any responses so.

A

There's one from eduardo.

C

A

That was a separate logic insert button container on why dot widget buttons to simplify class customization, that was last updated, 20.

C

A

And that's pull request 556.

A

And this one uh is an eduardo's camp because it looks like it needs some tests.

A

So the hard thing is, you can't really see who's the last commenter on here. So sometimes it's it's in the on the side of the contributor to contribute uh additional comments.

A

Just check this one to see if it's.

A

A

There's pull request, 596 added a.

C

Table keyboard navigation.

A

Module and tests, this is from satyam and it looks like it is getting.

C

Closer to being ready.

A

A

So I'm going to bring this one to the attention.

C

Of any reviewers that may.

A

Be watching this later on or I'm getting paid.

A

Oh yeah one was just responding on the rc about um a min request, option and shorter url. So he was really excited about that.

D

A

D

Looked at the discussion that went on in.

B

D

Contra uh mailings search for.

B

It yeah a couple weeks back so that's.

D

A

Pretty helpful.

D

A

Yeah, it would be interesting to see if there's a way to uh bring.

C

A

Of interest to the folks that are working on the stuff, you're saying that they don't have time right now like to just say, hey, there's a big pent-up desire for this yeah, because the thing is it's not that they don't want to work on the rights. Just they don't. Their priority list is different.

A

Yeah, yeah yeah so anyway, so on 596.

D

A

Find a person to can help review that and see. It looks like.

A

I think dave send them some feedback.

A

C

A

We can define someone for 5.96 um to take a look, so I'm taking notes.

B

A

As we go, um there's one pull request: 611 from wendy.

A

C

It's in one bank's camp as well, so let's keep that.

A

One check the next one.

A

C

Was looking at 480.

A

Configuring, the y instance to admit facade by default cause an error to be thrown by that focus, and so this one looks like satyen needs to respond back so I'll make a comment.

C

C

A

C

Resource prefix.

A

C

So there's pull request six.

A

One eight that says model saying caress, dot, add resource prefix, um I'm going to follow up on that one as well with eric, because it looks like uh simon.

C

Has simon eric if.

A

You had some back and forth. It looks like eric may need to respond to that.

A

A

Let's see checking to see some more that may be.

A

I think a lot of these are bugs that are issues that need to be looked at by the reviewers a bit more, so I'm going to sort of ping them and have them do a pass through, because I think some of these are sort of falling off the radar, because it's been a while right.

B

A

Not going to go into detail every single one of these there's a whole bunch of these that are like right on the.

C

Edge like seven days ago,.

A

So it's not really that useful to go through here, especially when we don't have that many members.

C

We don't have a review.

A

A

So I'm thinking that I'm gonna go through the list. That's here that has it's like right on the cusp in seven to nine days and just send this off to the reviewers and say: can you guys just sort of general partition these out and look them up and then I'll follow up next week to say you know which ones got updated or not, because I think a lot of this is.

C

A

Pent up stuff that needs to go through the process, and that would be an interesting thing to do- is sort of set aside a day that all the reviewers maybe get together. Do they they meet up periodically. Did they just sort of meet it formally.

A

I think this is something that they could probably knock out like in a few minutes like yes, no right which it may be this forum, but this is like the pull request. F is mainly a way to make sure things don't fall off the radars.

A

So outside of that, I don't really have anything extra to report this week.

A

There's one addition to the the wiki that we were talking about in the contributor mailing list and that was uh created a page called best practices for writing code that luke brought up. So if you have ideas for what may be added to that um feel free to talk about it on the contributor list and then if we get thumbs up on those kind of things, we'll just add that to that page.

A

In my my experience, though, I've seen it happen a lot of times where it's a very light. When you have a very light best practices page, it allows a lot of people like just you know, streamline stuff and as it gets heavier and heavier folks tend to like, ignore it right because they look at it go. Oh, I can't possibly follow all these, and then it falls that then it falls out into like this use, and then you get.

D

This whole other cycle where they go. Oh it's out of date: let's hold it revamp it do it yeah. Actually, my.

A

Initial reaction was.

D

To send you, like my vim settings, yeah to enforce that, but.

A

D

A

Could be that we could put pointers in there too, like handy things that we use like that or, like uh you know, profile stuff, or we have aliases that are useful. There's a couple sublime.

B

Text plugins uh that people could install.

A

Yeah I found one that I was talking with jeff. Recently it was the one that uh maker moves, trailing white space, yeah.

B

That's really handy, I I set that one up about a month or so ago, and um it's so nice having that on there not having trailing white spaces anywhere in the code yeah so and you get the sense of joy like when you open the page. You have edited for a while, and you write all this stuff.

A

It does make some of the diffs a little bit ugly, but.

B

I mean, I think, that's just kind of comes with the territory of cleaning up the library as you're. Just gonna have these um white space removal diffs, um so yeah.

A

Maybe we should have um if we had like a a down cycle where all we did was lint the crap and everything you know we have a giant check in it's just.

B

I would love to have the entire library limited in passing, so there's a number of components out there that that are um compliant with our lint settings, but the entire library as a whole is not, and that would make. I think, everything so much so much nicer.

A

Well, one thing it might be useful to do is uh scan the repo for the oldest uh change file and just sort of work. Your way backwards, because most likely those are the ones that are least compliant.

C

B

A

Probably so they'll be great when we get that intern wicked.

B

Because then, if the entire library is limited, then we could block um pull requests for. Oh do a um upload hook, yeah.

A

B

Yeah I mean you, could even do it a commit hook.

A

Those are scary because sometimes you have.

B

To have an exception there, like maybe some code, is a test for something well, so yeah I mean what we can do is set it up in ci is to have it where you have to pass a certain threshold of um js lens errors that are thrown.

C

And we could set that threshold.

B

Very very low um and yeah, so then any then any merges would fail, because right now the onus right is.

A

On the reviewer or the commander right.

B

A

Yeah, there's still definitely some uh some work. We can do, but one thing.

B

That came up in.

A

The on the contributor list was, I think, southam, had a good point where um you're working on some new code, and it's got a lot of like lint problems with it. What do you do? Do you put a do? Do you do a check in that? You just do a little plant like you do one commit, then you.

D

Come back and then.

A

You change your stuff right. Yeah does that seem.

D

A

Reasonable thing to do, he.

D

Said somebody complained about that, I don't know, I don't understand why there would be a complaint. I guess I don't have enough context.

B

That's what I always do, yeah commit with commit, do a very specific commit with all your lint changes, um lens and white space changes and then do a commit with uh your actual code changes that makes it really easy. Then, if you only have two commits, while the overall diff and the pull request might be uh all of it mixed together, you could at least point people to that specific, commit and say this is where any.

A

Code changes occur. I think the issue was um how much um linting stuff do you do before it sort of obscures the changes that you want to make right right.

B

Well, yeah, I mean if at that point, if you you can even submit two pull requests. I mean I it'd be awesome to have a pull request. That's just like hey. This file is now linted um yeah, so.

A

That might be one way to do is um when we want new folks to get involved in and in writing code and doing commits. We could just do a bunch of uh write, a bunch of issues for each component.

B

A

Say take this component and go lint everything and then give us a check. Yeah.

B

Yeah for anybody who's curious about like oh, what lit settings do we use and the project it's all built into yogi.

C

Lynch, so if.

B

You run yogi lynch within your component, then that'll that'll by default, use all of the project. um Json settings so yeah.

D

B

D

That's kind of the official way to do linting, yeah and all the rules are defined in the yui lint repository yeah. I I use that in one of my event plugins. So where is it that we're located it from yy3d.

A

B

No, it's a separate repository. Okay.

A

B

And so that uh yeah, it's just a known module that contains um that's a wrapper around lifting tools that contains all the settings. Yeah.

D

So this one is a recent file.

D

No it's not it's not in the tree.

A

A

So yeah guys check out github.com, yui yy dashland and that's where you can find the package.json things like that. The hint we're talking about.

B

Yeah and that's a node module that dave wrote, so you can import that into all of the apps that dave has written and then you can use the same linting tool throughout all of them very cool.

A

We miss you dave that.

C

Will be the last thing.

A

I say every week so we miss you so anyway. That's it for this week um pretty light week right now, but uh thanks everybody for coming, and we will see you next week thanks bye.