Hello,

After innocently following the instructions on the pyjs site, I've lost 
quite some time trying to get my hands into pyjamas' HEAD, only to find 
that all the bugs I had fixed, had actually been fixed (+ lots of 
goodies) in the LEGACY repository:
http://pyjamas.git.sourceforge.net/git/gitweb.cgi?p=pyjamas/pyjamas;a=summary
There was even Daniel Kluev's GSOC work there (that's quite scary 
actually, it seems that guy has just disappeared since july).

Really, for newcomers, pyjamas is everything but friendly, sources and 
tools are scatered/duplicated/triplicated all over the web, and there is 
no central, up-to-date manual on how to develop and test on it... need 
to browse the whole repo befoe understanding how it actually works.

Fixing this wouldn't be an incredible job really, it just requires a 
"green light" from core devs (and some admin credentials for me if 
nobody else wants to do it)

So here are my propositions:
- make deprecated repository(ies) readonly, or better delete them - 
after all source versioning is made to allow that, isn't it ?
- cleanup and update the pyjs site, which references deprecated depots, 
mailing lists, and has broken links for important pages like "supported 
cpython features". Why not speak about 0.8alpha in it ? And I think 
using pyjs for "static" explanation pages is very counter-productive, as 
you can't just bookmark/share the parts that interest you. Pyjs is for 
dynamic applications, not webpages for which pure html is 100% fit.
- use more robust tools: we have a mailing list that doesn't handle CCs, 
a source browser which is cute but doesn't have half the feature of 
mainstream source browsers... really in some case "eating your own dog 
food" is a hindrance, no need to reinvent the wheel for such basic 
needs. Why not come back to key-in-hand solutions for basic needs, and 
rather push to the front page pyjs demos that show its true usefulness ?

Regards,
Pascal

Reply via email to