Re: [Nix-dev] Google Summer of Code 2017

Hi Anderson, Please do! Just submit a PR and I'll give you push permissions. The more ideas we have the better. ~ On 28 March 2017 at 18:48, Anderson Torres wrote: > No problems, guys! Just keep calm and carry on! We gained another year > to rally efforts on a

Re: [Nix-dev] Google Summer of Code 2017

No problems, guys! Just keep calm and carry on! We gained another year to rally efforts on a GSOC 2018! Thomas, can I add my ideas to your Github repo? 2017-03-15 12:33 GMT-03:00 Oliver Charles : > On Wed, Mar 15, 2017 at 12:47 PM Domen Kožar wrote: >> >> We

Re: [Nix-dev] Google Summer of Code 2017

Added to calendar for next year :) On Wed, 15 Mar 2017, 22:03 Vladimír Čunát, wrote: > On 03/15/2017 04:33 PM, Oliver Charles wrote: > > On Wed, Mar 15, 2017 at 12:47 PM Domen Kožar > > wrote: > > That being said, I know people will be

Re: [Nix-dev] Google Summer of Code 2017

On 03/15/2017 04:33 PM, Oliver Charles wrote: > On Wed, Mar 15, 2017 at 12:47 PM Domen Kožar > wrote: > That being said, I know people will be disappointed by this. I'm sorry, > I have no excuses really. I was overworked at that time and totally >

Re: [Nix-dev] Google Summer of Code 2017

Oh dear, I had been thinking about 1 and 2 lately... On systemd, I don't think that it's worth it to even try to port dependent software. Nix is smart enough to warn about/fix dependencies. And "porting" the actual unit files sounds easy IMO, systemd has good documentation on unit files that

Re: [Nix-dev] Google Summer of Code 2017

On Wed, Mar 15, 2017 at 12:47 PM Domen Kožar wrote: > We aren't participating in GSOC 2017, because I missed the submission > deadline. > > > That being said, I know people will be disappointed by this. I'm sorry, > I have no excuses really. I was overworked at that time and

Re: [Nix-dev] Google Summer of Code 2017

I don't believe in individual failure. We should try to put a system in place to avoid this next time. A related issue is that GHC didn't get in either because they didn't have a good page with potential projects. I propose: * Several of us put the next deadline into our calendar (probably

Re: [Nix-dev] Google Summer of Code 2017

We aren't participating in GSOC 2017, because I missed the submission deadline. That being said, I know people will be disappointed by this. I'm sorry, I have no excuses really. I was overworked at that time and totally forgot to watch the dates. I already applied us two times, I hope I'll

Re: [Nix-dev] Google Summer of Code 2017

2017-01-08 18:40 GMT-02:00 Profpatsch : > On 17-01-04 09:42pm, Vladimír Čunát wrote: >> On 01/04/2017 08:51 PM, Peter Simons wrote: >> > Another very important topic that needs to be addressed in Nix / Hydra >> > is the question of how to deal with code that wants to import

Re: [Nix-dev] Google Summer of Code 2017

On 17-01-04 09:42pm, Vladimír Čunát wrote: > On 01/04/2017 08:51 PM, Peter Simons wrote: > > Another very important topic that needs to be addressed in Nix / Hydra > > is the question of how to deal with code that wants to import build > > products into the ongoing evaluation. [...] > > That

Re: [Nix-dev] Google Summer of Code 2017

Domen Kožar writes: > I'll prepare a list of things each idea needs and send a call for mentors. > > There's a GSoC label on github, so let's use that. Okay sounds good! We can start adding issues that were on the wiki that may still be viable.

Re: [Nix-dev] Google Summer of Code 2017

Hey! On Wed, Jan 4, 2017 at 3:49 AM, Matthew Bauer wrote: > Google Summer of Code applications open on January 19 for > organizations[1]. NixOS had previously applied to be an organization in > 2014 and 2015 but neither time was accepted. I think it would be great if > we

Re: [Nix-dev] Google Summer of Code 2017

On 01/04/2017 03:49 AM, Matthew Bauer wrote: > Obviously there are lots of other ideas that are worthwhile, hopefully > potential mentors can contribute more. I have almost no experience in nix except as a user, so I obviously can't mentor anything, but maybe finally getting rid of [1] (which,

Re: [Nix-dev] Google Summer of Code 2017

On Wed, Jan 4, 2017 at 12:54 PM Vladimír Čunát wrote: > On 01/04/2017 03:49 AM, Matthew Bauer wrote: > > Ideas > > I suggest we create a GitHub ticket for each hopeful idea. There each > gets a thread to discuss it and come to a better specification in the > end. For this

Re: [Nix-dev] Google Summer of Code 2017

On 01/04/2017 08:51 PM, Peter Simons wrote: > Another very important topic that needs to be addressed in Nix / Hydra > is the question of how to deal with code that wants to import build > products into the ongoing evaluation. [...] That feels rather vague topic ATM. My experience is that this

Re: [Nix-dev] Google Summer of Code 2017

As far as Haskell-related projects are concerned, there's a collection of ideas available at [1]. All of these have related discussion threads in the nix-dev archive which provide additional information. Another very important topic that needs to be addressed in Nix / Hydra is the question of how

Re: [Nix-dev] Google Summer of Code 2017

On 01/04/2017 03:49 AM, Matthew Bauer wrote: > Ideas I suggest we create a GitHub ticket for each hopeful idea. There each gets a thread to discuss it and come to a better specification in the end. For this could add a GSoC label. IIRC in past we mainly lacked in well-specified project ideas.

[Nix-dev] Google Summer of Code 2017

Google Summer of Code applications open on January 19 for organizations[1]. NixOS had previously applied to be an organization in 2014 and 2015 but neither time was accepted. I think it would be great if we could get an application in for this year. It's not clear what criteria the GSoC use for