home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
General Forums
Website/Forum/Wiki Feedback
Hard and big!
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Anonymous" data-source="post: 7123"><p>I agree completely. But what comes first, the chicken or the egg? My point in asking such a stupid question is that in order to evangelise a robust, mature product a strategy needs to be created. That stratgey and resulting roadmap will ensure that when we do have a robust, mature product that we can adequately evangelise it.</p><p></p><p>The ideas I threw out were ways we could execute parts of a strategy. If we want to do this right, we need to build a roadmap that the stakeholders (to be defined) can agree on. My ideas as a marketer and the ideas of a developer may be close but probably aren't the same. This is a developer lead project (as are most open source projects.) If I were one of those developers, I'd be very sensitive to someone coming in and trying to create a roadmap. I think portions of a roadmap exist (the infamous todo list) and I think a good place to start might be to tackle that list and try to make it a little more coherent. If the developers approve, of course. I'm sure if you ask frodo, he has a pretty clear roadmap in his head. </p><p></p><p>So I guess I am saying this is an area/project that we would need to tred lightly in and proceed slowly...</p><p></p><p>Thoughts?</p></blockquote><p></p>
[QUOTE="Anonymous, post: 7123"] I agree completely. But what comes first, the chicken or the egg? My point in asking such a stupid question is that in order to evangelise a robust, mature product a strategy needs to be created. That stratgey and resulting roadmap will ensure that when we do have a robust, mature product that we can adequately evangelise it. The ideas I threw out were ways we could execute parts of a strategy. If we want to do this right, we need to build a roadmap that the stakeholders (to be defined) can agree on. My ideas as a marketer and the ideas of a developer may be close but probably aren't the same. This is a developer lead project (as are most open source projects.) If I were one of those developers, I'd be very sensitive to someone coming in and trying to create a roadmap. I think portions of a roadmap exist (the infamous todo list) and I think a good place to start might be to tackle that list and try to make it a little more coherent. If the developers approve, of course. I'm sure if you ask frodo, he has a pretty clear roadmap in his head. So I guess I am saying this is an area/project that we would need to tred lightly in and proceed slowly... Thoughts? [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
General Forums
Website/Forum/Wiki Feedback
Hard and big!
Contact us
RSS
Top
Bottom