Hello,
we're currently thinking about how we improve the build service to allow more cooperation: People should be able to change projects that are not maintained by them and propose these changes to the maintainers of the project.
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,
Rather than introducing a new system, why not unify the _link, _aggregate and your branch idea? Would be much nicer.
a) Propagate links and aggregates back to the original project, so it is possible to see, where the own data is used (equals your list command). In my proposal there is no finer classification what "creating a branch
On Monday 03 September 2007 11:29, Dirk Stoecker wrote: project" means yet. That's simply because I am not sure yet, and I would not exclude linking or aggregating.
b) Allow better handling of patches: - Allow to edit the patched files and recreate a patch from it (instead of download and handmaking patches). That's a good idea.
d) Add your notification system in a slightly modified way. What modifications are you thinking of?
I did some branching the way, that I linked the project in my home, modified it and then told the original maintainer to incorporate the diffs. Worked fine for Factory ocaml related packages. Yes, but we like to have a more "organised" way :-)
Thanks for your feedback, Klaas -- Klaas Freitag Architect OPS/IPD SUSE LINUX Products GmbH - Nuernberg --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org