[TYPO3-dam] Any new news?

[Daniel Hinderink]

Michiel Roos [netcreators] schrieb:
> Daniel Hinderink wrote:
>> Hi Michiel,
>>
>> I appreciate your own work to improve the DAM.
>>
>> That being said, I believe you do not acknowledge the current 
>> situation we as DAM users are in.
> 
> DAM users includes me. I am voicing my own opinion as an objective 
> newcomer.

Yes, of course. My wording above was a bit off the mark. Excuse me please.

I meant to say something about grasping the general situation as it 
appears to me and others. That still is subjective and I do not want to 
patronize.


> 
>> Appeals like the one you are writing below will have no effect.
>> René _can't_ do as you ask him, if _we_ don't put him in a position 
>> where he can! That means time (paid for) and additional manpower (paid 
>> for) in his vicinity. That is the heart of Ekki's suggestion.
> 
> Rene cant apply the submitted patches to svn on typo3xdev because:
> - he doesn't have time?
> - he doesn't make time?
> - he cannot delegate tasks?
> - all of the above?

I cannot speak for René, but it seems that even reading (let alone 
answering) the amount of emails (including patches etc.) René receives 
would be taking more time than he has on his hands.

My partner, Daniel Thomas, published some extensions and the amount of 
time communication over them is binding is already impressive. It must 
be crushing considering the size and reach of the DAM.

>> Ekki's suggestion is an attempt to bring more accountability and 
>> stability into the development communication of the DAM. That includes 
>> SVN and answering to bug fixes.
> 
> Please replace the 'includes' with 'includes first and foremost'.

Yes, I agree. Please consider putting it out in SVN with all the control 
and approval processing over additions and patches it entails is a 
massive task that needs some preparation.

> 
>> This comes at a price, which is rather moderate if we can find enough 
>> companies to join in. I am prepared to pay this price, because the DAM 
>> is worth it to me and I believe this is also a model solution for some 
>> problems in the TYPO3 project. I sincerely hope many of you are 
>> willing and able to do this too.
> 
> There are more than enough dev's willing to contribute. Sponsoring a 
> project if fine with me. But the initiative is not in my hands. It's in 
> the hands of the current maintainders. So if you need sponsors . . . 
> please start writing companies and clients and convince them to start 
> sponsoring.

I believe some of them, like netcreators, snowflakes and plan2.net are 
on this list. So it seems like a fair start, before picking up the phone.

> 
>> If you feel this is too risky, then suggest criteria that make it less 
>> risky. If you think it is the wrong set of objectives, the suggest 
>> other ones. If you have some other form of factual criticism, then 
>> suggest a solution. Then we are moving in the right direction.
> 
> Please, please, I am up for any kind of model/solution as long as it 
> spearheads 'active maintenance and trackable development'. Posting a 
> reply to a bug on the bug tracker takes as much time as applying a diff 
> (which you can see is ok) to the trunk in svn.

I believe it is sometimes quite time-consuming to qualify and custom-fit 
patches. Some of them are probably no-brainers and I expect waiting for 
  them is tiresome. However other aren't.

> 
> I don't see what the time (having or making time, there's a difference 
> there)problem is for fixing small bugs.

I cannot answer that, but I imagine the perspective that René has is 
quite far apart from others, given is awareness and involvement in the code.

> 
> I unerstand that time is needed for 'developing' the dam further and 
> taking 'big' steps etc., but the small steps should be taken always.

It is the small steps that we all depend upon and that cost the most 
time. It is those that the sponsoring model concentrates on.

or as a friend of mine always says: 90% percent is only half of it.
Don't underestimate the little things!

> 
> I am sure that companies/clients are willing to sponsor a good 
> development 'plan' with clear milestones etc.

Shure, but how about sponsoring the little things with a minor glam factor?

> 
>> I really hope we can find a consensus resulting in common action and 
>> support here.
> 
> I am convinced all of us are with you on that one.

That is honestly very reassuring to read. I was afraid you and others 
might not see the problem I believe we are facing in terms of cooperation.

I so much hope we'll evolve into a community that readily joins forces 
to solve problems like this one, else I would not voice my views on a 
strictly-dev list like this one.

thanks again for your support and contribution.

Daniel