Re: [Nix-dev] NixOS-Wiki alternative. Was: What license does the content of the nixos wiki and the manuals have?

There is also Pelican, a static site generator written in python. I don't know how it compares to Jekyll: http://blog.getpelican.com/ https://github.com/getpelican/pelican -- Jascha Geerds j...@ekby.de ___ nix-dev mailing list

Re: [Nix-dev] NixOS-Wiki alternative. Was: What license does the content of the nixos wiki and the manuals have?

On 09/25/2015 04:28 PM, Matthias Beyer wrote: > and 1GB installation, as you mentioned. > > I used Jekyll because I don't know Haskell (I know a bit, but not > enough) and I can see that haskell puts off a lot of people just > because it is different. [...] I believe we can work around those as

Re: [Nix-dev] NixOS-Wiki alternative. Was: What license does the content of the nixos wiki and the manuals have?

Hi, On 25/09/15 16:04, Matthias Beyer wrote: >> This is essentially how the NixOS homepage is built, i.e., a git repository + >> Template Toolkit + a makefile. And of course you can make pull requests on >> GitHub. But I wouldn't call that a wiki, since you can't easily edit it from >> a >>

Re: [Nix-dev] NixOS-Wiki alternative. Was: What license does the content of the nixos wiki and the manuals have?

On 09/25/2015 04:58 PM, Jookia wrote: > On Fri, Sep 25, 2015 at 04:01:21PM +0200, Matthias Beyer wrote: >> What do you mean by proprietary tools? Jekyll, Bundler, git - all open >> source. The only thing which would be non-open source are the web >> servers who host the generated html files and

Re: [Nix-dev] NixOS-Wiki alternative. Was: What license does the content of the nixos wiki and the manuals have?

On 25-09-2015 17:07:23, Vladimír Čunát wrote: > > The point is you won't have to use github. Just edit files in your local > checkout and commit it. For creating a PR you maybe do need it (though > the CLI interface probably can do that as well), but that's much more of > concern for the main

Re: [Nix-dev] What license does the content of the nixos wiki and the manuals have?

On 24-09-2015 17:48:17, Edward Tjörnhammar wrote: > On Thu, Sep 24, 2015 at 05:24:58PM +0200, Domen Kožar wrote: > >I'm all for permissive creative commons license. > > +1 +1 We would need to contact these people: https://nixos.org/w/index.php?title=Special%3AListUsers===1=500 I

Re: [Nix-dev] What license does the content of the nixos wiki and the manuals have?

Hi, On 25/09/15 12:50, Kirill Elagin wrote: > I’d like to also point out another problem. > In case some of contributors do not agree to the new terms, how are we going > to > delete their contributions? My understanding is that simply deleting the > content > in question from the page is not

Re: [Nix-dev] What license does the content of the nixos wiki and the manuals have?

On 25 Sep 2015 15:29, "Joachim Schiele" wrote: > > two problems i see here: > - text can't be covered by GPL thus they created CC I suggested nix{os,pkgs} to be GPL3 or MPLv2 not the wiki. > - some edits in the wiki are anonymous (whom to ask?) I wouldn't care about anonymous

Re: [Nix-dev] What license does the content of the nixos wiki and the manuals have?

> However, an alternative to relicensing is to combine it with a move to a > different Wiki, which many people have wanted in the past anyway. For > instance, > we could set up a GitHub wiki, and people could copy their own contributions > to > the new wiki. The new wiki should of course have a

Re: [Nix-dev] NixOS-Wiki alternative. Was: What license does the content of the nixos wiki and the manuals have?

+1 for hakyll. -- Sincerely, Arseniy Seroka On 25 September 2015 18:07:38 Vladimír Čunát wrote: > On 09/25/2015 04:58 PM, Jookia wrote: >> On Fri, Sep 25, 2015 at 04:01:21PM +0200, Matthias Beyer wrote: >>> What do you mean by proprietary tools? Jekyll, Bundler, git - all

Re: [Nix-dev] NixOS-Wiki alternative. Was: What license does the content of the nixos wiki and the manuals have?

I think having a wiki in git can be a big trouble for users who don't know where to find the "edit" / "login" buttons, but I am sure that we can make the proper template in due time to wrap an interface around such system. On Fri, Sep 25, 2015 at 3:49 PM, Eelco Dolstra

Re: [Nix-dev] Providing Debian, Arch etc. packages counterproductive?

Hi Alaistair, Thanks for doing that change! We've tried your package on a fresh install and it doesn't add the channel or `$HOME/.nix-profile/etc/profile.d/nix.sh`. After we've added those manually we ran into the locale bug in [1]. Are you getting that bug as well? And if so, did you manage to

Re: [Nix-dev] NixOS-Wiki alternative. Was: What license does the content of the nixos wiki and the manuals have?

