Hi, On Wednesday, December 04, 2013 03:32:45 PM Henne Vogelsang wrote:
Hey,
On 30.11.2013 15:37, Robert Schweikert wrote:
The problem is that many things that need to be done to actually get a release out the door, one of our goals one would presume, are completed by the openSUSE Team.
They are done by the SUSE Team not because they have to be done by the SUSE team but because they chose to do them :-) If they stop doing them, someone else can.
I do not agree with this view completely. In 12.2 we had to do it and 12.3 too. In 13.1 I can consider it was partially a decision, yes.
According to progress.o.o there are 285 tasks to do, there are exactly 2 (very minor ones) that require action from SUSE.
All the ones related with infrastructure are currently done by SUSE. Legal ones too. The Release Team is SUSE..... We have worked on documenting the process, publishing the tasks around it and opening some tasks to the community. As I said some months ago, there is a lot to do in this direction. But the process is set up in a way that is very hard to handle it if you are not working full time on it. It is to great extend a product focus process based on what SUSE used to do. Open it step by step would simply take too long. One goal of Factory proposal is to open the process....in a way that is affordable on volunteer basis, removing the "product component", clarifying distributing and reducing the "work packages" so it is easier to manage on volunteer basis. Still the user centric release have that product component I was talking about before. On one side, increasing the release cycle and reducing the amount of software to be released (not counting OBS) might reduce the pressure. On the other side, the fact that we will be working with older code and the desirable QA standards to be applied might reduce the volunteer basis net contribution. We have a challenge there. Part of the success of this Release version will be: a.- To set up the process in a way that volunteers can participate in short/extensive periods of time. There is no need to apply intensive work with time pressure. b.- Put paid developers in those less attractive tasks that still needs to be done, at least initially. c.- Bring more volunteers willing to work in such a release (most of what we currently have would go for factory (is a guess) and bring more paid developers into the equation. In summary, focus the paid resources in those areas where their impact is bigger.... or their presence "unavoidable".
BTW that there is this much involvement from SUSE in the openSUSE release is a very recent development. Nothing that has to continue...
Henne
-- Agustin Benito Bethencourt openSUSE Team Lead at SUSE abebe@suse.com -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org