Join the conversation

Sign in to join this conversation, and others like it, in the communities you care about.

Wekan

Wekan is an open-source kanban board (Trello like) which allows a card-based task and to-do management.

Wekan / General

User Documentation

User Documentation

Wekan / General · January 6, 2021 at 1:17pm (Edited 3 years ago)

[Previous title: Give Permissions to Change a Board / Make Users "Owners"?]

Hi everyone, I'm terribly sorry if this question is asked elsewhere, but I couldn't find anything in the FAQ nor the docs.

Is there a possibility to give members of a board more permissions/to make them board owners, so they can also add columns/lists, if they want to?

The context is that we are a small team with several boards, and it would be nice to allow the team more freedom in how to structure their boards.

In our installation (Wekan 4.70.0) not even an admin can change the boards that were not created by her/himself.

I hope my question is clear enough, if not, don't hesitate to ask for more details.

Best, Clemens

Load previous messages

January 9, 2021 at 11:09pm

@kuchengrab I moved Wekan wiki docs to https://github.com/wekan/wekan-doc/wiki and invited you to directly edit that wiki

    • reply
    • like

    You can directly edit with webbrowser

      • reply
      • like

      You can also clone it with: git clone [email protected]:wekan/wekan-doc.wiki.git

        • reply
        • like

        git add --all && git commit -m "Updated something" && git push

          • reply
          • like

          January 10, 2021 at 2:31pm

          thanks @xet7 for adding me. I added my page both in the wiki and in the docs. unfortunately many of the links on the website linking to the old wiki location are now broken, though. The main task would be to do some bookbinding: to compile all the existing docs and make them accessible in one place. It's a nice task for non-programmer contributors – something that could be mentioned in "how to get involved". The aim would be to centralise the available information.

          Problem

          Right now, there are several places with partly redundant information:

          and then there is

          Goal

          Ideally, all of these different spots (maybe there are even more?) should boil down to maybe three locations where wekan users, people interested in hosting a wekan instance, commercial support seekers, future contributors as well as experienced developers can find the information they are looking for. that would mean that all users (of different target groups) would find a central page with all important links in order to eliminate ambiguity. Questions like "*Shall I post my bug report in vanila or on github? is the wiki the official documentation or wekan-doc? What do I have to read before posting?" should not arise for users.

            Edited
            • reply
            • like

            How to get there

            I would propose:

            • do some bookbinding of all the existing md-docs in wiki into the wekan-doc
            • make wekan.team a sub-webpage of the main website
            • archive incomplete projects like wekanhow
            • separate use of different forums (e.g. vanila not for bugs/features) -- make it clear, where the Wekan community "lives", and where it communicates to the outside
              • reply
              • like

              (Unfortunately I don't have the time to do what I propsed, myself. And I know, @xet7 you want to dedicate your time to software development, commercial support and bugfixing. So maybe this could be done either by someone enthusiastic in the community ... or by a person who gets paid for it. I'm sure it would pay off, as the core team will have less support issues and FAQs to deal with every day!)

                • reply
                • like

                if you want, I can open an issue in github, so possibly more people can see this post, discuss it or, even better, DO. 🙂

                  • reply
                  • like

                  Well, then I'll just move wiki back to original location

                    • reply
                    • like

                    I already removed from Wekan website link to this community

                      • reply
                      • like

                      I can not afford to pay anyone else for combining docs info

                        • reply
                        • like

                        It's not that important

                          • reply
                          • like

                          Question is, is having Wekan Open Source and free for commercial use enough for someone to spend their time contributing to Wekan docs etc

                            • reply
                            • like

                            January 10, 2021 at 10:08pm

                            Well, I added back to Wekan website link to this community

                              • reply
                              • like

                              And already moved wiki back to original location

                                • reply
                                • like

                                January 10, 2021 at 11:16pm

                                I can not afford to pay anyone else for combining docs info

                                  yeah, I understand. but maybe someone from the community can take on that task one day. :)

                                    • reply
                                    • like

                                    It's not that important

                                      good docs are quite important I think. but of course it takes time and effort, so I absolutely understand your prioritization. it was not meant as criticism. the work you do on this tool is amazing – thank you!

                                        • reply
                                        • like

                                        January 11, 2021 at 4:31am

                                        Thanks @kuchengrab :)

                                          • reply
                                          • like

                                          I have also rejected some website changes before https://github.com/wekan/wekan.github.io/issues/15#issuecomment-654428942

                                            • reply
                                            • like

                                            Wekan is not some big faceless corporation website

                                              • reply
                                              • like

                                              Actually, there has been problems with https://sandstorm.io website that it looks to pro and corporate, when it's actually a community effort

                                                • reply
                                                • like

                                                to => too

                                                  • reply
                                                  • like

                                                  January 12, 2021 at 12:00pm

                                                  Hmm, I see your point. Of course it should not look like advertising or a corporation with dozens of employees. It's a fine line ... but I do like the sandstorm page, it's very clear communication in my opinion. I guess it's also a matter of where you're coming from. If you have some design background, you want everything to be more designed. If you are a hacker, you want every tool to be operable via CLI. It's quite subjective.

                                                    • reply
                                                    • like

                                                    January 12, 2021 at 7:43pm

                                                    More designed is better, if it's an improvement in some way. And still different not exactly same as in some other website.

                                                      like-fill
                                                      1
                                                      • reply
                                                      • like

                                                      Changing URLs to break links is not an improvement

                                                        • reply
                                                        • like