Go back

What's the bare minimum to get an open source project flying?

I've been writing on a small hobby project for the last couple of months. It's nothing big nor fancy. It was born out of the frustration about not knowing what files were on what (home)servers. I wanted a way to get a complete list of all files - along with their types, size, etc - and be able to sort and filter.

Since my job as of late has been more about management rather than coding I wanted to code the solution rather then hacking together a few scripts or similar. Since Go (golang) is my go-to-language this became the natural choice.

After hacking a night here and a night there for a few weeks I got something nice going. It worked but took ages to index a few million files. I have since rewritten most of the code a few times and as of last night I got something that works and works faster.

Along with the actual functionality (one server and one client) for indexing files and concatenating the results from different machines I also wrote a web interface (for local use) where one can list, filter and sort the indexed files. In a later version free text search will be implemented along with the ability to click a file and trigger something to maybe stream through an ssh tunnel or just downloading the file.

Since I've been an open source guy for many years I wanted to also release the project as open source. But instead of just putting the code into repositories on github I figured I might as well buy a domain and write together a website with some documentation and so forth.

This is where my question arises; What is the YAGNI-style of getting an open source project up and running? The goal would perhaps be to get other people to use it and perhaps get one or two people to contribute to it's development.

The things I see right now as YAGNI-stuff would be;

the repositories (Do'h?) a website with documentation so people can understand what it is and how to use it contact information What else would be needed? Or is it enough?