First, I apologize for introducing bias towards a solution. I wasn't
trying to do that, I was just trying to remember off the top of my head
what the issues were. Please feel free to edit that entry and fix it
:-) (You can note that you did this in the "change log" box that comes
with the editing).
I don't know if a "Wiki" is a good way to keep track of these things,
unless we set up a wiki section which is only editable by committers +
selected others. I don't want to be worrying about others changing what
we've put up in lists of things to remember :-)
Instead of a wiki - we could have a section of our web page that serves
this purpose - that would of course only be updatable by committers.
Finally, I agree Jira's not the place for discussion of these items. I
only put this up in Jira as a reminder list of things we should get
around to discussing at some point. I agree discussions should occur on
the mailing lists.
-Marshall
Adam Lally wrote:
I don't think Jira is the place to put architectural discussions like
"index everything" (not sure what that even means) or an implementation
for singletons, where I think the name is already misleading (because
it's about a problem that is real, but points at a solution that I
happen to disagree with).
These are good points, but maybe the answer is just to be careful to
record what the real problem is in the JIRA issue and try not to
introduce a bias towards a particular solution. If it's a real
problem, then I think it's appropriate to have an issue opened for it.
Also maybe the JIRA "Wish" category is for things that some particular
person (whether developer or user) would like to see. It's still
appropriate to have the discussion on the dev-list and ultimately
decide to reject (or modify) the idea. And sure, we can refrence the
mail archive when we decide to close or edit the JIRA issue.
If we don't do this, then we'll need a Wiki or something to keep track
of these things, and I don't see the benefit of that.
-Adam
