[opensuse-project] openSUSE Team at SUSE update
Hi, 12.3 is out! For most of the people out there this is "just another Release". For us in the openSUSE Team it has been an extraordinary one for several reasons. What we understand as Release is fact formed by two different phases: * Development phase (integration) * Release phase During 12.2, openSUSE Team at SUSE documented and executed the last few milestones of the Release process[1]. This effort allowed us, together with the work done in the Development phase done by coolo and the one done by the formed Release Team (coolo + ismail) and your continuous effort, get a Release with good acceptance. Even though 12.3 was a shorter Release, we were better prepared for assuming the responsibility. we improved and extended the documentation of the Release process[2], we reinforced the management effort, lead by Ludwig, we introduced the Hackathons in the process, we introduced the content/communication tasks earlier in the process and we added a significant amount of effort in designing and introducing QA as a relevant action of the Release process. These actions allowed us to improve the engagement with community members in several areas, increase the impact and the quality of our communication, include complex features like Secure Boot in the distribution, increase our efficiency significantly despite we have integrated new members in the team, improve several new features introduced in 12.2 (translations, social media campaign) and correct several weak points detected during the previous release. In general, from our point of view, we improved as a team and we improved the Release process. It will take time before this internal improvements have a clear impact in the quality of the distribution but those of you who are close to this effort might confirm or not this internal conclusion. Now that the Release is over, the team goes back to other tasks and the Release Team focus on factory. As you know Ismail is no longer in the team and we expect during this year many SUSE employees helping us in the openSUSE development so we are now studying new approaches to the Release Team. we expect to have a solution soon so factory goes back to a normal state. A consequence of our new approach related with QA has been the detection of several limitations in the main tool we use, openQA. Together with upstream developers, we are currently dedicating most of team resources to this tasks[3]. There are some other tasks that we are currently working on (April): * Event organization: openSUSE Board Meeting, Joint Desktop Meeting, Plasma Frameworks 5 Sprint. Now that the Release is over, we will also put energy in openSUSE Conference. * Travel Support Program Management application[4]: as you know, the involvement of SUSE in the TSP program committee is now zero, which means that is the community who now run the program. Our support is focused on the administrative, financial area. In order to increase the relevance of the Program, we have detected a need for a tool that allow the TSP, the Board and SUSE to coordinate better to become more efficient. * At SUSE, we have been preparing several proposals for the Board that we are presenting this weekend to better coordinate the following areas: ** Event/Merchandising area ** Infrastructure ** Financial * SUSE strategy and Action plan in openSUSE. we are currently discussing what are we going to do in openSUSE the following years as part of the community. In a few weeks we expect to count with a new artist for the team and, during summer, a new hacker will join the team. As you know, we are also looking for a senior KDE developer since Will Stephenson has moved to another department (thanks Will for your work in openSUSE, see you around). In order to follow our activity please check our management tool[4]. I think it kind provide a good overview of the complexity of the Release process. [1] 12.2 release process documentation published: http://en.opensuse.org/openSUSE:Public_Release_Action_Plan [2] 12.3 release process management tool: http://board.opensuse.org/projects/opensuse-12-3-release/issues/gantt [3] openQA development sprint: http://board.opensuse.org/projects/openqa-improvement/activity?set_filter=1&... [4] Management tool: http://board.opensuse.org/projects Saludos -- 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
On Sun, 07 Apr 2013 12:51:09 +0200 Agustin Benito Bethencourt <abebe@suse.com> wrote:
Management tool: http://board.opensuse.org/projects
It is a cool tool and I learned a lot browsing the site. I like that many services depending on each other are integrated and it would be cool to have such tool on community disposal and replace bug tracker, wiki, forums, project management with all-in-one solution. Looked at the Chili Project web site and it seems that openSUSE is using default layout which is close to our bento theme, and in my humble, has one small improvement to bento. Red buttons at the top right are just about right color and shape to be spotted easily when one looks for more options, but not intrusive. Noted also, that they need more people for software development and documentation. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
On Sunday 07 April 2013 20:03:41 Rajko wrote:
On Sun, 07 Apr 2013 12:51:09 +0200
Agustin Benito Bethencourt <abebe@suse.com> wrote:
Management tool: http://board.opensuse.org/projects
It is a cool tool and I learned a lot browsing the site.
I like that many services depending on each other are integrated and it would be cool to have such tool on community disposal and replace bug tracker, wiki, forums, project management with all-in-one solution.
Looked at the Chili Project web site and it seems that openSUSE is using default layout which is close to our bento theme, and in my humble, has one small improvement to bento. Red buttons at the top right are just about right color and shape to be spotted easily when one looks for more options, but not intrusive.
Noted also, that they need more people for software development and documentation.
As a matter of fact you're free to create an account and come help us ;-) As far as creating new projects here is concerned (so the community can use it for more things), I don't know what the plans are but I'd expect that to be a plan for the future. /Jos
Hi,
It is a cool tool and I learned a lot browsing the site.
Great.
I like that many services depending on each other are integrated and it would be cool to have such tool on community disposal and replace bug tracker, wiki, forums, project management with all-in-one solution.
Looked at the Chili Project web site and it seems that openSUSE is using default layout which is close to our bento theme, and in my humble, has one small improvement to bento. Red buttons at the top right are just about right color and shape to be spotted easily when one looks for more options, but not intrusive.
We haven't put effort into the layout. We are waiting for the artwork specialist that will join the team for this task. In any case, if somebody have a special willing in providing a design, it is something we can implement once we are done with the openQA Sprint.
Noted also, that they need more people for software development and documentation.
As a matter of fact you're free to create an account and come help us ;-)
One of the reasons to implement such a tool is to be able to manage collaborations. In this Sprint this is not a key goal. since it is the first time the new team work in a sprint. It will be in the following ones. But yes, those interested in contributing can join. Please ping Alberto Planas, the openQA Srpint controller: aplanas@suse.com
As far as creating new projects here is concerned (so the community can use it for more things), I don't know what the plans are but I'd expect that to be a plan for the future.
This tool was implemented as the management tool for openSUSE Team. We believe that well organized teams that are already working as such and have a real need for such a tool will use it in the future. The first option we have in mind is the Service Team, that manages openSUSE infrastructure. We have also offer the possibility of using it to the openSUSE Board. In any case, teams will join little by little. We do not expect this tool to become the default tool to manage projects by the community in a short term. The internal design has been done basically for the openSUSE Team at SUSE, the current setup do not support heavy load and the flexibility of the tool is limited. On the feature side, we are still working on implement what we need. Saludos -- 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
participants (3)
-
Agustin Benito Bethencourt -
Jos Poortvliet -
Rajko