ZF2 issue report

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

ZF2 issue report

ThaDafinser
Hello together,

somehow inspired by the "PHP Pull requests report", i've started yesterday to go over the open issues of ZF2 in github.

First some numbers:
- 336 issues are open / 4549 are closed
- 199 labels are assigned on the open issues
- 43 issues are 10 months old (including enhancement suggestions)
- 98 issues are older than 6 months (including 10 months old issues)
- 64 issues were not updated for minimum 6 months

I've started now on some easy issues to ask for feedback from the people if the issues is still present or if it can get closed, to get rid of some old issues.

Surprising to me was, what there are many issues which has no labels at all. 
For example on this page is nearly nothing labeled or someone assigned: https://github.com/zendframework/zf2/issues?direction=asc&page=5&sort=created&state=open


Who is allowed to label issues and takes care of that?


Best regards
Martin
Reply | Threaded
Open this post in threaded view
|

Re: ZF2 issue report

weierophinney
Administrator
On Fri, Jul 26, 2013 at 5:40 AM, Martin Keckeis
<[hidden email]> wrote:
> I've started now on some easy issues to ask for feedback from the people if
> the issues is still present or if it can get closed, to get rid of some old
> issues.

Thank you for this -- many of the issues stem from the early betas,
and are likely irrelevant at this point; however, it's often hard to
triage that information properly.

> Surprising to me was, what there are many issues which has no labels at all.

Most of the ones with labels were actually imported from our old JIRA
instance, and labels were created based on tags/component of the
original issue. Unfortunately, GitHub has setup issues such that only
maintainers of a repository can assign labels -- which means for any
new issues, such as those in this link:

> For example on this page is nearly nothing labeled or someone assigned:
> https://github.com/zendframework/zf2/issues?direction=asc&page=5&sort=created&state=open

will not have labels unless a maintainer (my team, the community
review team) adds them.

To be honest, I typically forget to do so; you can usually figure out
what component it is, and whether it's a feature request or bug
report, by reading it.

> Who is allowed to label issues and takes care of that?

See above. If you want, you can suggest labels in a comment;
hopefully, then, one of us with maintainer rights will then add them.


--
Matthew Weier O'Phinney
Project Lead            | [hidden email]
Zend Framework          | http://framework.zend.com/
PGP key: http://framework.zend.com/zf-matthew-pgp-key.asc
Reply | Threaded
Open this post in threaded view
|

Re: ZF2 issue report

ThaDafinser
Hello together,

2013/7/26 Matthew Weier O'Phinney <[hidden email]>
On Fri, Jul 26, 2013 at 5:40 AM, Martin Keckeis
<[hidden email]> wrote:
> I've started now on some easy issues to ask for feedback from the people if
> the issues is still present or if it can get closed, to get rid of some old
> issues.

Thank you for this -- many of the issues stem from the early betas,
and are likely irrelevant at this point; however, it's often hard to
triage that information properly.


i've gone now through more issues and asked for feedback and some of them could get closed already.
I think there are plenty more around, so i'll continue to go through them.
 
> Surprising to me was, what there are many issues which has no labels at all.

Most of the ones with labels were actually imported from our old JIRA
instance, and labels were created based on tags/component of the
original issue. Unfortunately, GitHub has setup issues such that only
maintainers of a repository can assign labels -- which means for any
new issues, such as those in this link:

> For example on this page is nearly nothing labeled or someone assigned:
> https://github.com/zendframework/zf2/issues?direction=asc&page=5&sort=created&state=open

will not have labels unless a maintainer (my team, the community
review team) adds them.

To be honest, I typically forget to do so; you can usually figure out
what component it is, and whether it's a feature request or bug
report, by reading it.

> Who is allowed to label issues and takes care of that?

See above. If you want, you can suggest labels in a comment;
hopefully, then, one of us with maintainer rights will then add them.


I think this is not good, if issues have no labels....

Why labels?
- you can filter for components and find open tasks for them
- if you have an issue on a component you can filter for it
- issues dont get "lost"

It's easy to label and many people could do that (if they would be allowed).

Can't more people have this right to assign labels and assign people?

Best regards
Martin


Reply | Threaded
Open this post in threaded view
|

Re: ZF2 issue report

weierophinney
Administrator
On Tue, Jul 30, 2013 at 3:21 PM, Martin Keckeis
<[hidden email]> wrote:

> 2013/7/26 Matthew Weier O'Phinney <[hidden email]>
> > On Fri, Jul 26, 2013 at 5:40 AM, Martin Keckeis
> > <[hidden email]> wrote:
> > > Who is allowed to label issues and takes care of that?
> >
> > See above. If you want, you can suggest labels in a comment;
> > hopefully, then, one of us with maintainer rights will then add them.
> >
>
> I think this is not good, if issues have no labels....
>
> Why labels?
> - you can filter for components and find open tasks for them
> - if you have an issue on a component you can filter for it
> - issues dont get "lost"
>
> It's easy to label and many people could do that (if they would be allowed).
>
> Can't more people have this right to assign labels and assign people?

It's a GitHub limitation. Basically, to have that right (labeling),
you have _all_ maintainer rights, which includes pushing code to the
repository, tagging, etc. The problems come when somebody who is only
supposed to label stuff accidentally pushes code to the organization
repository instead of their personal repository -- a situation we want
to prevent as much as possible (and do so by having limited active
maintainers).

When it comes to assigning issues, again, it's a GitHub limitation:
you can only assign issues... to people with maintainer rights. Which
makes no sense, as _anybody_ can create a pull request.

Hopefully GitHub will make changes here -- I know there are a number
of issues posted in their own trackers asking for these changes, and
those are getting a lot of support; the question is when and how they
will happen.


--
Matthew Weier O'Phinney
Project Lead            | [hidden email]
Zend Framework          | http://framework.zend.com/
PGP key: http://framework.zend.com/zf-matthew-pgp-key.asc