First openSUSE Community Week Starts Monday

Techwriter10 0 Tallied Votes 333 Views Share

This coming Monday, May 11th, marks the start of the first annual openSUSE Community Week, an event conceived of by openSUSE community members to help mentor folks who want to get involved with the openSUSE open source Linux project, but don't know how to get started.

The virtual conference will be conducted almost entirely in IRC and runs from May 11th through the 17th. I asked Joe 'Zonker' Brockmeier, the openSUSE Community Manager (whom I interviewed in Joe 'Zonker' Brockmeier Discusses openSUSE 11.1) how it came together and what the virtual event entails.

RM: Describe the openSUSE Community Week concept.

JB: It's very straightforward -- contributing to an open source project is easy, in theory, but in practice there's a lot of knowledge that helps contributors to become efficient.

One way to get that knowledge is to go to the project's Web site, read the pages, how-tos, go into the mailing lists, ask questions and sort of poke around to become familiar with the project. This works for lots of people, and that's great. But, we think we can help a lot of people accelerate the process of becoming contributors by having the Community Week and giving tutorials and being available for questions and generally getting experienced contributors together to mentor newer contributors.

We'll also be "recording" sessions so that people who miss the live sessions can go through the tutorials and so forth to benefit from the sessions as well.

RM: This is the first openSUSE Community Week. How did this come together and why did you decide to do it?

JB: It started out as a discussion on how we could improve community participation in openSUSE. We decided to do this because we think it'll be a good way to pass on knowledge about working in the openSUSE Project. We have some really knowledgeable contributors, and this is a good way for them to pass on some of their expertise to new contributors.

RM: What do you as community manager hope to accomplish this week?

JB: Probably the same thing as everybody else participating -- that is, to help newer contributors come up to speed more quickly and help enable them to make contributions and shape the project.

RM: Is this a virtual event or will people be gathering together at a conventions somewhere? How many people will be attending?

JB: Totally virtual. Mostly in IRC, though we also have a web presentation tool we may use for some sessions. We'll also put up material on the openSUSE wiki that can be used for some of the tutorials.

Not sure how many people we'll have, I hope hundreds. Since it's a distributed event in multiple channels (packaging presentations will happen in one IRC channel, marketing discussions in another, and so forth) that take place over an entire week, I think we'll see quite a few people by the end of the Community Week.

RM: This is obviously important for openSUSE, but what are the broader implications for FOSS in general?

JB: World domination for Linux, obviously. :-)

Actually, I'm not sure this has broader implications for FOSS in general, except to help promote contribution. Just as we've taken some ideas from other projects, I hope our community week is successful and inspires other projects to do similar things.

RM: Why do you think you're the first openSUSE community manager to organize an event like this? Are other distros doing similar activities?

JB: To be clear, I don't want to take the credit for organizing the Community Week. I'm doing *some* of the organization, but so are many other people -- Michael Loeffler, Bryen Yunashko, Sascha Manns, Jan-Simon Möller, Will Stephenson, Vincent Untz, Holger Sickenberg, Vladimir Nadvornik, and many others. That's the beauty of community activities -- lots of people pile in and help out.

Other distros do similar activities. It's not unique to openSUSE. I think when most projects start to scale they find it useful to hold real-time events to reach out to their community and try to mentor new contributors.

Dani AI

Generated

A short, practical primer for anyone who saw 's announcement and plans to take part. The focus here is on concrete, hands-on steps you can complete in a few hours that make you useful during a mentor-led outreach effort — and that leave you positioned to keep contributing afterward.

Before you join: pick one very small goal (a typo, a failing unit test, or a single-line bug). Set up an isolated build/runtime environment (VM or container), configure your source-control identity, and create a short working branch. Reproduce the problem locally and reduce it to the smallest possible test case or command sequence — that minimal reproducer is the most valuable thing you can bring to a help session.

During a live session: be concise. Say what you tried, paste the exact commands and the short, relevant output, and point to a branch or patch if you have one. Use a paste service for long logs instead of dumping them inline. If you want a review, describe the change in one sentence, list tests you ran, and state exactly what kind of feedback you need (style, correctness, or integration). Follow the project code of conduct and be patient — maintainers are helping many people.

Afterward: convert the discussion into a real contribution. Open a small pull request or attach a patch to the issue, include a clear commit message and a brief test that demonstrates the fix. If you cannot finish, leave precise notes so someone else can pick up where you left off. Repeat this loop: one small fix, full test, documented PR. Consistent follow-through matters far more than a single large attempt.

A minimal commit-message template you can copy:

Short summary (<= 50 chars)

More detailed explanation (why, what, edge cases).
Fixes: #123
Signed-off-by: Your Name <you@example.com>
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.