On 25-09-2015 20:58:36, Nicolas Pierron wrote: > > Also, I wanted to mention that Github offers an option for modifying > pages without even cloning the repository on your computer. Which > makes this approach less painful for making contributions. > >

Re: [Nix-dev] NixOS-Wiki alternative. Was: What license does the content of the nixos wiki and the manuals have?

Hi, A few considerations: I would be great to have support for i18n, including guidelines and workflows for foreign languages. (eg: Who with merging privileges can determine if a contribution in thai is not spam?) Git and command line can be a big hurdle for non technical users, so to help

Re: [Nix-dev] What license does the content of the nixos wiki and the manuals have?

two problems i see here: - text can't be covered by GPL thus they created CC - some edits in the wiki are anonymous (whom to ask?) i like that we are adressing this issue now. it is very important. i'd go for CC BY SA 3.0 https://creativecommons.org/licenses/by-sa/3.0/ as IMHO this fits the

[Nix-dev] NixOS-Wiki alternative. Was: What license does the content of the nixos wiki and the manuals have?

On 25-09-2015 12:58:14, Eelco Dolstra wrote: > However, an alternative to relicensing is to combine it with a move to a > different Wiki, which many people have wanted in the past anyway. For > instance, > we could set up a GitHub wiki, and people could copy their own contributions > to > the

Re: [Nix-dev] What license does the content of the nixos wiki and the manuals have?

I’d like to also point out another problem. In case some of contributors do not agree to the new terms, how are we going to delete their contributions? My understanding is that simply deleting the content in question from the page is not enough, it’s wiki actually. We’ll have to see how, for

Re: [Nix-dev] What license does the content of the nixos wiki and the manuals have?

On Fri, Sep 25, 2015 at 09:28:36AM +0200, Joachim Schiele wrote: > two problems i see here: > - text can't be covered by GPL thus they created CC > - some edits in the wiki are anonymous (whom to ask?) > i like that we are adressing this issue now. it is very important. > i'd go for CC BY SA 3.0

Re: [Nix-dev] What license does the content of the nixos wiki and the manuals have?

hi rob, we need your help. can you please provide matthias beyer with all the email addresses from the wiki? you can run these commands: mysql -p or mysql show databases; use lastlogwiki; select user_name,user_real_name,user_email from user; mysql> select user_name,user_real_name,user_email

Re: [Nix-dev] NixOS-Wiki alternative. Was: What license does the content of the nixos wiki and the manuals have?

Hi, On 25/09/15 14:24, Matthias Beyer wrote: > So, an idea came up - why not using static pages for all of this? If you > want to do contributions via git, you can use github. If one want to > host it, one can use github pages and build it with travis-ci. These > things are documented and they

Re: [Nix-dev] NixOS-Wiki alternative. Was: What license does the content of the nixos wiki and the manuals have?

On Fri, Sep 25, 2015 at 03:49:08PM +0200, Eelco Dolstra wrote: > Hi, > > On 25/09/15 14:24, Matthias Beyer wrote: > > > So, an idea came up - why not using static pages for all of this? If you > > want to do contributions via git, you can use github. If one want to > > host it, one can use

Re: [Nix-dev] NixOS-Wiki alternative. Was: What license does the content of the nixos wiki and the manuals have?

On 25-09-2015 15:49:08, Eelco Dolstra wrote: > Hi, > > On 25/09/15 14:24, Matthias Beyer wrote: > > > So, an idea came up - why not using static pages for all of this? If you > > want to do contributions via git, you can use github. If one want to > > host it, one can use github pages and build

Re: [Nix-dev] NixOS-Wiki alternative. Was: What license does the content of the nixos wiki and the manuals have?

On Fri, Sep 25, 2015 at 11:53:24PM +1000, Jookia wrote: > On Fri, Sep 25, 2015 at 03:49:08PM +0200, Eelco Dolstra wrote: > > Hi, > > > > On 25/09/15 14:24, Matthias Beyer wrote: > > > > > So, an idea came up - why not using static pages for all of this? If you > > > want to do contributions via

Re: [Nix-dev] NixOS-Wiki alternative. Was: What license does the content of the nixos wiki and the manuals have?

On 09/25/2015 04:18 PM, Vladimír Čunát wrote: > I've got great experience with Hakyll The only downside to Hakyll I can see is that apparently you need ~1 GB of Haskell stuff to build the site :-/ smime.p7s Description: S/MIME Cryptographic Signature

Re: [Nix-dev] NixOS-Wiki alternative. Was: What license does the content of the nixos wiki and the manuals have?

On 25-09-2015 16:18:31, Vladimír Čunát wrote: > On 09/25/2015 02:24 PM, Matthias Beyer wrote: > > So, an idea came up - why not using static pages for all of this? > > Yeah, sounds good. Actually, you can edit and preview files on github > easily - it's two clicks to get a PR with the changes (at