I'm sure my opinion has very little weight around here, but since other people are discussing it I want to put in a plug for Savannah (Non-GNU):
https://savannah.nongnu.org/ If you aren't willing to run the proprietary JavaScript on Github it becomes a real pain to work with. (Gets an F rating from FSF <https://www.gnu.org/software/repo-criteria-evaluation.en.html>.) Includes Subversion and Git support. The only tradeoffs with savannah nongnu is it sometimes takes them a few weeks to approve your project hosting, and they require you to put licensing information on each code file (a really good idea anyway). On 02/20/2017 09:19 AM, Jakob Eriksson wrote: > > > I would love for the public repo to be on github! > > I think for many, an open source project does not really exist, > unless it is on Github. We should also try to resurrect somehow, > the [picolisp] tag on Stack Overflow. > > Given that it is encouraged to put in official documentation in the > form of Q/A on Stack Overflow, I think we could have a coordinated > effort from here to do it. > > > > > On 2017-02-20 18:15, Petr Gladkikh wrote: >> I admit that I am a passerby here but my impression is that things >> around PicoLisp feel closed and this is not about the code itself. >> In particular, there seems to be no public source code repository so >> source history can only be inferred somehow from releases. I see that >> some people already try to mirror it (see, >> e.g. https://github.com/taij33n/picolisp >> <https://github.com/taij33n/picolisp>) but since it is not "official" >> there's no development or associated discussions. Since revision control >> is essential for any non-trivial project, the lack of it is surprising. >> Also there's no public bug tracker. Instead I have to subscribe to this >> list so it is hard to track what happened to issues. >> >> That said removing some friction for outsiders would help to keep things >> running. >> >> >> 2017-02-03 8:47 GMT+01:00 Alexander Burger <a...@software-lab.de >> <mailto:a...@software-lab.de>>: >> >> Hi all, >> >> the future of PicoLisp is dark. I'm not sure if it can survive in >> packaged >> distribution. >> >> Ubuntu doesn't support it any more, probably due to the PIE (position >> independent executable) on x86-64. >> >> And at least on Android they seem to demand switching to Clang. The >> 32-bit >> versions of PicoLisp (pil32 and mini) which are written in C cannot >> be compiled >> on Clang, because Clang doesn't support dynamically allocated >> arrays, which >> pil32 depends on. As far as I notices, pil64 also has trouble on >> Clang/Android. >> >> :( Alex >> -- >> UNSUBSCRIBE: mailto:picolisp@software-lab.de >> <mailto:picolisp@software-lab.de>?subject=Unsubscribe >> >> >> >> >> -- >> Petr Gladkikh -- Christopher Howard, Computer Assistant Alaska Satellite Internet 3239 La Ree Way, Fairbanks, AK 99709 907-451-0088 or 888-396-5623 (toll free) fax: 888-260-3584 mailto:christop...@alaskasi.com http://www.alaskasatelliteinternet.com -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
