本指南介绍了如何参与 Quasar 的持续开发。

¥This guide covers ways in which you can become a part of the ongoing development of Quasar.

但是，在开始之前，首先需要注意的是：所有在 Quasar 中交互的用户都应遵循 Quasar 行为准则。

¥But, before we begin, a first important note. Everyone interacting in Quasar is expected to follow the Quasar Code of Conduct.

现在我们已经完成了所有操作，开始吧！

¥Now that we’ve got that covered, let’s go!

阅读本指南后，你将了解：

¥After reading this guide, you will know:

• 如何使用 GitHub 报告问题。

  ¥How to use GitHub to report issues.

• 如何克隆代码库并运行测试套件。

  ¥How to clone the repo and run the test suite.

• 如何帮助解决现有问题。

  ¥How to help resolve existing issues.

• 如何为 Quasar 文档做出贡献。

  ¥How to contribute to the Quasar documentation.

• 如何创建 Quasar 应用扩展。

  ¥How to create a Quasar App Extension.

• 如何为 Quasar 源代码做出贡献。

  ¥How to contribute to the Quasar source code.

Quasar 不是 “其他人的框架”。许多人为 Quasar 做出了贡献，从单个字符到大规模的架构变更或重要的文档。 - 所有这些都是为了让 Quasar 更好地服务于每个人。即使你还不想编写代码或文档，你也可以通过其他多种方式做出贡献，例如报告问题和测试补丁。

¥Quasar is not “someone else’s framework”. Many people have contributed to Quasar ranging from a single character to massive architectural changes or significant documentation - all with the goal of making Quasar better for everyone. Even if you don’t feel up to writing code or documentation yet, there are a variety of other ways that you can contribute, from reporting issues to testing patches.

支持帮助(Help with Support)

¥Help with Support

最简单的贡献方式之一是在我们不同的问答系统中回答问题。通过回答你知道答案的问题，甚至提供你最合理的猜测，成为 Quasar 社区的支持和积极成员。参与此类讨论也是一次很好的学习经历。双赢！

¥One of the easiest ways to contribute is to answer questions in the different Q&A systems we have. Be a supportive and positive member of the Quasar community by answering questions you know answers to, or even by adding your best guess. Being a part of such discussions can also be a good learning experience. It’s a win-win!

以下是我们的讨论/问答场所：

¥Here are our discussion/Q&A venues:

• GitHub 讨论区：一个可以提问并获得有关 Quasar 及其生态系统答案的地方。它也是与他人分享你的知识和经验的好地方。你还可以使用它来分享你的想法和功能请求。

  ¥GitHub Discussions: A place to ask questions and get answers about Quasar and its ecosystem. It’s also a great place to share your knowledge and experience with others. You can also use it to share your ideas and feature requests.

• Discord 服务器：Quasar 开发者实时见面和聊天的地方。你可以提出问题、分享知识并帮助他人。也可以在那里发布工作机会或寻找工作。

  ¥Discord Server: A place for Quasar devs to meet and chat in real time. You can ask questions, share your knowledge, and help others. It’s also possible to post job offers or look for a job there.

分享（和构建）你的体验(Share (and Build) Your Experience)

¥Share (and Build) Your Experience

除了在论坛和聊天中回答问题和分享资源外，还有一些不太明显的方式来分享和扩展你的知识：

¥Apart from answering questions and sharing resources in the forum and chat, there are a few other less obvious ways to share and expand what you know:

• 开发学习资料。人们常说，最好的学习方法就是教。如果你正在使用 Quasar 做一些有趣的事情，可以通过撰写博客文章、组织研讨会，甚至发布在社交媒体上分享的要点来增强你的专业知识。

  ¥Develop learning materials. It’s often said that the best way to learn is to teach. If there’s something interesting you’re doing with Quasar, strengthen your expertise by writing a blog post, developing a workshop, or even publishing a gist that you share on social media.

• 分享你的技术栈。向其他人展示哪些技术经过充分测试，可以与 Quasar 集成。推广你的项目和 填写你最喜欢的基于 Quasar 的技术栈。请确保提及 @Quasarframework 和所有其他相关技术。

  ¥Share your tech stack. Show others which technologies are well tested and can be integrated with Quasar. Promote your project and fill out your favorite Quasar-based stack. Make sure to mention @Quasarframework and all other relevant technologies.

