[aur-general] TU application - alex19EP
Hello, my name is Alexander Epaneshnikov. and I'd like to join the Trusted Users team to further improve the Arch Linux accessibility for people with disabilities. I am sponsored by David Runge <dvzrv> and Sven-Hendrik Haase <svenstaro>. I started using Arch Linux in 2018 and since then it has become my main distribution. I also do my best to help blind people learn about arch and start using it. regarding minimum basic requirements: * I know how to script some things. I use zsh on a daily basis, but I can work with bash / sh too. * I maintain a few packages in the AUR[1]. I also have a couple of pkgbuilds on github[2]. * I definitely know how to google. (using surfraw for that) * my involvement with the arch mailing lists and IRC is rather low, but I am very active in blind specific lists and IRC channels. There I help users, create bug reports about a11y related problems for projects and of course talk about Arch. I can be found on irc on oftc and liberachat under the alex19EP nickname. As I already said, I would like to become a TU to further improve the appeal of Arch for people with disabilities, so I want to maintain packages that are related to a11y: * lightdm-slick-greeter - the most accessible lightdm greeter. * rhvoice - Open source speech synthesizer. (I am one of the upstream maintainers) * fenrir - A user space console screen reader written in python3 Additionally, I would like to move some packages which are popular and that I use personally to the [community] repository. * etc-update * glulxe-term * bitwarden and bitwarden-cli - eh electron I know, but it is the only cross-platform password manager which is accessible. * hunspell-ru * magic-wormhole * yadm I can also help maintain packages which are already in community: * espeakup - I am now the upstream maintainer for this project. * espeak-ng * matrix-synapse My biggest and perhaps most significant contribution to Arch is the addition of accessibility features for blind people to archiso [3] [4]. I have also written and kept documentation for installing Arch with accessibility options [5] up-to-date. my other open source contributions: I maintain RHVoice [6] and espeakup[7]. Gladly I will answer any comments or questions. [1] https://aur.archlinux.org/packages/?O=3D0&SeB=3DM&K=3Dalex19EP [2] https://github.com/alex19EP/pkgbuilds [3] https://gitlab.archlinux.org/archlinux/archiso/-/merge_requests/79 [4] https://archlinux.org/news/accessible-installation-medium/ [5] https://wiki.archlinux.org/title/Install_Arch_Linux_with_accessibility_optio... [6] https://github.com/rHVoice/rHVoice [7] https://github.com/linux-speakup/espeakup Arch project accounts: Wiki: Alex19EP Forums: alex19EP (inactive there) Flyspray: https://bugs.archlinux.org/user/28985 -- Sincerely, Alexander
Em julho 19, 2021 14:23 Alexander Epaneshnikov via aur-general escreveu:
Hello, my name is Alexander Epaneshnikov. and I'd like to join the Trusted Users team to further improve the Arch Linux accessibility for people with disabilities. I am sponsored by David Runge <dvzrv> and Sven-Hendrik Haase <svenstaro>.
Even though I'm not a TU anymore, I was aware this application was cooking up and I'm glad to hear that it finally came through! I wish you luck and I'm sure you'll be able to help Arch's accessibility if you're made a TU. Regards, Giancarlo Razzolini
On 2021-07-19 20:23:09 (+0300), Alexander Epaneshnikov via aur-general wrote:
Hello, my name is Alexander Epaneshnikov. and I'd like to join the Trusted Users team to further improve the Arch Linux accessibility for people with disabilities. I am sponsored by David Runge <dvzrv> and Sven-Hendrik Haase <svenstaro>.
I hereby confirm my sponsorship! Best, David -- https://sleepmap.de
appeal of Arch for people with disabilities, so I want to maintain packages that are related to a11y: * lightdm-slick-greeter - the most accessible lightdm greeter. * rhvoice - Open source speech synthesizer. (I am one of the upstream maintainers) * fenrir - A user space console screen reader written in python3 Additionally, I would like to move some packages which are popular and that I use personally to the [community] repository. * etc-update * glulxe-term * bitwarden and bitwarden-cli - eh electron I know, but it is the only cross-platform password manager which is accessible. * hunspell-ru * magic-wormhole * yadm I can also help maintain packages which are already in community: * espeakup - I am now the upstream maintainer for this project. * espeak-ng * matrix-synapse
+1, this is something that I'd also love to help/participate with. I tried to get fenrir going almost two years ago but didn't have the bandwidth to set up. If you're looking for co-maintainers for some of these, I'm happy to join! -Santiago
On 19.07.21 19:23, Alexander Epaneshnikov via aur-general wrote:
Hello, my name is Alexander Epaneshnikov. and I'd like to join the Trusted Users team to further improve the Arch Linux accessibility for people with disabilities. I am sponsored by David Runge <dvzrv> and Sven-Hendrik Haase <svenstaro>.
I started using Arch Linux in 2018 and since then it has become my main distribution. I also do my best to help blind people learn about arch and start using it.
regarding minimum basic requirements:
* I know how to script some things. I use zsh on a daily basis, but I can work with bash / sh too. * I maintain a few packages in the AUR[1]. I also have a couple of pkgbuilds on github[2]. * I definitely know how to google. (using surfraw for that) * my involvement with the arch mailing lists and IRC is rather low, but I am very active in blind specific lists and IRC channels. There I help users, create bug reports about a11y related problems for projects and of course talk about Arch. I can be found on irc on oftc and liberachat under the alex19EP nickname.
As I already said, I would like to become a TU to further improve the appeal of Arch for people with disabilities, so I want to maintain packages that are related to a11y: * lightdm-slick-greeter - the most accessible lightdm greeter. * rhvoice - Open source speech synthesizer. (I am one of the upstream maintainers) * fenrir - A user space console screen reader written in python3 Additionally, I would like to move some packages which are popular and that I use personally to the [community] repository. * etc-update * glulxe-term * bitwarden and bitwarden-cli - eh electron I know, but it is the only cross-platform password manager which is accessible. * hunspell-ru * magic-wormhole * yadm I can also help maintain packages which are already in community: * espeakup - I am now the upstream maintainer for this project. * espeak-ng * matrix-synapse
My biggest and perhaps most significant contribution to Arch is the addition of accessibility features for blind people to archiso [3] [4].
I have also written and kept documentation for installing Arch with accessibility options [5] up-to-date.
my other open source contributions: I maintain RHVoice [6] and espeakup[7].
Gladly I will answer any comments or questions.
[1] https://aur.archlinux.org/packages/?O=3D0&SeB=3DM&K=3Dalex19EP [2] https://github.com/alex19EP/pkgbuilds [3] https://gitlab.archlinux.org/archlinux/archiso/-/merge_requests/79 [4] https://archlinux.org/news/accessible-installation-medium/ [5] https://wiki.archlinux.org/title/Install_Arch_Linux_with_accessibility_optio... [6] https://github.com/rHVoice/rHVoice [7] https://github.com/linux-speakup/espeakup
Arch project accounts: Wiki: Alex19EP Forums: alex19EP (inactive there) Flyspray: https://bugs.archlinux.org/user/28985
-- Sincerely, Alexander
I confirm my sponsorship! Cheers, Sven
On Mon, Jul 19, 2021 at 02:35:06PM -0300, Giancarlo Razzolini wrote:
Em julho 19, 2021 14:23 Alexander Epaneshnikov via aur-general escreveu:
Hello, my name is Alexander Epaneshnikov. and I'd like to join the Trusted Users team to further improve the Arch Linux accessibility for people with disabilities. I am sponsored by David Runge <dvzrv> and Sven-Hendrik Haase <svenstaro>.
Even though I'm not a TU anymore, I was aware this application was cooking up and I'm glad to hear that it finally came through! I wish you luck and I'm sure you'll be able to help Arch's accessibility if you're made a TU.
hello Giancarlo. Thank you for your encouraging words.
Regards, Giancarlo Razzolini
On Mon, Jul 19, 2021 at 03:44:15PM -0400, Santiago Torres-Arias wrote:
+1, this is something that I'd also love to help/participate with. I tried to get fenrir going almost two years ago but didn't have the bandwidth to set up.
Have you faced any specific problems or just didn't have enough time/knowledge/enthusiasm? The main difficulty with fenrir is to get the sound to work together in the console and in the gui. but this also applies to other console screen readers like speakup/espeakup.
If you're looking for co-maintainers for some of these, I'm happy to join!
Glad to hear that. in fact, the more people are interested in accessibility, the better.
-Santiago
On Tue, Jul 20, 2021 at 05:34:47PM +0300, Alexander Epaneshnikov wrote:
On Mon, Jul 19, 2021 at 03:44:15PM -0400, Santiago Torres-Arias wrote:
+1, this is something that I'd also love to help/participate with. I tried to get fenrir going almost two years ago but didn't have the bandwidth to set up.
Have you faced any specific problems or just didn't have enough time/knowledge/enthusiasm?
It was more a lack of specifics around what was the soundsystem inside of the ISO. If my memory doesn't fail me, Fenrir required a config file that defined a bunch of alsa/pulse internals. I not only didn't have the time, but I wasn't sure if we needed to figure out what was the reasonable approach for "auto-discovery" of audio cards and whatnot. Then again, this was a couple of years ago, and things may have changed with fenrir since... Cheers! -Santiago
On Tue, Jul 20, 2021 at 11:06:24AM -0400, Santiago Torres-Arias wrote:
On Tue, Jul 20, 2021 at 05:34:47PM +0300, Alexander Epaneshnikov wrote:
On Mon, Jul 19, 2021 at 03:44:15PM -0400, Santiago Torres-Arias wrote:
+1, this is something that I'd also love to help/participate with. I tried to get fenrir going almost two years ago but didn't have the bandwidth to set up.
Have you faced any specific problems or just didn't have enough time/knowledge/enthusiasm?
It was more a lack of specifics around what was the soundsystem inside of the ISO. If my memory doesn't fail me, Fenrir required a config file that defined a bunch of alsa/pulse internals. I not only didn't have the time, but I wasn't sure if we needed to figure out what was the reasonable approach for "auto-discovery" of audio cards and whatnot.
Well, I never had a goal to use fenrir as a screen reader for archiso. I still think that this is not a good idea, there are too many dependencies. and speakup in this context, it seems to me, performs its task quite well.
Then again, this was a couple of years ago, and things may have changed with fenrir since...
not much has changed.
Cheers! -Santiago
--- Sincerely, Alexander
Howdy, Fenrir settings do not include any sound device settings. It only has settings for if you want to hear sounds instead of some indications by speech. There is a pulse configuration script that is included, but it is optional. So pretty much the minimum you need to get Fenrir working is espeak-ng, and the python libraries it needs. I do agree that Speakup is plenty good enough for a live ISO. It's already there, part of the kernel, and will speak so long as espeakup is working. Also the keybindings are similar enough so that users won't have any problem using speakup to install and to get Fenrir installed onto their new system. Thanks, Storm
a friendly reminder that more than half of the discussion period has already passed. don't miss the opportunity to ask me tricky questions, or point out bugs in pkgbuilds, bad comments, etc. seriously, I'm really looking forward to it... I don't know if I should express unpopular opinions on all sorts of things. but just in case I'll try: * I am using visual-studio-code and enjoying this. * I like gnome - seriously, when I was sighted I liked its design. * the arch community is the friendliest I know of. * reading pkgbuilds before building is mandatory, a side effect of this is that sometimes you completely rewrite it. * I believe microsoft has no evil intentions about open-source. -- Sincerely, Alexander
On Thu, Jul 29, 2021 at 02:33:12AM +0300, Alexander Epaneshnikov via aur-general wrote:
a friendly reminder that more than half of the discussion period has already passed. don't miss the opportunity to ask me tricky questions, or point out bugs in pkgbuilds, bad comments, etc. seriously, I'm really looking forward to it...
Hmm, I'll bite. I think by now a mandatory question is "how do you track upstream releases?" I don't think I saw it asked anywhere else in this application. Cheers! -Santiago
29.07.2021 17:47, Santiago Torres-Arias пишет:
On Thu, Jul 29, 2021 at 02:33:12AM +0300, Alexander Epaneshnikov via aur-general wrote:
a friendly reminder that more than half of the discussion period has already passed. don't miss the opportunity to ask me tricky questions, or point out bugs in pkgbuilds, bad comments, etc. seriously, I'm really looking forward to it... Hmm, I'll bite.
I think by now a mandatory question is "how do you track upstream releases?" I don't think I saw it asked anywhere else in this application.
hello Santiago. I am glad you asked. at the moment I track most of my packages manually, as I participate in their development, or often send reports. I don't think it will always be that way, and that's why I recently started using nvchecker. so far I have not used it so much, but it seems to me its capabilities cover all my use cases.
Cheers! -Santiago
-- Sincerely, Alexander
I think by now a mandatory question is "how do you track upstream releases?" I don't think I saw it asked anywhere else in this application.
hello Santiago. I am glad you asked.
at the moment I track most of my packages manually, as I participate in their development, or often send reports. I don't think it will always be that way, and that's why I recently started using nvchecker. so far I have not used it so much, but it seems to me its capabilities cover all my use cases.
Cheers! -Santiago
yeah, the overall consensus is that urlwatch/nvchecker are the way to go. Glad you're checking it out, and feel free to reach out for config files/tips and tricks (I indeed learnt a lot from Anthraxx for configuring my urlwatch setup). Cheers! -Santiago
On 2021-07-19 20:23:09 (+0300), Alexander Epaneshnikov via aur-general wrote:
Hello, my name is Alexander Epaneshnikov. and I'd like to join the Trusted Users team to further improve the Arch Linux accessibility for people with disabilities.
The discussion period is now over and I have started a vote: https://aur.archlinux.org/tu/?id=131 Best, David -- https://sleepmap.de
On 2021-08-03 00:32:21 (+0200), David Runge via aur-general wrote:
The discussion period is now over and I have started a vote: https://aur.archlinux.org/tu/?id=131
And the results are in: Yes No Abstain Total Participation 45 2 9 56 91.80% Congratulations and welcome to the team! :) Best, David -- https://sleepmap.de
participants (6)
-
Alexander Epaneshnikov
-
David Runge
-
Giancarlo Razzolini
-
Santiago Torres-Arias
-
Storm Dragon
-
Sven-Hendrik Haase