apitech
/
wekan
mirror of https://github.com/wekan/wekan
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
The Open Source kanban (built with Meteor). Keep variable/table/field names camelCase. For translations, only add Pull Request changes to wekan/i18n/en.i18n.json , other translations are done at https://transifex.com/wekan/wekan only.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
12557 Commits
3 Branches
846 Tags
84 MiB
 
 
 
 
 
 
Tag: Branch: Tree: 088bc16072
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '088bc16072'
${ noResults }
wekan/docs/Platforms/FOSS/Sandstorm/FAQ.md

1.4 KiB
Raw Blame History

What is Wekan

Wekan FAQ

Anyone can already do this, no need to be a maintainer

  • Answer Github issues
  • Keep any Wekan wikis up-to-date

Wekan welcomes new co-maintainers

xet7 did have to bring Wekan back to life already once before. Generally in Open Source it's good to have more that one maintainer to keep project alive.

Requirements for maintainers

When you contributions on Wekan Team page starts growing, one of Wekan maintainers may ask if you'd like to become co-maintainer.

Responsibilities of maintainer

  • Check that pull requests work. Merge pull requests.
  • Make new releases for Wekan.
  • Ask other maintainers for more documentation how to maintain something.
  • Keep documentation on wikis up-to-date.

Maintainers do need to also remember

  • Do not try to rewrite whole project. That takes too much time and resources. We prefer small incremental improvements.
  • Do maintaining on your free time. There is no need to be always available. You are free to have pauses from maintaining for any length of time. Telling to other maintainers about long pauses is recommended but anyway optional.
  • Also take care of yourself and your personal life. Remember to take enough rest.