[TYPO3-workspace] Need advice on blocking bug

[Frank Gerards]

Hi Bernd,

as I wrote, i was getting upset for *not even a reaction* on my request. Even an answer like "no time, no skills, good luck",
would have been enough. 

Its not about taking anything for granted, its about spirit of community and esp. core issues, that thousands of installations may
concern. It was very unusual to see that there was NO reaction for a long time from a core-project team,
that is not how I know the TYPO3 community (and that is not how I take part in projects on forge) since 2007. 
But as I concluded, I will be more careful and esp. more careful when announcing "stable" core functionalities to customers,
which would like to use TYPO3 and support the community.

-----Ursprüngliche Nachricht-----
Von: typo3-team-workspace-bounces at lists.typo3.org [mailto:typo3-team-workspace-bounces at lists.typo3.org] Im Auftrag von Bernd Wilke
Gesendet: Donnerstag, 26. Januar 2012 14:22
An: typo3-team-workspace at lists.typo3.org
Betreff: Re: [TYPO3-workspace] Need advice on blocking bug

On 01/26/2012 12:08 PM, Frank Gerards wrote:
> Hi Steffen,
>
[...]
> I was getting upset when even my offer for sponsored development wasn't answered at all.
> I didn't ask for instantaneous , free excellent work, I just wanted 
> FEEDBACK so I can tell customers how things are planned.

sponsored development in TYPO3 <-> paid feature in closed source solution what do you /your customer expect?
and how much will it cost?

> Our customer needs a scalable workspace module and it's just harmful 
> to TYPO3 when enterprise customers (this has about 20.000 employees 
> and 1400 TYPO3 users) experience, that there is no support from the "TYPO3 company", not even a serious answer from what I thought is a core-team.
again:
TYPO3 <-> closed source solution
what do you expect? what will you pay?

> TYPO3 as a system should be trustworthy and kind of supported, because 
> i.e. the money companies make gets back to the association with member 
> fees (in our case gold status) and therefore makes it possible to  
> develop this system seriously further. It's a far better "swarm" 
> approach to coding a good software-product and I think any core-participant can be and is proud, when another big website is launched using his/her work.

as an opensource-solution you can't expect any support for granted:
there is nobody you can hold responsible for any features or behaviour.
you may pay someone to do things you expect, but he might need to get inside TYPO3 (and workspace-handling), which will take some time.

For TYPO3 there is a good (my view!) community and you can get response mostly within short time, but don't take it granted.
at first open-source means: you can dig into the code by yourself and modify it to fullfill your requests (or that of someone who pays you).

> PS:
> And yes I could dig into the code (you did,thankfully,too and sent me 
> the call-graph), but as u know for yourself, you gotta earn money for your company and cant spend days on remodeling the core.

you/everybody is free to select/change a 'better' solution.
My experience:
regardless which solution you select (includes programming something
yourself): you have drawbacks which might suggest to choose a 'better' 
solution. The 'better' solution mostly does not cover all aspects and/or the drawbacks are others.

just my view of Open-Source

bernd
--
http://www.pi-phi.de/cheatsheet.html
_______________________________________________
TYPO3-team-workspace mailing list
TYPO3-team-workspace at lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-team-workspace