HTML parser (again)

> I will try to push a CogVM for the mac this weekend, Eliot and I are  
> planing some time then to get this out the door.
>
> On 2010-08-18, at 2:05 PM, stephane ducasse wrote:
>
>> no CogVM is not ready for us.
>>
>>
>>
>
> --
> =
> =
> =
> =
> =
> ======================================================================
> John M. McIntosh <[hidden email]>   Twitter:  
> squeaker68882
> Corporate Smalltalk Consulting Ltd.  http://
> www.smalltalkconsulting.com
> =
> =
> =
> =
> =
> ======================================================================
>
>
>
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

> Yes Sean, actually SqueakSource is not really "Share Friendly".  I wonder if a solution is not having only one repository for all as Monticello seems to handle branches itself.  It seems INRIA will start working on this starting from sept. / oct.
>
> The automatic inbox is a solution too. But it doesn't mean packages will be integrated mainstream.
>
> I like public writable repository.
>
> I also wonder why SS is free for private repository, should be paying (so it can pay someone to manage / evolve SqueakSource).
>
> Laurent
>
>
> On Thu, Aug 19, 2010 at 12:30 AM, Sean P. DeNigris <[hidden email]> wrote:
>
>
> laurent laffont wrote:
> >
> > Sean, could you put your package there ?
> >
>
> The wonderful world of Squeak packages...  The package I fixed is Todd
> Blanchard's HTML & CSS Validating Parser at
> http://www.squeaksource.com/htmlcssparser/, not the Scamper HTML from
> http://www.squeaksource.com/HTML, although both packages are called "HTML."
>
> However, this is a lovely opportunity to repeat my call for either (or maybe
> both):
> * (my favorite) create an inbox for each project on SqS, just like for
> Squeak and Pharo trunk, so users can choose between the bleeding edge (which
> would include contributions like this one) or the last officially blessed
> one; but they would all be in the same place and obvious to find.
> * or, send an email to all SqS emails saying that if they don't affirm
> responsibility for their project within X amount of time, the repo will be
> released to the community i.e. made w/r.
>
> I also seem to remember a suggestion at one point to have a list of people
> that were approved to commit to any repo on SqS.
>
> The point is, make it easy to contribute and people will.  It is a downer to
> go through the work of fixing packages, only to put them in my own repo
> where they may never be found by users, because the repo is read-only and I
> can't get in touch with the admins.
>
> <rant>
> Also, adding oneself to each repo is RUBBISH!!!!!  Even though I usually
> take the time, I shudder at the thought of all the community fixes that were
> kept personally or thrown away because it was a hassle to share them.  I'm
> sure many people, like me, just fix things that are broken.  This is the
> whole beauty of a live system that's turtles all the way down - my system's
> menus are broken, great, I just spend 20 minutes fixing them for every user
> on the planet vs. the typical X months (if ever) for an OS vendor to get
> around to a fix
> </rant>
>
> Sean
> --
> View this message in context: http://forum.world.st/HTML-parser-again-tp2329387p2330466.html
> Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

>
>
> laurent laffont wrote:
>>
>> Sean, could you put your package there ?
>>
>
> The wonderful world of Squeak packages...  The package I fixed is Todd
> Blanchard's HTML & CSS Validating Parser at
> http://www.squeaksource.com/htmlcssparser/, not the Scamper HTML from
> http://www.squeaksource.com/HTML, although both packages are called "HTML."
>
> However, this is a lovely opportunity to repeat my call for either (or maybe
> both):
> * (my favorite) create an inbox for each project on SqS, just like for
> Squeak and Pharo trunk, so users can choose between the bleeding edge (which
> would include contributions like this one) or the last officially blessed
> one; but they would all be in the same place and obvious to find.
> * or, send an email to all SqS emails saying that if they don't affirm
> responsibility for their project within X amount of time, the repo will be
> released to the community i.e. made w/r.
>
> I also seem to remember a suggestion at one point to have a list of people
> that were approved to commit to any repo on SqS.
>
> The point is, make it easy to contribute and people will.  It is a downer to
> go through the work of fixing packages, only to put them in my own repo
> where they may never be found by users, because the repo is read-only and I
> can't get in touch with the admins.
>
> <rant>
> Also, adding oneself to each repo is RUBBISH!!!!!  Even though I usually
> take the time, I shudder at the thought of all the community fixes that were
> kept personally or thrown away because it was a hassle to share them.  I'm
> sure many people, like me, just fix things that are broken.  This is the
> whole beauty of a live system that's turtles all the way down - my system's
> menus are broken, great, I just spend 20 minutes fixing them for every user
> on the planet vs. the typical X months (if ever) for an OS vendor to get
> around to a fix
> </rant>
>
> Sean
> --
> View this message in context: http://forum.world.st/HTML-parser-again-tp2329387p2330466.html
> Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

> Yes we should do something.
> Now the question is how to do something that we can actually implement.
> I think that we should
> - start to identify package of interest (quality/topics////)
> - check their license status
> - check the author and get access
> - create an inbox
>
> Stef
>

> Stéphane Ducasse wrote:
>> Yes we should do something.
>> Now the question is how to do something that we can actually implement.
>> I think that we should
>> - start to identify package of interest (quality/topics////)
>> - check their license status
>> - check the author and get access
>> - create an inbox
>> Stef
> Stef,
>
> speaking of licenses...I was thinking that for mcz files, we should have a "directory" of each mcz file that contains the license statement for the code in that _version_ of the mcz file. Most tools would end up ignoring, but if we started including the license _in_ the mcz file, then license status would be _much clearer_.
>
> I also assume that a similar addition to mc2 files could/should be done....
>
> Dale
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

>
> Stef
>
>
>> Stéphane Ducasse wrote:
>>> Yes we should do something.
>>> Now the question is how to do something that we can actually implement.
>>> I think that we should
>>> - start to identify package of interest (quality/topics////)
>>> - check their license status
>>> - check the author and get access
>>> - create an inbox
>>> Stef
>> Stef,
>>
>> speaking of licenses...I was thinking that for mcz files, we should have a "directory" of each mcz file that contains the license statement for the code in that _version_ of the mcz file. Most tools would end up ignoring, but if we started including the license _in_ the mcz file, then license status would be _much clearer_.
>>
>> I also assume that a similar addition to mc2 files could/should be done....
>>
>> Dale
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

>
>> Stef
>>> Stéphane Ducasse wrote:
>>>> Yes we should do something.
>>>> Now the question is how to do something that we can actually implement.
>>>> I think that we should
>>>> - start to identify package of interest (quality/topics////)
>>>> - check their license status
>>>> - check the author and get access
>>>> - create an inbox
>>>> Stef
>>> Stef,
>>>
>>> speaking of licenses...I was thinking that for mcz files, we should have a "directory" of each mcz file that contains the license statement for the code in that _version_ of the mcz file. Most tools would end up ignoring, but if we started including the license _in_ the mcz file, then license status would be _much clearer_.
>>>
>>> I also assume that a similar addition to mc2 files could/should be done....
>>>
>>> Dale
>>>
>>> _______________________________________________
>>> Pharo-project mailing list
>>> [hidden email]
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project