On Fri, 21 Aug 2009, Henrik Sarvell wrote:

I think any kind of private server is overkill for a 250K source, my
suggestion then is to go for Google Code.

However, someone still needs to set it up.

If TC wants to/have the time then I suggest he sets it up on Google
code (he seems to be the best qualified here).

I have no problem with that, but it will have to wait a bit since google code 
is undergoing some scheduled manteinance at the moment.

With Pico on google code I could add my own stuff, such as JSON
encoding/decoding, templating, general helper library and robust RSS
XML parsing. This is all highly experimental and buggy stuff, that's
why I've never bothered having Alex put it there manually (so much is
changing in these things all the time).

That sounds interesting :¬)
Effective community coding.., this is what dvcs systems were conceived for ;¬)
Every contribution would eventually mature enough to make it's way to the 
stable branch, and... we would have a wider range of tools, libs and a more 
versatile picolisp distribution overall. All of this keeping picolisp bloat 
free of course ;¬)

/Henrik


On Fri, Aug 21, 2009 at 11:26 AM, Alexander Burger<a...@software-lab.de> wro=
te:
On Fri, Aug 21, 2009 at 09:48:57AM +0200, Henrik Sarvell wrote:
http://bitbucket.org/plans/. PicoLisp is such a small repository that
we can go free on either BitBucket or GitHub.
...
Then I randomly ended up at this comparison page:
http://www.rockstarprogrammer.org/post/2008/apr/06/differences-between-m=
ercurial-and-git/

In addition, we might want to consider other possibilities.

- Jakob Eriksson comes to mind, he once reserved the domain
=A0"picolisp.org" but we did not use it so far. Jakob?

- Or Tomas Hlavaty who already started the PicoWiki on his "logand.com".
=A0Wouldn't it make sense to put these things together?

- I could host it on "7fach.de", where the demo apps and this mailing
=A0list are running. But if possible I'd like to avoid another task ;-)

Cheers,
- Alex
--
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=3dunsubscribe

--
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe

Reply via email to