[TYPO3-dev] Core list now open for everyone

[Christian Kuhn]

Michael Stucki wrote:
> I still want to add that we not only expect more patches to be sent but also
> hope for support in doing reviews! Otherwise all patches will still depend
> too much on the help of the core team, and we'll end up at the same problem
> which we had for ages already...
> 

Ok, what else can I do to help?

The patches I will send will at least work for me, otherwise I would
start a thread in typo3-dev asking for advice.

As far as I see a non-core-dev now can:
- Test and review patches submitted to the bug tracker, and add
hopefully use full comments.
- Manage coordination of related bugs "off-site" (betwenn several
typo3-related non-core-devs) and try to commit them when they are
finished or need to be reviewed by a responsible team.
- Write mail to some bugtracker-dev (who?) with more rights and send
notes like "close #0815 because its obsolete", or "edit state of #0816
to x", or "set relation from bug #0817 to #0818". That is just about
cleaning up of the bt, many people might see things, but only a few
people can actually change. There are eg. currently a lot of bugs that
could be closed, they are just waiting for a dev to be informed and to
do so.
- Test and vote a svn request on typo3-team-core ml: I will try to do
this when I understand the impact and functionality of a submission. Is
it ok for a non-core-dev to vote +/-1 to a patch on the core list?
Should this be done in the bt?


Christian