Fedora Developer Interview: Chitlesh Goorah


After a lot of work during the Fedora 7 release cycle, it was made possible to re-spin Fedora to suit your needs, and although there were a few spins created during that release cycle, this time around we're seeing some really exciting uses of this feature. One of the coolest spins to be created is the Fedora Electronics Lab.
Read on for an interview with Chitlesh Goorah, the developer behind this feature - in which he discusses the help he had from the community, the target audience, his inspiration for creating this spin - along with some screenshots showing off some of the apps you can find on this spin...
To start, if you could tell us a bit about where the inspiration for this feature came from? Is it an area that hasn't been tackled by other distributions/OSs?
The inspiration for this feature came from HOW it got its name "Fedora Electronic Lab".
At the very beginning, there was neither the intention for a Fedora Electronic Lab nor its spin. During my post-graduate studies in Micro-Nano Electronic Engineering, I needed VLSI simulation tools. I started packaging the VLSI simulation tools for Fedora, which I needed for my studies. Then MirjamWaeckerlin and my lecturers in Strasbourg, France, encouraged the concept of introducing Application-Specific Integrated Circuit (ASIC) Design Flows on Fedora, so that they can recommend to other students or use those tools themselves.
After receiving some feedback from the Fedora community, the objectives got wider...
-
- Login or register to post comments
Printer-friendly version
- 952 reads
PDF version
More in Tux Machines
- Highlights
- Front Page
- Latest Headlines
- Archive
- Recent comments
- All-Time Popular Stories
- Hot Topics
- New Members
GitLab Web IDE
| Record Terminal Activity For Ubuntu 16.04 LTS Server
At times system administrators and developers need to use many, complex and lengthy commands in order to perform a critical task. Most of the users will copy those commands and output generated by those respective commands in a text file for review or future reference. Of course, “history” feature of the shell will help you in getting the list of commands used in the past but it won’t help in getting the output generated for those commands.
|
Linux Kernel Maintainer Statistics
As part of preparing my last two talks at LCA on the kernel community, “Burning Down the Castle” and “Maintainers Don’t Scale”, I have looked into how the Kernel’s maintainer structure can be measured. One very interesting approach is looking at the pull request flows, for example done in the LWN article “How 4.4’s patches got to the mainline”. Note that in the linux kernel process, pull requests are only used to submit development from entire subsystems, not individual contributions. What I’m trying to work out here isn’t so much the overall patch flow, but focusing on how maintainers work, and how that’s different in different subsystems.
| Security: Updates, Trustjacking, Breach Detection
|
Recent comments
2 hours 5 min ago
2 hours 6 min ago
2 hours 7 min ago
5 hours 13 min ago
5 hours 25 min ago
12 hours 18 min ago
1 day 14 hours ago
1 day 15 hours ago
1 day 21 hours ago
2 days 22 hours ago