[haiku] Re: Does the Haiku project still have any meaning at all?
- From: Jerry Babione <jerry.babione@xxxxxxxxx>
- To: "haiku@xxxxxxxxxxxxx" <haiku@xxxxxxxxxxxxx>
- Date: Sun, 24 Nov 2013 10:31:45 -0600
Haiku is viable as long as we believe. Distribution can come with modern
apps. Many of the old apps are still modern as they were ahead of their
time. Reality is the need of a Office Suite that works consistently and is
Free in all cases. I'd gladly work for and on Haiku more. I still have
clients using BeOS 5r3 and BeOS 4 Pro. I'd love to spend, this old and
nearly blind mans time developing. I have a 300+ client list using Linux,
Unix (As far back as Version 5r2), and BeOS. My time is taken up keeping
them alive and as current as possible. Ports have to be done and made that
are often unique to the AT&T B3 or the IBM 4341a6 I still support. I have
been contacted by a Bank still using a Borroughs B1985 and Gemcos over the
MCPII, and I can't afford to hire more people anymore than Haiku can. So,
please, get off their backs, and help us all. Beta will be here ASAP and
not anytime sooner.
On Sun, Nov 24, 2013 at 9:34 AM, Matt Madia <mattmadia@xxxxxxxxx> wrote:
> On 11/24/13, a_j_2014@xxxxxxx <a_j_2014@xxxxxxx> wrote:
> > Coming to the point of this email, could some of the developers please
> > state clearly when they predict the release of a beta version?
>
> In the past, I've had discussions on how to answer these types of
> questions.
>
> Making unrealistic predictions about when HAIKU R1 (beta) will be
> released does not improve things for the Haiku project. In fact, I'd
> suggest that it hurts more than it helps. At the same time, the
> "Real Soon Now (TM)" answer is not better.
>
> Instead of giving a random release date or giving a cop-out of
> "Real Soon Now (TM)", these questions are an opportunity to reach out to
> you and other people, to inform them of exactly where we need their help.
>
>
> The honest truth is that we need people who are interested in advancing
> HAIKU.
>
>
> People need to realize that while Haiku has achieved great things, each
> and every patch is appreciated. Patches that may seem insignificant to
> larger open source communities are vital to Haiku, because our pool is
> so much smaller in comparison. Whether it is a patch that fixes a
> spelling mistake, a patch that documents a single function in the Haiku
> API, or any other patch, they all are worthy contributions that help
> make Haiku a better product. This is not even getting into the 3rd-party
> opportunities, which is as wide as one's creativity. (And yes, I think
> there needs to be a stronger group effort to consolidate the information
> of where and what those opportunities are.)
>
> The last thing this project needs is to support the notion that everything
> will be handed to them in a few more months; all they need to do is wait.
> That idea holds Haiku back. It discourages people from taking action
> today.
>
> The best part, now that Haiku has moved to distributed version control
> system (Git specifically), it is even easier for people to tinker with
> Haiku. More importantly people get better recognition for their
> contributed patches. E.g., not only commit messages but sites like
> ohloh.net even recognize them --
> We need people to realize that while Haiku has achieved great things,
> each and every patch is appreciated. Patches that may seem
> insignificant to larger open source communities are vital to Haiku,
> because our pool is so much smaller in comparison. Whether it is a
> patch that fixes a spelling mistake, a patch that documents a single
> function in the Haiku API, or any other patch, they all are worthy
> contributions that help make Haiku a better product. This is not even
> getting into the 3rd-party opportunities, which is as wide as one's
> creativity. (And yes, I think there needs to be a stronger group
> effort to consolidate the information of where and what those
> opportunities are.)
>
> The last thing we need is to support the notion that everything will
> be handed to them in a few more months; all they need to do is wait.
> That idea holds Haiku back. It discourages people from taking action
> today.
>
> The best part, now that we have moved to distributed version control
> system (Git specifically), it is even easier for people to tinker with
> Haiku. More importantly people get better recognition for their
> contributed patches. E.g., not only commit messages but sites like
> ohloh.net even recognize them --
>
> http://www.ohloh.net/p/haiku/contributors?highlight_key=first_checkin&time_span=30+days
>
>
> --mmadia
>
>
--
Jerry Babione
Founder-Just Plain Folks Org. Inc.
Other related posts:
