@anon71687268, @anon95694377, anyone else,
Below is a list of the items (an initial list anyway) which I think need to be considered for creation of a plugin repository.
Rules needed for:
- Plugin Submission
- Including when/how Freemium/Premium
- Should there be a cost for Freemium/Premium? If so, when does the cost apply? Upfront or as a slice of cost?
- The former means the dev can use own payment channel; the latter means it would need to be managed by ClassicPress.
- Plugin Maintenance
- Plugin Adoption
- This is very poor on WP Plugin Repository. Both for visibility and ability to adopt.
Repository view in CP sites
- Premium
- Freemium
- Rest
- Top Rated (last n days)
- Most Popular (downloaded last n days)
- Search
Also required:
- Understanding of how GitHub works.
- Costs of GitHub/building repository.
As a first draft for rules, I’d suggest we look to the WordPress Plugin Repository rules (possibly ; I think in spirit they are mostly reasonable. I’m not sure what sort of licence they’re under so I don’t know if we can copy and tweak or need to write fresh along similar lines?
If someone knows the answer to the above, I’m happy to go through them to produce a draft to consider for the rules.
Does anyone know Github who can explain how it works? I assume it’ll need to like WordPress uses SVN; one repository with approved plugins being added with the developer having write permissions, but everyone else being read-only?
I think I need an understanding of Github before I’ll understand all relevance of the Elementary AppCenter.