Skip to content
This repository has been archived by the owner on Sep 6, 2022. It is now read-only.

The Plan for Picturefill #374

Closed
Wilto opened this issue Nov 19, 2014 · 13 comments
Closed

The Plan for Picturefill #374

Wilto opened this issue Nov 19, 2014 · 13 comments
Milestone

Comments

@Wilto
Copy link
Collaborator

Wilto commented Nov 19, 2014

Picturefill 2.2 just shipped, which we’re incredibly excited about. Now, you might notice that there aren’t as many changes in this latest version as you’d hoped. And in some cases, there are still situations where we’re deviating slightly from the specification—never in massive glaring ways, but we’re striving for total spec compliance here.

We have high hopes for Picturefill 2.3, but there’s a reason 2.2 is a modest release: we’re short-handed. We have tremendous support from the RICG, but we’re short on day-to-day coding time—we have a lot going on in the RICG, from getting responsive images into the WordPress core to starting the effort for element queries. That’s where we need your help.

Even though the script itself is relatively small, Picturefill is a massive open source project in terms of usage and scope. We need to grow the team if we want to keep up.

Sound off in the comments here if you want to join the team, and I’m happy to help you get started. I’ve got a Slack channel started up for Picturefill team discussion (and we can go with an IRC channel if people are more comfortable there).

I didn’t cut any corners on the 2.3 milestone. There are a hell of a lot of people depending on Picturefill to do their day-to-day work, and we’ll be adding every single WordPress user to that list soon. If you want to be a part of bringing real responsive images to the web, I want to hear from you, and I want to work with you on this.

@Wilto Wilto added this to the Version 2.3 Beta milestone Nov 19, 2014
@aFarkas
Copy link
Collaborator

aFarkas commented Nov 19, 2014

me ;-)

@benedfit
Copy link

Sign me up

@sherred
Copy link

sherred commented Nov 19, 2014

Let's do this

@nhoizey
Copy link

nhoizey commented Nov 19, 2014

I'm not really good enough in JS to help on the library code, but I can give time to help make some tests, enhance the docs and examples, etc.

@vfalconi
Copy link

Down.

@jegtnes
Copy link
Collaborator

jegtnes commented Nov 19, 2014

Same as @nhoizey–my JS-fu is lacking, but I'd love to help with docs, issue triaging, etc.

You have my sword.

@mike-engel
Copy link
Collaborator

I may not be the best at Javascript either, but I can certainly try and help. There's also documentation and testing I can do as well!

@jonathantneal
Copy link
Collaborator

And my axe!

@slicethendice
Copy link

Count me in!

@Wilto
Copy link
Collaborator Author

Wilto commented Nov 20, 2014

Awesome.

Alongside all of us doing the heavy-duty JS, I think a “triage team” is a great idea—working on docs, reproducing issues and building test cases, keeping the issue tracker sorted, etc.

So yeah, we’d be psyched to have everyone on this thread involved. Shoot me an email at mat at matmarquis dot com so I have your address, and I’ll get everyone invited shortly.

@zoltan-dulac
Copy link

I am definitely in. I've done a bit of research already on alternative image formats (WEBP, JPEG-XR and JPEG 2000), and am totally up to getting on board building support one way or another with them as well as anything else that needs to be done (think project, IMHO, is a really important one).

@bryanstedman
Copy link

Happy to help out where I can

@4nduril
Copy link
Collaborator

4nduril commented Nov 24, 2014

I also would like to help on this. I'll write you an email.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests