Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[Docs] Plugins technical review checklist#10731

Merged
GSadee merged 3 commits into
Sylius:masterfrom
Zales0123:technical-plugin-review-checklist
Oct 29, 2019
Merged

[Docs] Plugins technical review checklist#10731
GSadee merged 3 commits into
Sylius:masterfrom
Zales0123:technical-plugin-review-checklist

Conversation

@Zales0123
Copy link
Copy Markdown
Contributor

Q A
Branch? master
Bug fix? no
New feature? no
BC breaks? no
Deprecations? no
Related tickets
License MIT

Since the very beginning of the Sylius plugins system, we are giving the availability to make your plugin officially approved. This technical review checklist is a detailed instruction what you should focus on, to make the approval process smoother and faster 🎉

@Zales0123 Zales0123 added the Documentation Documentation related issues and PRs - requests, fixes, proposals. label Oct 2, 2019
@Zales0123 Zales0123 requested a review from a team as a code owner October 2, 2019 10:32
Comment thread docs/book/plugins/approved-plugins.rst Outdated
Comment thread docs/book/plugins/approved-plugins.rst Outdated
Comment thread docs/book/plugins/approved-plugins.rst Outdated
Co-Authored-By: Grzegorz Sadowski <[email protected]>
@GSadee GSadee merged commit a8f47e3 into Sylius:master Oct 29, 2019
@GSadee
Copy link
Copy Markdown
Member

GSadee commented Oct 29, 2019

Thank you, Mateusz! 🥇

@Zales0123 Zales0123 deleted the technical-plugin-review-checklist branch October 29, 2019 11:41
lchrusciel added a commit that referenced this pull request Dec 11, 2019
… (Zales0123)

This PR was merged into the 1.6 branch.

Discussion
----------

| Q               | A
| --------------- | -----
| Branch?         | 1.6
| Bug fix?        | no
| New feature?    | no
| BC breaks?      | no
| Deprecations?   | no
| Related tickets | 
| License         | MIT

This PR contains changes from #10731, which in fact should be from the beginning opened to `1.6` 😄 

Due to the release of Sylius Store, I propose a slightly new approach to approving/accepting plugins. We want to develop our plugins ecosystem, but on the other hand, we still want to keep the high quality of these extensions. There is also a new way to propose plugins to our plugins list - a [plugin request submit form](https://store.sylius.com/submit).

So my proposal is to accept all the plugins that work, provide a valuable extension to Sylius features and is documented enough to make installation as less problematic as possible. On the other hand, only plugins that fulfill more strict requirements from the "Should have" section, can get an "Approved by Sylius" badge. I believe it will be a better change for both Sylius users and developers 🏅 Let me know what you think about it 🖖 

Commits
-------

1fe0b86 [Docs] Plugins technical review checklist
ccefb84 PR review fixes
8c9a42f Fix recommended tests name
5a40edd Move tests requirements to "Should have" with an explanation
e5ce6c9 Plugins technical requirement changes due to Sylius Store release
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Documentation Documentation related issues and PRs - requests, fixes, proposals.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants