Release Engineering

This project is intented for all release related issues (isos, installer, etc), under the umbrella of the ArchLinux Release Engineers
Tasklist

FS#63166 - accessibility for blind and visual impaired users

Attached to Project: Release Engineering
Opened by Alexander Epaneshnikov (erik_pro) - Thursday, 11 July 2019, 19:43 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Saturday, 02 November 2019, 22:56 GMT
Task Type Feature Request
Category ArchISO
Status Unconfirmed
Assigned To No-one
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

i started working on ArchIso accessibility support here : https://github.com/alex19EP/talkingarch/tree/accessible-upstreem
currently i have done:
included alsa, brltty and espeakup packages. for brltty i used brltty-minimal at https://aur.archlinux.org/packages/brltty-minimal/
created a special boot option to boot archiso live session with speech enabled.

I would like to know opinions about these changes. and what to do next to complete this project.
Comment by Gerardo Exequiel Pozzi (djgera) - Friday, 26 July 2019, 16:52 GMT
All packages used by archiso must be in repos. So I recommend as first step to do is, open a task to included needed packages.
Comment by Alexander Epaneshnikov (erik_pro) - Friday, 26 July 2019, 20:16 GMT
ok. I did it here: https://bugs.archlinux.org/task/63285
I hope that everything is correct.
Comment by David Runge (dvzrv) - Sunday, 01 September 2019, 22:02 GMT
As a general question to understand the background: Why does it have to be brltty-minimal? We have brltty [1] in the repositories.

[1] https://www.archlinux.org/packages/extra/x86_64/brltty/
Comment by Alexander Epaneshnikov (erik_pro) - Monday, 02 September 2019, 07:05 GMT
because brltty-minimal have much less dependencies
for example in live-iso we do not need bluetooth and x-server support.
Comment by David Runge (dvzrv) - Monday, 02 September 2019, 09:27 GMT
@erik_pro: I'll check whether bluez-libs and libxaw can somehow be made optional for brltty.
Comment by David Runge (dvzrv) - Monday, 02 September 2019, 10:56 GMT
@erik_pro: I've added brltty 0.6-3 to [testing]. It has further features enabled (available through optdepends) and libxaw and bluez-libs as optdepends.
Please check whether this works for you!
Comment by Eli Schwartz (eschwartz) - Monday, 02 September 2019, 16:36 GMT
The installation footprint for our releng profile, when adding brltty, has now dropped from:

+ 30.56 MiB
to
+ 18.22 MiB

So that will help. :)
Comment by Alexander Epaneshnikov (erik_pro) - Wednesday, 04 September 2019, 11:55 GMT
@David Runge i built archiso with brltty 6.0.3 from testing. and it works fine. i think it is good solution and now brltty-minimal is unneeded.
Comment by David Runge (dvzrv) - Wednesday, 04 September 2019, 18:12 GMT
@erik_pro, thank you for testing. I will move the updated brltty to [extra].
Comment by Alexander Epaneshnikov (erik_pro) - Sunday, 13 October 2019, 15:37 GMT
Hello. I think I finished the project. at least my testing showed that everything works. this is not the best solution, but it works and I haven’t come up with a better one yet.
can someone look and tell: what should I do next?
Comment by David Runge (dvzrv) - Thursday, 17 October 2019, 17:25 GMT
@erik_pro: I assume that you would need to incorporate changes into https://git.archlinux.org/archiso.git/ and send a patch to https://lists.archlinux.org/listinfo/arch-releng
Comment by Alexander Epaneshnikov (erik_pro) - Saturday, 02 November 2019, 11:08 GMT
hello. sum time ago i send patches to arch-releng@archlinux.org
I hope that everything is correct.
if there’s just no time for this yet, I understand.

Loading...