Re: [Nix-dev] Fractalide is ready to use.

Interesting. Do you have any further examples than the readme ? I wonder if we should extend nix's multi-line string syntax to accept a shebang-like so that editors can can switch the syntax in that context. On Sat, 20 Feb 2016 at 19:14 stewart mackenzie wrote: > Ah yes a

Re: [Nix-dev] Fwd: Wiki is dead

> On Feb 20, 2016, at 3:20 PM, Kosyrev Serge <_deepf...@feelingofgreen.ru> > wrote: > > Anthony Cowley writes: >> Bringing together what Thomas and Freddy say here, it seems to me that >> a rather ideal mixture would be something unstructured like a wiki >> with buttons for

Re: [Nix-dev] Printing test failure preventing unstable channel update

https://github.com/NixOS/nixpkgs/commit/35e1f4954555f465fb4499880dcb6a68417fb959#commitcomment-16221919 On Sat, Feb 20, 2016 at 6:18 PM, Kevin Cox wrote: > The raw log links were working for me. I don't know why the others aren't. > On Feb 20, 2016 13:08, "Jascha Geerds"

Re: [Nix-dev] Fwd: Wiki is dead

Bringing together what Thomas and Freddy say here, it seems to me that a rather ideal mixture would be something unstructured like a wiki with buttons for readers saying, "This helped me" or "This did not work". The point being that once a wiki item gets a handful of positive votes, it gets

Re: [Nix-dev] Fractalide is ready to use.

Ah yes a link would be useful (thanks anon) github.com/fractalide/fractalide /sjm ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Printing test failure preventing unstable channel update

The raw log links were working for me. I don't know why the others aren't. On Feb 20, 2016 13:08, "Jascha Geerds" wrote: > Unfortunately, I don't see any logs for the build > ___ > nix-dev mailing list > nix-dev@lists.science.uu.nl

Re: [Nix-dev] Printing test failure preventing unstable channel update

Unfortunately, I don't see any logs for the build ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] Fractalide is ready to use.

Hi all, I'd say Fractalide is in a state ready to use now. It's still very experimental so don't bet the house on it. Fractalide is a flow-based programming platform implemented in Rust, it uses Nix as its package manager, and aims to thwart three classes of problems: Memory safety, Dependency

Re: [Nix-dev] Fwd: Wiki is dead

On Saturday, February 20, 2016 15:16:12 zimbatm wrote: > That's exactly why the wiki is good. The contribution barrier is fairly low > and you can do things without having to ask for permission. > It's very easy for anyone to come along and fix typos. Having the change > appear directly is also

Re: [Nix-dev] Fwd: Wiki is dead

Adding documentation is one thing, maintaining it is a second. It's great if someone is willing to convert contributions to Docbook, and I'm thankful for that. However, that does not help much if you want to modify parts of it. And as Nixpkgs is updated, so should the documentation. I agree

Re: [Nix-dev] codetriage.com

I was looking for a way to visualize the number of open issues over time and found this: https://9-volt.github.io/bug-life/?repo=nixos/nixpkgs .Unfortunately we have too much content and it's hitting the API rate/limit. The idea was to see the current trend. Maybe after 2-3 weeks of codetriage the

Re: [Nix-dev] Fwd: Wiki is dead

I'm tool agnostic but +1 on having a cookbook in git for the review-workflow (avoids wiki spam). I have a number of snippets (how to remove gc roots, haskell profiling, how to use ihaskell properly, many more) but no good place to put them. I've started a git-book thing [1] a while back to

Re: [Nix-dev] Fwd: Wiki is dead

Someone (I think Vladimir?) offered to translate docs in any format into the necessary docbook, and has done so at least for one of my PRs. As long as that offer still stands and isn't overwhelming him, we can avoid spending time and resources switching over our format until we actually have

[Nix-dev] Fwd: Wiki is dead

I agree with Vladimir that we already have the infrastructure, the Nixpkgs repository. What is needed is a clearer way where to put certain documentation and a lower barrier for contributing. In `Redesign of documentation` I came with a proposal of how to structure the documentation. A wiki has a

Re: [Nix-dev] codetriage.com

On 02/20/2016 12:31 PM, Michael Raskin wrote: >> https://github.com/NixOS/nixpkgs/pulls?utf8=✓=is:pr+is:open+updated:<2015-10-01 > > My point was ?if the submitter has got commit rights by now?. > > That seems to be harder to query for. Yeah, there seems to be no way. I can only see filtering

Re: [Nix-dev] Wiki is dead

On 02/20/2016 12:52 AM, zimbatm wrote: > It's a great staging area for content where people can edit without > asking for permission. [...] What are the advantages in comparison to standard pull requests with discussion underneath? We already have lots of infrastructure advantages in there, such

Re: [Nix-dev] codetriage.com

>https://github.com/NixOS/nixpkgs/pulls?utf8=✓=is:pr+is:open+updated:<2015-10-01 My point was ?if the submitter has got commit rights by now?. That seems to be harder to query for. ___ nix-dev mailing list nix-dev@lists.science.uu.nl

Re: [Nix-dev] codetriage.com

On 02/20/2016 10:45 AM, Wout Mertens wrote: > Now if we could run a query for that… :-) GitHub can run similar queries easily: https://github.com/NixOS/nixpkgs/pulls?utf8=✓=is:pr+is:open+updated:<2015-10-01 smime.p7s Description: S/MIME Cryptographic Signature

Re: [Nix-dev] codetriage.com

Now if we could run a query for that… :-) On Sat, Feb 20, 2016, 10:26 AM Michael Raskin <7c6f4...@mail.ru> wrote: > >Same for PRs, we have some really old ones. What is a good cutoff? 6 > months? > > I would start with «6 months without any updates except non-submitter > pings and the submitter

[Nix-dev] [***SPAM***] Re: codetriage.com

>Same for PRs, we have some really old ones. What is a good cutoff? 6 months? I would start with «6 months without any updates except non-submitter pings and the submitter now has commit rights» ___ nix-dev mailing list nix-dev@lists.science.uu.nl