Last week, I’ve got ill and that is still killing me. However, I meant an old friend Larry. At one point, Larry said “Everywhere you go people talk about innovation, but in the end if you really look deeper it is only mentioned by websites and marketing agents. The development team does not employed the word “innovation” in their daily sentences.”
Then, the discussion got into a serious tone where we were concluded that the word “innovation” is no longer attractive to us. We started thinking about how to present FEL efficiently. Fedora is an innovative technology and Fedora Project deserves the use of word “innovative” here. FEL is a subset of Fedora. So here is no actually meaning or advantage FEL will have if FEL mentioned “innovation” too. But only the other hand, if some people come to seek FEL without knowing Fedora on the first place how could that particular person know that we are the actual leader in opensource EDA deployment.
After those thoughts, Larry and I were shocked to hear us talking like this. It is not us. So what actually does FEL ? We provide a mature environment to rapidly implement, deliver and evolve the technology. While our users bet their success on EDA tools(under the FEL umbrella), our roles at Fedora become serious in order to keep our ecosystem healthy.
Just like, larger EDA companies need to focus on their sales pipelines for existing products and cost-control staff, FEL has to provide manpower for both maintenance of existing RPMs together with manpower to provide new set of EDA solutions to FEL community. So from a top level, view we are feeding the ecosystem and ecoculture with opensource tools and solutions.
Our goals during the F8 and F9 timeframe was to provide RTL-GDSII design flow for both analog and digital. We did it, but still we(FEL) are not satisfied yet, we could do much better. But time limits us.
During the F10 and F11 development cycles we were focussing on “technology-to-product” transition. The user should be able to make a hardware product out of FEL. Thus, we are bridging the real world and this puts on more pressure on our shoulders. It should be noted that technology-to-product transition is not only about package updates, but extending our existing supported design flows into a specific use model with a clear roadmap. Because we are “technology enthusiast”.