Today i learned something on IRC regarding hosting Picolisp: [11:30] <freeemint_> I found a mistake in (doc '+Joint) > [11:30] <Regenaxer> oh > [11:31] <freeemint_> is the missing part: pos (+Ord)) ? > [11:32] <Regenaxer> then parenthesis? > [11:32] <Regenaxer> yes, something is missing > [11:33] <Regenaxer> it depends how much we want to write > [11:33] <Regenaxer> The +Dep is in the original source > [11:33] <Regenaxer> and then 2 more lines > [11:33] <Regenaxer> Thanks! I fix it > [11:33] <Regenaxer> without the +Dep though, to avoid confusion > [11:34] <freeemint_> when will the fix be in the wiki? > [11:34] <Regenaxer> It is not in the wiki, but on the download page > [11:34] <Regenaxer> A few minutes > [11:34] <freeemint_> ok > [11:35] <freeemint_> I have the feeling the irc fixes bugs faster than > git would :D > [11:35] <Regenaxer> indeed :) > [11:36] <Regenaxer> OK, I fixed it. Releasing now > [11:36] <Regenaxer> Thanks!! >
Actions speak louder than words. So do not add anything that makes picoLisp less actionable and talk about bugs with Regenaxer. 2017-03-10 13:50 GMT+01:00 Jakob Eriksson <ja...@aurorasystems.eu>: > > > 10 mars 2017 kl. 01:17 skrev <andr...@itship.ch> <andr...@itship.ch>: > > Thanks for your comments and insights, Jakob. > I just want to shortly assure you that I really liked your emails and your > participation. > > > > Thanks. > > > Sidenote: > Before GitHub, sourceforge.net was the singular main hoster for FOSS > sourcecode. > They lost their status when they bundled the downloads with adware (and > malware). > > > Something like that can happen. > > But I stand by my point - github and it's social network is unique. > > > > > > BitKeeper vs. Linux (the reason we have git now). > > > So thanks to Bitkeeper we could push the state of the art away from CVS. > Great. > > > > > GitHub: > On 2017-03-01 GitHub introduced > > .... > > Basically, when uploading FOSS-licensed content to GitHub, the uploader > automatically grants GitHub a special license, so actually a case of > dual-licensing. > The problem now is, that when the content is copyrighted by other authors > beside the uploader, > then the uploader cannot (in usual cases) actually grant this license > legally to GitHub, as most FOSS-licenses forbid sublicensing and/or removal > of the original attributions. > > > > Just .. not accurate. > > https://news.ycombinator.com/item?id=13767975 > > > > > I don't believe GitHub will take big damage because of this, especially as > there is no serious contender on the rise. > > > Exactly there's none. > > But it's surely a sign that GitHub is not a singularity from the usual > development of such things. > It's not an idealistic group of nerds anymore, but a big company (e.g. > lookup the "github meritocracy" drama). > > > I never said nor implied such a thing. > I just observe that github is the largest community of software developers > in the history of the Universe. > > > For the other points mentioned by you and others about picolisp: > Just do it. PicoLisp is MIT-licensed. Action speaks louder than words. > > > Put up or shut up? Of course you are right. About me. Because I know where > to find everything picolisp related. But I argue (maybe incorrectly) that > there can be other people in a kind of Hitchikers guide to the Galaxy > situation - Picolisp is behind the leopard etc.. > > > But all this is beside the point for PicoLisp, we know now that it won't > come to github. I just wanted to defend my own viewpoint, I didn't like how > I was understood. > > > This! > I'm on it. > > > Speaking of, anybody tried to compile emu pico in emscripten? > > -- Jakob >
