Re: [Nix-dev] Repo for incomplete/unmaintained work

2014-04-06 Thread Marc Weber
We've had some discussion, my proposal was:
Add a marker such as "unmaintained-since: ..."
then remove after 6 month or so. Due to the "since" you know exactly
what to remove.

The hard thing is to define what it means to be "maintained or
unmaintained".

Thus you could also introduce markers such as

  maintainance-levels = [ "gets-updated-within-a-week-if-new-version-appears" 
"somebody is reviewing code" ".."];

Not sure whether it would make sense.

Whether such code gets moved to another repository or not - which is the
benefit/ difference from having a simple wiki page "unmaintained
packages for nixos/ can be found in nixpkgs git history"? Then at least
google finds it .. No idea.

Marc Weber
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev


Re: [Nix-dev] Repo for incomplete/unmaintained work

2014-04-06 Thread Vladimír Čunát

On 04/05/2014 10:25 PM, Mathijs Kwik wrote:

I propose "nixnut" :P
But that might not be clear to non-dutch-speaking users.


:-D I thought "niksnut" referred to "nut" as "an extreme enthusiast" (in 
English).





smime.p7s
Description: S/MIME Cryptographic Signature
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev


Re: [Nix-dev] Repo for incomplete/unmaintained work

2014-04-06 Thread Bjørn Forsman
On 5 April 2014 21:46, Shea Levy  wrote:
> Hi all,
>
> Currently we have quite a lot of unmaintained, broken, or work-in
> progress components in nixpkgs. It would be great if we could get to the
> point where everything in nixpkgs was expected to work and be
> maintained, but part of that I think is having a place for this other
> work that isn't quite up to scratch but still may be valuable can live
> (it could also include experimental coding styles, proprietary services,
> etc.).
>
> Thoughts on the idea? Any idea for a name for the repo? Eelco, would you
> be able to make the repo if you think this is a good approach?

While I of course want to improve the quality of nixpkgs, I don't
think a separate repo is a good idea. I don't think it will improve
the situation.

Btw, do you mean that we'd create an (even more) "unstable" fork of
nixpkgs, or a brand new repo where *just* nix package expressions
would live (no build-support, stdenv etc.)?

Stuff are broken because 1) it was never finished in the first place
or 2) it has been unmaintained for so long that the surroundings has
changed from underneath it.

A separate repo will only fix the first issue, it cannot possibly fix
the second. And IMHO the first issue is solved by using git already:
PRs, feature branches in official repo that are built in Hydra.

I think marking packages as "broken" and having "allowUnfree"
configuration option is the best solution. And we already have that
:-)

Best regards,
Bjørn Forsman
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev


Re: [Nix-dev] Repo for incomplete/unmaintained work

2014-04-06 Thread Shea Levy
A branch suggests merging, but really there will be tons of merges
*into* to branch and only ever be cherry-picks *out of* the branch,
which IMO negates most of the benefits of having it be in the same repo.

On Sun, Apr 06, 2014 at 10:17:45AM +0100, Matthew Sackman wrote:
> On Sat, Apr 05, 2014 at 03:46:20PM -0400, Shea Levy wrote:
> > Thoughts on the idea? Any idea for a name for the repo? Eelco, would you
> > be able to make the repo if you think this is a good approach?
> 
> Is a whole other repo really necessary? Why not just a branch of
> nixpkgs?
> 
> Matthew
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev


Re: [Nix-dev] Repo for incomplete/unmaintained work

2014-04-06 Thread Matthew Sackman
On Sat, Apr 05, 2014 at 03:46:20PM -0400, Shea Levy wrote:
> Thoughts on the idea? Any idea for a name for the repo? Eelco, would you
> be able to make the repo if you think this is a good approach?

Is a whole other repo really necessary? Why not just a branch of
nixpkgs?

Matthew
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev


Re: [Nix-dev] Repo for incomplete/unmaintained work

2014-04-05 Thread Lluís Batlle i Rossell
On Sat, Apr 05, 2014 at 10:25:59PM +0200, Mathijs Kwik wrote:
> Shea Levy  writes:
> 
> > Hi all,
> >
> > Currently we have quite a lot of unmaintained, broken, or work-in
> > progress components in nixpkgs. It would be great if we could get to the
> > point where everything in nixpkgs was expected to work and be
> > maintained, but part of that I think is having a place for this other
> > work that isn't quite up to scratch but still may be valuable can live
> > (it could also include experimental coding styles, proprietary services,
> > etc.).
> >
> > Thoughts on the idea? Any idea for a name for the repo? 
> 
> I propose "nixnut" :P
> But that might not be clear to non-dutch-speaking users.
> 
> The idea itself sounds good.
> But isn't the `broken` attribute aiming for something similar?

I think it's important to have the broken packages *in front* of the
potential fixers. The broken attribute (which I discovered last week)
sounds fine to me too.
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev


Re: [Nix-dev] Repo for incomplete/unmaintained work

2014-04-05 Thread Mathijs Kwik
Shea Levy  writes:

> Hi all,
>
> Currently we have quite a lot of unmaintained, broken, or work-in
> progress components in nixpkgs. It would be great if we could get to the
> point where everything in nixpkgs was expected to work and be
> maintained, but part of that I think is having a place for this other
> work that isn't quite up to scratch but still may be valuable can live
> (it could also include experimental coding styles, proprietary services,
> etc.).
>
> Thoughts on the idea? Any idea for a name for the repo? 

I propose "nixnut" :P
But that might not be clear to non-dutch-speaking users.

The idea itself sounds good.
But isn't the `broken` attribute aiming for something similar?

> Eelco, would you
> be able to make the repo if you think this is a good approach?
>
> ~Shea
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev


[Nix-dev] Repo for incomplete/unmaintained work

2014-04-05 Thread Shea Levy
Hi all,

Currently we have quite a lot of unmaintained, broken, or work-in
progress components in nixpkgs. It would be great if we could get to the
point where everything in nixpkgs was expected to work and be
maintained, but part of that I think is having a place for this other
work that isn't quite up to scratch but still may be valuable can live
(it could also include experimental coding styles, proprietary services,
etc.).

Thoughts on the idea? Any idea for a name for the repo? Eelco, would you
be able to make the repo if you think this is a good approach?

~Shea
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev