Software like wakan

In the world of the Lakota, the word wakan means many things, yet nothing that is easily understood. Even among the Lakota themselves a great deal of thought and study is necessary in a quest to understand the concept of wakan. To the Lakota, those which made everything are Wakan Tanka. They are never born and they never die. The Wakanpi, spirits, have power over everything on earth and control everything mankind does.

There are benevolent Wakanpi that will bestow the wishes man asks of them, and evil Wakanpi that are to be feared. Man uses songs, ceremony and gifts to honor and appease, all under the auspices of the holy man or shaman, wicasa wakan.

Prayers offered to the wakan beings as a whole are addressed to Wakan Tanka, but prayers offered to a specific being should address the being by name. Music is a good vehicle of prayer, and it is said the Wanka Tanka always give attention when they hear the drums and rattles. While the good wakan beings are fond of prayers that reach them on the smoke of sweetgrass, the evil wakan beings fear the smoke of sage.

All the Wakan Tanka are pleased with the smoke of the Lakota pipe. This is incorrect because the Lakota call something a medicine only when it is being used to tend to the sick or injured, and so the proper term would be pejuta. A wicasa wakan is wise, one who knows and has power with the spirits and can communicate with them.

He knows the songs and the ceremonies and can interpret visions. He can tell people what the spirits expect of them, predict the future, speak to nature…to everything on earth.

So one, the pejuta wacasa, tends to the physical being, while the other, wicasa wakan, tends to the spiritual. Ton is the power to do the supernatural. Rattle, smoke, feather…once anything has tonwicasa wakan has the power of wakan beings, bestowed upon him by wakanton has been placed, called a Wasicun, from which the shaman do their work from. For that we researched and found that Keen was a good choice very good free tier limits and also it is very simple to setup and real simple to send data to.

Slack and Trello are our defaults tools to comunicate ideas and discuss topics, so, no brainer using them as well for this project. Last time we shared there information about our decision about using YouTrack over Jira actually we found much better solution that our team have loved. Linear is a minimalistic issue tracker that integrates well with Sentry , GitHub , Slack and Figma which are our basic tools.

I would like to recommend checking out Linear as a potential alternative to "heavy" issue trackers, maybe at enterprises that may not work but when we're a startup that works awesome! We were using a hosted version of Redmine to track defects and user stories originally. We migrated to Jira. I know there are alot of other tools in this space but not even considering anything else at the moment.

Love Jira! I have mixed feelings on GitHub as a product and our use of it for the Zulip open source project. On the one hand, I do feel that being on GitHub helps people discover Zulip, because we have enough stars etc.

But even ignoring how one might feel about their new corporate owner MicroSoft , in a lot of ways GitHub is a bad product for open source projects.

Years after the "Dear GitHub" letter, there are still basic gaps in its issue tracker:. It's embarrassing, because I've talked to GitHub product managers at various open source events about these things for 3 years, and they always agree the thing is important, but then nothing ever improves in the Issues product. Maybe the new management at MicroSoft will fix their product management situation, but if not, I imagine we'll eventually do the migration to GitLab. We use GitLab CI because of the great native integration as a part of the GitLab framework and the linting-capabilities it offers.

The visualization of complex pipelines and the embedding within the project overview made Gitlab CI even more convenient. We use it for all projects, all deployments and as a part of GitLab Pages. While we initially used the Shell-executor, we quickly switched to the Docker-executor and use it exclusively now. We formerly used Jenkins but preferred to handle everything within GitLab.

Aside from the unification of our infrastructure another motivation was the "configuration-in-file"-approach, that Gitlab CI offered, while Jenkins support of this concept was very limited and users had to resort to using the webinterface.

Since the file is included within the repository, it is also version controlled, which was a huge plus for us. Alternatives to Wekan. Trello, Taiga. View Jobs. Stacks Follow I use this. What is Wekan and what are its top alternatives? They give you a visual overview of the current state of your project, and make you productive by allowing you to focus on the few items that matter the most. Wekan is a tool in the Project Management category of a tech stack.

Wekan is an open source tool with Top Alternatives to Wekan Trello Trello is a collaboration tool that organizes your projects into boards. Restyaboard Trello like kanban board.

Based on Restya platform. Kanboard It is a free and open source Kanban project management software. OpenProject It is an open source software for project management with a wide set of features and plugins and an active international community. Jira Jira's secret sauce is the way it simplifies the complexities of software development into manageable units of work.

Redmine Redmine is a flexible project management web application. GitLab GitLab offers git repository management, code reviews, issue tracking, activity feeds and wikis. Shared insights.