'Re: [FreeNX-kNX] Compiling NX1.5.0 on amd64'

[prev in list] [next in list] [prev in thread] [next in thread] 

List: freenx-knx
Subject: Re: [FreeNX-kNX] Compiling NX1.5.0 on amd64
From: Xiong Jiang <linuster () gmail ! com>
Date: 2005-09-29 17:02:06
Message-ID: 9b5164430509291002182211b6 () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

Bugs are found first then fixed later. Have a bug tracking system is more
useful than mailing list. Before that bug report in mailing list is still
useful.

People finding bugs also did great help to a project. Fixing the bug need
more knowledge/experience about the code though.

It's true that most people try a package and go away because it's just too
hard for them to fix. How much portion of C programmers understand X server
code on this planet? However the bugs they found is still valuable help.

Thanks for your time and lengthy words.
If I had been trolling, you were replying back with a lot more trolling-lik=
e
words, with the sole standing from NoMachine or yourself. It's normal as
we've seen similar things between companies and OSS projects. bitmover is a
very good example.

I am only tracking NX in little spare time so I am doomed to miss a lot of
document/emails/READMEs. I complained because it's not easy for me to find
the information needed. I do not ask for forgiveness on this and feel
grateful for those who pointed me to the documents.

Once a software package is released, it is expected to receive critism.
So, be humble and build the software stronger. That's the mutual interest o=
f
this project and your company.

I said no flamebait so I do not reply anything more than this.

Have fun,
Xiong

On 9/29/05, Gian Filippo Pinzari <pinzari@nomachine.com> wrote:
>
> LROUFAIL@nc.rr.com wrote:
> > We are fortunate they don't just create software for Windows like most
> > commercial software.
>
> It's not a matter of luck. I think there is an implicit pact between
> a company releasing its software as OSS and the community. NX is OSS
> not because of a late attempt to save a product that doesn't sell.
> NX has always been OSS and since 2001 we have not received a single
> significant contribution. On the contrary, we have had to defend
> ourselves from the repeated attacks coming from all fronts. Don't
> forget that a system like NX is a welcome addition to any big vendor's
> software stack. Destroying a company developing an interesting
> software is a much better alternative than partnering and sharing the
> outcomes. Because of that, we have developed a very defensive attitude.
> People can't expect NoMachine to be more open than it is already.
>
> About FreeNX, things work with OSS when developers contribute to the
> advance of a software, not when they just copy it and don't give
> anything back. About the ability of FreeNX to uncover bugs and help
> NoMachine to test the software, I can say that this help doesn't pay
> the bill. It's quite easy to find bugs. Users, for example, are
> wonderful at that. NoMachine offers free downloads already and has a
> staff trained at taking care of filling Trouble Reports. I think that
> FreeNX developers should rather concentrate on helping with these
> bugs, if they care about the future of NX.
>
> I know that the most fierce OSS defenders would like to see FreeNX out-
> pace NoMachine in every respect and would like to see NX finally freed
> of any commercial inheritance. These kind of people will never help
> us. They will rather throw their FUD at us, one of the preferred sports
> in this industry. We are not concerned of competition. On the contrary
> we think that there can be a place for both a OSS and a commercial
> NX version. Unfortunately it's difficult to compete with FreeNX when
> we do 99% of the work and FreeNX keeps doing the 1% and giving it
> away for free. Is this the way OSS development should work?
>
> > Don't take potshots at them from a free forum. They don't owe us better
> > documentation. The code is a good enough gift to the community. If you
> > want more you should pay for it.
>
> Nothing is ever perfect. We are more than wishful to listen and improve,
> as long as there is a clear idea of who's supposed to do the work.
> Bugs don't get fixed automatically just because somebody mentions them
> in a mailing list. The same is true for the documentation. Instead of
> criticizing all the time, people should rather ask themselves if they
> have really tried to help, or have gone the easier route, consisting
> in the usual "thanks a lot, unfortunately this stuff is not good enough
> for me, I'll come when it's ready". As far as I know, everytime I have
> asked somebody in the OSS community to help, he always responded that
> he was already busy with some other thing. I can reassure you that I'm
> tremendously busy too, and all the other people here are busy as well.
>
> /Gian Filippo.
>
>
> _______________________________________________
> FreeNX-kNX mailing list
> FreeNX-kNX@kde.org
> https://mail.kde.org/mailman/listinfo/freenx-knx
>

