I backed out the sensors framework

YoctoGram yoctogram at gmail.com
Tue Oct 16 04:47:38 PDT 2007


> If it is biased, it is biased against the code and not the person(s).

I'm sorry, but who are you to decide?
Who did accept and approved this project in the first place?

Why should Google be spending any more money on "approved" FreeBSD SoC... 
if, at the end, it get "backed out" ?

I personally don't care about this project.
But, for what I can remember, the members of this project seemed to be one 
of the most enthusiastic and voluble about it...
So, if there was a problem with "the code"... why didn't you (or any of the 
FreeBSD leaders) took action(s) sooner?

// Yocto

----- Original Message ----- 
From: "Poul-Henning Kamp" <phk at phk.freebsd.dk>
To: "Constantine A. Murenin" <cnst at FreeBSD.org>
Cc: "Shteryana Shopova" <syrinx at FreeBSD.org>; <freebsd-current at FreeBSD.org>; 
"Alexander Leidinger" <netchild at FreeBSD.org>
Sent: Tuesday, October 16, 2007 2:36 AM
Subject: Re: I backed out the sensors framework


> In message <47143BE4.6060905 at FreeBSD.org>, "Constantine A. Murenin" 
> writes:
>>On 15/10/2007 16:13, Alexander Leidinger wrote:
>>
>
>>There are tonnes of unused compatibility stuff in FreeBSD; backing out
>>some interface that could have been used as a compatibility layer with
>>something that is actually heavily used in the neighbouring BSD projects
>>is unwarranted and obviously biased.
>
> If it is biased, it is biased against the code and not the person(s).
>
> If you compare at NetBSD, OpenBSD and FreeBSD, you will find a quite
> visible difference in the architectural attitude the projects take
> to various problems.
>
> The short summary is that NetBSD focuses a lot on portability,
> OpenBSD on security and FreeBSD on scalability and usability.
>
> The area where the architectural mindset is most different
> is probably security, closely followed by system management.
>
> These differences are a good thing.
>
> But it also means, that what may seem architecturally sound in one
> project, is not going to fly in another.
>
> -- 
> Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
> phk at FreeBSD.ORG         | TCP/IP since RFC 956
> FreeBSD committer       | BSD since 4.3-tahoe
> Never attribute to malice what can adequately be explained by 
> incompetence.
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
> 



More information about the freebsd-current mailing list