I have a new project cooking. Free software, AGPL3+, Python3. What can I do to make it more accessible to would-be contributors?

Follow-up question: when should I got public with the new project? When I have an empty git repo? Or when I have a first alpha version that does anything useful at all?

@liw I would start with a public repository right from day one. But I would recommend not to "advertise" it before you have at least some code. Doesn't need to be in alpha state already. But if you advertise it and people get interested they should be able to find something so that they can have a look at it, try it and start contributing.


Having an alpha version will provide a project core to which contributors may feel inclined to add.

At a minimum, there should be a solid description of the project's purpose, perhaps with a fundamental feature list and possible timeline.

Sign in to participate in the conversation
Mastodon @ SUNET

mastodon.acc.sunet.se is run by the Academic Computer Club at Umeå University located in Umeå, Sweden. ACC is actively involved in several open source projects and we provide mirrors for Debian, Ubuntu, Gnome and GIMP. We also host servers for the Gimpnet, Freenode, and OFTC IRC networks. You can read more about our projects and our servers on the ACC website.

Registration is open to the public, but we ask you read over and comply with our terms of use.