I was looking for a way to visualize the number of open issues over time
and found this: https://9-volt.github.io/bug-life/?repo=nixos/nixpkgs
.Unfortunately
we have too much content and it's hitting the API rate/limit.
The idea was to see the current trend. Maybe after 2-3 weeks of codetriage
the
>>> https://github.com/NixOS/nixpkgs/pulls?utf8=✓&q=is:pr+is:open+updated:<2015-10-01
>>
>> My point was ?if the submitter has got commit rights by now?.
>>
>> That seems to be harder to query for.
>
>Yeah, there seems to be no way. I can only see filtering by mentions of
>the whole nixos/nixpkgs
On 02/20/2016 12:31 PM, Michael Raskin wrote:
>> https://github.com/NixOS/nixpkgs/pulls?utf8=✓&q=is:pr+is:open+updated:<2015-10-01
>
> My point was ?if the submitter has got commit rights by now?.
>
> That seems to be harder to query for.
Yeah, there seems to be no way. I can only see filtering
>https://github.com/NixOS/nixpkgs/pulls?utf8=✓&q=is:pr+is:open+updated:<2015-10-01
My point was ?if the submitter has got commit rights by now?.
That seems to be harder to query for.
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.s
On 02/20/2016 10:45 AM, Wout Mertens wrote:
> Now if we could run a query for that… :-)
GitHub can run similar queries easily:
https://github.com/NixOS/nixpkgs/pulls?utf8=✓&q=is:pr+is:open+updated:<2015-10-01
smime.p7s
Description: S/MIME Cryptographic Signature
___
Now if we could run a query for that… :-)
On Sat, Feb 20, 2016, 10:26 AM Michael Raskin <7c6f4...@mail.ru> wrote:
> >Same for PRs, we have some really old ones. What is a good cutoff? 6
> months?
>
> I would start with «6 months without any updates except non-submitter
> pings and the submitter n
Same for PRs, we have some really old ones. What is a good cutoff? 6 months?
On Thu, Feb 18, 2016, 7:50 PM Profpatsch wrote:
> On 16-02-17 08:18pm, Rok Garbas wrote:
> > I would suggest closing tickets that you think are not crucial or
> > reporter does not provide code that we can include. Ofco
On 16-02-17 08:18pm, Rok Garbas wrote:
> I would suggest closing tickets that you think are not crucial or
> reporter does not provide code that we can include. Ofcourse be nice
> in comment and ask reported to reopen if they think you are wrong to
> do this.
>
> What you say, could this work and
On Wed, Feb 17, 2016 at 7:54 PM, Vladimír Čunát wrote:
> On 02/17/2016 07:49 PM, William Casarin wrote:
>> How would I go about triaging this? I went and made sure it hasn't
>> been done yet, and then move on I guess...
>
> I added a label, but I don't see what else to do, except for packaging
> i
On 02/17/2016 07:49 PM, William Casarin wrote:
> How would I go about triaging this? I went and made sure it hasn't
> been done yet, and then move on I guess...
I added a label, but I don't see what else to do, except for packaging
it, but my personal priorities are elsewhere...
There are quite a
On Wed, Feb 17, 2016 at 12:24 AM, Vladimír Čunát wrote:
> Interesting. I'm rather doubtful about this approach for this kind of
> project, but maybe it will work out well.
>
> --Vladimir
Yeah, I got this issue: https://github.com/NixOS/nixpkgs/issues/11647
How would I go about triaging this? I w
Interesting. I'm rather doubtful about this approach for this kind of
project, but maybe it will work out well.
--Vladimir
smime.p7s
Description: S/MIME Cryptographic Signature
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science
i've signed up as well. looks interesting to load balance the issue
delegation work automatically.
On Tue, Feb 16, 2016 at 11:48 PM, Jakob Gillich wrote:
> Interesting, that looks like a good way to reduce the amount of open
> issues. I've signed up.
>
> On Tue, Feb 16, 2016, at 11:43 PM, Profpat
Interesting, that looks like a good way to reduce the amount of open
issues. I've signed up.
On Tue, Feb 16, 2016, at 11:43 PM, Profpatsch wrote:
> I just created a Repo page for nixpkgs at codetriage.com.
>
> It is a simple site that sends you 1 open issue each day once
> you sign up with your G
I just created a Repo page for nixpkgs at codetriage.com.
It is a simple site that sends you 1 open issue each day once
you sign up with your Github account.
Maybe a few people want to join me.
--
Proudly written in Mutt with Vim on NixOS.
Q: Why is this email five sentences or less?
A: http://
15 matches
Mail list logo
