Re: [webkit-dev] Filling the features.json files

[Benjamin Poulain]

On 4/8/15 10:41 PM, Daryle Walker wrote:

On Apr 8, 2015, at 6:45 PM, Benjamin Poulain  wrote:


On 4/8/15 12:01 PM, Bem Jones-Bey wrote:


On 4/7/15, 21:09, "Benjamin Poulain"  wrote:


The only mandatory fields are "name" and "status".


What are the valid values for the “status” field, and what is the criteria for 
a feature to be classified under each value?


-"enabled-by-default" tells if the feature is in WebKit nightly.
-"status" is free text, it will be shown as it is.
-"shipped" is the list of the first release versions shipping the feature.


Add, at least eventually, a “retired” column for the release version that 
dropped the feature. Maybe include a list of newer features that (at least 
partially) replace it. (An empty list would mean no replacement, or none yet.)


Yep, that's a good point, Shared workers is a good example of such case.


For the status text, I have not made up any rule yet. I used:
-"Done": fully functional, maybe some minor bugs left.
-"Prototyping": proof of concept kind of work.
-"In Development": anything in between the other two. Even something that 
barely work can use this.

Outside status, you can also add "comment" if you want to clarify something, 
want feedback, etc.


—
Daryle Walker
Mac, Internet, and Video Game Junkie
darylew AT mac DOT com



___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Filling the features.json files

[Daryle Walker]

On Apr 8, 2015, at 6:45 PM, Benjamin Poulain  wrote:
> 
> On 4/8/15 12:01 PM, Bem Jones-Bey wrote:
>> 
>> On 4/7/15, 21:09, "Benjamin Poulain"  wrote:
>>> 
>>> The only mandatory fields are "name" and "status".
>> 
>> What are the valid values for the “status” field, and what is the criteria 
>> for a feature to be classified under each value?
> 
> -"enabled-by-default" tells if the feature is in WebKit nightly.
> -"status" is free text, it will be shown as it is.
> -"shipped" is the list of the first release versions shipping the feature.

Add, at least eventually, a “retired” column for the release version that 
dropped the feature. Maybe include a list of newer features that (at least 
partially) replace it. (An empty list would mean no replacement, or none yet.)

> For the status text, I have not made up any rule yet. I used:
> -"Done": fully functional, maybe some minor bugs left.
> -"Prototyping": proof of concept kind of work.
> -"In Development": anything in between the other two. Even something that 
> barely work can use this.
> 
> Outside status, you can also add "comment" if you want to clarify something, 
> want feedback, etc.

— 
Daryle Walker
Mac, Internet, and Video Game Junkie
darylew AT mac DOT com 

___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Filling the features.json files

[Benjamin Poulain]

On 4/8/15 3:52 PM, Bem Jones-Bey wrote:



On Apr 8, 2015, at 15:45, Benjamin Poulain 
wrote:

On 4/8/15 12:01 PM, Bem Jones-Bey wrote:


On 4/7/15, 21:09, "Benjamin Poulain" 
wrote:


The only mandatory fields are "name" and "status".


What are the valid values for the “status” field, and what is the
criteria for a feature to be classified under each value?


-"enabled-by-default" tells if the feature is in WebKit nightly.
-"status" is free text, it will be shown as it is. -"shipped" is
the list of the first release versions shipping the feature.

For the status text, I have not made up any rule yet. I used:
-"Done": fully functional, maybe some minor bugs left.
-"Prototyping": proof of concept kind of work. -"In Development":
anything in between the other two. Even something that barely work
can use this.

Outside status, you can also add "comment" if you want to clarify
something, want feedback, etc.


What do you think about having a version of “Done” for fully
functional, but -webkit prefixed? For example, we’ve implemented all
the features of CSS Shapes Level 1, the spec is in CR, but we still
have some bugs to fix. I’d assume that would be past the prototyping
phase at this point, but not quite Done, given that it’s still
prefixed.


If there are only minor bugs left, my first preference would be to 
unprefix. :)


If the bugs are not so minor, I think "In Development" would be okay.

You can also make up your own status string for now, I'll triage them at 
some point :)


All of this is really about documentation. Add as much comments as you 
need in "comment" to explain the state of the feature.


Benjamin
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Filling the features.json files

[Bem Jones-Bey]

> On Apr 8, 2015, at 15:45, Benjamin Poulain  wrote:
> 
> On 4/8/15 12:01 PM, Bem Jones-Bey wrote:
>> 
>> On 4/7/15, 21:09, "Benjamin Poulain"  wrote:
>>> 
>>> The only mandatory fields are "name" and "status".
>> 
>> What are the valid values for the “status” field, and what is the criteria 
>> for a feature to be classified under each value?
> 
> -"enabled-by-default" tells if the feature is in WebKit nightly.
> -"status" is free text, it will be shown as it is.
> -"shipped" is the list of the first release versions shipping the feature.
> 
> For the status text, I have not made up any rule yet. I used:
> -"Done": fully functional, maybe some minor bugs left.
> -"Prototyping": proof of concept kind of work.
> -"In Development": anything in between the other two. Even something that 
> barely work can use this.
> 
> Outside status, you can also add "comment" if you want to clarify something, 
> want feedback, etc.

