Community requests repo

[Nicolas Gallagher]

Hey,

I'd like to get the H5BP org's "lazyweb requests" repo set up soon. It would be

a good place for community requests and projects to be born. Maybe not called

"lazyweb" though.

The way Dave has set up his repo is quite nice. Issues to discuss, but .md

files to contain the "spec"/details in one place. Any other thoughts on a nice 

way to organize things?

[Addy Osmani]

As per Twitter, I think placing this under H5BP would be a good idea. It would certainly 

be useful for us to have a 'centralized' place where people in the community 

could post requests/ideas for OSS projects as well as H5BP itself. 

It could even be tied in with the previous efforts we put into movethewebforward as it's 

actually giving people specific issues they can start working on. 

(P.S: I had previously suggested moving over some of Paul's lazywebs to H5BP if

he thinks that would help improve people getting involved or exposure, but anything

that can really get the ball rolling would be helpful)

[divya manian]

Addy, why dont you create one then? We can add all our ideas in there
to get the ball rolling. Also I wonder if desandro would be interested
in pushing his lazyweb stuff to that.

[Addy Osmani]

Sure thing, Divya. Will do! :)

--

Addy Osmani

Software Engineer at Aol | jQuery Team member
Blogger at: http://addyosmani.com

Phone: +44 7501 594 382

[Addy Osmani]

Here we go: https://github.com/h5bp/lazyweb-requests

There are a few ideas I'll be throwing in later today but if anyone has some they'd like

to submit, please feel free to!. We'll probably also flesh out the submission guidelines

and README shortly.

[Nicolas Gallagher]

Erm, ok. I wanted to use this thread to discuss the structure and name

of the repo. But, nevermind.

[Addy Osmani]

I figured that might be the case. As it's only just been created, can we still have

discussions about structure and name? (it's really just a skeleton to kick things off atm)

[Mike Almond]

I'm a little late to the party, but I think moving the lazyweb repo to H5BP was a great idea. I think a name change might be in order. 

I had a few thoughts as to how it should be set up. I like the way PHP Framework Interoperability Group has set up their standards repo with folders and .md files describing them. https://github.com/php-fig/fig-standards. There could be folders for completed, active, and proposed projects. Proposed projects are projects that make the first cut from the issue tracker to a commit in the repo.

In order to keep the repo clean from projects that shouldn't make the cut, I propose the following criteria to push a project to the repo

1. A project that can help other developers in some way (tools, learning aides, etc)

2. Something that pushes what HTML5 can do (mothereffinanimatedgif)

Thoughts?

[Nicolas Gallagher]

I had thought about using Dave's approach, but I'm not sure it is going

to be very easy to manage when it's a community repo and not just one

individual's.

You'll end up having to repeat the contents of the issues in the .md files.

Accepted ideas can be labelled "accepted", rejected ideas can be closed.

My feeling is that sticking to managing things in the issue tracker is going

to be more flexible and introduce less redundancy. It will also be easier 

for the issue creator to edit it as the discussion goes on, etc.

The simpler, the better imo. While we aren't drowning in requests I don't

think we need anything more complicated than the issue tracker.

[Addy Osmani]

Thanks to Nicolas for fleshing out the readme!

I like the idea of project proposals going in markdown files and we could certainly allow 

people to file pull requests to include new ideas in there. Would we just have accepted

(high-level) ideas go into the issue tracker or would people file proposals there too? 

(it might not make sense to have both .md files and use the issue tracker for proposals,

perhaps just one for those accepted).

[Addy Osmani]

I think the below has answered my question. +1 to just using the tracker for ideas

we've accepted with sensible labels.

[Paul Irish]

Divya and I just moved over the paulirish/lazyweb-requests into https://github.com/h5bp/lazyweb-requests/issues

I have a post summarizing the last 14 months of lazyweb requests (currently here https://www.stypi.com/files/9t43lcsu )  that I'm trying to finish and publish. I think it does a lot to show off the power of the community. ;D

If anyone wants to expand on the prose, I'd love the help!

It'll also draw more attention to the repo as it should make a big splash.

The rules of how we triage incoming issues and close longstanding ones can perhaps emerge over time, as this is not a standard use of open source or the issue tracker. :)

Also, I heard Alex Maccaw (creator of Spine, works at Twitter) was thinking of getting a year's worth of financing via Kickstarter to just work on all these issues for the communities benefit. :) Pretty awesome.

[Addy Osmani]

Awesome Paul! Thanks so much for moving your lazyweb's over :)

I think a post would definitely help improve awareness of the idea and hopefully get a few more people

interested in taking up some of the existing issues on there.

If Alex is thinking of getting a Kickstarter up to work on these issues that would be *amazing*. He could

probably knock each of them out in a few weeks if not a lot quicker.

[Paul Irish]

On Thu, Apr 12, 2012 at 5:13 PM, Addy Osmani <addyo...@gmail.com> wrote:

If Alex is thinking of getting a Kickstarter up to work on these issues that would be *amazing*. He could

probably knock each of them out in a few weeks if not a lot quicker.

True. He probably won't but I know plenty of other people that are very much inspired by this repo. It's a good thing