Task #45474

Update project gabriel -> scheduler

Added by Adrien Crivelli almost 9 years ago. Updated about 5 years ago.

Should have
Target version:
Start date:
Due date:
% Done:


Estimated time:


This project is slightly confusing for newcomers because it refers to what seems to be (very) old things, such as Gabriel and an outdated, unused repository (https://svn.typo3.org/TYPO3v4/CoreProjects/GabrielIntegration/). However the project is still very active in "issues" parts.

To clarify the situation, I would suggest the following:

  • Make on last commit on https://svn.typo3.org/TYPO3v4/CoreProjects/GabrielIntegration/ to delete all files and replace with a readme explaining the situation (see example)
  • Update Redmine project settings to point to current repository: http://git.typo3.org/TYPO3v4/Core.git
  • Update Redmine slug from "typo3v4-gabriel" to "typo3v4-scheduler" (this might be a bad idea though, since it would break existings links, but it would make it incredibly more clear)
  • Publish a News (on Redmine) explaining briefly the situation
  • Update project setting "Overview" to say something like: "This is the official Scheduler extension from TYPO3 Core"

I'll gladly take care of all that, if given proper access.


Updated by Steffen Gebert almost 9 years ago

  • Project changed from 739 to forge.typo3.org

Updated by Adrien Crivelli almost 9 years ago

Since this issue was moved to another project, I feel I should mentioned it originally came from http://forge.typo3.org/projects/show/typo3v4-gabriel.

Also there are several things that can be done by project members. The only things for forge team is to update repository setting and change slug.


Updated by Steffen Gebert over 8 years ago

  • Subject changed from Update project to Update project gabriel -> scheduler

Updated by Bastian Bringenberg about 8 years ago

What is status here?


Updated by Adrien Crivelli about 8 years ago

Nothings has been done. And to be honest I don't even know why this ticket was moved to team-forge, since it actually concerns Gabriel/Scheduler. The only thing that may requires team-forge help is for changing the project slug.


Updated by Bastian Bringenberg about 8 years ago

It was moved because you requested a forge task and not a Gabriel task. Changing a name is a work for the Server Team and not for you, developing the project.

Shall I rename the project and move the ticket back again after that?

Have a nice day,



Updated by Adrien Crivelli about 8 years ago

Yes, please do so. Thanks !


Updated by Bastian Bringenberg about 8 years ago

I just recognized that there is nothing done in the code since 4 years... Why is this project important once again? Isn't it part of the core?


Updated by Peter Niederlag about 8 years ago

@basti: this project http://forge.typo3.org/projects/typo3v4-gabriel is not important anymore, as it is "merged/dead". It is replaced/succeeded by the scheduler which by now is part of the core and very vital.
This ticket is just a wish to somehow hook these parts together. ;)
Extension gabriel is dead/obsolete. scheduler is activ and alive.

Actually it probably makes sense to revise the whole list of projects that are listed underneath Core http://forge.typo3.org/projects/typo3v4-core in the left column.


Updated by Adrien Crivelli about 8 years ago

@Bastian, this is exactly the reason for this ticket. Gabriel is dead, but Scheduler still lives on within the core (as an evolution of Gabriel). So SVN repository is dead, but the project (http://forge.typo3.org/projects/typo3v4-gabriel) is still active. There are still issues opened and closed.

@Peter, I don't know what the policy is regarding sysext. Should they have a project of their own ? or are they supposed to be managed from http://forge.typo3.org/projects/typo3v4-core ? Digging further, I notice that there are issues concerning Scheduler in Core project

So maybe the best would be to actually completely close Gabriel/Scheduler project and only use Core project ?

I wish I could CC Francois Suter about that, but I can't add him as watcher on this issue...


Updated by Francois Suter about 8 years ago

Yes, the Gabriel project should be closed, since it has been part of the Core since 4.3. New issues should be opened as Core issues with category "scheduler". Also I would not appear as "leader of scheduler" anymore, which would be a relief ;-)

However, it's true that there are still some open issues in this old project. I can take the time to review them and close those that have been addressed in the meantime. Others should be move to the Core project, with category "scheduler".

I'll keep you posted here.


Updated by Francois Suter about 8 years ago

All open issues are still valid.

Is there a way they could all be moved to the TYPO3 CMS Core project with category "scheduler" or does this have to be done manually?


Updated by Adrien Crivelli about 8 years ago

You should be able to select all issues on the list view, then right-click -> edit, and select new project.


Updated by Adrien Crivelli about 5 years ago

This issue should be closed now (but I can't change its status myself).


Updated by Bastian Bringenberg about 5 years ago

  • Status changed from New to Closed

Closed on request.

Also available in: Atom PDF