On Tuesday, August 02, 2016 08:16:15 PM Florent Daigniere wrote:
> This has been started three months ago now... and there hasn't been any
> visible progress (nothing on this mailing list) for the last two.
> What's up?
>
> It really makes the project look bad.
Ian was too busy to finish it for
On Tue, 2016-05-03 at 18:58 +, Ian Clarke wrote:
> I've written a proposal for how we can do this, based on my learnings
> over a
> decade and a half of managing software projects (mostly commercial).
> Feedback from the core team has been positive so-far, with the main
> objection
> being
On 06/05/16 00:10, x...@freenetproject.org wrote:
> On Friday, May 06, 2016 12:33:12 AM x...@freenetproject.org wrote:
>> At the current exchange rate, it would be 23.6 hours/week.
>> This is the average of what I had delivered during the past few months of
>> work. In other words, the $27500 was
On Thursday, May 05, 2016 11:51:17 PM Ian Clarke wrote:
> So can I assume that, since the conversation went off on some weird tangent,
> that everyone is comfortable with my proposal?
Sorry, I don't want to block the procedure, was merely trying to help Arne
with the numbers he didn't have.
I
So can I assume that, since the conversation went off on some weird tangent,
that everyone is comfortable with my proposal?
On Thu, May 5, 2016 6:35 PM, x...@freenetproject.org wrote:
On Friday, May 06, 2016 01:27:29 AM Arne Babenhauserheide wrote:
> Am Freitag, 6. Mai 2016, 00:33:12 schrieb
On Friday, May 06, 2016 01:27:29 AM Arne Babenhauserheide wrote:
> Am Freitag, 6. Mai 2016, 00:33:12 schrieb x...@freenetproject.org:
> > You wouldn't have needed to blindguess them manually
>
> It wasn’t blindguessing. It was giving the numbers how Freenet can hire
> peoplel without forcing them
Arne Babenhauserheide writes:
> xor at freenetproject.org writes:
>
>> On Tuesday, May 03, 2016 10:03:03 PM Arne Babenhauserheide wrote:
>>> As cost-metric I would suggest using full-time person-weeks. Reasons:
>>>
>>> - We have money for ~20 of these. Thatâs a number we can easily handle.
Arne Babenhauserheide writes:
> x...@freenetproject.org writes:
>
>> On Tuesday, May 03, 2016 10:03:03 PM Arne Babenhauserheide wrote:
>>> As cost-metric I would suggest using full-time person-weeks. Reasons:
>>>
>>> - We have money for ~20 of these. That’s a number we can easily handle.
>>> -
On Wed, May 4, 2016 1:45 PM, Arne Babenhauserheide arne_...@web.de wrote: Ian
Clarke writes:> Well, one important component of the allocation process is to
start with an
even
> allocation of points between all tasks,
Did I overlook that in the description?
Yes you did, from my proposal:
x...@freenetproject.org writes:
> On Tuesday, May 03, 2016 10:03:03 PM Arne Babenhauserheide wrote:
>> As cost-metric I would suggest using full-time person-weeks. Reasons:
>>
>> - We have money for ~20 of these. That’s a number we can easily handle.
>> - Cost is very different from salary (by
Ian Clarke writes:
> Well, one important component of the allocation process is to start with an
> even
> allocation of points between all tasks,
Did I overlook that in the description?
> As cost-metric I would suggest using full-time person-weeks.
>
> The problem is that some things we could
On Wednesday, May 04, 2016 12:40:38 AM x...@freenetproject.org wrote:
> It might also be OK to have this be less than 25% until we have satisfied
> our users with major new features being released.
Nevermind, I am probably wrong with "less than 25%":
I had only thought of the "code quality" part,
On Tuesday, May 03, 2016 08:14:18 PM Ian Clarke wrote:
> I agree that we can't be too granular with these tasks, if there are too
> many then people will have trouble allocating intelligently between them.
> However, I don't agree that if a task is less than a week's work that we
> should
On Tuesday, May 03, 2016 10:03:03 PM Arne Babenhauserheide wrote:
> As cost-metric I would suggest using full-time person-weeks. Reasons:
>
> - We have money for ~20 of these. That’s a number we can easily handle.
> - Cost is very different from salary (by roughly factor 2). Time isn’t.
Our
On Tue, May 3, 2016 3:03 PM, Arne Babenhauserheide arne_...@web.de wrote:The
intro shows values from 1 to 100, the later description uses 1 to
1000.
Oops, fixed.
I do not think 1000 points are useful in terms of limited
volunteer time resources. How about making it 20? This then requires
Ian Clarke writes:
> I've written a proposal for how we can do this, based on my learnings over a
> decade and a half of managing software projects (mostly commercial).
> Feedback from the core team has been positive so-far, with the main objection
> being that it may be too elaborate for our
On Tue, May 3, 2016 2:14 PM, Michael Grube michael.gr...@gmail.com wrote:
I think it can be implemented
easily enough with intelligent use of Google Docs and a little bit of elbow
grease, which I'm ok with providing if others can help.
On Tue, May 3, 2016 at 2:58 PM, Ian Clarke wrote:
> I've written a proposal for how we can do this, based on my learnings over
> a
> decade and a half of managing software projects (mostly commercial).
> Feedback from the core team has been positive so-far, with the main
I've changed my mind to support this! :)
The 6 months of fundraising difficulties have left me in a state of very very
high fear that the project may fail.
My anxiety has lifted me into a state of perhaps somehow insane fear that a
re-discussion of the project's goals could cause a failure as
I've written a proposal for how we can do this, based on my learnings over a
decade and a half of managing software projects (mostly commercial).
Feedback from the core team has been positive so-far, with the main objection
being that it may be too elaborate for our needs. I think it can be
20 matches
Mail list logo