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


> 
> 
> 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
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to