XSF Communications Team - 2020-07-06

emus: I tried, but uploading files requires push access to the repository

maybe we can start a link collection for potential images, and then someone with access pushes them?

👋

yeah, should be fine. Maybe at the end of the month we drop some links in the PR

what should be fine ?

Should be fine to do so

> maybe we can start a link collection for potential images, and then someone with access pushes them?

ok

so, for now, nobody has the possibility to upload images ?

:-D

are there still images needed for the current issue?

emus?

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 ✏

emus, as an XSF member, could you join him to ask for permission to reuse the gif linked in the july newsletter ?

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)

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

peetah: I have the permission I think

SouL: okay, but I think there is no one in general

great

peetah: I think there is a right to quote someones publications?

anyway I can contact them

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

so I guess it would be better to ask for it, if not for legal reason, at least for courtesy

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

or we just drop our own screenshot... I mean that is allowed, right?

sure :)

maybe that is the easiest way^^

then I'll do it

but it will have to be uploaded on the repo

permission to reuse profanity screenshot granted

emus: sorry, when I said I would do it, for whatever reason, I had profanity screenshot in mind

the only image permission missing is now from wolfieanmmol gsoc-blog which I won't be able to reproduce

Will ask them

thanks

I contacted him ✏

Apart fromt the picture thing - any last points?

can't think of anything else

Hmm, formating is weird. It shows each picture twice

things like this: <img src="https://github.com/xsf/xmpp.org/blob/master/content/images/blog/profanity090.png" width="500">

are rendered twice

waite

wait

ahh, omg the preview also renders the diff!

that really weird

are you inserting the html directly inside the markdown ? ✏

ok lets see - the html think usually works in markdown. I need to resize the picture

Muy bien: https://github.com/xsf/xmpp.org/pull/714/files?short_path=83d5783#diff-83d5783deabe9450b0964958b7ab9da3

so I will release now

you should not, because pelican won't understand

Ah wait

no tomorrow

But I will close now

Are you sure?

wait, then I have to resize the picutre manually

you should use the markdown formating with:  ✏

pelican will look for the /images path according to its configuration and generate the appropriate html ✏

and from the current pelican conf, /images is the /content/images path in the repo

there is one blog post that did exactly that... give me a sec to find it

https://github.com/xsf/xmpp.org/blob/master/content/posts/blog/Return_of_experience_on_XMPP_meetup_in_Krakow.md

an we should not put the newsletter related images into the blog directory

we should create a /content/images/newsletters/<monthYYYY> directory and store them there

Okay wait

 but they dont use the ending nameing

pep. are you here?

can you create a folder in here?

https://github.com/xsf/xmpp.org/tree/master/content

sorr in here: https://github.com/xsf/xmpp.org/tree/master/content/images

"newsletter" ?

the text between double-quotes inside the parenthesis is the one used as the image title when you hover it

ok

!

of course, the images won't be displayed in the github preview

emus, you can't "create a folder" in git

it doesn't make sense

Okay, but how did they do 😀

git does not understand the "folder" concept

you have to create a file into that folder

ah okay

so that is that I do in the "name file" field on the top?

hmmm, maybe you can enter slashes in there :/

yeah

Yes ok

but I dont need to add a file in that step, right?

I just "commit" the new file (/../...)

what do you want to do? Add an image somewhere?

in that location afterwards. but now it just has the editor look

I have no idea how to do that via github's interface

ok

I just try

if i remember correctly, there is a "upload file" button

add files > upload file ✏

add files > upload files ✏

Yes, but there I cannot create an location 😕

Have somebody else upload the first image? and upload the rest

yes was wondering

I would go in the /content/images/ folder, then clich on upload files and proceed from there ✏

I guess it will ask for a file from your computer and a target folder

emus, wasn't there a desktop client for github? Maybe it's easier to use

but I can't say for sure since I just have a "File uploads require push access to this repository." message

can't you just clone the repo and commit the file from there

then push

?

Ok, now I know how it works

give me another 5 minutes

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

in the future

great ! thanks !

Okay guys, we are close! Just the new linking missing ... 🏃‍♂️️




Si?

I guess so

I'm looking for a way to limit image size via pelican conf

ok, hmm Github is not rendering - are you sure I cannot use the full link?

Shouldnt be a problem or?

if you want pelican to do its job, then I think it has to be this way

Okay, then I ignore it and leave it like this

======= Redaction Closing for June 2020 XMPP Newsletter======

🤸‍♂️️

emus, I guess you have to remove the leading "/" from the image link

