[TYPO3-core] [FYI] Changed DBAL to svn:externals

[Ernesto Baschny [cron IT]]

Hi Xavier,

please don't be frustrated!

The process is not that fast because the relevant persons are not easy
to reach currently.

I personally have no direct interest in DBAL, but I see the benefit we
have in having it working in our core. This is why I am trying to insist
upon this issue and trying to bridge your concearns to the core team.
Don't think there is "nothing" happening, it is just slow because the
persons involved are not very active at the moment.

Cheers,
Ernesto

Xavier Perseguers schrieb:
> Hi Steffen,
> 
> Thank you for replying. Hopefully there some core member out there ;-)
> 
> But perhaps the problem is that nobody read threads that contain "DBAL".
> I swear, I'll be more tactical next time...
> 
>> it seems something went wrong here.
>>
>> When i look in forge, rep of DBAL points to
>> https://svn.typo3.org/TYPO3v4/Core/trunk/typo3/sysext/dbal/
>> And that is core trunk svn, so it's obvious that noone can commit there.
>>
>> It should be an own rep with trunk and branches, importing current
>> core version, and core shoud be set to svn_externals.
>>
>> Please fix that!
> 
> Actually the svn:externals is OK and points to
> https://svn.typo3.org/TYPO3v4/Extensions/dbal/trunk
> 
> But the pending tasks that I already wrote a few days ago have still not
> been performed:
> 
> - Updating forge repository
> - Give me access to it (am I going to be the new leader / co-leader of
> DBAL yes or no?)
> - Give me management access to DBAL projet on bugs.typo3.org
> 
> @Ernesto: I understand your concerns regarding the insurance only stable
> and reviewed code goes in but I'm not a "let's do it quick" committer
> for the projects I managed and I must admit that if I have to wait for a
> review as it is currently going on, I'd better forget wanting to get
> DBAL working again because I'm very patient but as said, frustration is
> really near.
> 
> I need DBAL for an Oracle project as now everybody should know. My goal
> as such is to get it running "properly" as it should. If those patches
> are of little concern to the community, I have enough to do and could as
> well patch DBAL in my business repository. Now as TYPO3 is open source,
> I want my work to benefit others but not at any price and my time is as
> much valuable as other.
> 
> As such I would say that until even members of DBAL are proved to be
> active again and are able to review patches quite "quickly" then review
> will be an option to be used as rule but until then, I would suggest
> that *I* review others commit on it and I would suggest people that use
> DBAL and are already active on this list (I think to Ries for instance)
> to join the project.
>