Replies: 1 comment
-
Hi Peter. I believe the Pelican community is best served when that community can collaborate on developing plugins in a collective manner. For that reason, plugin developers are indeed encouraged to locate plugin repositories under the Pelican Plugins organization. To see other examples of how this type of development is managed, you can have a look at Jazzband and Django Commons. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The plugin migration table on the legacy pelican-plugins repository README suggests that the only canonical source for Pelican plugins is meant to be the pelican-plugins GitHub organization.
What should plugin authors do to get their plugin used and promoted? Should they transfer repository ownership to the pelican-plugins organization?
Beta Was this translation helpful? Give feedback.
All reactions