Hi folks - first of all thank you for this powerfull extension.
Now - as you are heading for beeing the major player in this community game it makes sense to communicate more with your plugin/extension develpers. As to name the most important: Techjoomla, ReadyBytes, Joomlaxi, etc.
Their extensions are a must for all serious community providers.
So if you are planning to publish a new release of your wonderful peace of software, get in touch with these developers BEFORE you release. Maybe a tool like basecamp (if don't have ambitions to setup your own project management with e.g. projectfork) should make the dialog smooth. Ensuring you will not harm our running systems with your update.
Why I'm suggesting this? Because I was spending my weekend with rolling back Joomla to 3.1.5 and afterwords JomSocial back to 3.0.4. XIPT and, as a consequence PayPlans, stopped working as expected. Can you imagine what this means? Our users are irritated if something like this happens! Without OUR users, your business model doesn't work too.
I had several discussions, for example with the developers from PayPlans, that everyone of us involved has to reflect the situation of the users out there by means of their regional legal affairs like taxation or personal habits caused by cultural diversity.
So, you're the ones providing the core for building our communities. This implies your responsibility to take care of your plugin developers and the proper functionality of their products .
of course you have to rely on the stability of Joomla and i'm sure you will do your best to ensure this. The example with my rollback maybe was kind of lacking...
As i mentioned - Much more important is the cooperation/communication with the subordinate extension/plugin developers during your development cycles...11 years ago
Mark OliverFor getting ideas these "open" groups are surely fine.
To keep the major subordinate developers on the line a groupware like projectfork on your own servers or basecamp (free version is working well because you have only one project) is more suitable.
There you can provide code changes in a closed environment by the minute. This gives these developers much more responsiveness in...For getting ideas these "open" groups are surely fine.
To keep the major subordinate developers on the line a groupware like projectfork on your own servers or basecamp (free version is working well because you have only one project) is more suitable.
There you can provide code changes in a closed environment by the minute. This gives these developers much more responsiveness in updating/tweaking their code.
As you are working with timelines, milestones and depending tasks you, as the project owner, can coordinate the release management for all involved.
Example: You are planning the next release with influence on the user management and acl. So it's clever to involve the PayPlans people as well as David Deutsch from AEC (ok, think he isn't so active lately...) . So you set up a project and invite these guys to the project.
As they are project membes now you can hand over some tasks - one could be the testing of your new code in their invironments As soon as you get the status - green from all involved you're good to go with the rollout.
Shared development cycles in this way have also big impact by means of marketing. If not only your new release is to be published but also the extensions of your subordinate developers, you will spread the word together and gain more attention to your product. (This must not inevitably mean you have to bundle ...)
From customer view it gives extended confidence. Knowing that upgrading to future releases is mostly hassle free. An argument for more long term subscriptions I think.
Mark OliverP.S. Facebook is (maybe) fine for attracting new customers. But, hey - you have your own community running here. So this is the place to discuss these matters!
Hi folks - first of all thank you for this powerfull extension.
Now - as you are heading for beeing the major player in this community game it makes sense to communicate more with your plugin/extension develpers. As to name the most important: Techjoomla, ReadyBytes, Joomlaxi, etc.
Their extensions are a must for all serious community providers.
So if you are planning to publish a new release of your wonderful peace of software, get in touch with these developers BEFORE you release. Maybe a tool like basecamp (if don't have ambitions to setup your own project management with e.g. projectfork) should make the dialog smooth. Ensuring you will not harm our running systems with your update.
Why I'm suggesting this? Because I was spending my weekend with rolling back Joomla to 3.1.5 and afterwords JomSocial back to 3.0.4. XIPT and, as a consequence PayPlans, stopped working as expected. Can you imagine what this means? Our users are irritated if something like this happens! Without OUR users, your business model doesn't work too.
I had several discussions, for example with the developers from PayPlans, that everyone of us involved has to reflect the situation of the users out there by means of their regional legal affairs like taxation or personal habits caused by cultural diversity.
So, you're the ones providing the core for building our communities. This implies your responsibility to take care of your plugin developers and the proper functionality of their products .
Develop - Communicate - Test - Release ;-)
Thanks in advance,
MO