I don't think they *need* to understand coding deeply. I think even a
beginner programmer could do much of this.
Consider these two one-line summaries:
1. "improve help output of 'svn status'"
2. "revamp the editor interface to invert RA layer's server communication"
Which do you think is bite-sized, and which is Really Hard? :-)
Sure, there will be some issues where a non-coder, or somebody not
intimately familiar with the Subversion source code, will not know how
to classify something. But that's okay. Any work on the issue tracker
is a *positive* help.
Cheers,
-g
On Fri, Mar 20, 2009 at 08:38, Edmund Wong <edmund_at_belfordhk.com> wrote:
> Hi,
>
> I was reading the 'job description' and noticed a slight,
> for lack of a better word, 'weirdness' to it. I quote:
>
> "One thing such a person could do would be to go
> through the list of outstanding issues, figure
> out which ones are likely to be bite-sized tasks,
> and mark them as such, so that other volunteers
> have an easier time choosing things to work on."
>
> Doesn't this imply the issue manager must also understand
> coding in order to determine which issue would be
> considered 'bite-sized' and which aren't?
>
> Any clarifications appreciated.
>
> Edmund
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1362623
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1364205
Received on 2009-03-20 13:20:27 CET