A lot of people are probably wondering what Ryan as project lead and Jay as community/marketing manager feel about this. They've been laying low and can't comment on this subject as much as they'd like to, but I would suggest to check out their twitter feed from the past two days to get an idea of where they stand in this TV-worthy sitcom.
https://twitter.com/rthrash https://twitter.com/jaygilmore
Quote from: splittingred at Mar 29, 2013, 01:40 AMQuote from: dinocorn at Mar 28, 2013, 06:22 PM
One thing I find myself wondering is how much is the SiphonLabs team going to prioritize developing Wordpress Cloud features over requested features such as script automation with CRON jobs (or something similar). I've got a handful of clients that were ready to move sites over the day that feature landed, when it was MODX Cloud at least.
As Director of Cloud, I can guarantee that won't happen. If you'd like to know, I'll be blatantly transparent: here's our priority roadmap for SiphonLabs for the next couple quarters:
1. Get WordPress in the system
2. Add Domain and Email Hosting
3. Add SSL
4. Work on getting MODX 2.3 released
5. Work on smaller Cloud issues, such as CRON/Settings/et al
If you'd like more info on that list, please ask.
You may want to get going on that list instead of trying to manage to manage a PR situation - as you say, you're Director of Cloud, not Director of Marketing.
Go off and do the Cloud thing and instead of
talking about how MODX is so important,
show the community how SiphonLabs is going to help MODX and that SiphonLabs will always have MODX first and foremost, even when it offers competing systems such as WordPress (which, because of its inherit much larger market, will likely outnumber MODX installs in no time). Show it, don't preach it.
I don't think anyone will trust SiphonLabs to do the right thing for MODX until they have proven that to be the case, but I do wish you all the luck and wisdom in the world. The Cloud platform is quite special and deserves more than the in my opinion (which seems shared with others here) poor management and marketing decisions.
Until then, there was a great discussion going on in this thread about how we, as a community, can make the MODX community even bigger and better. I've seen some great ideas come by and frankly I think we should make some of the things said happen.
I'd love to migrate issues to Github as I really don't think we need everything Redmine offers. We just need to have bug reports, people assigned to handle them, and a milestone version assigned to it and more people to discuss and close the bugs. Keeping everything in one place (code and bugs, on github) I think that will make it easier for people to contribute and it also adds another sense of transparency of the project. It's also a step into the right direction in terms of making the infrastructure easier to handle.
[ed. note: markh last edited this post 11 years, 1 month ago.]
☆ A M B ☆
☆ A M B ☆
the url is slightly changed due to a censure filter i guess. it leads to Japanese crisis-management. The irony 
☆ A M B ☆
☆ A M B ☆