• 关注你关注的 repo。每当该存储库中有活动时，它都会向你发送通知，让你了解正在进行的讨论和即将推出的功能。这是一个积累专业知识的绝佳方式，最终你将能够帮助解决问题和提交拉取请求。

  ¥Watch a repo you care about. This will send you notifications whenever there’s activity in that repository, giving you insider knowledge about ongoing discussions and upcoming features. It’s a fantastic way to build expertise so that you’re eventually able to help address issues and pull requests.

报告问题(Reporting an Issue)

¥Reporting an Issue

• GitHub：如果你想创建错误报告或文档报告，请参阅 GitHub Issues。请确保你选择了正确的模板并在创建问题时遵循给出的说明。

  ¥GitHub: If you want to create a bug report or a docs report, that’s what the GitHub issues are for. Make sure that you select the correct template and follow the given instructions while creating an issue.

如果你在 Quasar 中发现一个不构成安全风险的问题，请在 GitHub 上搜索 问题，检查该问题是否已在开发分支 (dev) 中得到解答或修复。

¥If you’ve found a problem in Quasar which is not a security risk, do a search on GitHub under Issues to check if it is already answered or even fixed in the development branch (dev).

• 主仓库 的问题列表仅用于错误报告和文档报告。不符合要求的问题将立即关闭。

  ¥The issue list of the main repo is exclusively for bug reports and docs reports. Non-conforming issues will be closed immediately.

  • 对于简单的初学者问题，你可以从 Quasar Discord 聊天 获得快速解答。

    ¥For simple beginner questions, you can get quick answers from the Quasar Discord chat.

  • 对于更复杂的问题，你可以使用 讨论区。提问时请务必提供足够的信息。 - 这方便其他人帮助你！

    ¥For more complicated questions, you can use the Discussions section. Make sure to provide enough information when asking your questions - this makes it easier for others to help you!

  • 对于功能请求，你可以使用 发起新功能讨论。

    ¥For feature requests, you can start a new feature discussion.

• 尝试搜索你的问题，它可能已经在开发分支 (dev) 中得到解答，甚至已修复。

  ¥Try to search for your issue, it may have already been answered or even fixed in the development branch (dev).

• 检查该问题是否可以在最新稳定版本的 Quasar 中重现。请始终指明你正在使用的具体版本。

  ¥Check if the issue is reproducible with the latest stable version of Quasar. Please always indicate the specific version you are using.

• 你需要清晰地描述重现所遇到问题所需的步骤。虽然我们希望尽可能地帮助用户，但在没有清晰复现步骤的情况下诊断问题非常耗时，而且不可持续。

  ¥It is required that you clearly describe the steps necessary to reproduce the issue you are running into. Although we would love to help our users as much as possible, diagnosing issues without clear reproduction steps is extremely time-consuming and simply not sustainable.

• 仅使用重现意外行为所需的最少代码。一份好的错误报告应该隔离表现出意外行为的特定方法，并准确定义如何违反了预期。你期望该方法执行什么操作？观察到的行为有何不同？你越精确地隔离问题，我们就能越快地进行调查。

  ¥Use only the minimum amount of code necessary to reproduce the unexpected behavior. A good bug report should isolate specific methods that exhibit unexpected behavior and precisely define how expectations were violated. What did you expect the method or methods to do, and how did the observed behavior differ? The more precisely you isolate the issue, the faster we can investigate.

• 没有明确复现步骤的问题将不会被分类。如果标记为 “bug/0-needs-info” 的问题在相当长的一段时间内没有收到问题作者的进一步回复，它将被关闭。

  ¥Issues with no clear reproduction steps will not be triaged. If an issue labeled “bug/0-needs-info” receives no further input from the issue author for a significant period of time, it will be closed.

• 如果你的问题已解决但仍未解决，请随时关闭它。如果你自己找到了解决方案，解释一下你的解决方法可能会有所帮助。

  ¥If your issue is resolved but still open, don’t hesitate to close it. In case you found a solution by yourself, it could be helpful to explain how you fixed it.

• 最重要的是，请耐心等待：团队必须平衡你的请求与许多其他职责 - 修复其他错误、回答其他问题、新功能、新文档等等。问题列表并非付费支持，我们无法保证你的问题能够快速解决，但我们会尽力而为。

  ¥Most importantly, we beg your patience: the team must balance your request against many other responsibilities — fixing other bugs, answering other questions, new features, new documentation, etc. The issue list is not paid support and we cannot make guarantees about how fast your issue can be resolved, although we do our very best.

