The to-do app to organize your life. Public API Roadmap here: https://my.vikunja.cloud/share/QFyzYEmEYfSyQfTOmIRSwLUpkFjboaBqQCnaPmWd/auth?view=kanban
Go to file
konrad b912ff4176
the build was successful Details
updated drone config
2018-09-22 23:52:19 +02:00
REST-Tests
docker/etc/services.d
docs
models fmt 2018-09-22 11:06:39 +02:00
public/swagger updated swagger docs 2018-09-20 22:06:19 +02:00
routes
vendor
.drone.yml updated drone config 2018-09-22 23:52:19 +02:00
.gitignore
Dockerfile
Featurecreep.md fixed a bug where xorm treid to insert something with an id wich already exist 2018-09-21 08:41:28 +02:00
Gopkg.lock
Gopkg.toml
LICENSE
Makefile
README.md updated readme 2018-09-20 21:59:43 +02:00
config.yml.sample
main.go

README.md

Vikunja API

The Todo-app to organize your life.

Build Status License: LGPL v3 Download Docker Pulls Swagger Docs

Features

  • Create TODO lists with tasks
    • Reminder for tasks
  • Namespaces: A "group" which bundels multiple lists
  • Share lists and namespaces with teams and users with granular permissions

Try it under try.vikunja.io!

Roadmap

  • Labels for todo lists and tasks

  • Prioritize tasks

  • More sharing features

    • Share with individual users
    • Share via a world-readable link with or without password, like Nextcloud
  • Mobile apps (seperate repo)

  • Webapp (seperate repo)

  • "Native" clients (will probably be something with electron)

Development

To contribute to Vikunja, fork the project and work on the master branch.

Some internal packages are referenced using their respective package URL. This can become problematic. To “trick” the Go tool into thinking this is a clone from the official repository, download the source code into $GOPATH/code.vikunja.io/api. Fork the Vikunja repository, it should then be possible to switch the source directory on the command line.

cd $GOPATH/src/code.vikunja.io/api

To be able to create pull requests, the forked repository should be added as a remote to the Vikunja sources, otherwise changes cant be pushed.

git remote rename origin upstream
git remote add origin git@git.kolaente.de:<USERNAME>/vikunja.git
git fetch --all --prune

This should provide a working development environment for Vikunja. Take a look at the Makefile to get an overview about the available tasks. The most common tasks should be make test which will start our test environment and make build which will build a vikunja binary into the working directory. Writing test cases is not mandatory to contribute, but it is highly encouraged and helps developers sleep at night.

Thats it! You are ready to hack on Vikunja. Test changes, push them to the repository, and open a pull request.