[Typo3-dev] The Right Crew

[Christopher]

Hello,

On 27/10/05, Patrick Gaumond <patrick at typo3quebec.org> wrote:
> Kasper Skårhøj wrote:
>
> > its a pity that
> > this list (Dev-list) has been discussing core features and architecture for
> > years without devicing how it intends to put it into action. Success is no
> > suit and certainly not talk. Where are the people with the hats on?
>
> Kasper, you're the one with the biggest hat. Sometimes you're not
> visible on the DEV-list for months and reappear with TV or Workspace
> that no one ever heard before.
>
> > With no results in terms of release-worthy code we could just as well rename the list /dev/null.
>
> I've seen quite some code and patches in the bug tracker and the Gremlin
> effort looks like a great way to get some things done. In a perfect
> world, Gremlin would be a constant project but it's possible only if the
> patches are reviewed and accepted.

Just a question on the subject of contributing to code:

I have no hesitation in saying that I'm _not_ as experienced or
sophisticated a programmer as the core developers on this list. Having
said that, I have a very good understanding of programming logic, and
a broad enough knowledge of php to contribute small pieces of good
quality code.

My question is this -- and in part it stems out of ignorance about how
large programming projects are actually carried out, so forgive me if
it sounds idiotic: does anyone see any value in setting up a part of
the bug tracker for _requested_ code contributions?

I have in mind a process whereby a busy developer that knows s/he will
need functions a(u) = x, b(v) = y and c(w) = z to complete some
component s/he's working on could post the expected input and output
to a list and other users such as myself could write a function to do
the required job. The developer could then evaluate and merge the
functions into the main component.

What I don't know is if this actually makes any sense from the point
of view of a person taking on large programming tasks...but I would
like to find a way for less sophisticated coders to contribute while
keeping quality high.

Any thoughts?


-Christopher