帮助解决现有问题(Helping to Resolve Existing Issues)

¥Helping to Resolve Existing Issues

除了报告问题之外，下一步，你可以通过提供反馈来帮助 Quasar 团队解决现有问题。如果你是 Quasar 开发新手，这可能是迈出第一步的好方法，你将熟悉代码库和流程。

¥As a next step beyond reporting issues, you can help the Quasar Team resolve existing ones by providing feedback about them. If you are new to Quasar development, that might be a great way to walk your first steps, you’ll get familiar with the code base and the processes.

如果你查看 GitHub 问题 中的问题列表，你会发现许多问题已经需要注意。你可以做些什么？实际上，相当多：

¥If you check the issues list in GitHub Issues, you’ll find lots of issues already requiring attention. What can you do for these? Quite a bit, actually:

验证 Bug 报告(Verifying Bug Reports)

¥Verifying Bug Reports

对于初学者，它仅有助于验证错误报告。你能在自己的电脑上重现报告的问题吗？如果是这样，你可以在问题中添加评论，说明你看到了同样的情况。

¥For starters, it helps just to verify bug reports. Can you reproduce the reported issue on your own computer? If so, you can add a comment to the issue saying that you’re seeing the same thing.

如果问题非常模糊，你能否帮助将其缩小到更具体的问题？也许你可以提供更多信息来帮助重现错误，或者通过消除不必要的步骤来提供帮助，这些步骤与演示问题无关。

¥If an issue is very vague, can you help narrow it down to something more specific? Maybe you can provide additional information to help reproduce a bug, or help by eliminating needless steps that aren’t required to demonstrate the problem.

任何能让错误报告更简洁或更容易重现的方法都能帮助那些试图编写代码修复这些错误的人们。 - 你最终是否需要自己编写代码。

¥Anything you can do to make bug reports more succinct or easier to reproduce helps folks trying to write code to fix those bugs - whether you end up writing the code yourself or not.

测试补丁(Testing Patches)

¥Testing Patches

你还可以通过检查已通过 GitHub 提交给 Quasar 的拉取请求来提供帮助。为了应用某人的更改，你需要首先创建一个专用分支：

¥You can also help out by examining pull requests that have been submitted to Quasar via GitHub. In order to apply someone’s changes, you need to first create a dedicated branch:

$ git checkout -b testing_branch

然后，你可以使用它们的远程分支来更新你的代码库。例如，假设 GitHub 用户 JohnSmith 已分叉并推送到位于 https://github.com/JohnSmith/quasar 的主题分支 “orange”。

¥Then, you can use their remote branch to update your codebase. For example, let’s say the GitHub user JohnSmith has forked and pushed to a topic branch “orange” located at https://github.com/JohnSmith/quasar.

$ git remote add JohnSmith https://github.com/JohnSmith/quasar.git
$ git pull JohnSmith orange

应用他们的分支后，请测试一下！以下是一些需要考虑的事项：

¥After applying their branch, test it out! Here are some things to think about:

• 这些更改真的有效吗？

  ¥Does the change actually work?

• 它是否提供了适当的文档？是否应该更新其他地方的文档？

  ¥Does it have the proper documentation coverage? Should documentation elsewhere be updated?

• 你喜欢这个实现吗？你能想到一个更好或更快的方法来实现部分更改吗？

  ¥Do you like the implementation? Can you think of a nicer or faster way to implement a part of their change?

如果你对拉取请求包含的改进感到满意，请在 GitHub 问题上发表评论以表明你的同意。你的评论应该表明你对这项更改的认可以及你对它的满意之处。类似内容：

¥Once you’re happy that the pull request contains a good change, comment on the GitHub issue indicating your approval. Your comment should indicate that you like the change and what you like about it. Something like:

如果你的评论只是 “+1”，那么其他审阅者可能不会太认真对待它。表明你花时间审查了拉取请求。

¥If your comment simply reads “+1”, then odds are that other reviewers aren’t going to take it too seriously. Show that you took the time to review the pull request.

为 Quasar 文档做贡献(Contributing to the Quasar Documentation)

¥Contributing to the Quasar Documentation

