ligoxi
Crew Member
Posts: 197
Likes: 356
|
Post by ligoxi on Mar 13, 2022 12:24:48 GMT
Stefan yesterday figured out that a fix from E regarding the keyboard module should be ported to moksha since it solves an issue.
1. Taking into account that i saw the code Stefan changed and i did not understand a thing
2. Dev team needs help since what they have to do from what i understand is way too much for their free time
Could i somehow read E code commits or could i contact say any E dev to document which code they judge should be backported to moksha in priority?
I am looking for ways to give back to the bodhi project not just be a user.
Unfortunately c code and efl seems too hard for me to understand. Eventhough E team has good tutorials.
|
|
|
|
Post by Hippytaff on Mar 13, 2022 12:55:51 GMT
|
|
|
|
Post by thewaiter on Mar 13, 2022 13:21:26 GMT
Dear ligoxi
We are in touch with some e devs. Mostly with raster, the main lead dev. The situation is sort of ehmm, let's call it "fragile". Raster is not very OK about the Moksha existence. He calls it "the act of arrogance". He is reffering to the Jeff's decision of forking E17 in E18-E19 era. It was caused with the incidents between Jeff and e-devs. Jeff announced lots of EFL and E bugs and E devs were not able to solve them in reasonable time frame. This is everything I can say about that situation. I was only on my dev beginnigs with Moksha and Bodhi work. Anyway, the situation sort of changed a bit when Ylee took over the project. He and me contacted raster and were able to communicate in a diplomatic way about the code etc. Raster always wants us to cooperate on E work together but the situation is as it is. I can confirm the good relations between Bodhi staff and E devs for last 3 years (we even announce E bugs to raster) but Moksha will always be an unwanted baby for raster. E is the only baby which he will take care of.
The fact is, there are still two desktops developed independently. Ylee made an E25 BODHI ISO and users can consider which desktop is better for them. As I told many times the desktops are very similar (Moksha still based on E17 code) but we are different in many features which E25 lacks and vice versa. Ylee ported many security patches from E and even checked the code with one online service for check memory leaks and code bugs. Moksha is very stable these days.
I doubt there is any e dev willing to judge code for backporting from E to Moksha. It is our role. Yes, we are very tiny crew and honestly just real 2 devs can not cover those duties with maintaining such a big deal like Linux distrubution. There are still some guys helping us finding the bugs, giving a helping hand with server (Tristam), web (oblio, hippytaff), themes (Hipytaff) and support (Enigma), also guys who translate mostly my contributions to Moksha code (and more guys I did not mention). So, it is not that bad...
Stefan
|
|
ligoxi
Crew Member
Posts: 197
Likes: 356
|
Post by ligoxi on Mar 13, 2022 14:31:57 GMT
Going to test the keyboard issue.
Regarding E vs moksha. If the de consumes idle around 400 500 mb then one can as well choose xfce. Which is rock solid and snappy. From my experience i find people that helped them revive an old laptop with the use of Bodhi. Unfortunately i have not met anyone say i am using latest E. As far as the history of E. I have tried to find each mention and every comments on the net. I have seen people being very aggressive eventhough they thought E was innovative at least in the beginning. Why not E team accept that moksha is like debian stable or a more snappy lightweight version that has the features one really needs while E is a more feature rich testing de. Fingerprint support in latest E is perhaps great but not for me. Perhaps a user through bodhi finds out about E and decides she should use latest E rather than moksha. So moksha is good publicity for E. As far as it is stable snappy and lightweight. If moksha could import all bug fixes or anything that would improve performance with the use of latest efl libraries and all other latest dependencies and continue to search for the best base os (now it is ubuntu) to host it i believe can be a real decent proposal in the linux ecosystem. Here i have heard a word for bodhi from a user: it is honest. Hope you can understand what the user is trying to say about his experience using bodhi in an old acer aspire.
|
|
|
|
Post by ylee on Mar 13, 2022 17:21:47 GMT
I pay attention to all e commits. Stefan also looks to e commits for guidance. I backport all commits that I deem relevant and actually understand if they address an issue Moksha also has. If I do not understand the commit sometimes I will talk to Raster about it.
But in the evolution of e17 into e25 many things have changed internally in the way the code works. Some commits are not relevant at all to moksha and some commits can not be easily backported. And some commits introduce new features or modules we may or may not want. As more and more time goes by moksha code and enlightenment code further diverge and the e commits are less and less useful.
As to any of the e-devs actually helping backport enlightenment commits that seems unlikely. Some are uninterested and even the few that show any interest simply lack time to take on any more FOSS work.
Since Jeff forked Moksha we have been actively hunting for any C programmers willing to help us. We found a few that showed interest but the difficulty of the task scared them off once they started looking at EFL programming and our codebase.
|
|
