On Wed, Feb 1, 2012 at 12:46 PM, Peter Bittner <[email protected]> wrote: > Luke, > >> the git clone commands are: >> >> git clone [email protected]:pyjamaslamson >> git clone [email protected]:pyjamasgitweb > > Shall we add this information to the developer section on the website?
mrhhm.... *thinks*... if going to do that, then it's time to kill off sf.net because the pyjamas one is of course git clone [email protected]:pyjamas but *only* for those people who've given me gitolite ssh public keys (which is... everyone in the past 18 months i.e. about 30 people, amazingly enough). > To make sure that (new) contributors get the full picture about what > source code is all around from the pyjs project. yep. sourceforge goes. go for it peter. ok ladies (people with write-access to the sf.net pyjamas repository): sf.net is history - you can do this one of several ways: i have the following in ~/pyjamas/.git/config [remote "origin"] fetch = +refs/heads/*:refs/remotes/origin/* url = ssh://[email protected]/gitroot/pyjamas/pyjamas [branch "master"] remote = origin merge = refs/heads/master [remote "pyjs"] fetch = +refs/heads/*:refs/remotes/origin/* url = [email protected]:pyjamas and that should be: [remote "origin"] fetch = +refs/heads/*:refs/remotes/origin/* url = [email protected]:pyjamas [branch "master"] remote = origin merge = refs/heads/master if you make that modification to ~/.git/config you will *not* need to do a "new checkout" blah blah. for everyone who has read-only access, the git repo access is "git clone git://pyjs.org/git/pyjamas.git" > I'd also like to clean up the code and files for the website in the > repo. In my eyes it's all a weired mess (sorry if I hurt someone's > feelings). pffh. welcome to egoless programming - i'm just delighted that you're happy to sort things out. to hell with "aww mee, ohh myy, my feelings are hurt because i'm sooo attached to that cooode and it means sooo much to me i put sooo much of my eego into that web site" *lol*. > Can we move everything that has to do with the website > (incl. all docs, api, Pyjamas book) to a dedicated repository? *ambivalent* - anyone else got any opinions on this? the reason why i put the docs and the pyjamas book into the repository is that if anyone wants a local copy, it'll be one repository, that's all they need, done. run the Makefile - done, it's compiled. > The > directory structure should IMO reflect the actual structure on the web > server (or so). yeahh, it's a bit of a mish-mash because of course 95% of the stuff that goes on the web site is of course auto-generated. btw you're NOT allowed to commit compiled code to the git repos, ok? that would create absolute merry hell. > The only downside I currently see is we won't have pygit and the > mailing list mail app in the same repo, because they are in a separate > repo already. yeahh, that's deliberate - they're separate apps. hmm... i tell you what - shall i create a new repository that has all these things as "submodules"? i only just discovered git submodules - they're cool. you _should_ be able to just have absolutely everything in that one repo, hit "make install" and blat, you should have an entire copy of the entire pyjs.org web site. l.