你可以通过使 Quasar 文档更加连贯、一致或可读，添加缺失信息、纠正事实错误、修复拼写错误或使其与最新的 Quasar 版本保持同步，来帮助改进文档。

¥You can help improve the Quasar documentation by making it more coherent, consistent, or readable, adding missing information, correcting factual errors, fixing typos, or bringing them up to date with the latest edge Quasar.

如果需要进行更大规模的编辑，请更改 Quasar 源文件（位于 GitHub 上的 此处）。

¥For larger edits change the Quasar source files (located here on GitHub).

文档最佳实践(Documentation Best Practices)

¥Documentation Best Practices

随着时间的推移，我们整合了一套规则并遵循这些规则，遵循这些规则将加快合并过程：

¥Over time we consolidated a set of rules which we follow and following them will speed up the merge process:

• 标题请大写，请参阅 如何使用大写标题。

  ¥Capitalize titles, see How to Use Capitalize My Title.

• 使用现在时。

  ¥Use the present tense.

• 简洁明了，避免文本/代码重复。

  ¥Be concise, avoid text / code duplication.

• 链接到用作主要信息源且通常更新更频繁的外部来源，例如 Mozilla MDN、Vue.js API，而不是往往很快就会过时的编译教程。

  ¥Link to the external sources which are used as master information sources and are usually updated more frequently, like Mozilla MDN, Vue.js API rather than compiled tutorials which tend to be outdated soon.

• 在提交 PR 之前进行校对

  ¥Do the proofreading before opening a PR

• 不要重复其他来源的文本，只保留与 Quasar 特定功能相关的内容。

  ¥Do not repeat texts from other sources, but keep only things which are relevant and shows in a context Quasar specific features

• 使用官方名称。例如，使用 Firebase 而不是 firebase

  ¥Use official names. For example use Firebase instead of firebase

• 从 PR 中排除所有草稿和未完成的页面

  ¥Exclude from PR all drafts and unfinished pages

Fork(Fork)

找到 Quasar GitHub 代码库 文件夹并点击右上角的 “Fork”。

¥Navigate to the Quasar GitHub repository and press “Fork” in the upper right-hand corner.

克隆分叉的仓库(Clone the forked repository)

¥Clone the forked repository

为了能够更改文档，你需要克隆分叉的存储库：

¥To be able to change the documentation, you need to clone forked repository:

$ git clone https://github.com/your-user-name/quasar.git
$ cd quasar
$ git checkout dev

安装依赖(Install dependencies)

¥Install dependencies

安装所需的依赖。

¥Install the required dependencies.

$ pnpm i

针对本地存储库运行文档(Running documentation against your local repository)

¥Running documentation against your local repository

$ cd docs
$ pnpm dev

文档将针对你本地克隆的存储库运行。

¥The documentation runs against your local cloned repository.

在本地编辑并测试你的更改(Edit and test your changes locally)

¥Edit and test your changes locally

提交更改(Commit your changes)

¥Commit your changes

当你对计算机上的更改感到满意时，需要将更改提交到 Git：

¥When you’re happy with the change on your computer, you need to commit the changes to Git:

$ git commit -a

这将启动你的编辑器来编写提交消息。完成后，保存并关闭以继续。

¥This should fire up your editor to write a commit message. When you have finished, save and close to continue.

更新本地仓库(Update your local repository)

¥Update your local repository

很可能在你工作期间，master 分支发生了其他更改。获取它们。

¥It’s pretty likely that other changes to master have happened while you were working. Go get them.

1. 添加一个远程 Quasar 仓库作为上游

   ¥Add a remote Quasar repository as an upstream

$ git remote add upstream https://github.com/quasarframework/quasar.git

2. 获取所有远程分支

   ¥Fetch all remote branches

$ git fetch upstream

3. 检查你 fork 的本地 dev 分支。

   ¥Check out your fork’s local dev branch.

$ git checkout dev
> Switched to branch 'dev'

4. 将 upstream/dev 中的更改合并到你本地的 dev 分支中。这将使你 fork 的 dev 分支与上游存储库同步，而不会丢失你的本地更改。

   ¥Merge the changes from upstream/dev into your local dev branch. This brings your fork’s dev branch into sync with the upstream repository, without losing your local changes.

$ git merge upstream/dev

没有冲突？测试仍然通过？你觉得更改仍然合理吗？然后继续并打开拉取请求，将你的更改应用到主 Quasar 存储库中的开发分支。