What do you think about having a version of “Done” for fully functional, but 
-webkit prefixed? For example, we’ve implemented all the features of CSS Shapes 
Level 1, the spec is in CR, but we still have some bugs to fix. I’d assume that 
would be past the prototyping phase at this point, but not quite Done, given 
that it’s still prefixed.

- Bem
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Filling the features.json files

[Benjamin Poulain]

On 4/8/15 12:01 PM, Bem Jones-Bey wrote:


On 4/7/15, 21:09, "Benjamin Poulain"  wrote:


The only mandatory fields are "name" and "status".


What are the valid values for the “status” field, and what is the criteria for 
a feature to be classified under each value?


-"enabled-by-default" tells if the feature is in WebKit nightly.
-"status" is free text, it will be shown as it is.
-"shipped" is the list of the first release versions shipping the feature.

For the status text, I have not made up any rule yet. I used:
-"Done": fully functional, maybe some minor bugs left.
-"Prototyping": proof of concept kind of work.
-"In Development": anything in between the other two. Even something 
that barely work can use this.


Outside status, you can also add "comment" if you want to clarify 
something, want feedback, etc.


Benjamin

___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Filling the features.json files

[Benjamin Poulain]

On 4/8/15 10:34 AM, Maciej Stachowiak wrote:



On Apr 8, 2015, at 5:42 AM, Antti Koivisto mailto:koivi...@iki.fi>> wrote:

On Wed, Apr 8, 2015 at 7:09 AM, Benjamin Poulain mailto:benja...@webkit.org>>wrote:

Hi WebKit,

The two features.json files are in the tree (WebCore/features.json
and JavaScriptCore/features.json). The style checker now checks
the basic structure of the files.


Could you also explain what these files are used for?


They’ll be used to generate a feature status page similar to the ones
that Chrome, IE and Firefox have.

I am curious if we have a way to generate the page yet.


The page is not there yet, hopefully I'll have time to start that next 
weekend.


Benjamin
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Filling the features.json files

[Bem Jones-Bey]

On 4/7/15, 21:09, "Benjamin Poulain"  wrote:





>
>The only mandatory fields are "name" and "status".

What are the valid values for the “status” field, and what is the criteria for 
a feature to be classified under each value?

Thanks,
Bem
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Filling the features.json files

[Maciej Stachowiak]

> On Apr 8, 2015, at 5:42 AM, Antti Koivisto  wrote:
> 
> On Wed, Apr 8, 2015 at 7:09 AM, Benjamin Poulain  > wrote:
> Hi WebKit,
> 
> The two features.json files are in the tree (WebCore/features.json and 
> JavaScriptCore/features.json). The style checker now checks the basic 
> structure of the files.
> 
> Could you also explain what these files are used for?

They’ll be used to generate a feature status page similar to the ones that 
Chrome, IE and Firefox have.

I am curious if we have a way to generate the page yet.

Regards,
Maciej

___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Filling the features.json files

[Antti Koivisto]

On Wed, Apr 8, 2015 at 7:09 AM, Benjamin Poulain 
wrote:

> Hi WebKit,
>
> The two features.json files are in the tree (WebCore/features.json and
> JavaScriptCore/features.json). The style checker now checks the basic
> structure of the files.
>

Could you also explain what these files are used for?


  antti


>
> I have added some basic things in there to show the basic structure. I
> would like help setting up those lists.
>
> If you have worked on a feature in the last 12 months, and you want to
> give it the visibility it deserves, please add it to features.json.
>
> An other type of feature that would be useful for those files are features
> that are not as popular as they should (image-set, srcset,
> sticky-positioning, etc).
>
> The only mandatory fields are "name" and "status".
>
> Committers can edit those files without reviews. Other contributors can
> make patches and ping me for review.
>
> Any question? Email me or poke me on IRC.
>
> Benjamin
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-dev
>
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

[webkit-dev] Filling the features.json files

[Benjamin Poulain]

Hi WebKit,

The two features.json files are in the tree (WebCore/features.json and 
JavaScriptCore/features.json). The style checker now checks the basic 
structure of the files.


I have added some basic things in there to show the basic structure. I 
would like help setting up those lists.


If you have worked on a feature in the last 12 months, and you want to 
give it the visibility it deserves, please add it to features.json.


An other type of feature that would be useful for those files are 
features that are not as popular as they should (image-set, srcset, 
sticky-positioning, etc).


The only mandatory fields are "name" and "status".

Committers can edit those files without reviews. Other contributors can 
make patches and ping me for review.


Any question? Email me or poke me on IRC.

Benjamin
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev