ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Branko ─îibej <br...@apache.org>
Subject Re: Jira accounts
Date Fri, 14 Nov 2014 20:52:28 GMT
On 14.11.2014 20:34, Dmitriy Setrakyan wrote:
> Understood.
> To be honest, I want people to have Jira accounts to make it possible to
> assign a task to someone other than me.

As Henry already said, everyone should already have a Jira account.
Credentials are the same as for repository access (i.e., it uses LDAP).

> Now that we are on the subject, the process I had in mind is to create Jira
> tickets, discuss them with folks beforehand, and assign them to interested
> parties. Are there any suggestions to how this should be handled
> differently within Apache?

It's up to you guys to figure out what works best. Only two things are
really important:

  * Discussions (about procedure, features, etc.) must happen on this
    mailing list. That doesn't mean people aren't allowed to talk about
    things offline, of course; but the mailing list is the official
    archive of community decisions.
  * Community is more important than code, and consensus is more
    important than "being right". And when I say "community," that
    includes users and other contributors, not just committers or PMC.

Within these constraints, everything is pretty much open. Some projects
write down detailed bylaws; some depend just on tradition and community
contiguity to get the same effect. Some are very open to new
contributions, others are very restrictive in that respect.

I have a pretty strong opinion of how things should work, but it's not
my place to tell you guys how to run the project. I'll just speak up
loudly if I see something that looks like it's going in the wrong
direction. :)

Back to your question about assigning to interested parties: that's the
right kind of approach (as opposed to, e.g., just assigning suff without
asking about "interest"). Ideally, said interested parties would just
assign the tasks to themselves; a functioning community shouldn't need
that kind of centralized management.

-- Brane

> On Fri, Nov 14, 2014 at 10:45 AM, Branko ─îibej <brane@apache.org> wrote:
>> On 14.11.2014 18:53, Dmitriy Setrakyan wrote:
>>> Hi,
>>> I would like to ask everyone on the committer list to create a Jira
>> account:
>>> https://issues.apache.org/jira/browse/IGNITE
>>> I am beginning to file tickets and will be assigning them within the main
>>> committers.
>> So .... you are acting as if you are the lead of this project and have
>> the power to assign tasks to other contributors.
>> Before this gets out of hand, let me begin by saying that this is not
>> how things work around here. Every committer is a volunteer. Development
>> is driven by consensus in the community, not by dictate. It doesn't
>> matter if that's how you do things at your day job; this is not your day
>> job (even if you're employed specifically to work on Apache Ignite).
>> Clearly, any community that wants to get things done has to have some
>> kind of process and guidelines (or bylaws, if you like). However, the
>> way to set this up is to discuss it first here, on the dev list, how you
>> want to operate. Then document that.
>> It /is/ valid to decide that someone should take responsibility for
>> handling Jira issues and defining tasks. But again, you don't pull them
>> from thin air, and you don't "assign" them to anyone/./ One of the most
>> important criteria for graduation from the Incubator is that you
>> demonstrate that you can work together and reach consensus as a
>> community of individual volunteers. This pretty much precludes what
>> you've just started doing.
>> -- Brane

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message