|
Post by Hippytaff on Sept 4, 2020 21:54:27 GMT
Hey Bodhi Crew I'm going to cut to the chase. There are a lot of EFL applications that are awesome that need some love. Currently we only maintain Bodhi's core EFL applications, which are ephoto, evisum, and the legendary terminology. It would be really awesome if we could package and maintain all the other EFL applications in our repo as well. So we are going to do just that. This is why we need the help of the Bodhi community. If you have the time and inclination and want to contribute...and get involved in all that open source stuff that we all love so much...Testing efl packages and reporting issues would really help this community a really lot. If you have the mind to. Find our moreCheers The Bodhi Team(Crew)...or something :/
|
|
rcatbc
Member
Posts: 38
Likes: 14
|
Post by rcatbc on Sept 4, 2020 23:02:36 GMT
i would be interested in seeing if i could help. i don't see a whole lot of info at your "apply within" link (other than "use at your own risk") that says how to help or what the other efl applications are that need testing. can you provide some more info or is it best to ask in that thread? thanks 
|
|
|
Post by Hippytaff on Sept 5, 2020 8:42:09 GMT
Thanks for the reply rcatbc. I’m planning on writing a testing and reporting guide soon with a list of applications to install and test from the repo once they are packaged and put there if there is enough interest. In the mean time there are efl gadgets, modules etc that could all do with testing. Thanks again for your interest.
Edit - I changed the link name from apply within to the more suitable, find out more. I won’t lie, I might have had a beer before posting last night. Broke my own drink posting rule 😬
|
|
|
Post by ylee on Sept 5, 2020 16:27:06 GMT
i would be interested in seeing if i could help. i don't see a whole lot of info at your "apply within" link (other than "use at your own risk") that says how to help or what the other efl applications are that need testing. can you provide some more info or is it best to ask in that thread? thanks  I will create a full list soon as I can. More focused on packaging stuff for our next release. That is quite a task in itself. I will slowly be added some of these apps to BL 5.x repos and of course they all will be in BL 6.0 repo when 6.0 is released. At least the more or less stable ones. For the record two have been in our repo for some time now: - ecrire a simple text editor
- epdfview an efl pdf viewer
epdfview is a C++ program and is using some now deprecated functions. I could probably take a few hrs or a day and fix all the depreciated functions warnings. It needs to be done but who knows when I will find the time. I opened a few pdfs with it and it appears to work ok enough. for the record I use Evince.
|
|
rcatbc
Member
Posts: 38
Likes: 14
|
Post by rcatbc on Sept 5, 2020 21:17:54 GMT
Thanks for the reply rcatbc. I’m planning on writing a testing and reporting guide soon with a list of applications to install and test from the repo once they are packaged and put there if there is enough interest. In the mean time there are efl gadgets, modules etc that could all do with testing. Thanks again for your interest. happy to try and help. that guide sounds about like what i was looking for. a list of what needs testing as well as what kind of feedback will be helpful. i look forward to getting that  I will create a full list soon as I can. More focused on packaging stuff for our next release. That is quite a task in itself. thanks. that list and/or Hippytaff's guide sound like they will do the trick. my test system has the testing repos added. will that work for what you are looking for or would you prefer results from a system using the main repos?
|
|
|
Post by ylee on Sept 5, 2020 21:19:58 GMT
... my test system has the testing repos added. will that work for what you are looking for or would you prefer results from a system using the main repos? The testing repo is ok. Anything stable enough I will be added to the main repo anyway. But question stuff I may add to the testing repo.
|
|