[Attachment #5 (text/html)]

Bugs are found first then fixed later. Have a bug tracking system is more useful than mailing list. \
Before that bug report in mailing list is still useful. People finding bugs also did great help to \
a project. Fixing the bug need more knowledge/experience about the code though. It's true that \
most people try a package and go away because it's just too hard for them to fix. How much portion of C \
programmers understand X server code on this planet? However the bugs they found is still valuable help. \
 Thanks for your time and lengthy words. If I had been trolling, you were replying back with a \
lot more trolling-like words, with the sole standing from NoMachine or yourself. It's normal as we've \
seen similar things between companies and OSS projects. bitmover is a very good example. I am \
only tracking NX in little spare time so I am doomed to miss a lot of document/emails/READMEs. I \
complained because it's not easy for me to find the information needed. I do not ask for forgiveness on \
this and feel grateful for those who pointed me to the documents. Once a software package is \
released, it is expected to receive critism. So, be humble and build the software stronger. That's \
the mutual interest of this project and your company. I said no flamebait so I do not reply \
anything more than this. Have fun, Xiong <div> On 9/29/05, Gian Filippo Pinzari &lt;<a \
href="mailto:pinzari@nomachine.com">pinzari@nomachine.com</a>&gt; wrote:<blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; \
padding-left: 1ex;"> <a href="mailto:LROUFAIL@nc.rr.com">LROUFAIL@nc.rr.com</a> wrote: &gt; We are \
fortunate they don't just create software for Windows like most &gt; commercial software. It's \
not a matter of luck. I think there is an implicit pact between a company releasing its software as \
OSS and the community. NX is OSS not because of a late attempt to save a product that doesn't \
sell. NX has always been OSS and since 2001 we have not received a single significant contribution. \
On the contrary, we have had to defend ourselves from the repeated attacks coming from all fronts. \
Don't forget that a system like NX is a welcome addition to any big vendor's software stack. \
Destroying a company developing an interesting software is a much better alternative than partnering \
and sharing the outcomes. Because of that, we have developed a very defensive attitude. People \
can't expect NoMachine to be more open than it is already. About FreeNX, things work with OSS when \
developers contribute to the advance of a software, not when they just copy it and don't \
give anything back. About the ability of FreeNX to uncover bugs and help NoMachine to test the \
software, I can say that this help doesn't pay the bill. It's quite easy to find bugs. Users, for \
example, are wonderful at that. NoMachine offers free downloads already and has a staff trained at \
taking care of filling Trouble Reports. I think that FreeNX developers should rather concentrate on \
helping with these bugs, if they care about the future of NX. I know that the most fierce OSS \
defenders would like to see FreeNX out- pace NoMachine in every respect and would like to see NX \
finally freed of any commercial inheritance. These kind of people will never help us. They will \
rather throw their FUD at us, one of the preferred sports in this industry. We are not concerned of \
competition. On the contrary we think that there can be a place for both a OSS and a commercial NX \
version. Unfortunately it's difficult to compete with FreeNX when we do 99% of the work and FreeNX \
keeps doing the 1% and giving it away for free. Is this the way OSS development should \
work? &gt; Don't take potshots at them from a free forum.&nbsp;&nbsp;They don't owe us better \
 &gt; documentation.&nbsp;&nbsp;The code is a good enough gift to the community.&nbsp;&nbsp;If \
you &gt; want more you should pay for it. Nothing is ever perfect. We are more than wishful to \
listen and improve, as long as there is a clear idea of who's supposed to do the work. Bugs don't \
get fixed automatically just because somebody mentions them in a mailing list. The same is true for \
the documentation. Instead of criticizing all the time, people should rather ask themselves if \
they have really tried to help, or have gone the easier route, consisting in the usual \
&quot;thanks a lot, unfortunately this stuff is not good enough for me, I'll come when it's \
ready&quot;. As far as I know, everytime I have asked somebody in the OSS community to help, he \
always responded that he was already busy with some other thing. I can reassure you that \
I'm tremendously busy too, and all the other people here are busy as well. /Gian \
Filippo. _______________________________________________ FreeNX-kNX mailing list <a \
href="mailto:FreeNX-kNX@kde.org">FreeNX-kNX@kde.org</a> <a \
href="https://mail.kde.org/mailman/listinfo/freenx-knx"> \
https://mail.kde.org/mailman/listinfo/freenx-knx</a> </blockquote></div>

_______________________________________________
FreeNX-kNX mailing list
FreeNX-kNX@kde.org
https://mail.kde.org/mailman/listinfo/freenx-knx

[prev in list] [next in list] [prev in thread] [next in thread] 