Author: sumantrom (page 14 of 14)

Fedora Media Writer Test Day – 2016-09-20

Fedora Media Writer Test Day - 2016-09-20Today, Tuesday, 2016-09-20, is the Fedora Media Writer Test Day! As part of this planned Change for Fedora 25, the Fedora graphical USB writing tool is being extensively revised and rewritten. This tool was formerly called the “Live USB Creator” and is now re=branded as “Fedora Media Writer”.

Why test the Media Writer

The idea is the new tool will be sufficiently capable, reliable, and cross-platform to be the primary download for Fedora Workstation 25. The main ‘flow’ of the Workstation download page will run through the tool instead of giving you a download link to the ISO file and various instructions for using it in different ways. This would be a pretty big change, and of course, it would be a bad idea to do it if the tool isn’t ready.

So this is an important Test Day! We’ll be testing the new version (Fedora, Windows, and macOS) of the tool to see whether it’s working well enough and catch any remaining issues. It’s also pretty easy to join in. All you’ll need is a USB stick you don’t mind overwriting and a system (or ideally more than one!) you can test booting the stick on (but you don’t need to make any permanent changes to it).

Help test the Media Writer!

All the instructions are on the wiki page, so please read through and come help us test! As always, the event will be in #fedora-test-day on Freenode IRC.

On-boarding Kickoff: Fedora QA, Bhopal, India

Fedora QA on-boarding kickoff in Bhopal, India: Starting the video call

Getting the mentorship call started

Furthering the FOSS Wave initiative to prepare students for the industry, it required us to work closely with and mentor people in the right way. Bhopal, India, has a good number of contributors who want to learn about Fedora Quality Assurance (QA). I started off by helping them to start with a few QA activities.

Continue reading

FOSS Wave: Delhi, India

FOSS Wave in Delhi, India: Getting started for the dayOpen source is the new trend. When major corporations are moving towards open architecture by using open source tools and even pushing their internal projects into open source, it makes your contributions especially worthy. But before starting with contributing, many people face the same common set of questions. How they can start, how should they introduce themselves in the community, and where they can contribute. To answer these questions, I planned a session on free and open source software (FOSS) and Fedora at the Northern India Engineering College in Delhi, India.

During the planning phase, I got in touch with Sumantro, who is himself an open source enthusiast and contributing to various open source projects including the Fedora Project. With his help, we planned the agenda for the session and gathered the resources to conduct the session. On 12th August, 2016, this session on FOSS and Fedora was conducted to:

  • Answer these questions
  • Bring up new people in the open source arena
  • Show where they can contribute, learn and make an impact

Continue reading

FOSS Wave: Bhopal, Madhya Pradesh, India

FOSS virtual meetup, Bhopal, Madhya Pradesh, India

A start of a big journey!

Furthering the efforts of some work around building a strong, tight-knit FOSS community around Fedora, I approached a few people from Bhopal, Madhya Pradesh. I figured out the scope to talk about Fedora and Fedora quality assurance (QA). The target audience was bringing more college students from Bhopal into open source and Fedora.

Talking FOSS and Fedora with Bhopal

The meeting was short and simple. The audience was well-versed with free and open source software (FOSS) and many of them are presently contributing to various FOSS projects. We started off talking about how contributing to FOSS makes contributors industry-ready. As the cog wheel of time revolved, we shifted to “how people can join” the Fedora Project and start contributing!

Continue reading

Getting started with Fedora QA (Part 3)

This article is a part of a series introducing what the Fedora Quality Assurance (QA) team is, what they do, and how you can get involved. If you’ve wanted to get involved with contributing to Fedora and testing is interesting to you, this series explains what it is and how you can get started.

This is the third and last part of the Getting started with Fedora QA series. In the last post, we talked about how to create your test environment and use Bodhi to test updates and leave feedback. This article will focus on running test cases and how to complete one.

Continue reading

Getting started with Fedora QA (Part 2)

This article is a part of a series introducing what the Fedora Quality Assurance (QA) team is, what they do, and how you can get involved. If you’ve wanted to get involved with contributing to Fedora and testing is interesting to you, this series explains what it is and how you can get started.

Next steps towards Fedora Quality Assurance (QA)

This is a continuation of the previous post in this series of how to get involved with the Fedora Quality Assurance (QA) team. Make sure you have the Bugzilla, FAS account, and email alias set up before following these steps. You can find more information about how to get those accounts in the earlier post.

There are several different tools and services available to help us test Fedora. This helps us insure the quality of software and stay on target for a stable release. One of the easiest ways to get involved is to run Rawhide, the ever-changing development version of Fedora, or a pre-release version like the Alpha or Beta. While you are able to upgrade your system directly to these versions, sometimes you may want to use a virtual machine (VM) to work in. We’ll cover some of the Fedora-specific tools for quality assurance testing as well as setting up your environment for testing.

Continue reading

Fedora 24 Release Party: Bangalore, India

Fedora 24 Release Party, Bangalore, India: Contributors earning badges

Attendees earning badges as contributors!

Over the past few months, many of us in the Bangalore open source community have focused our efforts of writing test cases for Fedora, organizing a few sessions where one can learn about testing, and how we can do things together. All this while, it has been fun: I’ve met new people, learned things, and realized that sharing even small pieces of knowledge and experiences makes it easier for newcomers to feel welcome.

Organizing a release party

