openSUSE admin

You can also use https://github.com/openSUSE/jekyll-template/ to make it easier, though you may need to adjust the index page to display posts. I can probably help out a bit with that

Thanks a lot for the help! I will definitely take a look at the jekyll-template.

Regarding the repository, I was wondering if it would be possible to pull this in from a private repository? Reason is that we could internally review PRs to the repo before they are merged and being published without having the drafts or comments public.
If that would be a lot of work, we can probably also find another workflow with a public repo.

My colleagues suggested the repository name to be "openSUSE/security-team-blog". I just checked and we have already have a team in github, maybe you could just assign the repository to us:
https://github.com/orgs/openSUSE/teams/security

If that does not work, please just add me (github username: ca-hu) and I will add the others.

Thanks a lot!

I created https://github.com/openSUSE/security-team-blog with you as admin, and the security team as maintainers (I'm not a big fan of making everybody repo admin). Feel free to adjust as needed.

Just wondering - what's the reason why you consider to keep drafts and comments private? Just a preference ("nobody should see my typos"), or are there serious reasons like planned articles about embargoed vulnerabilities?

Our jekyll setup assumes that repos are public and can be cloned over https. Therefore I'd prefer if you keep the repo public (or tell me how we can access it over https if it's private ;-)

Speaking about jekyll - as soon as you have something in the repo, please tell me so that we can add it on our jekyll server and publish it.

Thanks a lot for creating the repo, we will let you know when we created the page, probably in the next week(s) :)
Just another question, what is the interval that the server pulls from the repo and deploys?

About the private drafts and comments: we won't have embargoed vulns on there, it is more to avoid confusion or drama (sometimes upstream projects feel they are wrongly represented by a draft report, so we try to find a solution privately before publishing).
I talked to my colleagues and the public repo that you created will be fine for the use case, we will just review the changes via other means, thanks a lot :)

Jekyll pages get updated and deployed hourly (at or a few minutes after the full hour).

I'm a bit surprised that some upstream projects don't like public PRs - maybe you should tell them that a PR is a draft? ;-) (but then, open source projects should already know this...)

Hi :)

sorry for the long delay, we pushed content to the repo now: https://github.com/openSUSE/security-team-blog
If you could deploy the page, that would be great :)

Thanks a lot!