So, [here][1] we have a nice example of discussions in pull requests. This
shows that this model actually works.
I hope one day we'll get a document explaining how to work pull requests,
and I'd like to suggest the following. In cases like this one, when there
are lots of commits fixing small
More on policy.
AFAIK, many projects follow [git's own recommendations on sending
patches][1]. We should look at this document and decide what is acceptable
for us to adopt.
Especially, we have to agree on commit message format (ignoring sign-offs
for now) and tenses used. Right know most commits
Also, i know that nix is young and multipage policies will be overkill,
but something like README.md in pkgs/data/fonts/ and other dirs could
work.
What do you think?
Shea Levy s...@shealevy.com writes:
I think these are good ideas. More structure and policy in nixpkgs
would probably
On Jun 24, 2012, at 9:18 AM, Antono Vasiljev s...@antono.info wrote:
I created initial draft (really small) for fonts:
https://github.com/antono/nixpkgs/tree/fonts-policy-proposal/pkgs/data/fonts#font-packaging
What do you think? :)
+1 from me.
On Sun, 24 Jun 2012 16:18:08 +0300, Antono Vasiljev s...@antono.info wrote:
Shea Levy s...@shealevy.com writes:
I think these are good ideas. More structure and policy in nixpkgs
would probably be helpful especially to new contributors. The big
question is: Who will do the initial work?
Shouldn't we introduce a separate attrset to hold fonts instead of putting
them into top-level?
Ok, guys, let's be honest. Nix needs something like categories. And, no,
suffixes in package names are not a good solution. And, by the way, nested
attrsets won't work either, because, as I know, after
for nixpkggs the attr path is also very important.
What about also moving everything into
fonts.* attr path?
Same as xserver python-packages etc.
Marc Weber
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
On Sun, 24 Jun 2012 17:53:58 +0200, Marc Weber marco-owe...@gmx.de wrote:
for nixpkggs the attr path is also very important.
What about also moving everything into
fonts.* attr path?
+1
--
Florian Friesdorf f...@chaoflow.net
GPG FPR: 7A13 5EEE 1421 9FC2 108D BAAF 38F8 99A3 0C45 F083
Ok, guys, let's be honest. Nix needs something like categories.
What if you have a python library which is also a compiler?
Put into category compilers or python-library?
Thus do you want to assign multiple categories to a package?
suffixes in package names are not a good solution.
Depends on
2012/6/24 Marc Weber marco-owe...@gmx.de
Ok, guys, let's be honest. Nix needs something like categories.
What if you have a python library which is also a compiler?
Put into category compilers or python-library?
Well, yeah, this might be a problem, but other package managers solve this
Hi Kirill,
On Sun, 24 Jun 2012 23:32:03 +0400, Kirill Elagin kirela...@gmail.com wrote:
2012/6/24 Marc Weber marco-owe...@gmx.de
Ok, guys, let's be honest. Nix needs something like categories.
What if you have a python library which is also a compiler?
Put into category compilers or
Hi Eelco,
as a NixOS organization member you can configure notifications for
yourself at github. Currently, only a small subset of nix-dev are
organization members. Even if all subversion committers are organization
members again, it would be handy if non-organization members could
subscribe to
Hi,
On 24/06/12 18:48, Florian Friesdorf wrote:
- nix-tickets@/nix-issues@/similar - notifications about tickets, could
also be sent to nix-dev@
Unfortunately, GitHub doesn't seem to support this. At least I can't find any
place in the interface to set notifications for issues.
--
Eelco
Excerpts from Eelco Dolstra's message of Mon Jun 25 00:55:40 +0200 2012:
Unfortunately, GitHub doesn't seem to support this. At least I can't find any
place in the interface to set notifications for issues.
It could be done by using the API: compare old list with new list and
send difference
14 matches
Mail list logo
