emus: I tried, but uploading files requires push access to the repository
wurstsalat
maybe we can start a link collection for potential images, and then someone with access pushes them?
arnaudjhas left
arnaudjhas joined
emus
👋
emus
yeah, should be fine. Maybe at the end of the month we drop some links in the PR
arnaudjhas left
Nÿcohas left
debaclehas joined
arnaudjhas joined
Nÿcohas joined
peetah
what should be fine ?
emus
Should be fine to do so
emus
> maybe we can start a link collection for potential images, and then someone with access pushes them?
peetah
ok
peetah
so, for now, nobody has the possibility to upload images ?
DebXWoody
:-D
arnaudjhas left
arnaudjhas joined
debaclehas left
wurstsalat
are there still images needed for the current issue?
wurstsalat
emus?
peetah
JSCX images are free to reuse for "reviews and similar", I'm waiting for permission to resuse screenshot from profanity since their blog does not have copyright notice, and wolfieanmmol gsocmblog does not have copyright notice either✎
peetah
JSCX images are free to reuse for "reviews and similar", I'm waiting for permission to resuse screenshot from profanity since their blog does not have copyright notice, and wolfieanmmol gsoc-blog does not have copyright notice either ✏
peetah
emus, as an XSF member, could you join him to ask for permission to reuse the gif linked in the july newsletter ?
wurstsalat
for the 1.2 release of gajim we could use https://gajim.org/img/news/account-badges.png (which is CC-BY-SA, from the release post on gajim.org)
SouL
emus, regarding the other PRs that there are, no, none of the current ones apart from the newsletter belong to commteam, so don't worry
alacerhas left
alacerhas joined
alacerhas left
alacerhas joined
arnaudjhas left
arnaudjhas joined
Alexhas left
Alexhas joined
alacerhas left
alacerhas joined
emus
peetah: I have the permission I think
emus
SouL: okay, but I think there is no one in general
peetah
great
Nÿcohas left
emus
peetah: I think there is a right to quote someones publications?
emus
anyway I can contact them
arnaudjhas left
peetah
reusing images is not the same as quoting someone, and if there is nothing indicating the licence for republication, it is legally required to get an authorization first
Nÿcohas joined
peetah
so I guess it would be better to ask for it, if not for legal reason, at least for courtesy
alacerhas left
alacerhas joined
arnaudjhas joined
arnaudjhas left
arnaudjhas joined
emus
If I get all that managed by tonight I can do so otherweise I prefer to take it out and we do for the next version this procedure
emus
or we just drop our own screenshot... I mean that is allowed, right?
peetah
sure :)
emus
maybe that is the easiest way^^
peetah
then I'll do it
peetah
but it will have to be uploaded on the repo
DebXWoodyhas left
DebXWoodyhas joined
arnaudjhas left
arnaudjhas joined
peetah
permission to reuse profanity screenshot granted
peetah
emus: sorry, when I said I would do it, for whatever reason, I had profanity screenshot in mind
peetah
the only image permission missing is now from wolfieanmmol gsoc-blog which I won't be able to reproduce
Have somebody else upload the first image? and upload the rest
emus
yes was wondering
peetah
I would go in the /content/images/ folder, then clich on upload files and proceed from ther✎
peetah
I would go in the /content/images/ folder, then clich on upload files and proceed from there ✏
peetah
I guess it will ask for a file from your computer and a target folder
pep.
emus, wasn't there a desktop client for github? Maybe it's easier to use
peetah
but I can't say for sure since I just have a "File uploads require push access to this repository." message
peetah
can't you just clone the repo and commit the file from there
peetah
then push
peetah
?
emus
Ok, now I know how it works
emus
give me another 5 minutes
emus
everything is ready, you can now commit resized (smaller sized) pictures to the new location: https://github.com/xsf/xmpp.org/tree/master/content/images/newsletter
emus
in the future
peetah
great ! thanks !
emus
Okay guys, we are close! Just the new linking missing ... 🏃♂️️

