For wvkbd, the core contributors need access on github.

We should split the list from https://sxmo.org/source with "internal" "others" to give an idea of what is running on sxmo setups.

I agree ~stacyharper

We should also add the readme section recommended on this page: https://sfconservancy.org/GiveUpGitHub/ to our readme on wvkbd's github.

On 22-11-16 10:02, ~anjan wrote:

~stacyharper, ~phartman, and I ~anjan need read and write access to the wvkbd and wayout repositories.

Cc: ~proycon

Right! wvkbd on srht was already set properly. Wayout wasn't yet, added you all now. Also checked clickclack.

For github jjsullivan5196/wvkbd we might have to poke John Sullivan if we're not all in there as I can't access the repo settings either.

--

Maarten van Gompel

proycon@anaproy.nl https://proycon.anaproy.nl https://github.com/proycon

GnuPG key: 0x39FE11201A31555C XMPP: proycon@anaproy.nl Matrix: @proycon:matrix.anaproy.nl Telegram: proycon IRC: proycon (libera.chat + oftc) Mastodon: https://social.anaproy.nl/@proycon (@proycon@social.anaproy.nl) Keyoxide: https://keyoxide.org/8AC624881EF2AC30C0E68E2C39FE11201A31555C

btw can you add my luc.edu e-mail address to sxmo-devel so I can flag things as closed/etc. via e-mail. I think I'm entered with my gmail.com account. Catch me on #sxmo for details.

On 23-01-19 01:50, ~phartman wrote:

btw can you add my luc.edu e-mail address to sxmo-devel so I can flag things as closed/etc. via e-mail. I think I'm entered with my gmail.com account. Catch me on #sxmo for details.

I think we need Miles (~mla) to do that. Poking him on IRC may be quickest?