Home

Welcome to the Codidact wiki!

This project was created to coordinate and keep track of current efforts by a group of (mostly unsatisfied) users of Stack Overflow and the Stack Exchange Network to develop an alternative to these platforms.

The group first gathered on 2019-10-16 over an off-site online chat system. Our preliminary focus is to come up with a plan on how this idea can be achieved best, and to gather enough able hands to make it possible.

This wiki will be updated regularly as we define more aspects, technical or otherwise, that are required to succeed in this endeavor. This homepage will be consistently updated to provide accurate and up-to-date resources about the project.

This very wiki page is still a draft and is subject to change.

The Elevator Pitch

Our goal is to enable community-driven and community-governed Q&A. We want to build a place for questions, a place for answers, a place for community.

To do this, we'll build an open-source platform for Q&A sites and host an instance of it for interested communities. We'll fund the effort by seeking donations, not by paywalls, and work with individual communities that want to join us on customizations to fit their needs.

Requirements, under development.

Getting Involved

The best way to get involved with this project is to jump into the forum. Of particular note is the MVP tag. Help us prioritize and refine feature ideas! All are welcome.

Work on Codidact is distributed thusly:

• the forum, for working out ideas, talking about use cases, building consensus, etc

• GitHub, for actual development

• Discord, for casual chat -- we're trying to move artifacts out of there so nobody has to dig through Discord, and are archiving some old channels there

See also: organizational structure.

Project TODO list:

• Decide on whether to use a frontend framework and if so, which one.

• Decide on site structure, i.e our own approach to a Q&A system.

• Agree on a set of architectural and code style guidelines in written form.

• Settle on a license for the software.

• Coordinate everyone's general attributions and roles, and begin development.

• Decide on the community management approach.

• Decide on which site(s) to replicate first.