Does the October Team have a policy oh how they deal with unresponsive developers that have paid products available.
Whereas I completely understand that some are not an actual business, and have staff or a lot of free time to answer questions everyday. However after using many different means of communication for a month now without an answer is some cause for concern. My project has basically been on hold this entire time and Im now debating if I need to move in a different direction. If it wasn’t for the fact I have invested a huge amount of time and resources into October I would have already moved on. However I see a lot of potential in the product and want to see it through. To me there needs to be some kind of accountability towards developers that are allowed to distribute their products through your platform.
welcome. it may be concerning that plugin/theme is paid and there are no support for that. but let me ask you this. how exactly you will gain any information if developer will answer or may have a ticketing system, to ensure, that OC dev team can “approve” such developers?
what is exactly that questions that may be asked before publishing any plugin etc?
first of all, it is on each developer to take responsibility for work, right? not a “marketplace”
I dont think is a matter of what questions to ask a developer before allowing them to publish a plugin etc. Its a matter of the October Team setting exceptions that a developer must follow to have the privilege of having their products in the Marketplace.
The October Team is providing a direct conduit for a developer to sell and market the products they create. Yes, October redeems some benefit and value from this. However it can create some negative benefits and reduce its value add as well. Such as this case where I am trying to get some information. When I discovered October I was super excited because this was my direct replacement from DotNetNuke. Originally I thought I was going to stuck Wordpress after seeing the decline of DotNetNuke. However after diving deep into Wordpress I found out it wasn’t the solution I was looking for.
I see huge promise in October, I just need to get over its learning curve. This takes time due to my schedule.