I made an Intro to Koji video. It answers the following questions:
- What is Koji, and how does it work?
- What is the history of Koji in Fedora?
- What are the unique design features of Koji?
I've created repo  for restructuralization of documentation. Original
flat howto structure is confusing these days as there are a lot of
documents in one heap.
I'm going to split them into four basic
Operations/Administration/User/Developer guides. In the process of moving
documents I'm also trying to "beautify" documents (some syntax
highlighting, etc.) and updating obsolete parts. Also creating some new
pages there. If you're interested in it, please check the (still a bit
unstable) structure and let me know what you think, what should be
P.S. I've created a separate repo for that as it will involve a lot of
random commits. In the moment when it will be finished I'm planning to
merge it back to the koji repo.
P.P.S. I've also to deal with a problem that links to original
documentation will not work. I've to somehow create a redirection structure
or find some other solution, so I'll not break existing links to our docs.
If you've some ideas on how to make it painless, ping me :-)
Tomas Kopecek <tkopecek(a)redhat.com>
RHEL Build Development, RedHat
Hi. My name is Cappy Ishihara, and I work on a downstream remix of Fedora called Ultramarine.
I'm here to talk about my woes with setting up and maintaining Koji as a small developer (and how I literally managed to write up another build system to address said issue).
To be short, Koji in it's current state is a mess. The Koji Hub code is a ~60k line block of monolithic code. Koji Web relies on legacy web technologies like cHTML.
- Setting up Koji itself is a massive pain and I think there should be an easier method to set it up. We should bring back password authentication and instead hash and salt our passwords for security. Authentication should be done instead using tokens like Copr.
- The documentation is very confusing, it took me weeks to get my Koji instance up and running.
I want Koji to be simple to set up and get running and the web UI to be modernized, especially for dist repos.
Here's my prototype/proof of concept of how I think Koji should be: https://gitlab.ultramarine-linux.org/lapis/lapis-backend
I'm getting distracted at the moment so I'll end it here for now, thank you.
Can we document that Koji has completely dropped el6 support in the
I was cleaning up some things in devtools/containers and I want to
delete Dockerfile.centos6 since it's currently broken.