Hi guys,
it is my pleasure to announce the free-nix project, which aims to provide a
user- and developer-friendly free Linux distribution based on the Nix package
manager. The project is hosted on Github at
http://github.com/free-nix
and it offers two repositories:
- pkgs is a
Excerpts from Peter Simons's message of Tue Jun 26 12:45:18 +0200 2012:
project's goals, policies, and procedures.
Stating a vision or project goal is great. That has been lacking for
nixos IMHO.
Whether new mailinglists will be created or not - will be discussed
later then?
Announcing a new
Hi Peter.
On Tue, Jun 26, 2012 at 12:45 PM, Peter Simons sim...@cryp.to wrote:
Hi guys,
it is my pleasure to announce the free-nix project, which aims to provide a
user- and developer-friendly free Linux distribution based on the Nix package
manager. The project is hosted on Github at
Is
Hi,
On 26/06/12 06:45, Peter Simons wrote:
it is my pleasure to announce the free-nix project, which aims to provide a
user- and developer-friendly free Linux distribution based on the Nix package
manager.
Well, forking is the most sincere form of flattery, but...
I told you a few days ago
Hello.
I've made a bunch of changes to nixpkgs that I would like to share.
* new-and-fixes.patch
* adds
* libraries
* gconfmm -- This
* gtkglextmm -- and this are not used by any package that I'm ready to
share. They are for lintesia game that doesn't run nicely for me yet.
On Tue, Jun 26, 2012 at 02:34:58PM +0200, Andres Loeh wrote:
Hi Peter.
On Tue, Jun 26, 2012 at 12:45 PM, Peter Simons sim...@cryp.to wrote:
Hi guys,
it is my pleasure to announce the free-nix project, which aims to provide a
user- and developer-friendly free Linux distribution based on
On Tue, Jun 26, 2012 at 08:50:52AM -0400, Eelco Dolstra wrote:
On 26/06/12 06:45, Peter Simons wrote:
it is my pleasure to announce the free-nix project, which aims to provide a
user- and developer-friendly free Linux distribution based on the Nix
package
manager.
Well, forking is
Hi Peter,
On Jun 26, 2012, at 6:45 AM, Peter Simons sim...@cryp.to wrote:
- pkgs is a database of free software packages that can be installed
with the Nix package manager.
Will proprietary or non-GPL'd software be allowed to be packaged in free-nix?
Or, what do you
Excerpts from Shea Levy's message of Tue Jun 26 15:36:17 +0200 2012:
Will proprietary or non-GPL'd software be allowed to be packaged in
free-nix? Or, what do you mean by the 'free' in free-nix?
Peter said:
and then the group of
people that comes out of this process is going to constitute
Hi Shea,
- pkgs is a database of free software packages that can be installed
with the Nix package manager.
Will proprietary or non-GPL'd software be allowed to be packaged in
free-nix? Or, what do you mean by the 'free' in free-nix?
personally, I believe
Hi all,
It seems apparent to me that many in the community have some level of
dissatisfaction with how contributions to the various nix projects are handled.
Sometimes the only solution to problems like this is a fork (as Peter seems to
believe), but I think there is a good chance that things
log into github, there you can become a member for both gists yourself
somehow:
nixpkgs: https://gist.github.com/2995910
public git://github.com/NixOS/nixpkgs.git
private (push): git remote add gist g...@gist.github.com:2995910.git
nixos: https://gist.github.com/2995911
Hi Jan,
On Jun 26, 2012, at 8:52 AM, Jan Malakhovski o...@oxij.org wrote:
Hello.
I've made a bunch of changes to nixpkgs that I would like to share.
Thanks for contributing!
* new-and-fixes.patch
* adds
* libraries
* gconfmm -- This
* gtkglextmm -- and this are not
I've made a bunch of changes to nixpkgs that I would like to share.
I've just created two gist repositories (let's see how well it works. I
don't know whether github gives any guarantees - but people have local
copies anyway):
nixpkgs: https://gist.github.com/2995910 (upload still taking place)
:) I've been at that point (wanting to fork) in the past as well.
But I couldn't afford the costs. And I also don't think it will benefit
us all splitting the community. I tried to solve the most urgent issues
(patch submitting) by setting up gists and hope you all start using it
so that we can
For me, the two biggest issues I see are:
a) Lack of clear documentation of policy. The closest thing we have is
the nixpkgs manual, but it's not enough. As a newcomer to a project (and even
sometimes as a veteran), I want to be able to easily find answers to questions
like how should
On Jun 26, 2012, at 10:52 AM, Marc Weber marco-owe...@gmx.de wrote:
:) I've been at that point (wanting to fork) in the past as well.
But I couldn't afford the costs. And I also don't think it will benefit
us all splitting the community. I tried to solve the most urgent issues
(patch
Hi Andres,
If you're unhappy with the way Nix is being run, why not bring it up
and try to convince people to change the overall policy [...]?
where exactly could anyone bring anything up so that people change
NixOS policy?
Who exactly has the ability to change NixOS policy?
What exactly
Let's not forget that in the end we all compete with ubuntu, apple,
Microsoft etc - because we all depend on a working system (to run our
servers or write private mail)
Actually, the core that is complex enough to need collaboration is quite
small. I tried to share everything - with medium-easy
Hi Peter.
where exactly could anyone bring anything up so that people change
NixOS policy?
Who exactly has the ability to change NixOS policy?
It's vaguely defined. But even if Eelco has in practice most of the
power, it's still in fact a community project, as can be observed by
the fact
What exactly *is* NixOS's policy?
Also not clearly defined, but so far, it seems to have been
functioning reasonably well without people feeling the need to fork.
Its lack also has created a few weird and unfiortunate outcomes, and
currently we seem to have a chance to get more.
Eelco revoked
free-nix as a chance:
See happening to Mandriva / Mageia:
http://www.linuxplanet.com/news/mandriva-rejoining-mageia-fork-as-mint-freshens-up-linux.html
This post (German) says that 30 previous employees started this fork:
Eelco revoked all access of all regular contributors without prior
warning.
Everything is still open source - so we all could fork anytime (which
you actually proofed). We all have local copies - so ...
But its also known (to me) that Eelco started getting more and more
interested in git very
On Tue, 26 Jun 2012 00:48:36 +0200, l...@gnu.org (Ludovic
=?iso-8859-1?Q?Court=E8s?=) wrote:
Hi,
Eelco Dolstra eelco.dols...@logicblox.com skribis:
On 25/06/12 17:00, Ludovic Courtès wrote:
Oh, and could we get diffs in the commit notifications? :-)
Yes, by volunteering to
Shea Levy s...@shealevy.com writes:
Hi Peter,
On Jun 26, 2012, at 6:45 AM, Peter Simons sim...@cryp.to wrote:
- pkgs is a database of free software packages that can be installed
with the Nix package manager.
Will proprietary or non-GPL'd software be allowed to be
This kind of problem absolutely should be reported as an issue in GitHub or
elsewhere.
For me as for still a pretty outside observer it seems that the main
problem of NixOS for now is lack of… let's call it specifications. I'm sure
all those issues will be addressed sooner or later when we
Hi Jan,
your patch is now available here:
https://github.com/free-nix/pkgs/tree/malakhovski/master
I committed it into a branch because compilers.patch causes a massive
re-build, so I'd hesitate to place that change into the master branch
without some additional testing.
By the way, do you
I've just collected those two items here.
https://nixos.org/wiki/TODO_-_What_is_missing_in_the_nix_community%3F
If more popup add them.
Let's keep in mind that nixos is young - and that there might be
additional requirements tomorrow. Thus let's think carefully about which
policies we need - the
2012/6/26 Jan Malakhovski o...@oxij.org
I'm kind of confused with gist vs. pull request controversy. I did
carefully read the thread about moving to github, but still don't get this
nonlinear history/merge problem.
No offense, but I feel that gists somehow diminish contributions (or maybe
I
2012/6/26 Peter Simons sim...@cryp.to
By the way, do you have a user on Github? I'll give you access to the
repository in case you have more changes that you'd like to share.
If you look carefully at commits you've commited into your repo, you'll
notice that, yes, he has a GitHub account.
--
Excerpts from Jan Malakhovski's message of Tue Jun 26 18:56:26 +0200 2012:
I'm kind of confused with gist vs. pull request controversy. I did carefully
read the thread about moving to github, but still don't get this nonlinear
history/merge problem.
Well - the gist was meant to also take
Hi Kirill,
If you look carefully at commits you've commited into your repo,
you'll notice that, yes, he has a GitHub account.
you are right. Still, it would be impolite to add someone to the
organization without asking first, so I'd prefer to have explicit
consent.
Take care,
Peter
Excerpts from Kirill Elagin's message of Tue Jun 26 20:05:21 +0200 2012:
Just to note: I don't get this gist idea either. Gist is, you know,
slightly enhanced pastebin, and using it for collecting contributions looks
weird.
Yes - I'm abusing it :) But its fine to understand whether the idea
2012/6/26 Marc Weber marco-owe...@gmx.de
Excerpts from Kirill Elagin's message of Tue Jun 26 20:05:21 +0200 2012:
Just to note: I don't get this gist idea either. Gist is, you know,
slightly enhanced pastebin, and using it for collecting contributions
looks
weird.
Yes - I'm abusing it :)
Its meant for all those small changes which are no worth creating pull
requests for, too.
I can't imagine a change not worth creating a pull request. Creating a pull
request is two clicks, accepting it is one click.
Not just two clicks, but pulling the trunk into your fork which is not
done
2012/6/26 Michael Raskin 7c6f4...@mail.ru
Sending patch to mailing list can be done with a single
pipeline command in shell...
So yes, for simple fixes pull request is more effort than contributing
the fix would save.
No doubt, we _must_ still accept contributions by `git format-patch`
Sending patch to mailing list can be done with a single
pipeline command in shell...
So yes, for simple fixes pull request is more effort than contributing
the fix would save.
No doubt, we _must_ still accept contributions by `git format-patch` from
those who prefer it.
I would say that the
I've just noticed that there is a very big mailing list discussion going on
here. Actually, I'm very busy now with writing my PhD thesis and I didn't
really have the time to respond yet. Nonetheless, I think it's important that I
express my thoughts about this matter, although I haven't read
In the Linux kernel development process, the only official tree is Linus'
kernel tree. Linus only works with a small group of people each maintaining
a subsystem of the kernel, such as the memory manager, I/O scheduler etc.
These subsystem maintainers have their own tree (which they regularly
Hi,
On 26/06/12 18:58, Bryce L Nordgren wrote:
Seen from this perspective, the nixpkgs/nixos repositories are rather
monolithic: You'd have to manually assemble a complete Nix expression in a
directory on your system, composed of some free-nix expressions and some
NixOS expressions. Then
Hi,
On 26/06/12 12:02, Peter Simons wrote:
Eelco revoked all access of all regular contributors without prior
warning.
The Git migration has been going on for a while, so in that sense the actual
switchover shouldn't be *that* unexpected. I then asked for input on the
desired development
Hi all,
Since there appears to be strong^Wpassionate support for having direct commit
access to the main Nixpkgs/NixOS repositories, it's clear we should stick to the
existing development model at the moment. So if you want commit access, please
let me know your GitHub username and I'll add you
Hi Eelco,
if you bear with me for a second, I'd like to explain where I'm coming
from.
I have contributed to Nix regularly for the last 4 years. According to
the stats at Github, I've submitted an average of 1.6 commits per day
over that entire period of time. I'm not saying that because want to
Hi Michael,
On Jun 26, 2012, at 12:16 PM, Michael Raskin 7c6f4...@mail.ru wrote:
that things can be improved without fracturing the already-small group.
It looks like the main project will be conservative enough to be simple
to pull...
Are you basing this assessment only on the git
Anyway, I don't have any meaningful change history. I can make one up if you
insist, but this could get another year or two.
I'm not hurrying anyone, but if you merge the current set of patches in
sometime I promise to carefully fake meaningful history for the next one. :)
OK, fair
It looks like the main project will be conservative enough to be simple
to pull...
Are you basing this assessment only on the git situation over the last 6 days,
or do you consider the project pre-git to be fairly conservative?
This is based on the recent (couple years) history of the actual
46 matches
Mail list logo
