peetahemus: I tried, but uploading files requires push access to the repository
wurstsalatmaybe we can start a link collection for potential images, and then someone with access pushes them?
arnaudjhas left
arnaudjhas joined
emus๐
emusyeah, 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
peetahwhat should be fine ?
emusShould be fine to do so
emus> maybe we can start a link collection for potential images, and then someone with access pushes them?
peetahok
peetahso, for now, nobody has the possibility to upload images ?
DebXWoody:-D
arnaudjhas left
arnaudjhas joined
debaclehas left
wurstsalatare there still images needed for the current issue?
wurstsalatemus?
peetahJSCX 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
peetahemus, as an XSF member, could you join him to ask for permission to reuse the gif linked in the july newsletter ?
wurstsalatfor 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)
SouLemus, 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
emuspeetah: I have the permission I think
emusSouL: okay, but I think there is no one in general
peetahgreat
Nรฟcohas left
emuspeetah: I think there is a right to quote someones publications?
emusanyway I can contact them
arnaudjhas left
peetahreusing 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
peetahso 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
emusIf 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
emusor we just drop our own screenshot... I mean that is allowed, right?
peetahsure :)
emusmaybe that is the easiest way^^
peetahthen I'll do it
peetahbut it will have to be uploaded on the repo
DebXWoodyhas left
DebXWoodyhas joined
arnaudjhas left
arnaudjhas joined
peetahpermission to reuse profanity screenshot granted
peetahemus: sorry, when I said I would do it, for whatever reason, I had profanity screenshot in mind
peetahthe only image permission missing is now from wolfieanmmol gsoc-blog which I won't be able to reproduce
emusWill ask them
peetahthanks
emusI cobtected him
emusI contacted him
Nรฟcohas left
alacerhas left
alacerhas joined
Nรฟcohas joined
Alexhas left
Alexhas joined
jcbrandhas left
jcbrandhas joined
Nรฟcohas left
Nรฟcohas joined
arnaudjhas left
arnaudjhas joined
arnaudjhas left
arnaudjhas joined
debaclehas joined
arnaudjhas left
arnaudjhas joined
DebXWoodyhas left
DebXWoodyhas joined
arnaudjhas left
arnaudjhas joined
DebXWoodyhas left
DebXWoodyhas joined
kikuchiyohas left
Vaulorhas left
Vaulorhas joined
kikuchiyohas joined
kikuchiyohas left
DebXWoodyhas left
DebXWoodyhas joined
DebXWoodyhas left
DebXWoodyhas joined
Alexhas left
Alexhas joined
DebXWoodyhas left
DebXWoodyhas joined
DebXWoodyhas left
DebXWoodyhas joined
kikuchiyohas joined
DebXWoodyhas left
DebXWoodyhas joined
jcbrandhas left
kikuchiyohas left
jcbrandhas joined
kikuchiyohas joined
kikuchiyohas left
arnaudjhas left
arnaudjhas joined
kikuchiyohas joined
alacerhas left
alacerhas joined
emusApart fromt the picture thing - any last points?
peetahcan't think of anything else
arnaudjhas left
arnaudjhas joined
Wojtekhas joined
kikuchiyohas left
emusHmm, formating is weird. It shows each picture twice
emusthings like this: <img src="https://github.com/xsf/xmpp.org/blob/master/content/images/blog/profanity090.png" width="500">
emusare rendered twice
emuswaite
emuswait
emusahh, omg the preview also renders the diff!
emusthat really weird
peetahare you inserting the html directy inside the markdown ?
peetahare you inserting the html directly inside the markdown ?
emusok lets see - the html think usually works in markdown. I need to resize the picture
emussorr in here: https://github.com/xsf/xmpp.org/tree/master/content/images
emus"newsletter" ?
peetahthe text between double-quotes inside the parenthesis is the one used as the image title when you hover it
emusok
pep.!
peetahof course, the images won't be displayed in the github preview
pep.emus, you can't "create a folder" in git
pep.it doesn't make sense
emusOkay, but how did they do ๐
peetahgit does not understand the "folder" concept
peetahyou have to create a file into that folder
emusah okay
emusso that is that I do in the "name file" field on the top?
pep.hmmm, maybe you can enter slashes in there :/
pep.yeah
emusYes ok
emusbut I dont need to add a file in that step, right?
emusI just "commit" the new file (/../...)
pep.what do you want to do? Add an image somewhere?
emusin that location afterwards. but now it just has the editor look
pep.I have no idea how to do that via github's interface
emusok
emusI just try
peetahif i remember correctly, there is a "upload file" button
peetahadd files > upload fil
peetahadd files > upload file
peetahadd files > upload files
emusYes, but there I cannot create an location ๐
alacerhas left
alacerhas joined
pep.Have somebody else upload the first image? and upload the rest
emusyes was wondering
peetahI would go in the /content/images/ folder, then clich on upload files and proceed from ther
peetahI would go in the /content/images/ folder, then clich on upload files and proceed from there
peetahI 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
peetahbut I can't say for sure since I just have a "File uploads require push access to this repository." message
peetahcan't you just clone the repo and commit the file from there
peetahthen push
peetah?
emusOk, now I know how it works
emusgive me another 5 minutes
emuseverything 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
emusin the future
peetahgreat ! thanks !
emusOkay guys, we are close! Just the new linking missing ... ๐โโ๏ธ๏ธ
emus
emusSi?
peetahI guess so
peetahI'm looking for a way to limit image size via pelican conf
emusok, hmm Github is not rendering - are you sure I cannot use the full link?
emusShouldnt be a problem or?
peetahif you want pelican to do its job, then I think it has to be this way
emusOkay, then I ignore it and leave it like this
emus======= Redaction Closing for June 2020 XMPP Newsletter======
emus๐คธโโ๏ธ๏ธ
vanitasvitaeemus, I guess you have to remove the leading "/" from the image link
emusokay, but also for pelican?
emusI focus on what pelican wants to see
peetahno you have to keep the leading /
emusok
peetahthis is how the blog post linked above did, and it is perfectly rendered on the web site
vanitasvitaeokay, havent used pelican
vanitasvitaejust for markdown you'd have to remove the slash.
peetahif images was in the same folder as the md, which is not the case
peetahif "images" folder was in the same folder as the md, which is not the case
emuswe will see tomorrow
peetahemus: you created the folder in "master" : should'nt have been created in newsletter-july2020 branch and then merged with the rest of your PR ?
peetahI have absolutely no clue about the possible consequences
emusfuck, I knew I did something wrong
emushow was that possible ๐๏ธ
peetahnot wrong, open to improvements :)
emusbut wait - in the master branch everything is fine?
peetahit is
pep.fwiw, if the image is meant to stay it might be best just to leave it there
vanitasvitaeOh boy, dat commit history ๐
pep.since it's a big binary file, otherwise you're gonna have git storing big diffs
peetahI would have used "newsletters" rather than "newsletter" though
pep.renaming should be fine
pep.I think
emusvanitasvitae: ๐ I know I know
emusI used newsletter because thats the general top term. details will come if you click it
emusvanitasvitae: If you have well experience you can sqatsch the commits but I rather leave my hands of foe today ๐ค
emusvanitasvitae: If you are well experience you can sqatsch the commits but I rather leave my hands of foe today ๐ค
emusvanitasvitae: If you are well experienced you can sqatsch the commits but I rather leave my hands of foe today ๐ค
vanitasvitaesquashing on master is a bad idea
vanitasvitaeguess for that it's too late.
vanitasvitaeIn general, you should work in feature branches and merge those into master once you are ready.
vanitasvitaeIt may be a good idea to make the master branch protected, so that nobody can directly push to it
peetahcan't we just reset master to the latest good commit ?
emusvanitasvitae: Yeah, I wonder actually why that is not the case
vanitasvitaepeetah, sure, but maybe someone/something already pulled and will then have to deal with merge conflicts and stuff
emusbut on the other side we need someone to continuiously manage this
vanitasvitaeprotecting the branch is a good thing imho
vanitasvitaethat way you can only contribute to it via merge requests
emusyeah
pep.yeah maybe ask iteam. It's also good to do that just to avoid common mistakes
vanitasvitaeyup
emusNow I ruined it for everyone ๐
pep.haha
emusNo fun anymore guys ยฏ\_(ใ)_/ยฏ
vanitasvitaequick! hide it under a ton of good commits!!!
peetah:D
emusHaha - actually I wonder how I commited to the wrong branch. it is hard in the Github interface ๐ค
vanitasvitae๐
emusEnough 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 ๐
peetahthanks emus for your work on this new newsletter
DebXWoodyHi. 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
emusla|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
emusDebXWoody: 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
DebXWoodyquestion?
DebXWoodyWhat is the question?
emusDebXWoody: jonas was evaluating if Gitlab is interesting for XSF
DebXWoodyAh,... +1, this would be nice. I would also start to help on some topics for XSF.
peetahI'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.
DebXWoodyadministrate the beast?
pep.peetah, it's not gitlab but gitlab.com
pep.So same as github.com
pep."same", admin-wise
peetahI mean , being independent vs depending on a microsoft owned closed source forge => no brainer
peetahahhhh I thought we were talking about an independant instance of gitlab
DebXWoodyI 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
peetahnot 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
DebXWoodypep.: It's not only Microsoft. GoogleAPI, closed software, etc. I prefer codeberg.org, but gitlab has more features and is also quite nice.
peetahwhat is codeberg ? I see several projects moving there, but I did not take the time to gather information about this platform.
DebXWoodypeetah: Is't Gitea hosted by a german e.V.
emusGuys --> offtopic, didnt wanted to provoke a discussing ๐จ
ldkjgoiwehas left
ldkjgoiwehas joined
kikuchiyohas left
vanitasvitaeemus: by the way, "Redaktionsschluss" is "copy deadline" or "editorial deadline" ;)
ldkjgoiweSuggestion: 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 )
emusOkay, 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)
emusldkjgoiwe: 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?
emusldkjgoiwe: 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?
emusldkjgoiwe: 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?
emuspep.: I think that does not really happen. people have educated good filters for stuff they dont care about in the internet
emusBut I think its okay to first give peopl what they wanna read
wurstsalatemus: I'd put the 'help us' part at the end as well. don't know about the subscribe part
emusok, 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?