emus
Si?
peetah
I guess so
peetah
I'm looking for a way to limit image size via pelican conf
emus
ok, hmm Github is not rendering - are you sure I cannot use the full link?
emus
Shouldnt be a problem or?
peetah
if you want pelican to do its job, then I think it has to be this way
emus
Okay, then I ignore it and leave it like this
emus
======= Redaction Closing for June 2020 XMPP Newsletter======
emus
🤸♂️️
vanitasvitae
emus, I guess you have to remove the leading "/" from the image link
emus
okay, but also for pelican?
emus
I focus on what pelican wants to see
peetah
no you have to keep the leading /
emus
ok
peetah
this is how the blog post linked above did, and it is perfectly rendered on the web site
vanitasvitae
okay, havent used pelican
vanitasvitae
just for markdown you'd have to remove the slash.
peetah
if images was in the same folder as the md, which is not the case✎
peetah
if "images" folder was in the same folder as the md, which is not the case ✏
emus
we will see tomorrow
peetah
emus: you created the folder in "master" : should'nt have been created in newsletter-july2020 branch and then merged with the rest of your PR ?
peetah
I have absolutely no clue about the possible consequences
emus
fuck, I knew I did something wrong
emus
how was that possible 🙈️
peetah
not wrong, open to improvements :)
emus
but wait - in the master branch everything is fine?
peetah
it is
pep.
fwiw, if the image is meant to stay it might be best just to leave it there
vanitasvitae
Oh boy, dat commit history 😛
pep.
since it's a big binary file, otherwise you're gonna have git storing big diffs
peetah
I would have used "newsletters" rather than "newsletter" though
pep.
renaming should be fine
pep.
I think
emus
vanitasvitae: 🙄 I know I know
emus
I used newsletter because thats the general top term. details will come if you click it
emus
vanitasvitae: If you have well experience you can sqatsch the commits but I rather leave my hands of foe today 🤐✎
emus
vanitasvitae: If you are well experience you can sqatsch the commits but I rather leave my hands of foe today 🤐 ✏
emus
vanitasvitae: If you are well experienced you can sqatsch the commits but I rather leave my hands of foe today 🤐 ✏
vanitasvitae
squashing on master is a bad idea
vanitasvitae
guess for that it's too late.
vanitasvitae
In general, you should work in feature branches and merge those into master once you are ready.
vanitasvitae
It may be a good idea to make the master branch protected, so that nobody can directly push to it
peetah
can't we just reset master to the latest good commit ?
emus
vanitasvitae: Yeah, I wonder actually why that is not the case
vanitasvitae
peetah, sure, but maybe someone/something already pulled and will then have to deal with merge conflicts and stuff
emus
but on the other side we need someone to continuiously manage this
vanitasvitae
protecting the branch is a good thing imho
vanitasvitae
that way you can only contribute to it via merge requests
emus
yeah
pep.
yeah maybe ask iteam. It's also good to do that just to avoid common mistakes
vanitasvitae
yup
emus
Now I ruined it for everyone 😄
pep.
haha
emus
No fun anymore guys ¯\_(ツ)_/¯
vanitasvitae
quick! hide it under a ton of good commits!!!
peetah
:D
emus
Haha - actually I wonder how I commited to the wrong branch. it is hard in the Github interface 🤔
vanitasvitae
😀
emus
Enough crazy commits for today. Thanks everyone for helping out and create the release for tomorrow. The new draft PR is already open. From now on only wonderful perfect commits 🙂
peetah
thanks emus for your work on this new newsletter
emus
Sure - now we all dance XMPP like YMCA:
emus
🙅♂️️🙆♂️️🤦♂️️🤦♂️️
emus
😄️
emus
uhh, you have icon duplication? I do in Conversations
emus
Dino is doing weird things maybe?
Licaon_Kterhas left
Licaon_Kterhas joined
arnaudjhas left
arnaudjhas joined
kikuchiyohas left
alacerhas left
alacerhas joined
kikuchiyohas joined
kikuchiyohas left
kikuchiyohas joined
kikuchiyohas left
kikuchiyohas joined
kikuchiyohas left
kikuchiyohas joined
kikuchiyohas left
kikuchiyohas joined
arnaudjhas left
arnaudjhas joined
la|r|ma
interesting. So dino sends [person gesuring no][join][male symbol][emojify][emojify]
This makes sense to some degree, but [emojify] is often not needed.
[male symbol] = ♂
[male symbol][emojify] = ♂️
[person gesturing no] = 🙅
[person gesturing no][join][male symbol] = 🙅♂
[person gesturing no][join][male symbol][emojify] = 🙅♂️
[person gesturing no][join][male symbol][emojify][emojify] = 🙅♂️️
[person gesturing no][join][male symbol][emojify][emojify][emojify] = 🙅♂️️️
la|r|ma
ahaa it's not getting better when trying to send these things from dino 😀
la|r|ma
where is my unicode codepoint input field 😀
ldkjgoiwehas joined
ldkjgoiwehas left
ldkjgoiwehas joined
la|r|ma
emus, file a bug with Conversations, something is very weird with Conversations here...
Hi. I think it would be much easier for the team if the commteam would have an own repository where they can work. Maybe it's possible to give just access to this reposiory and the team would be able to work on master for the daily work.
ldkjgoiwehas left
ldkjgoiwehas joined
kikuchiyohas left
ldkjgoiwehas left
ldkjgoiwehas joined
arnaudjhas left
arnaudjhas joined
kikuchiyohas joined
kikuchiyohas left
emus
la|r|ma: ouh you are seeing this :D
pep. can you imagine I got that far 😂😂😂 (yesterday I made actually the joke to him with the emojis)
jcbrandhas left
kikuchiyohas joined
pep.
Yeah I had to open Conversations because I wouldn't see it properly in poezio, but I'm used to that anyway :p
emus
DebXWoody: yes, I think we try to keep it easy. I will wait if there is any outcome of the Gitlab question. But lets keep that in mind fir the september release
DebXWoody
question?
DebXWoody
What is the question?
emus
DebXWoody: jonas was evaluating if Gitlab is interesting for XSF
DebXWoody
Ah,... +1, this would be nice. I would also start to help on some topics for XSF.
peetah
I'm not sure if being interesting is really the question… the real question is rather what burden will it bring and who is going to administrate the beast.
DebXWoody
administrate the beast?
pep.
peetah, it's not gitlab but gitlab.com
pep.
So same as github.com
pep.
"same", admin-wise
peetah
I mean , being independent vs depending on a microsoft owned closed source forge => no brainer
peetah
ahhhh I thought we were talking about an independant instance of gitlab
DebXWoody
I think is not requiered to have an own server. gitlab.com would be fine.
pep.
DebXWoody, well.. moving from github.com to gitlab.com because you want to stop depending on Microsoft is somewhat missing the point :p
peetah
not for me: I've been there and fled when they changed their ToS to include sharing data with third parties
pep.
There are other reasons to do this move, but this is not really one IMO
DebXWoody
pep.: It's not only Microsoft. GoogleAPI, closed software, etc. I prefer codeberg.org, but gitlab has more features and is also quite nice.
peetah
what is codeberg ? I see several projects moving there, but I did not take the time to gather information about this platform.
DebXWoody
peetah: Is't Gitea hosted by a german e.V.
emus
Guys --> offtopic, didnt wanted to provoke a discussing 👨
ldkjgoiwehas left
ldkjgoiwehas joined
kikuchiyohas left
vanitasvitae
emus: by the way, "Redaktionsschluss" is "copy deadline" or "editorial deadline" ;)
emus
The German helps the German 🙂
emus
https://github.com/xsf/xmpp.org/pull/714 😉️
vaulorhas joined
vaulorhas left
vaulorhas joined
vaulorhas left
vaulorhas joined
debaclehas left
jcbrandhas joined
DebXWoodyhas left
kikuchiyohas joined
kikuchiyohas left
kikuchiyohas joined
vaulorhas left
Martinhas left
Martinhas joined
debaclehas joined
debaclehas left
debaclehas joined
kikuchiyohas left
ldkjgoiwe
Suggestion: I think the "Help us to build the newsletter" part would fit better in the end of the newsletter. It's rather long and has a rather narrow target group. With the current layout, everything I see when opening the newsletter is not actually news content. I'd also consider moving the "Subscribe to the newsletter" to the end - after the reader has seen how great the newsletter is and not before. ( cc emus )
emus
Okay, interesting point. I would be okay to change this.
Other opinions?
pep.
Yeah I think I agree with both points
pep.
I'd be interesting to know if putting "subscribe to the newsletter" at the top is actually efficient in terms of getting people to subscribe, and also in terms of getting people to read the article (not close it because "pff I don't want to subscribe" or similar)
emus
ldkjgoiwe: Lets see if most agrees or have other suggestion - then - if you want create a PR and suggest the actual changes. Would that be possible for you?✎
emus
ldkjgoiwe: Lets see if most agrees or have other suggestions - then - if you want create a PR and suggest the actual changes. Would that be possible for you? ✏
emus
ldkjgoiwe: Lets see if most agrees or have other suggestions - then you can create a PR if you want and suggest the actual changes. Would that be possible for you? ✏
emus
pep.: I think that does not really happen. people have educated good filters for stuff they dont care about in the internet
emus
But I think its okay to first give peopl what they wanna read
wurstsalat
emus: I'd put the 'help us' part at the end as well. don't know about the subscribe part
emus
ok, I think both is fine. most have subscribed anyway and if they want to they likely will fine it there aswell. so we dont both readers with stuff they know
pep.
Tbh I'm not subscribed to it as I'll see it anyway either here or on mastodon or.. I wonder what is the target of the newsletter really, and who actually subscribes :p
pep.
Talking of Mastodon, did Nyco share credentials with anybody else in commteam?