Sorry, no repo (Was: Google Code closing)
Hi Jon, hi all! I'm very sorry, but from now on I won't support any repo for PicoLisp. As ever, the most up-to-date version can be downloaded from http://software-lab.de/picoLisp.tgz and related stuff is linked from the Download page http://software-lab.de/down.html I like being able to keep an eye on what Alex is working on. ;-) Sure :) I'll provide a ChangeLog file with more extensive notes about what is going on. ♪♫ Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Sorry, no repo (Was: Google Code closing)
Fair enough! Whatever works best for you is for the best. On March 17, 2015 7:34:09 AM CET, Alexander Burger a...@software-lab.de wrote: Hi Jon, hi all! I'm very sorry, but from now on I won't support any repo for PicoLisp. As ever, the most up-to-date version can be downloaded from http://software-lab.de/picoLisp.tgz and related stuff is linked from the Download page http://software-lab.de/down.html I like being able to keep an eye on what Alex is working on. ;-) Sure :) I'll provide a ChangeLog file with more extensive notes about what is going on. ♪♫ Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe -- Skickat från min Android-telefon med K-9 E-post. Ursäkta min fåordighet.
Re: Sorry, no repo (Was: Google Code closing)
Hi Jakob, Fair enough! Whatever works best for you is for the best. Thanks. No big issue anyway. Git Co. may be good for maintaining Linux kernels, but for PicoLisp it is just overkill. As I explained in IRC during the last days, my main problem is that they destroy my file meta data (most notably the modification date), so I don't use it at the core of my dev environment. The argument (that the time stamp should be modified upon check out) is that 'make' should rebuild properly. But that's ridiculous for PicoLisp, which builds in a second after a make clean. ♪♫ Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Google Code closing
Hi, It looks like PicoLisp will have to move from Google Code: http://arstechnica.com/information-technology/2015/03/google-to-close-google-code-open-source-project-hosting/ Maybe GitHub could be a good alternative? I like being able to keep an eye on what Alex is working on. ;-) /Jon-- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Google Code closing
Github.com is really nice. On March 13, 2015 9:02:10 AM CET, Jon Kleiser jon.klei...@fsat.no wrote: Hi, It looks like PicoLisp will have to move from Google Code: http://arstechnica.com/information-technology/2015/03/google-to-close-google-code-open-source-project-hosting/ Maybe GitHub could be a good alternative? I like being able to keep an eye on what Alex is working on. ;-) /Jon-- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe -- Skickat från min Android-telefon med K-9 E-post. Ursäkta min fåordighet.
Re: Google Code closing
On Fri, Mar 13, 2015 at 10:02 AM, Jon Kleiser jon.klei...@fsat.no wrote: Maybe GitHub could be a good alternative? I like being able to keep an eye on what Alex is working on. ;-) +1 for GitHub please -- If technology is your thing plan to die reading manuals --Gene Woolsey -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Google Code closing
Github.com is more than a repo, it's a community of developers. On March 13, 2015 12:56:32 PM CET, Alexander Burger a...@software-lab.de wrote: Hi all, Alea iacta est :) Mike Pechkin has set up a repo at bitbucket. More next week. ♪♫ Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe -- Skickat från min Android-telefon med K-9 E-post. Ursäkta min fåordighet.
RE: Google Code closing
Mike Pechkin has set up a repo at bitbucket. More next week. [...] Github.com is more than a repo, it's a community of developers. Once the repo is available on bitbucket, it will be trivial to set up an automatic mirror. Philosophically, I favor bitbucket. Pragmatically, I favor github(R). A mirror (with bitbucket being primary) serves both masters. If no one on the list already knows how to set up the automatic mirror and volunteers to do it, I'll volunteer to learn how to do it. Cheers, --Dave
Re: Google Code closing
Everyone's comments are valid, but we need to remember: For PicoLisp's user base to grow, lowering barriers to entry should be the first priority. On Fri, Mar 13, 2015 at 2:51 PM, Loyall, David david.loy...@nebraska.gov wrote: Mike Pechkin has set up a repo at bitbucket. More next week. [...] Github.com is more than a repo, it's a community of developers. Once the repo is available on bitbucket, it will be trivial to set up an automatic mirror. Philosophically, I favor bitbucket. Pragmatically, I favor github(R). A mirror (with bitbucket being primary) serves both masters. If no one on the list already knows how to set up the automatic mirror and volunteers to do it, I'll volunteer to learn how to do it. Cheers, --Dave
Re: Google Code closing
On Fri, Mar 13, 2015 at 9:23 PM, Alexander Burger a...@software-lab.de wrote: On Fri, Mar 13, 2015 at 02:04:21PM +0100, Jakob Eriksson wrote: Github.com is more than a repo, it's a community of developers. Hmm, this may well be. I have no idea, as I personally have no deep interest in code repositories. The power of the github community worth consideration. It might attract the attention of exceptional talent... -- tom
Re: Google Code closing
The power of the github community and the level of talent there are impressive. Seems like others have generally recognized that: http://www.engadget.com/2015/03/13/google-code-closing/. Cheers. On Fri, Mar 13, 2015 at 09:41:11PM +0800, Tamas Herman wrote: On Fri, Mar 13, 2015 at 9:23 PM, Alexander Burger a...@software-lab.de wrote: On Fri, Mar 13, 2015 at 02:04:21PM +0100, Jakob Eriksson wrote: Github.com is more than a repo, it's a community of developers. Hmm, this may well be. I have no idea, as I personally have no deep interest in code repositories. The power of the github community worth consideration. It might attract the attention of exceptional talent... -- tom -- Joe Golden -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Google Code closing
On Fri, Mar 13, 2015 at 02:04:21PM +0100, Jakob Eriksson wrote: Github.com is more than a repo, it's a community of developers. Hmm, this may well be. I have no idea, as I personally have no deep interest in code repositories. We discussed and discuss such things in IRC usually. Those who offer their help first win ;) ♪♫ Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Google Code closing
I'm on both networks and we actually use both at work and we are paid users of both. The current idea is to use bitbucket for the in-house private source repos and github for the open source projects. I don't have a strong preference for either one, because I think git is suck in general. I was a long time fan of http://darcs.net , but I didn't have the chance to use it recently. I have to admit though that the lack of proper interactive commit tool for darcs puts it behind git, no matter how crap git is otherwise. :( It really makes me sad but I'm not skilled enough to write such a tool... The equivalent of github in darcs land is http://hub.darcs.net which looks very simple but quite powerful actually and u can host it yourself too. There is http://fossil-scm.org too which has a lot of nice aspects, like size, built-in wiki, etc, but there is no equivalent of github for it as far as I know. These last 2 are closer to the spirit of picolisp's minimalis, that's why I thought it's worth mentioning them. -- tom
Re: Google Code closing
On Fri, Mar 13, 2015 at 4:32 PM, Alexander Williams a...@unscramble.co.jp wrote: Everyone's comments are valid, but we need to remember: For PicoLisp's user base to grow, lowering barriers to entry should be the first priority. The choice of the repo wouldn't have any effect on pure picolisp users, but on developers or translators of the language. Except maybe for contributing to documentation. Personaly, I'd prefer git/GitHub since I already tried to contribute to a project on BitBucket but failed miserably. Anyway, I'm more a user than a dev of picolisp. https://code.google.com/p/support-tools/wiki/MigratingToBitbucket seems to require several steps. https://code.google.com/export-to-github/ seems to be more automated, but: «The Google Code Exporter is experiencing extremely high traffic. The export queue is full. Please come back later. » chri -- http://profgra.org/lycee/ (site pro) http://delicious.com/profgraorg (liens, favoris) https://twitter.com/profgraorg http://microalg.info -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Google Code closing
And github.com has like, what, 1000 times more developers. :-) On March 13, 2015 4:32:05 PM CET, Alexander Williams a...@unscramble.co.jp wrote: Everyone's comments are valid, but we need to remember: For PicoLisp's user base to grow, lowering barriers to entry should be the first priority. On Fri, Mar 13, 2015 at 2:51 PM, Loyall, David david.loy...@nebraska.gov wrote: Mike Pechkin has set up a repo at bitbucket. More next week. [...] Github.com is more than a repo, it's a community of developers. Once the repo is available on bitbucket, it will be trivial to set up an automatic mirror. Philosophically, I favor bitbucket. Pragmatically, I favor github(R). A mirror (with bitbucket being primary) serves both masters. If no one on the list already knows how to set up the automatic mirror and volunteers to do it, I'll volunteer to learn how to do it. Cheers, --Dave -- Skickat från min Android-telefon med K-9 E-post. Ursäkta min fåordighet.