XSF Discussion - 2018-10-22

candidates, mostly

I also don't seem to be receiving members emails since a while

the last one I received is Oct 1st, "Board & Council elections" by Alex

Seve: once I have your email I can check

Alex would you mind checking for me as well? AFAIK it should be lists@opkode.com

jcbrand: not on there, adding now

Thanks

jcbrand: done

Alex Is there a confirmation step?

I need to copy my application from last year and add a remark that I've been lazy

jcbrand: not that I am aware of

ok

Ge0rG: go aheah, or do you need some permissions?

Alex: I'm too lazy :P

developers are lazy, nothing wrong with tha ;-)

Alex, seve@delape.net

Maybe my old one is there but didn't notify about the change

Seve/SouL: done

thank you Alex!

Do we have a wiki page or some other intro for people who want to get involved with the XSF, and maybe volunteer for Board/Council?

Ge0rG, from zero to council is probably not a good idea anyways

for board, maybe this is interesting? https://xmpp.org/about/xmpp-standards-foundation.html

jonas’: indeed

Don't think you would make it to the council nor board without prior "experience" as a member

For board, that shouldn’t be an issue.

I didn't have experience with Council before applying ;)

Seve/SouL, I think for board, that’s fine

Seve, if you're interested, please do apply.

Seve/SouL, for board, it’s more relevant to have management skills than technical skills

so you don’t need to (IMO) have member experience

if someone who worked as CEO for $company applied for board, I think they would have a good chance to be elected

Hmm, okay, yeah, I get your point

Guus, suggestion is appreciated :)

somebody tell me I’m wrong on this

https://tools.ietf.org/html/rfc7622#section-3.3 > The localpart of a JID is an instance of the UsernameCaseMapped profile of the PRECIS IdentifierClass, which is specified in [RFC7613].

RFC 7613 is obsoleted by RFC 8265, so going there (<https://tools.ietf.org/html/rfc8265#section-3.3>): > Ensure that the string consists only of Unicode code points that are explicitly allowed by the PRECIS IdentifierClass defined in Section 4.2 of [RFC8264].

going there (<https://tools.ietf.org/html/rfc8264#section-4.2.1>): > Code points in the range U+0021 through U+007E, i.e., the (printable) ASCII7 ("K") category defined under Section 9.11.

this includes the "/" character. which would become valid in localparts of JIDs

ahhh

I am luckily very wrong

https://tools.ietf.org/html/rfc7622#section-3.3.1 excludes the characters

It's explicitly forbidden somewhere else yes