Re: URL comparison

(- some groups, +alex)

Yeah, I've been delaying a bigger conversation on a whole
lifecycle/registry how we progress things into real standards
bodies/hand off to vendors, whatever until we had a few other things
in place... I'd suggest that should be a different thread if someone
really wants to start it now.

Separately from that perhaps (for now at least, since that is a bigger
topic) - is there a handy way that we can suggest that a single item
collect use cases, feedback, build out test cases, etc...  I know alex
has been using github just for DOM Futures
(https://github.com/slightlyoff/DOMFuture/) - maybe that the best way
to go for now?  We can start pumping through the uri ones to help
Anne/Tab collect feedback, I'm just wondering if we can get any input
on a sane/reasonable way to do so because at least for our stuff that
was mentioned, it has been kinda all over the place and hard to gather
together.  Pushing it out on HN is a good exercise, same with twitter,
etc - but all of those kinds of comments get lost unless someone is
tracking them somewhere.  Maybe github is the way to go for now...

Alex?  Any feedback on your experience with that?



On Wed, May 1, 2013 at 6:05 PM, Clint Hill <clint.hill@gmail.com> wrote:
> I'd like to add to what Brian is saying below: This is effectively the
> goal of the public-nextweb group as I see it. We want to provide a way for
> developers to build these types of prollyfills and .. More importantly ..
> Share and publicize them to get the necessary exposure and feedback.
>
> Without that second part there is no point in the first. I think
> prollyfill.org could be more useful if it acted as a registry for these
> things. In fact Brian and I did this with Hitch (leveraging Github as the
> source host) and I tend to believe this is the right way. Right now there
> is a wiki listing the known prollyfills out in the wild but maybe this is
> not easy to find and not easy to provide feedback too.
>
> It's my opinion that prollyfill.org turn into a registry that is simply
> pointer to Github projects.
>
> Thoughts?
>
>
> On 5/1/13 10:03 AM, "Brian Kardell" <bkardell@gmail.com> wrote:
>
>>+ the public-nextweb list...
>>
>>On Wed, May 1, 2013 at 9:00 AM, Anne van Kesteren <annevk@annevk.nl>
>>wrote:
>>> On Sun, Apr 28, 2013 at 12:56 PM, Brian Kardell <bkardell@gmail.com>
>>>wrote:
>>>> We created a prollyfill for this about a year ago (called :-link-local
>>>> instead of :local-link for forward compatibility):
>>>>
>>>> http://hitchjs.wordpress.com/2012/05/18/content-based-css-link/
>>>
>>> Cool!
>>>
>>>
>>>> If you can specify the workings, we (public-nextweb community group)
>>>>can rev
>>>> the prollyfill, help create tests, collect feedback, etc so that when
>>>>it
>>>> comes time for implementation and rec there are few surprises.
>>>
>>> Did you get any feedback thus far about desired functionality,
>>> problems that are difficult to overcome, ..?
>>>
>>>
>>> --
>>> http://annevankesteren.nl/
>>
>>We have not uncovered much on this one other than that the few people
>>who commented were confused by what it meant - but we didn't really
>>make a huge effort to push it out there... By comparison to some
>>others it isn't a very 'exciting' fill (our :has() for example had
>>lots of comment as did our mathematical attribute selectors) - but we
>>definitely can.  I'd like to open it up to these groups where/how you
>>think might be an effective means of collecting necessary data -
>>should we ask people to contribute comments to the list? set up a git
>>project where people can pull/create issues, register tests/track fork
>>suggestions, etc?  Most of our stuff for collecting information has
>>been admittedly all over the place (twitter, HN, reddit, blog
>>comments, etc), but this predates the nextweb group and larger
>>coordination, so I'm *very happy* if we can begin to change that.
>>
>>
>>
>>--
>>Brian Kardell :: @briankardell :: hitchjs.com
>>
>
>



-- 
Brian Kardell :: @briankardell :: hitchjs.com

Received on Wednesday, 1 May 2013 22:25:53 UTC