Are you saying there are differences between...

I thought this was master

git://pyjamas.git.sourceforge.net/gitroot/pyjamas/pyjamas

And this was regularly pulled to...

git clone git://pyjs.org/git/pyjamas.git

Are you saying that this isn't the case ?

And yeah where did Daniel Kluev disappear to, his user is always signed in
to #pyjamas irc channel but never responds.

I agree alot with what you're saying regarding the state of the project.

It makes me wonder how many people have been put off using pyjamas who
never leave any feedback on the mailing list as they never get that far.

I know Luke and others have put a lot of effort in to the project and I
don't want this to sounds bad becase as Luke says, he isn't PAID to do any
of this but the way I see it is incorrect/misleading/old information is
worse than none at all in most cases.

Also if people don't want to document things then it would at least be nice
for people to put more docsctrings/comments with rationale and reasoning
behind what they have been doing so that if you have to fall back to the
source code for documentation then at least more junior devs have a chance
to understand whats going on.

Why can't you just send messages using the google groups interface and
avoid being spammed with email.

Also please for can we get rid of the pyjamas apps (source browsing and
mailing list viewer), they haven't been updated and don't work very well
and obv. it would seem no one wants to make them any better and doesn;t
care, why don't we just use the tools already out there, and yeah why are
there still references to a version of pyjamas that shouldn;t be used there
on the pyjamas website.

Also whenever anyone has a query they seem to be told to update from GIT,
then why do we even have a link to a distribution that is out of date
anyway.




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
> 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