Warning, /maui/mauiman/README.md is written in an unsupported language. File is not indexed.
0001 # MauiMan 0002 0003 Maui Manager Library. Server and Library 0004 0005 ## Getting started 0006 0007 To make it easy for you to get started with GitLab, here's a list of recommended next steps. 0008 0009 Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)! 0010 0011 ## Add your files 0012 0013 - [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files 0014 - [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command: 0015 0016 ``` 0017 cd existing_repo 0018 git remote add origin https://invent.kde.org/camiloh/mauiman.git 0019 git branch -M master 0020 git push -uf origin master 0021 ``` 0022 0023 ## Integrate with your tools 0024 0025 - [ ] [Set up project integrations](https://invent.kde.org/camiloh/mauiman/-/settings/integrations) 0026 0027 ## Collaborate with your team 0028 0029 - [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/) 0030 - [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html) 0031 - [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically) 0032 - [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/) 0033 - [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html) 0034 0035 ## Test and Deploy 0036 0037 Use the built-in continuous integration in GitLab. 0038 0039 - [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html) 0040 - [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/) 0041 - [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html) 0042 - [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/) 0043 - [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html) 0044 0045 *** 0046 0047 # Editing this README 0048 0049 When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template. 0050 0051 ## Suggestions for a good README 0052 Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information. 0053 0054 ## Name 0055 Choose a self-explaining name for your project. 0056 0057 ## Description 0058 Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors. 0059 0060 ## Badges 0061 On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge. 0062 0063 ## Visuals 0064 Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method. 0065 0066 ## Installation 0067 Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection. 0068 0069 ## Usage 0070 Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README. 0071 0072 ## Support 0073 Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc. 0074 0075 ## Roadmap 0076 If you have ideas for releases in the future, it is a good idea to list them in the README. 0077 0078 ## Contributing 0079 State if you are open to contributions and what your requirements are for accepting them. 0080 0081 For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self. 0082 0083 You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser. 0084 0085 ## Authors and acknowledgment 0086 Show your appreciation to those who have contributed to the project. 0087 0088 ## License 0089 For open source projects, say how it is licensed. 0090 0091 ## Project status 0092 If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.