Add guidelines for feature addition to webkit.org (per disccusion at contributor meeting)

• Component: New Bugs
• Status: RESOLVED FIXED

[Eric Seidel (no email)]

Add guidelines for feature addition to webkit.org (per disccusion at contributor meeting)

[Eric Seidel (no email)]

Created attachment 91430 [details]
Patch

[Alexey Proskuryakov]

I feel like the policy is experimental at this point, and may need to be adjusted a lot. Publishing it without acknowledging that can cause tension when such adjustments happen.

[Eric Seidel (no email)]

Specific language you'd like to see?

My intended approach was not to dictate experimental policy, but rather offer (toothless) guidelines.  I believe we had consensus for that at both the meeting and on webkit-reviewers.  But I'm very open to changing the language if you have specific suggestions.

It seems we should probably take this discussion to webkit-reviewers.

[George Staikos]

I like this so far, but I also think that we need to work harder to make it possible for people to do work in branches and effectively and efficiently maintain those branches.  Some suggestions for that would be great.

[Adam Barth]

Comment on attachment 91430 [details]
Patch

This looks like a good start.  Can you address Alexey's comment by adding some text indicating that this policy is an experiment and setting a date (maybe six months from now) when we should either decide to keep the policy or chuck it?

[Eric Seidel (no email)]

Committed r86062: <http://trac.webkit.org/changeset/86062>

[Eric Seidel (no email)]

Done.

These guidelines were created in response to the "Can WebKit Say No?" session at the 2011 contributors meeting.  These guidelines should be regarded as "experimental" as we plan to review their effectiveness (and possibly amend/remove them) at the 2012 contributors meeting.