Do you put the translation in a vcs so we can review and make PRs?
Martin
I was also considering translating the newsletter to german but you were faster. π
emus
Martin: is fine, do the stuff I cannot do or what is more advanced. If you show me a place where to upload I can do so
Martin
Up to you. Xsf uses github for the.newsletter. I don't if it would make sense to also have translations in their repo. nyco what do you think?✎
Martin
Up to you. Xsf uses github for the newsletter. I don't know if it would make sense to also have translations in their repo. nyco what do you think? ✏
afphas left
afphas joined
emus
whatever you think is right. Github would be fine for me
emus
nyco: There is one guy having an unbelievable innovative suggestion/request: Why not sending the newsletter also through XMPP? π
ok srysly, why not? could be a read only group^^
afphas left
debaclehas joined
pep.
Yeah I believe that should also be done. There could be a pubsub server on xmpp.org for this
afphas joined
debaclehas left
emus
> Yeah I believe that should also be done. There could be a pubsub server on xmpp.org for this
For what exactly now?
emus
The newsletter via xmpp?
pep.
What you said
pep.
Yeah
emus
ok
emus
Is there a todo list in the wiki?
ldkjgoiwehas joined
Martin
> whatever you think is right. Github would be fine for me
Then push it to github, let us have a look at it and if someone of the xsf wants to have it in their repo as well they can easily pull it.
afphas left
emus
but why pull? I meant you said I need to find another pub'ish as xsf cannot do it?
emus
publisher
pep.
Martin: yeah, atm I don't think it's possible to publish multiple languages for one article. Somebody needs to put in the work and see if pelican can support that
debaclehas joined
Martin
emus: I don't talk about publishing there. But maybe the want to put the translation somewhere in their repo for the sake of completeness. π
emus
ok
Martin
Regarding publishing: Did you reach jabber.de guys?
afphas joined
Danielhas left
emus
Martin: yes, they are happy to do so
afphas left
Martin
Great, thx.
afphas joined
Danielhas joined
Link Mauve
β12:05:10 pep.> For the French translations we publish it on jabberfr.orgβ, also on LinuxFR.org.
Danielhas left
nyco
>> nyco> it is not about agreeing, it is about doing the right thing
>Then yes it is about agreeing on what the right thing is..
still wrong
it is about experimenting what users like/want
nyco
can you please stop the fight? it's boring...
nyco
> cool - then the first translation to German is done! SLIGHTLY SMILING FACE Good thing on the German unification day GRINNING FACE
OH YEAH, cool!
is it published somewehere? emus
nyco
> Up to you. Xsf uses github for the newsletter. I don't know if it would make sense to also have translations in their repo. nyco what do you think?
what's best for translators and publishers?
nyco
> nyco: There is one guy having an unbelievable innovative suggestion/request: Why not sending the newsletter also through XMPP? FACE WITH TEARS OF JOY
> ok srysly, why not? could be a read only group^^
great idea! let's try it! where and how? I guess the links will be broken though
nyco
https://docs.getpelican.com/en/stable/index.html#features
Features
Pelican 4 currently supports:
[...]
Publication of articles in multiple languages
[...]
nyco
actually, we (XSF) could host the translations? not sure, need to check more in detail at what cost/effort
should we do it? not sure, imho it is cool than local communities who do the work host the article
do translations need to be published at the same time as the original? not for me
Martin
emus: Did you upload it somewhere already?
Martin
I was busy molesting debacle to do a debian xmpp team blog post to advertise the newsletter. :D
nyco
Martin wow, great idea!
nyco
I mean... not molesting! :)
nyco
so, the DE version of the newsletter is ready, the FR just started... :)
nyco
call to translators: if we need to rephrase the English version before it is published, in order to ease all/most translations, then let's just do that, ok?
nyco
also, question to translations: what format do you need? Mediawiki markup? Markdown? HTML? other?
emus
Martin: no, working atm
Martin
jabber.de seems to be using wordpress. No idea if they still use their own markup or work with markdown now.
emus
nyco: I can translate afterwards. I recomment to just link ala
The German version will be publish in the next days overhere: jabber. de/abcde
emus
Martin: will figure out
emus
nyco: Html said Sven is goo
emus
good
Martin
emus: No rush. The publishing for proof reading is also only an offer, like 4-2*x eyes principle. If you think it is good as is you can also just publish it.
emus
Martin: ok, PM your mail and I can send you the German one for review. I just made it in a text document for the monent
emus
moment
nyco
hey, translations can be worked on the wiki as well (in addition to the Git repo)
nyco
pep. JabberFr wants/prefers what format?
nyco
translators: I think JabberFr usually does the translations on an Etherpad, but I've just participated once
jcbrandhas left
emus
> hey, translations can be worked on the wiki as well (in addition to the Git repo)
> pep. JabberFr wants/prefers what format?
can you send me a link, so I dont need to search where
jcbrandhas joined
nyco
emus we collect links here: https://wiki.xmpp.org/web/News_and_Articles_for_the_next_XMPP_Newsletter
but maybe you can create a page, linking from: https://wiki.xmpp.org/web/CommTeam
or use whatever tool is best for your translation team
emus
I have it in a text document at the moment. need to talk to Sven, he is on vacation as he doesnt reply I think
pep.
Jabberfr uses WordPress and I can't seem to be able to escape the crappy wysiwyg, so any format will do as I have to translate it anyway
emus
Yes, I dont see the big problem with it for the moment. I`d suggest, if we hit the 1000 subcribers point, we should rediscuss the system, also to include multilanguage
nyco
pep. in my WordPresses, I can always switch to HTML: you can't?
emus
thats what Sven from Jabber.de said aswell
emus
he asked for HTML
Danielhas joined
pep.
I don't know, arnaudj might know better, I'm not WordPress expert
Martin
Hehe, seems like opening the newsletter is a lot of hassle for nyco but also pays out. π
Danielhas left
jcbrandhas left
nyco
indeed, it has greatly improved imho
jcbrandhas joined
emushas left
jcbrandhas left
emushas joined
jcbrandhas joined
emushas left
Danielhas joined
Danielhas left
Martin
> nyco: problem: how do I get an account?^^
Ge0rg gave me an account
emushas joined
nyco
good
nyco
emus do you have a wiki account as well?
Martin
So far he send me an odt via email and I added my comments. But maybe for the next one we can use the wiki so more people can participate. Slowly but steady improving. π✎
Martin
So far he sent me an odt via email and I added my comments. But maybe for the next one we can use the wiki so more people can participate. Slowly but steady improving. π ✏
nyco
great, good mindset :)
nyco
btw, maybe we can split that page:
https://wiki.xmpp.org/web/News_and_Articles_for_the_next_XMPP_Newsletter
nyco
we keep that content:
1 To contributors, editors, reviewers, translators
1.1 Live discussion
1.2 What determines relevancy?
1.3 Process
1.4 Planning
nyco
and we move this part to a dedicated page, that changes every month: 2 Submissions for next newsletter
emushas left
nyco
this "central" page would be much lighter and would not move a lot, only updates in the process that happen not that often
nyco
and there would be no need to empty the content each month, to restart
nyco
for the per-newsletter pages, there would be on per month: we create it at the beginning of the moth, it grows, and then it's finished at the end of the month
nyco
what do you think? SouL emus Martin
emushas joined
nyco
also, each per-month page can have its subpage per translation
Martin
Sounds reasonable. People interested in participating are not scared away by an empty wiki page when first looking and have all necessary information (relevancy, process) at hand.
emus
> emus do you have a wiki account as well?
not yet
emus
> what do you think? SouL emus Martin
i didnt full understand your plan and i am maybe to new to this to make a decent statement. I dont really care, youre probably right and is fine