On Monday 03 September 2007 10:24:40 wrote Klaas Freitag: ..
Please read a DRAFT concept for this what we call branching of sources under http://en.opensuse.org/Build_Service/Concepts
I am looking forward to reading your feedback,
[Details] "In case the user does not have write permission to the project, a branch of the base project is created by the API."
I would just keep in mind, that a user might want still branch, even if he has write permissions. For example for pre-testing a change, which is maybe risky.
[API Calls] It does look that you want alsa allow branching of a complete project. How would that work ? I suppose either
1) create new project and create source links for each package
2) create a new mechanism which allows linking of projects.
The "/source/home:<person>/_branchprojects" should maybe
because of handling multiple project branches.
Do you really want to create notifications when branching ? Isn't this something what should get defined later in a generic event notification proposal ? Shouldn't this be called "Merge request notifier" here ?
Apart from my comments, I think your proposal describes the needed api tasks completely :) We may should also create some end-user workflows dealing with typical use cases to get also a picture what needs to done in the clients.
Do you have any opinion how the actual merge should be done ? Will it happen in the backend like it happens already when you have source linked + patched packages ?