This is an excellent idea. As one of those newcomers you'd like to attract,
may I suggest that the best place to start for site content would be on a
getting started guide for Koji users and for a setup/installation guide
that does a better job of simplifying/walking someone through the process
of setting up a Koji instance. When I was evaluating build system options
for the CloudRouter project, one of my colleagues suggested Koji as a good
solution. However, the combination of high complexity and lack of
consolidated setup documentation has made me decide that no matter how good
Koji is as a build system, it was not going to be worth the pain of
I am happy to put the user startup and Koji install guide docs together,
but the primary information needed to make them more comprehensive will
have to come from the members of this Koji community.
On Friday, 6 November 2015, Adam Miller <maxamillion(a)fedoraproject.org>
We had previously talked about making some changes to the koji
project as a whole and for those who might not have noticed, koji is
now hosted on pagure which opens up all kinds of opportunities for
git topic branch style workflows.
Aside from the move to pagure it was being discussed to have a Koji
project website such that it will exist as a stand alone single point
of entry for newcomers who are not familiar with the project.
I've written a proposal website skeleton with a very small amount of
content written in reStructured Text and rendered using Nikola
static site generator. This proposal has been submitted as a pull
request to the koji code base.
Now, we would need to expand the content substantially and decide on a
domain name for the project site to live. I was initially thinking of
just because it came to mind but I'm very open to
Another thing I worked on is converting all relevant documentation I
could find in the Fedora Wiki as well as pre-existing in the koji git
repository to reStructured Text to be rendered with sphinx-doc.
This has also been submitted as a pull request to the koji code
The main motivation behind this is to make koji more inviting to new
users and developers who share a common interest in build systems and
to hopefully foster a growing community of users and developers around
With these changes my hope is that the koji project will have a single
unified "landing space" on the internet where we can easily direct new
community members. As it stands today, koji content is a bit spread
across many different areas which isn't necessarily problematic so
long as we index or present it properly, but this series of changes
takes it a step further and brings all the content (in source
"unrendered" format anyways) under the umbrella of the koji git
repository so everything truly lives in one place.
I look forward to your feedback.
 - https://pagure.io/koji
 - https://getnikola.com/
 - https://pagure.io/koji/pull-request/3
 - http://sphinx-doc.org/
 - https://pagure.io/koji/pull-request/2
koji-devel mailing list