okay, but also for pelican?

I focus on what pelican wants to see

no you have to keep the leading /

ok

this is how the blog post linked above did, and it is perfectly rendered on the web site

okay, havent used pelican

just for markdown you'd have to remove the slash.

if "images" folder was in the same folder as the md, which is not the case ✏

we will see tomorrow

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 ?

I have absolutely no clue about the possible consequences

fuck, I knew I did something wrong

how was that possible 🙈️

not wrong, open to improvements :)

but wait - in the master branch everything is fine?

it is

fwiw, if the image is meant to stay it might be best just to leave it there

Oh boy, dat commit history 😛

since it's a big binary file, otherwise you're gonna have git storing big diffs

I would have used "newsletters" rather than "newsletter" though

renaming should be fine

I think

vanitasvitae: 🙄 I know I know

I used newsletter because thats the general top term. details will come if you click it

vanitasvitae: If you are well experience you can sqatsch the commits but I rather leave my hands of foe today 🤐 ✏

vanitasvitae: If you are well experienced you can sqatsch the commits but I rather leave my hands of foe today 🤐 ✏

squashing on master is a bad idea

guess for that it's too late.

In general, you should work in feature branches and merge those into master once you are ready.

It may be a good idea to make the master branch protected, so that nobody can directly push to it

can't we just reset master to the latest good commit ?

vanitasvitae: Yeah, I wonder actually why that is not the case

peetah, sure, but maybe someone/something already pulled and will then have to deal with merge conflicts and stuff

but on the other side we need someone to continuiously manage this

protecting the branch is a good thing imho

that way you can only contribute to it via merge requests

yeah

yeah maybe ask iteam. It's also good to do that just to avoid common mistakes

yup

Now I ruined it for everyone 😄

haha

No fun anymore guys ¯\_(ツ)_/¯

quick! hide it under a ton of good commits!!!

:D

Haha - actually I wonder how I commited to the wrong branch. it is hard in the Github interface 🤔

😀

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 🙂

thanks emus for your work on this new newsletter

Sure - now we all dance XMPP like YMCA:

🙅‍♂️️🙆‍♂️️🤦‍♂️️🤦‍♂️️

😄️

uhh, you have icon duplication? I do in Conversations

Dino is doing weird things maybe?

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] = 🙅‍♂️️️

ahaa it's not getting better when trying to send these things from dino 😀

where is my unicode codepoint input field 😀

emus, file a bug with Conversations, something is very weird with Conversations here...

https://logs.xmpp.org/commteam/2020-07-06#2020-07-06-87caed30d601b091

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.

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)

Yeah I had to open Conversations because I wouldn't see it properly in poezio, but I'm used to that anyway :p

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

question?

What is the question?

DebXWoody: jonas was evaluating if Gitlab is interesting for XSF

Ah,... +1, this would be nice. I would also start to help on some topics for XSF.

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.

administrate the beast?

peetah, it's not gitlab but gitlab.com

So same as github.com

"same", admin-wise

I mean , being independent vs depending on a microsoft owned closed source forge => no brainer

ahhhh I thought we were talking about an independant instance of gitlab

I think is not requiered to have an own server. gitlab.com would be fine.

DebXWoody, well.. moving from github.com to gitlab.com because you want to stop depending on Microsoft is somewhat missing the point :p

not for me: I've been there and fled when they changed their ToS to include sharing data with third parties

There are other reasons to do this move, but this is not really one IMO

pep.: It's not only Microsoft. GoogleAPI, closed software, etc. I prefer codeberg.org, but gitlab has more features and is also quite nice.

what is codeberg ? I see several projects moving there, but I did not take the time to gather information about this platform.

peetah: Is't Gitea hosted by a german e.V.

Guys --> offtopic, didnt wanted to provoke a discussing 👨

emus: by the way, "Redaktionsschluss" is "copy deadline" or "editorial deadline" ;)

The German helps the German 🙂

https://github.com/xsf/xmpp.org/pull/714 😉️

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 )

Okay, interesting point. I would be okay to change this. Other opinions?

Yeah I think I agree with both points

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)

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? ✏

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? ✏

pep.: I think that does not really happen. people have educated good filters for stuff they dont care about in the internet

But I think its okay to first give peopl what they wanna read

emus: I'd put the 'help us' part at the end as well. don't know about the subscribe part

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

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

Talking of Mastodon, did Nyco share credentials with anybody else in commteam?

Nÿco, ^

It's very inactive at the moment

Nope

Is it possible?

pep.: there are people subscribed