¥No conflicts? Tests still pass? Change still seems reasonable to you? Then move on and open a pull request to apply your changes to the dev branch in main Quasar repository.

发起拉取请求(Issue a pull request)

¥Issue a pull request

找到你刚刚推送到的仓库（例如 https://github.com/your-user-name/quasar），然后点击左上角面板中显示的 “新的拉取请求”。

¥Navigate to your repository you just pushed to (e.g. https://github.com/your-user-name/quasar) and click on “New Pull Request” seen in the left top panel.

确保你引入的变更集已包含在内。填写一些关于你潜在补丁的详细信息，包括一个有意义的标题。完成后，点击 “创建拉取请求”。Quasar 核心团队将收到你提交的通知。

¥Ensure the change sets you introduced are included. Fill in some details about your potential patch including a meaningful title. When finished, press Click on “Create pull request”. The Quasar core team will be notified about your submission.

编写你的故事(Write your Story)

¥Write your Story

我们一直在寻找关于你如何使用 Quasar 或你在使用 Quasar 过程中获得的良好体验的精彩文章。如果你撰写了文章，我们会将其发布在我们的 Medium 发布通道上，并且我们还会确保你的文章在我们的社交媒体上获得应有的关注。如果你感兴趣，请联系 blog(at)quasar.dev。我们期待你的反馈！

¥We’re always looking for great write-ups on how you are using Quasar or the great experiences you’ve had with Quasar. If you write an article, we will publish it on our Medium publication channel and we’ll also make sure your article gets the attention it deserves with our social media presence. If you are interested, please contact blog(at)quasar.dev. We’d love to hear from you!

创建新的 Quasar 应用扩展(Create new Quasar App Extension)

¥Create new Quasar App Extension

开始为 Quasar 做出贡献的一个简单方法是将你在项目中创建的代码进行泛化，并将其发布为 Quasar 应用扩展。请按照本指南了解如何进行 创建一个新的扩展。

¥An easy way to start to contribute to Quasar is to generalize the code you have created on your project and publish it as a Quasar App Extension. Follow this guide on how to create a new extension.

完成后，请在 Quasar Awesome 上提交 PR，并通过 Quasar 论坛 分享你的成果。

¥When done, submit a PR on Quasar Awesome, share your achievement via Quasar Forum.

为 Quasar UI 源代码做贡献(Contributing to the Quasar UI Source Code)

¥Contributing to the Quasar UI Source Code

与任何项目一样，贡献也有规则。我们的配置写在这里，请仔细阅读。之后，请阅读 Quasar 行为准则，然后你就可以为 Quasar 的核心代码库做出贡献了。

¥As with any project, there are rules to contributing. Ours are written here, please read them carefully. After that, read the Quasar code of conduct and you’ll be ready to contribute to Quasar’s core repositories.

文章 查看源代码 将帮助你熟悉 Quasar 代码库。

¥An article Look at the source code will help you to get familiar with a Quasar code base.

拉取请求指南(Pull Request Guidelines)

¥Pull Request Guidelines

• 从相关分支检出一个主题分支，例如 dev (Qv2) 或 v1 (Qv1)，然后合并回该分支。

  ¥Checkout a topic branch from the relevant branch, e.g. dev (Qv2) or v1 (Qv1), and merge back against that branch.

• 请勿在提交中签入 dist 文件。

  ¥DO NOT check in dist in the commits.

• 在处理 PR 时，可以进行多次小规模的提交 - 我们将让 GitHub 在合并之前自动压缩它。

  ¥It’s OK to have multiple small commits as you work on the PR - we will let GitHub automatically squash it before merging.

• 如果添加新功能：

  ¥If adding new feature:

  • 提供添加此功能的令人信服的理由。

    ¥Provide convincing reason to add this feature.

  • 图标名称采用连字符分隔，并始终以 、、 或 前缀开头。否则，你可能会花费大量时间处理一些可能根本不会被接受或无法达到你期望格式的内容。

    ¥Ideally you should open a suggestion issue first and have it green-lighted before working on it. Otherwise, you risk spending a lot of time on something which might not get accepted at all or not in the form you expect.

• 如果修复错误：

  ¥If fixing a bug:

  • 如果你正在解决特定问题，请在 PR 标题中添加 (fix: #xxxx[,#xxx])（#xxxx 为问题 ID），以便更好地显示发布日志，例如 fix: update entities encoding/decoding (fix #3899)。

    ¥If you are resolving a specific issue, add (fix: #xxxx[,#xxx]) (#xxxx is the issue id) in your PR title for a better release log, e.g. fix: update entities encoding/decoding (fix #3899).

  • 请在 PR 中提供 bug 的详细描述。最好有现场演示。

    ¥Provide detailed description of the bug in the PR. A live demo is preferred.

开发设置(Development Setup)

¥Development Setup

你需要 Node.js 版本 v16+ 以及 pnpm。阅读 package.json 并注意你可以使用的脚本。

¥You will need Node.js version v16+ along pnpm. Read package.json and take notice of the scripts you can use.

克隆代码库后，运行：

¥After cloning the repo, run:

$ pnpm i

常用 NPM 脚本(Commonly used NPM scripts)

¥Commonly used NPM scripts

# Start dev server with a demo app. This app has Quasar source code linked directly so any change will trigger HMR (Hot Module Reload) on the dev server.
# There's a section for each feature where tests are made.
$ pnpm dev

# build all dist files, including npm packages
$ pnpm build
# build only js dist files
$ pnpm build js
# build only type related files
$ pnpm build js types
# build only css dist files
$ pnpm build css

# lint sources
$ pnpm lint

项目结构 (/ui)(Project Structure (/ui))

¥Project Structure (/ui)

• build - 包含与构建相关的配置文件。大多数情况下，你无需修改​​它们。

  ¥build - contains build-related configuration files. In most cases you don’t need to touch them.

• src - 包含源代码。代码库使用 ES2015 编写。

  ¥src - contains the source code. The codebase is written in ES2015.

  • components - Quasar Vue 组件的 JS、Sass 和 JSON（API）文件

    ¥components - JS, Sass and JSON (API) files for Quasar Vue components

  • composables - Quasar 的 Vue 3 Composition API 可组合项

    ¥composables - Quasar’s composables for Vue 3 Composition API

  • directives - Quasar 提供的 Vue 指令

    ¥directives - Vue directives supplied by Quasar

  • plugins - Quasar 插件

    ¥plugins - Quasar plugins

  • css - Quasar 样式的 Sass 定义和核心代码

    ¥css - Sass definitions and core code for Quasar styles

  • utils - 框架使用并导出到公共 API 的实用程序

    ¥utils - utilities used by the framework and exported to the public API

• lang - Quasar 语言包

  ¥lang - Quasar language packs

• icon-set - Quasar 图标集

  ¥icon-set - Quasar icon sets

• dist - 包含用于分发的构建文件（仅在构建后）。

  ¥dist - contains built files for distribution (only after a build).

• dev - 直接链接 Quasar 源用于测试目的的应用。每个功能/组件都有自己的 *.vue 文件。添加新文件会自动为其创建路由并将其添加到 “homepage” 列表中（基于文件名）。

  ¥dev - app with Quasar sources linked directly used for testing purposes. Each feature/component has its own *.vue file. Adding a new file automatically creates a route for it and adds it to the “homepage” list (based on the file name).

Quasar 开发服务器 (/ui)(Dev Server for Quasar (/ui))

¥Dev Server for Quasar (/ui)

运行 pnpm dev 将启动一个使用 HMR（热模块重载）来处理 Quasar 源代码的开发服务器。你可以通过对 /dev *.vue 文件进行必要的更改来轻松测试你的更改。

¥Running pnpm dev starts up a dev server which uses HMR (Hot Module Reload) for Quasar source code. You can easily test your changes by making necessary changes to /dev *.vue files.

资金贡献(Financial Contribution)

¥Financial Contribution

Quasar 框架是一个遵循 MIT 许可的开源项目。得益于这些出色的 backers 的支持，它的持续开发才得以实现。

¥Quasar Framework is an MIT-licensed open source project. Its ongoing development is made possible thanks to the support by these awesome backers.

请阅读我们关于 为什么捐赠很重要 的清单。如果你想成为捐赠者，请查看 Quasar 框架的捐赠者活动。

¥Please read our manifest on Why donations are important. If you’d like to become a donator, check out Quasar Framework’s Donator campaign.

Quasar 贡献者(Quasar Contributors)

¥Quasar Contributors

感谢所有已经使用 为 Quasar 做出贡献 的用户！

¥Thank you to all the people who already contributed to Quasar!