On 23/06/10 21:49, Raistmer wrote:
There is a huge difference between feedback and bashing.
We aren't talking about feedback. Feedback is constructive.
[...]
BTW, just one more thought on topic:
there are 2 kinds of feedback actually.
Feedback on technical actions were done - bug
As I still know very little about what will happen about the new credit
proposal could I please ask a few questions in the hope that others may be
able to clarify the situation.
1. I assume that Seti is still using new credits. Has the trial of new
credits there been considered successful?
2.
On 6/24/10, Maureen Vilar mavi...@gmail.com wrote:
3. Are there any plans yet to add the code for the new credits to a future
Boinc server version?
The BOINC server doesn't have versioned releases. Projects usually run
the latest code available (from 'trunk'). There is also the
'server_stable'
On 24-Jun-2010 8:36 AM, Maureen Vilar wrote:
As I still know very little about what will happen about the new credit
proposal could I please ask a few questions in the hope that others may be
able to clarify the situation.
1. I assume that Seti is still using new credits. Has the trial of
On 6/24/10, David Anderson da...@ssl.berkeley.edu wrote:
On 24-Jun-2010 8:36 AM, Maureen Vilar wrote:
8. Can anyone explain how the new proposal works?
http://boinc.berkeley.edu/trac/wiki/CreditNew
That's an implementation plan, not an explanation. It mentions what
database fields will be
This is really addressed to the whole BOINC development team, but I suppose to
David in particular.
I wonder if it would be possible for you to post, hopefully in the
not-too-distant future, a summary of where we're up to with the whole
'CreditNew' bundle (which of course includes important
At the same time, I think it's time that some of the noisier
volunteers grew up.
First, we need to keep in mind that BOINC and CPDN are different. I
understand the problem in the SETI forums, but I wouldn't think that
needs to be said here.
Second, projects like s...@home make a number of
No one like to recive negative feedback, especially for poorly implemented
stuff (and even softly speaking it was poorly implemented on SETI main
indeed). But w/o such feedback next attempt would be even worse. BTW, bugs
like ridiculous quota numbers still reported even now...
I'd go so far
There is a huge difference between feedback and bashing.
We aren't talking about feedback. Feedback is constructive.
When most of the threads talk about blame that isn't feedback, that's
a witch-hunt.
... and at some point, people get tired of reading the bashing, get
tired of the witch
I have one more comment on this subject, and then I'll not comment further.
Milo Bloom said The first sign of a nervous breakdown is when you think
your work is terribly important.
This isn't like mail servers or web sites or DNS where everything has to
work perfectly -- or else!
It is a
I hear what you're saying.
What you're saying is that a project *IS REQUIRED* to provide enough
work to keep every host fully occupied at all times.
... because that's the only thing that will keep some volunteers from
getting so very angry.
I know of no organization that relies on volunteers
I hear what you're saying.
What you're saying is that a project *IS REQUIRED* to provide enough
work to keep every host fully occupied at all times.
... because that's the only thing that will keep some volunteers from
getting so very angry.
Actually not. I just want to point out that
... and that's the problem.
If you say there is a problem that's respectful.
If you go straight to they did this on purpose, just to cause trouble
for the volunteers then that is not respectful.
-- Lynn
On 6/23/2010 1:21 PM, Raistmer wrote:
I hear what you're saying.
What you're saying is
... and that's the problem.
If you say there is a problem that's respectful.
If you go straight to they did this on purpose, just to cause trouble
for the volunteers then that is not respectful.
-- Lynn
Agree.
And when you give notice of changes before breaking all system down and some
I know of no developer who intentionally breaks things.
Suggesting that an operational project would intentionally install
broken software is disrespectful in the extreme.
So is the term geek minority -- which I've now objected to twice.
Some volunteers strictly follow what was asked, and
There is a huge difference between feedback and bashing.
We aren't talking about feedback. Feedback is constructive.
When most of the threads talk about blame that isn't feedback, that's a
witch-hunt.
BTW, just one more thought on topic:
there are 2 kinds of feedback actually.
Feedback
...@ssl.berkeley.edu
Cc: BOINC Developers Mailing List boinc_dev@ssl.berkeley.edu
Sent: Wednesday, June 23, 2010 3:47 PM
Subject: [boinc_dev] Current status of CreditNew?
This is really addressed to the whole BOINC development team, but I suppose
to David in particular.
I wonder if it would
I can't think of a bigger disaster than software development by
democratic votes.
Sorry, you missed my point :( I didn't propose _to ask_ participants do
changes or not, where you read that? I proposed to adequately _INFORM_
participants of what is going to be and what happened. As it's well
18 matches
Mail list logo
