the advantage of a roadmap is that allows people that can agree on principle on a specific kind of approach can work together as a team towards a common goal under the same project.

People who cant find someone else to agree with them, or dont like the existing solutions can always follow their own path and create their own code. On other hand those kind of people can also benefit from a roadmap because a roadmap is always an attractive force for contributors.

When I (used here generally not just to refer to me) know what your intention is with this code in the future , I will be far more willing to help you out if our goals are common. If not then roadmap can still be useful if I dont want our two projects , mine and yours to overlap.

So a roadmap is a win win situation.

And I dont even need to go into the advantages of planning ahead.

On Sat, Mar 28, 2015 at 5:05 PM, Tudor Girba <tudor@tudorgirba.com> wrote:
I think the fear that someone else might do something similar should not stop action.

Having multiple solutions to choose from is a good thing :)

Cheers,
Doru

On Sat, Mar 28, 2015 at 2:32 PM, Sean P. DeNigris <sean@clipperadams.com> wrote:
stepharo wrote
> So I would like to propose that we share a kind of board of announce on
> what people are doing.

Thank you! This is great. I've also been hesitant to work on certain things
(e.g. cleaning up Morphic events) because I didn't want to unintentionally
overlap with someone else's work.



-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/Improving-communication-and-roadmap-tp4815705p4815753.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.




--

"Every thing has its own flow"