The Community Task was instead of creating
a new group. If there is a non-committer group it’s a mute point. For the
following I don’t see the point of a contributor assignment as the task
should not even be created until the issue is to the point of the artifact
being ready:
-
proof of
concept. This has to be discussed in the design forum so I don’t see why
a jira issue is needed in addition.
-
Testing.
What functionality exists for which no testcase exists? If you are just wanting
to punt the work of testcase to the community, ok to the extent that this does
not mean a test is not written. This is border line broken development in that
untested features are being released.
-
Provide
code examples. Unless this is making it into the project docbook, what use is
it? It’s just going to be out of date as time goes by.
For a patch, I can see assigning it to
someone just so that there is a notion of ownership to prevent duplicate work.
Same for a wiki page or article.
A more basic jira question is, can jira be
setup such that a contributor can assign a task to anyone, but only the contributors
show up in the drop down list? If that is allowed let’s set this up and
forget the community task and separate contributor group as the distinction and
maintenance of the group is questionable to me.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ovidiu Feodorov
Sent: Thursday, December 29, 2005
10:35 AM
To: JBoss Development
Subject: [JBoss-dev] Assigning
JIRA tasks to non-committers
Sometimes it is probably appropriate to assign a JIRA task to somebody who is
not a CVS committer. These are cases in which I find this useful:
- Creating a proof of concept or a prototype that most likely won't make it
into the main code base in its actual form.
- Providing patches that will be ultimately applied by a committer to the code
base
- Testing functionality and specific configurations.
- Provide code examples
- Write a wiki documentation page or other type of article
None of these tasks require their assignee to have committer access since they
don't imply CVS write access. However they would help a project lead to keep
track of who is doing what and administer more easily work that is done by
non-JBoss volunteers.
The current JIRA setup doesn't allow this. In order to enable it, we will need
to add a new group to JIRA ("Contributor" or similar) and probably a
new task type "Community Task" (Scott's idea). Personally I
don't see the usefulness of the last one, I think the existing "Task"
is sufficient. Following the same logic, a "Contributor" can report
an (existing type) "Bug" or can suggest an (existing type)
"Feature Request" and he can be also assigned to it, pending a patch
submission. The patch will be be applied to CVS by a committer, usually the one
who assigned the task to the contributor.
A project lead should be able to include an user in the project's
"Contributor" group. Again, this DOES NOT implies that the user will
be granted CVS access.
This arrangement could also be a good motivator for volunteers, as they see
their contributions publicly recognized and documented. Being a
"Contributor" should be prerequisite of becoming a
"Committer".
Please let me know if you find this useful.
Regards,
Ovidiu
