Problems contributing to the Linux
I’m an Electronic engineer. I did several embedded projects with hardware and software interworking. So, I am somehow experienced in programming. I also had several projects in Windows in Delphi language. As I became familiar with Linux, it was always one of my wishes to contribute in this huge project. I even wrote some open source projects myself. Which are stored in Sourceforge.net site (autoppp, blackwar and jalaliapplet).
Actually I have some problems contributing to already started projects. To describe you my problems, I bring here Blur effect in KDE as an example and If you know answers of my questions, please do not hesitate to leave me a comment how to solve my problems. Recently I installed Kubuntu 11.04 with KDE 4.6 on my laptop. Blur effect is enabled on Panel as is working there without any problem. But the problem is that transparent windows are not blurred. The scenario is always like this:
|
OSS projects vary in accepting user contributions. Some are open and others are more tightly controlled. People have submitted patches to Firefox that are desired by many users and been turned down if it is something the core developers don't want to include. Just because someone invites you into their home, it doesn't mean they will let you paint the walls a different color. I don't know the specifics of KDE, you would have to look into who supports it and how open they are.
Changing it for yourself is another matter. You should be able to get all of the source in tarballs or srpm, unpack them, patch them and build them. As for switching back and forth - maybe. I have 6000+ files with the letters 'kde' in them on my system, and that's with no source installed. The easiest way would be to deploy your test builds to separate virtual machines, but you might be lucky and find the code you want to change isolated in one library somewhere. I naively tried to make a change to Evolution, once. I never got past the first step of getting it to build. There were so many dependencies and conflicts on latest and greatest tools, libraries, kernel, etc. that I eventually gave up. I suspect the KDE team has their own build environment which may or may not be described in the READMEs. Good luck. |
Quote:
Quote:
Quote:
For example, if I have a graphics-related problem, I first Google for the problem keywords and my desktop environment. In your case, using +KDE +transparent +blur will yield the answer in the third hit, in a KDE forum post. If that did not work, I'd look at my distribution's (Kubuntu) forums and bug reports. If that did not work, I'd look at the desktop environment's (KDE) forums and bug reports. If that did not work, I'd look at the graphics stuff developers mailing lists (mostly here) and the Linux kernel mailing list archives (for example here). Quote:
Hope this helps. |
I humbly suggest that perhaps you are not yet receiving a warm reception because your apparent level of background knowledge (e.g. "what is SVN?") might leave them a little skeptical.
Mind you, I'm not passing judgment here; not at all. What I'm saying is that these are first impressions. As they say, "first, you gotta get past the gatekeepers." Perseverance and persistence, coupled with a lot of humility, might be the key here. First, you need to be sure that you are aware, not only of how to solve the problem at hand, but also how it would integrate into the (KDE...) project and clearly benefit that project. Then, consider how you can portray that level-of-knowledge to a perfect stranger. Then, on a much more pure-political level, you must persuade another engineer whom you do not yet know that they really should answer the phone when you call. (Remember, that phone rings all the time ... and much of the time it's not worth answering. As an engineer yourself, you know how that is ...) :) I hope that you might find these suggestions useful. Good luck. |
All times are GMT -5. The time now is 03:42 PM. |