git.net

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: JIRA notifications


> Do you have other ideas about how to increase engagement on issues?
> Ultimately, the issues _are_ the project. Large projects like this
> have to be well-organized to properly function, make releases, and so
> forth.

I use JIRA components to track issues by components or labels. While going through issues I update their status or request feedback.

Projects like Flink or Beam are almost impossible to keep up with in its entirety, at least for engineers who focus on specific parts of the projects. Arrow is probably comparable in size, yet I have some doubts many people can keep up with all the threads while working on highly technical aspects of the project.

Ideally, a project has committers distributed across all its components. Some projects have dedicated component leads or maintainers. A few people will still track everything but the majority just focuses on specific parts of the project.

How to get people to join and feel responsible for at least parts of the project? That's the tough question. I suppose it requires demand, open communication, leadership, and a fair bit of marketing. Happy to help where I can :)

-Max

On 21.11.18 16:16, Wes McKinney wrote:
hi

On Wed, Nov 21, 2018 at 9:22 AM Maximilian Michels <mxm@xxxxxxxxxx> wrote:

Hi Wes,

I understand that you want to be up to date with regards to all issues
in Arrow. I think for a lot of people that won't be the case. They'd
rather opt-in in or watch individual issues.

Agreed. The hope/intent is that people will see new issues and then
Watch the ones that are relevant so they will receive updates.


However, it looks like there is no other way to get notified of newly
created issues; unless you're an admin of the project. So the existing
setting seems to be fine.

Good point on the governance aspect of informing everyone on the dev
list. Frankly, I'm not sure this is an effective way of getting more
people to maintain JIRA issues.

Do you have other ideas about how to increase engagement on issues?
Ultimately, the issues _are_ the project. Large projects like this
have to be well-organized to properly function, make releases, and so
forth.

-Max

On 21.11.18 13:07, Wes McKinney wrote:
Only new issue notifications are being sent to the mailing list. issues@
receives all comments / changes so is at least 10x higher traffic. I get
issues@ in my inbox personally because it helps me stay on top of what's
going on in all aspects of the project.

I think new issues are relevant to general Arrow development. Developers
need to see bug reports, feature requests, etc so they can actively
participate in the project's governance. Otherwise the work will fall even
more disproportionately on the few of us that actively maintain and
prioritize the issues than it already does.

Of course, people with no interest in the the project issues can filter out
issues with "[jira]" in the title into a separate place in their e-mail.

Wes

On Wed, Nov 21, 2018, 5:58 AM Maximilian Michels <mxm@xxxxxxxxxx wrote:

Hi!

Do you think it would make sense to send JIRA notifications to a
separate mailing list? Some people just want to casually follow the
mailing list and it requires a filter to delete all the JIRA spam.

I see there is already an "issues" mailing list which receives the JIRA
notifications: https://mail-archives.apache.org/mod_mbox/arrow-issues/

What do you think?

Thanks,
Max