At one point when Fedora 24 was released, it was exciting as we were closely involved with Fedora release validation testing and so we wanted to put together a release party. All open source projects encourage their communities to celebrate software release and similar milestones. Ours was a simple plan! We were having a really good time learning together and we wanted to get more people to know that there is a better way to gain knowledge: by sharing and working together.

Continue reading

Hosting your own Fedora Test Day

Many important packages and software are developed for Fedora every day. One of the most important parts of software development is quality assurance, or testing. For important software collections in Fedora, there are sometimes concentrated testing efforts for pulling large groups of people in who might not always help test. Organizing a Fedora Test Day is a great way to help expose your project and bring more testers to trialing a new update before it goes live.

Most of the time, you will be able to test software updates without help. But for larger software or packages crucial to Fedora, having more eyes and hands to poke around is useful and helpful. This post explains and walks you through the process for organizing your own Fedora Test Day and what work goes into it.

Continue reading

Getting started with Fedora QA (Part 1)

This article is a part of a series introducing what the Fedora Quality Assurance (QA) team is, what they do, and how you can get involved. If you’ve wanted to get involved with contributing to Fedora and testing is interesting to you, this series explains what it is and how you can get started.

What is Fedora QA?

Fedora is an open source Linux-based operating system with a new release once every six months.The development environment is fast-paced, and with every release, users require new features or updates for existing features. To make sure everything works and performance is improving, testing and quality checks are a must. In Fedora, we have to encompass the user experience as there are thousands and thousands of people who expect a more stable, feature-enriched operating system that gets better with each release.

The Fedora Quality Assurance (QA) team is the group of Fedora contributors that helps cover testing of the software that makes up Fedora. Through various test cases and different hardware, the team goes through important software that makes up Fedora and helps make sure it works as expected.

Understanding the release cycle

Before jumping into getting started, it is important to understand the testing process. Rawhide is an ever-growing “branch” of Fedora where contributors can push their packages. Rawhide is the future of new Fedora development versions where bleeding edge updates are pushed. At regular time intervals, Rawhide will be branched into an alpha release for the next version of Fedora. Rawhide will keep moving forward, but the next version of Fedora will begin taking a more stable form from this point.

If you’re not sure what branched means, it’s when part of Rawhide is “pulled” out for extended testing and refining for the final release. As we reach the branch point, the QA testing cycle switches its focus towards the upcoming release.

Where can you start?

To get started, you will need to register in the Fedora Account System (FAS). Every project needs a contributor to have an account for basic details and logging into different services. FAS is the beginning point for every Fedora contributor and it is used for the entire time you are involved with Fedora.

For quality assurance, a Bugzilla account is a must. No code is 100% bug-free, so whenever you discover an issue, you can file a bug. Someone will then be able to fix your bug once they have enough information, or if you’re looking for a challenge, you can try fixing it yourself! Whichever is the case, a Bugzilla account is an important tool to start off with.

Next, you will need to get a @fedoraproject.org email alias. There are some places in QA where you might need to log in with Mozilla Persona, and it will ask you for your @fedoraproject.org alias. This alias is formatted as your_FAS_username@fedoraproject.org. These pages will look similar to this.

Getting started with Fedora Quality Assurance (QA): Logging into Phabricator

This is the Fedora QA Phabricator instance.

It is worth noting that to obtain a @fedoraproject.org email alias, you need to be what is called “CLA+1”. This just means you are a member of at least one group or sub-project in Fedora besides signing the Fedora Project Contributor Agreement. With this, you also get a web-hosting space that can be used for hosting projects or packages outside of Copr.

Once you meet the CLA+1 requirement, you will be able to receive mail with your Fedora Project email alias. It is possible to use it for sending email as well, although you will have to use a workaround. There is a wiki page that explains how to do with email clients, or if you use Gmail, you can do it from the web email client.

Now that you have your accounts set up, it’s time that you know what people are working on and where you can chip in.

Introduction to IRC and mailing lists

The QA team mostly uses Internet Relay Chat (IRC) and mailing lists for communicating and working on the project. It’s important to use these tools for contributing as this is where the rest of the team works on testing and quality assurance.

IRC

This is a good place to know and interact with others. It’s also good for having 1:1 interactions! IRC is meant for people who want to have a topic-focused discussion. For a variety of different discussion topics, you will find channels for those topics. For Fedora QA, join #fedora-qa. This is a global communication tool, so asynchronous chat happens often.

Never used IRC before or a little bit intimidated? Check out this IRC Beginner’s Guide on the Fedora Magazine for more help getting started.

Mailing list

When you are in doubt, want to have a discussion, get feedback, and/or catch up with what people are doing in other parts of the world, mailing lists are the place to be. A mailing list is a subscription-based tool. You have to subscribe to the list where you want to post to. In Fedora QA, you subscribe to test@lists.fedoraproject.org.

After you hit the Login button, you authenticate with Mozilla Persona, your FAS account, or a Yahoo account. To subscribe to the list, you can use any email. You don’t have to use a @fedoraproject.org alias. You should probably avoid subscribing with that email if possible if you don’t have sending set up for it (otherwise you will receive emails but your replies will never make it for others).

The Fedora QA mailing list is very welcoming, so just introduce yourself!

The next post in this series will be talking about how you get involved with QA after introducing yourself and getting familiar with the basic tools like FAS and Bugzilla. Stay tuned!


Debug courtesy of Lemon Liu, Crash Test Dummy courtesy of James Keuning (from the Noun Project)

Newerposts

Copyright © 2024 Fedora Community Blog

Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 International License.

Theme by Anders NorenUp ↑