Okay, I know I keep mentioning them (and I am sure it is getting annoying), but in my opinion, this is the right way to setup the plugin directory:
Everything is handled through Github (so no learning new tools), semi-automated review system, using Stripe Connected Account to handle payments. The split they do is 70/30 with a minimum of 50c.
Seems reasonable to me but I don’t have stroke (as they say in the South).
I would pay for a CP version of WordFence, Gravity Forms, and some other central plugins as long as their price points are within reach.
I really like the elementary approach. Clean and simple. As we’re already using Stripe, that part will be pretty easy.
I think the fees are a bit off though, and we’d want to be more competitive than Themeforest.
RE: Corepress: I’m going off the idea of having it as a separate entity. It adds another name to the mix and just makes for a confusing experience. They will also have to solve the same problems we’re already solving (infrastructure, documentation, funding, branding etc). In addition, adding support for monetisation of the directory via a 3rd party doesn’t make sense as we would have no way of allowing our community to make decisions on how this is done, and there is no guarantee that they will even want to make it possible.
Lastly, a goal of corepress is to stop forks doing the same work twice. Definitely a noble idea, but the reality is that there will, at some point, be a difference of opinion about how corepress wants to do something and how ClassicPress’s community want to do something and it’ll all come tumbling down.
Instead I would suggest that we make the directory and officially allow other forks to use it. All forks could still collaborate on core plugins, and it simplifies the whole process.
I hate the way WP does their plugin directory. Whatever decision is made regarding the plugin directory for CP, I strongly suggest that whatever rules are decided upon, stick with those rules.
It is really irritating to look at the rules over there and seeing the reality of what is allowed. As I have said many times in emails to them, their plugin directory is a cesspool. Too many developers are allowed to use the plugin directory as a sales page, contrary to the rules. If you have sections where sales are allowed, that’s great. But don’t let them overlap. Have a section for freemium so people have the opportunity to know before installing, what a plugin developer is doing.
I would also be careful about some of the “IM” people getting into the plugin directory and scamming users with their funnels. There should also be required agreement to terms (strictly enforced).
Of course, there is also the possibility of welcoming those “IM” people with a section that competes with the likes of jvzoo. Depends on what you want to do and how much headache you want someone to take on. One person wouldn’t be able to manage it, that’s for sure.
Honesty and not showing favoritism to some developers over others will be a nice change. Not that WP knowingly does anything like that… 
If there is going to be a sales section of the plugin directory, then encouraging developers to have reasonable prices would be good. Downloadable software replicates itself. There’s no need to get rich off a few people. If there is a concern about supporting something that doesn’t cost much, I would suggest extra pricing for support, or coding with best practices in mind. Just a thought.
I really like the idea of open, honest & reasonable. Premium, Freemium & free, works for me.
Themeforest handles this quite nicely - you can pay for support as an addon for each theme / plugin
As you say having it as a separate entity could be confusing and could lead to disagreements between ClassicPress and other forks.
I’d agree with the repository being a ClassicPress one first and foremost with others able to use it.
What do you think about offering a “ClassicPress Premium” service for WP hobbyists or even agencies that don’t know what’s going on, don’t have technical capabilities, and just want someone to diagnose their site to see if it’s compatible, and just switch it over to ClassicPress and keep it going for them? In other words, a type of “we do everything for you” service you could offer as a subscription service? There are many small business owners out there who would not find ClassicPress,not know how to migrate from WP to CP, and that offering could be a revenue generator going forward. Just a thought.
This is something we had discussed in passing on Slack. The way we were going to approach that though was to allow our devs (contributors) to sell their services on the side, not directly through ClassicPress. We are planning a job portal where companies can go to post what services they are looking for, that would provide a source of revenue (from premium job posts, or something along those lines).
Great idea! I’d love to be able to hep “mom and pop shops” make the transition to ClassicPress and every source of income (minor or major) helps pay our bills. And if it could lead to web design or other things, all the better.
If/when you get that going, am assuming you would have a page up for it… with the committee’s permission, I would be happy to establish a subdomain/site to assist with that. Let me know when/if
Dick, I’m a total web-head, and would love to get involved also. I just don’t feel I’m the Master Programmer many others here are. I can build just about anything using CP at this point since it’s forked.
Everyone starts somewhere. Even if you’re not a master programmer, there’s still plenty of ways to be involved. In fact, it seems like you’re doing a great job of it so far! 
This is something we are trying very hard to change, the perception that you have to be a good coder to get involved.
That was why I personally appreciated the discussion here
Just out of curiosity, is there a thread somewhere for discussions on how CP could create more revenue generating streams, such as a donation page or a Kickstarter page, a jobs listing page, premium plugin offerings, and so on?
There can be, I will set up a category when I get home. I think that is a great idea!
Unfortunately, Envato doesn’t require “Authors” to support their products. Don’t know how that could be improved upon. But I do agree with the idea of a full service platform for supporting plugins and themes if CP is up to it.
I think it would be received well. Encourage devs to participate. I would like that, for sure.
Let’s use the marketing forum for that discussion, I think it probably fits best there
I have updated the description for that forum so it is more clear as well.
Thanks! Feel free to give me all the credit (just kidding, sort of), and please let me know when that is up. I’d like to see what’s there.
My suggestion wasn’t to force it, if you select the 5 stars the idea was to show another donate field with a dropdown that by default could say don’t donate.
The normal donate button in the WordPress plugin page just don’t works, it’s rare to someone donate using that. I’m talking from my experience but you can easily conclude that if you check the most famous Free plugins donate links(most of them go to their own websites).
I understand what you’re saying, Rui. I don’t think it’s actually the placement of the buttons that causes them to not-perform. I think it’s simply that few (if any) people ever donate. This is why I’m against sliding it into the review process - if feels like cruft. A donation button/option (IMHO) gives people the feeling that other people are probably doing it, so my few bucks won’t be missed – which leads to nobody donating. In the 15+ years I’ve been involved in open source, I’ve only donated twice even though I probably run across 20+ donation buttons in a day. I think people have developed “banner blindness” to donation buttons.