On Wed, 23 Nov 2011, Boris Zbarsky wrote:
> On 11/21/11 7:40 PM, Ian Hickson wrote:
> > If people could e-mail me the lists of topics they would be interested in
> > being e-mailed diffs for, it would give me a good idea of what coarseness
> > would be helpful here, and thus whether this is a reali
On 11/21/11 7:40 PM, Ian Hickson wrote:
If people could e-mail me the lists of topics they would be interested in
being e-mailed diffs for, it would give me a good idea of what coarseness
would be helpful here, and thus whether this is a realistic idea.
Things I probably care about right now:
On Mon, Nov 21, 2011 at 11:43 PM, Silvia Pfeiffer
wrote:
> However, I don't think this rough classification actually helps me
> much to identify what I want to look at. If at least the area of
> change is mentioned in your descriptive text, that would help me much
> more. For me "media" (or "video
On Tue, 22 Nov 2011 01:40:10 +0100, Ian Hickson wrote:
On Mon, 21 Nov 2011, Boris Zbarsky wrote:
>
> Another option is for someone (possibly me) to create a system whereby
> people can subscribe to specific portions of the specification, and
> for a tool to detect when a diff affects that port
On Tue, Nov 22, 2011 at 7:54 AM, Ian Hickson wrote:
> On Mon, 21 Nov 2011, Boris Zbarsky wrote:
>> On 11/21/11 3:39 PM, Ian Hickson wrote:
>> > If you can tell me which pieces those are, I can see what I can do
>> > about updating the annotations mechanism to make those checkins easier
>> > to fil
On Mon, 21 Nov 2011, Boris Zbarsky wrote:
> >
> > Another option is for someone (possibly me) to create a system whereby
> > people can subscribe to specific portions of the specification, and
> > for a tool to detect when a diff affects that portion and e-mail them.
> > I'm not exactly sure ho
On 11/21/11 3:54 PM, Ian Hickson wrote:
If the number of people who would benefit from explicit annotations is
small, I would be happy to add explicit annotations for those people.
Given that the set of people who would like to know about spec changes
in "their" area probably includes all deve
On Mon, 21 Nov 2011, L. David Baron wrote:
>
> I have tried to use these markings to filter changes; however, my sense
> was that a majority of those marked as "g" didn't actually require Gecko
> changes. I think that's because you often mark things as affecting
> browsers simply because the b
On Monday 2011-11-21 20:26 +, Ian Hickson wrote:
> On Mon, 21 Nov 2011, Boris Zbarsky wrote:
> >
> > What's needed is a way to notice when changes to a particular piece
> > happen. There isn't one.
>
> Which pieces do you _not_ want to be notified of changes to?
>
> I currently (try to) ma
On Mon, 21 Nov 2011, Boris Zbarsky wrote:
> On 11/21/11 3:39 PM, Ian Hickson wrote:
> > If you can tell me which pieces those are, I can see what I can do
> > about updating the annotations mechanism to make those checkins easier
> > to filter out.
>
> That's the problem. The set of changes tha
On 11/21/11 3:39 PM, Ian Hickson wrote:
If you can tell me which pieces those are, I can see what I can do about
updating the annotations mechanism to make those checkins easier to filter
out.
That's the problem. The set of changes that matter to a particular
person is not static...
Up unti
On Mon, 21 Nov 2011, Boris Zbarsky wrote:
> On 11/21/11 3:26 PM, Ian Hickson wrote:
> > > What's needed is a way to notice when changes to a particular piece
> > > happen. There isn't one.
> >
> > Which pieces do you _not_ want to be notified of changes to?
>
> "Whatever doesn't affect code I ma
On 11/21/11 3:26 PM, Ian Hickson wrote:
What's needed is a way to notice when changes to a particular piece
happen. There isn't one.
Which pieces do you _not_ want to be notified of changes to?
"Whatever doesn't affect code I maintain", with my implementor hat on.
Yes, I know this is vague.
On Mon, 21 Nov 2011, Boris Zbarsky wrote:
>
> What's needed is a way to notice when changes to a particular piece
> happen. There isn't one.
Which pieces do you _not_ want to be notified of changes to?
I currently (try to) mark all changes that affect browser vendors as such
in the checkin co
On 11/21/11 11:04 AM, Anne van Kesteren wrote:
Following everything what is going on with regards to the platform is
impossible these days. There are too many pieces.
Indeed. What's needed is a way to notice when changes to a particular
piece happen. There isn't one.
A poor stand-in would
On Mon, 21 Nov 2011 16:35:09 +0100, Nils Dagsson Moskopp
wrote:
"Anne van Kesteren" schrieb am Mon, 21 Nov 2011
15:14:16 +0100:
I personally had a number of
useful technical discussions on Google+. Maybe some of those will
take place on the WHATWG Google+ page.
Excluding those without an ac
On 11/21/11 10:48 AM, Boris Zbarsky wrote:
My "impression" is that following all changes to the specification via
the revision control system is a pretty large burden, if nothing else
because there is no obvious way to do it linked from anywhere I can
find. Maybe a small set of people "in the kno
On 11/21/11 10:38 AM, Anne van Kesteren wrote:
On Mon, 21 Nov 2011 16:16:22 +0100, Boris Zbarsky wrote:
As long as all technical discussion ends up in a central place where
everyone can see it at some point, no harm done.
My experience is that once you have side channels for technical
discussi
On Mon, 21 Nov 2011 16:16:22 +0100, Boris Zbarsky wrote:
As long as all technical discussion ends up in a central place where
everyone can see it at some point, no harm done.
My experience is that once you have side channels for technical
discussion, that doesn't happen anymore. Plenty of
"Anne van Kesteren" schrieb am Mon, 21 Nov 2011
15:14:16 +0100:
> On Mon, 21 Nov 2011 14:54:38 +0100, Nils Dagsson Moskopp
> wrote:
> > With less sarcasm: What use is this if one already reads the blog?
> […]
> Basically, I'm hoping to find out.
I can understand you. I tried out G+ too and f
On 11/21/11 9:22 AM, Jake Verbaten wrote:
As long as G+ is only an optional addition for people who want to use it,
does it really do harm?
As long as all technical discussion ends up in a central place where
everyone can see it at some point, no harm done.
My experience is that once you hav
(11/11/21 22:14), Anne van Kesteren wrote:
> We started with email, branched out to IRC, got forums and wiki, a blog,
> a Twitter account. Each of those has proven successful I think. Not
> always to the same people, but I think that is the value. By giving
> people choice in how to participate we
>
> With less sarcasm: What use is this if one already reads the blog?
None, this isn't for you. It's for people who use G+. It's a minor addition
that increases the total number of ways you can get information.
As long as G+ is only an optional addition for people who want to use it,
does it re
On Mon, 21 Nov 2011 14:54:38 +0100, Nils Dagsson Moskopp
wrote:
With less sarcasm: What use is this if one already reads the blog?
This was brought up on IRC as well:
http://krijnhoetmer.nl/irc-logs/whatwg/2021#l-348
Basically, I'm hoping to find out. I personally had a number of useful
"Anne van Kesteren" schrieb am Mon, 21 Nov 2011
13:44:58 +0100:
> Not knowing what the Pages feature was on Google+, I decided to try
> it out. Now WHATWG is represented there:
>
>https://plus.google.com/110228011578241735536/
>
> I plan on sharing links to the WHATWG Weekly. Ideas welcome,
Not knowing what the Pages feature was on Google+, I decided to try it
out. Now WHATWG is represented there:
https://plus.google.com/110228011578241735536/
I plan on sharing links to the WHATWG Weekly. Ideas welcome, but since
apparently there can only be one maintainer for a given page on
26 matches
Mail list logo
