[openbeos] Re: The importance of good communications

"Haiku Security" <info@xxxxxxxxxxxxxxxxxx> wrote:
> Communications and marketing are what is going to get you new devs 
> and 
> contributors.   A well designed platform for communications is what 
> Haiku 
> has needed for a LONG time.  You  AREN'T GOING to get R1 if no new 
> talent 
> comes on board!

We'll get to R1 if I'd be alone. It would just take longer :-)
We have a great team right now, and we will definitely take us to R1, 
whatever conspiracy theories you can come up with. More help is always 
appreciated, and it will certainly help to speed up things, but it's 
not like we have a problem now we desperately need to solve.
Sure graphics drivers will be neglected a bit, since Rudolf stepped 
down, and Haiku will suffer from that, but new talent, no matter how 
many, could hardly replace him. You need the right people for the job. 
And a lot of dedication.

> We need to get/keep people excited.  We need to give incentive to 
> contribute.  I've already been turned off a number of times due to 
> the lack 
> of leadership in a number of aspects in the project--this is exactly 
> what 
> you do not want.  Especially from people who have a lot of drive and 
> a lot 
> of spare time.

If you have a lot of drive, you would certainly be able to contribute. 
Others have done so in the past, others will do so in the future. I 
wasn't one of the initial developers, too, I just joined at some point 
and did what I think we needed.

> Unified authoritative messages are desperately needed.  It doesn't 
> matter 
> how you COME UP WITH THE MESSAGE!  Thru collaboration or whatever.  
> It just 
> matters that it be consistent, and come thru a clear chain of 
> command, and 
> be separate from public debate until the message is actually formed!

It's free for anyone of the core developers or members of our team to 
follow this thread or not.
If they don't contribute to it, I don't blame them.

> I think you should take up Koki's offer of Marketing Communications 
> director, and I would be happy to help him do the job.

You usually don't just offer to be someone in an open source project, 
you become someone by doing such things. Even if some of you might not 
feel officially-blessed, I could have the same problem if I really 
wanted to - there is usually no one who reads my code and correct 
design errors and bugs, and if someone does, they usually find lots of 
shortcomings, too (thanks Ingo, thanks Oliver, thanks Jérôme, thanks 
Stefano, thanks ...! :-)).
Oh, and there is also usually no one saying to me: do that, do that 
next, etc. This is not a job, it's the part of your life you can do 
what you want to do :-)

Bye,
   Axel.

Other related posts: