I would like to change the way "quilt setup" is implemented.
At the moment, we call rpmbuild and intercept the calls to tar and patch in order to record the location where archives are extracted and the order and options of the patches which apply to them. Then we replay that record to create our own quilt-compatible source tree.
The idea is to have an internal web page that mainly presents new SUSE employees or the ones you might not know yet. Other topics can be covered like reports about hack week projects or other interesting stuff apart from the daily work we all do.
As a start there would be a questionnaire which results are posted on a web page.
I'm in SUSE for about a month and as a fresh graduate I had to learn a lot of stuff during this period. And there is a bunch of other things I will have to learn of course. Therefore I would like to use Hackweek to deepen my knowledge of various tools, processes, techniques or other packagers related stuff. However it would be quite a pity to hold the acquired information just to myself. So I would like to keep the result of my learning for further usage either by enhancing the Innerweb wiki, the public openSUSE wiki or by creating new wiki for packagers' purposes.
Who can utilize this knowledge base? Newly employed packagers to learn important things quickly. Current packagers to share interesting techniques or hacks among them. Or just whoever else wants to quickly understand certain packagers' process or tool.
We all pant for customer data. Which hardware do customers run ? Which packages are installed ? Which services are running ? etc. pp.
A lot of this data is in the supportconfig. But this is neither collected, nor centralized, not easily accessible.
L3 workflow is implemented in a custom, developed in-house, tool called SolidGround
Explore possibilities to implement existing L3 workflow in Jira to determine whether it could potentially replace SolidGround, thus reducing the effort needed to develop and maintain SolidGround.
over 4 years
4 hacker ♥️.
Has no hacker:
1% of SUSE Manager's functionality in 0.1% of the lines of code
Let's create a much simpler SUSE Manager — one you could use at home! Users should be able to deploy and operate in minutes with minimal configuration, while still retaining the very core features that make SUSE Manager useful!
Over the years, our bugzilla database has grown up in size, becoming a very valuable source of truth for most support and development cases; still searching for specific items is quite tricky and the results do not always match the expectations.