emusI think they are a good way to enable community involvement from people with not so much tech-background. Translations would be great in general I think.
However with the lack of ressources dunno where to go.
jcbrandhas joined
jcbrandLink Mauve: because coordinating them takes time and energy and we're few people. It's better to be a bit less ambitious and be able to do something for longer than to burn out quickly by doing too much.
jcbrandI'll never stop someone from making translations, but I don't see the point in going out of our way to accommodate them either
emushas left
Alexhas left
Alexhas joined
Guus+1
pep.well the technical/infra stuff only has to be done once
emushas joined
emus> well the technical/infra stuff only has to be done once
Yes, I'm happy to translate. but what burns down is transfering between the platforms. I at least that is what we should improve.
And even without translations, there are still needs to transfer text back to the Wiki and someone has to merge it to the website from github. Last time also formating was not process (no offence, just to clarify about the problem). And we althought think about not using pictures anymore because of traffic or so...... I mean, ... really?
emusGuus: Thanks for your help in the Monal issue btw
GuusNp
jcbrandhas left
jcbrandhas joined
Neustradamushas joined
Neustradamushas left
debaclehas joined
emushas left
emushas joined
SouLhas left
SouLhas joined
intosihas left
intosihas joined
Wojtekhas joined
Wojtekhas left
Wojtekhas joined
Wojtekhas left
Wojtekhas joined
Guushas left
Guushas joined
Link MauveSomething I’d like to do wrt translations is more technical ones.
Link MauveFor instance the XEPs are unreadable if you don’t speak English.
Link MauveSame for xmpp.org.
Link MauveWhen I wrote my first XMPP client, XMPP wasn’t any more open than any proprietary protocol due to the specs being English-encrypted.
Link MauveI don’t have the time or energy to pour into doing a translation of xmpp.org, but that would be a good direction to go imo.
emusLink Mauve: For that sounds like a good suggestion! I still would stick to keep the term wording english. But yes. that would be a cool project I think✎
emusLink Mauve: For me that sounds like a good suggestion! I still would stick to keep the term wording english. But yes. that would be a cool project I think ✏
Link MauveDepends on the language, we tend not to do that in French for instance.
emusYes, I know, you should try to translate once, eg. Last Message Correction. But afterwards stick to the english term. (My intention is, that we keep the wording in general similar)
emuson an inter-cultural basis
Link MauveI still think it depends on the language.
Link MauveLanguages not using a Latin alphabet will probably want to use names in their languages instead.
Link MauveFrench too usually.
Link MauveExcept maybe for acronyms?
Link MauveGerman is usually fine with keeping English terms around.
jcbrandemus: my issues with images was that it's not clear where they should be hosted and I'm not sure simply copying URLs from somewhere else is a good idea.
jcbrandPerhaps others here have some ideas or suggestions
jcbrandTo host them ourselves, we need to put them in our repo, which I don't think is a good idea
jcbrandBut perhaps there's another way
DebXWoodyWhy not keep the files of newsletter in a repo in md-format an deploy all within on site?
DebXWoodyThe english is on xmpp.org, isn't it?
jcbrandI'm specifically talking about images here
jcbrandThe newsletter is already in markdown format in the xmpp.org repo
emusOk, yes. Absolute not blaming or offending. I just wanted to show that we think about think we maybe shouldn`t about. I mean that in a positive manner✎
emusOk, yes. Absolutely not blaming or offending. I just wanted to show that we think about think we maybe shouldn`t about. I mean that in a positive manner
jcbrand: ✏
DebXWoodyWhy not keep the fr, de,... at the same place?
jcbrandDebXWoody: that would probably be better than having them hosted elsewhere.
emus> To host them ourselves, we need to put them in our repo, which I don't think is a good idea
> But perhaps there's another way
Yes sure, I agree
DebXWoodyIn a second step we can think about to generate tar.gz files to download.
DebXWoodyan generate some small "post records" like "The new newsletter of xmpp is avaiable on xmpp.org site.... <link>". Which can be used by others (microblog, social media,...)
emusDebXWoody: If you have an open repo for this, you just fork it or?
Sounds a bit complicated, or?