[TYPO3-dev] Contribution to community extensions

[Stefan Padberg]

Am 17.08.2014 um 08:46 schrieb Xavier Perseguers:

> USE CASE 1
> ==========
>
> You - as a user - spot a problem.
>
> 1) How difficult is it to report it? It may be asking for help in the
> mailing list/forum/social network/friend/... or in a bug tracker

This is almost impossible for me. I am used a little bit to the 
TYPO3-Forge, and I report bugs to the extension which are hosted there. 
But anything else is too much for me. It is not intuitive, and it costs 
me too much time, or I need another account to do that.

 From my point of view, all extensions should be hosted on the Typo3 
forge. That was the plan some years ago, and that was a good plan. I 
don't understand why the good plans are always changed, and in the end 
nobody knows what to do because of too much choices.


>
> 2) Do you think of creating a ticket? Are you comfortable with that? Do
> you feel like creating a ticket means additional work such as going back
> regularly (maybe in a tool you are not usually monitoring) to see if
> there is something new?

The system of the Forge is good. I stay informed, and I can participate, 
or I can leave it.

>
> 3) Regarding a bug tracker, do you get notification about changes,
> author asking for further detail, fix being prepared and waiting for
> double-check, ... or not?

That was many times impossible. A patch to test came often many month, 
even years after I reported the bug, and I had moved to another 
version/extension or what ever long time ago and could even not remember 
the problem.

>
> 4) How do you feel with *testing* a fix? You reported a bug (or found
> someone else having the same and already having reported it), and
> suddenly either a one line change is proposed in one of the comments or
> a patch is attached (typically SVN) or a review on Gerrit
> (review.typo3.org) is waiting approval, or a pull request is ready, ...
> As a user, is it something you understand how to test, are ready and
> able to do? (productive system or local environment, FTP only or
> SSH/console/tools to apply patches, understand how a patch is to be
> "applied" or don't get what that means, ...). Or are you more "I
> reported it, I don't know how to test a pending fix but I'm willing to
> install *a* new version as soon as it is available" (I mean even if
> that's not an officially released version but one that is intermediate
> and fixes my problem)

I would test the fix if it is within a short delay time, lets say 3 
days. After that time I probabely have found another solution or fixed 
the problem - which I would report as well.

All the best
Stefan Padberg, Wuppertal

---
Diese E-Mail ist frei von Viren und Malware, denn der avast! Antivirus Schutz ist aktiv.
http://www.avast.com