On Wed, Dec 7, 2011 at 7:20 PM, Pascal Chambon <[email protected]> wrote: > 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
that's not the legacy repository, pascal. > There was even Daniel Kluev's GSOC work there (that's quite scary > actually, it seems that guy has just disappeared since july). yeah i know. very weird. > 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... yes there is - it's DEVELOPER.RULES and also, there is a general expectation that if there's something you don't understand, it's best to ask on the mailing list. that's how free software projects work. > need > to browse the whole repo befoe understanding how it actually works. there are very few free software projects where you *don't* need to browse the entire source code to understand how it actually works. luckily in this case, it's quite a compact codebase. but, again: if there's something you need advice on, it's best to ask. > 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) works for me. hmmm... i've got an ssh public key for you already, haven't i? > So here are my propositions: > - make deprecated repository(ies) readonly, there aren't any. the one on pyjs.org is "sync'd" - i keep meaning to shut down the one on sf.net, just keep not getting round to 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 ? because i work on pyjamas when *i* need it. and, given that i have not had any major paid-for contract work (web sites etc.) that require pyjamas, i am operating in a much more "passive" role. if on the other hand there was a rush of people requiring pyjamas contract work, i would immediately have the time, money and incentive - personally - to do things like update the web site. however, given that there is not, i am keeping my role to an absolute minimum. > 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. yes you can - those that have "#" history token tags.... if the application has that enabled. http://pyjs.org/#FAQ hmmm.. doesn't seem to work as expected. that's a bug. > Pyjs is for > dynamic applications, not webpages for which pure html is 100% fit. it's not a panacea. you have to follow the "AJAX search" rules in the server back-end. there was some discussion about how google had added ! and # and some half-baked scheme into their search engine in order to index AJAXified sites. a pyjamas site is no different. you just have to follow the rules. > - use more robust tools: we have a mailing list that doesn't handle CCs, if you'd like to do an update to lamson, that will get taken care of. however you have to watch out because i had to fix some bugs in lamson. > 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, sorry, but tough. read richard stallman's essays on the principles behind free software. if it's "monetarily zero cost" it's *NOT* Software Libre. i'm a Software Libre Developer, not a banged up wannabe pretender looking to screw people over in the name of maximising profits. > no need to reinvent the wheel for such basic needs. if it's "non-free" then as far as i'm concerned it doesn't exist. therefore it *has* to be invented - from scratch. and, critically, released under a Software Libre license. the only reason i haven't shut down the use of code.google.com and the sf.net sites is lack of time to create alternatives that are pyjs-based. > Why not come back to key-in-hand solutions for basic needs, tell me where i can get the source code for such key-in-hand solutions, under Software Libre Licenses, written in python and better yet designed such that a pyjamas front-end can easily be slotted on top of them and i will happily replace them. > and rather push to the front page pyjs demos that show its true usefulness ? hmmm. yeah that does appear to be lacking - squashed over into the corner.

