| 1 |
> whoa right there. a lot of people are on crack, too. especially where |
| 2 |
> concerns a bunch wondering when someone is going to hurry up and give |
| 3 |
> them something for free. |
| 4 |
> |
| 5 |
> enough software in this world is tossed over the fence according to a |
| 6 |
> schedule. i don't need any more software that was developed to a |
| 7 |
> schedule. i've got enought of that at work. i need software that is |
| 8 |
> actually ready when it is ready, whenever that is. i'm glad there is |
| 9 |
> some. eye on the ball, not some bean counter's stopwatch. |
| 10 |
> |
| 11 |
> i don't know how realistic it is, but it seems to be expected to have a |
| 12 |
> schedule for software if someone is paying for the development. and that |
| 13 |
> causes an awful lot of crappy software to get developed. not to mention, |
| 14 |
> missed schedules anyway. a pmi study showed only 27% of software |
| 15 |
> projects meet schedule (up from 19% a decade ago). so much for software |
| 16 |
> schedules. what works for highway construction doesn't have much to do |
| 17 |
> with software. |
| 18 |
> |
| 19 |
> a ballpark figure has been given more than once, and missed more than |
| 20 |
> once. i say, enough. it's plain to see there is no point in such straw |
| 21 |
> men, especially in free, volunteer, community efforts. obviously it will |
| 22 |
> be ready when it's ready. and only when it's ready should i want it. -i |
| 23 |
> wouldn't have it any other way!- in certain circumstances i would expect |
| 24 |
> to hear, "are we there yet?" from the backseat. this is not one of them. |
| 25 |
|
| 26 |
But i have not told the developers to hurry! I'm sure that it's better |
| 27 |
to wait until the work is finished that have a bugged or incomplete product. |
| 28 |
I'm only sayng that have developers giving a feedback once a week about |
| 29 |
what was done and what todo (even 4 rows of plain text could do the |
| 30 |
work!) should be nice. |
| 31 |
And i don't need a schedule with calendar! Only what is done and what not. |
| 32 |
|
| 33 |
|
| 34 |
>>In fact the status of the development is covered by an incredible mistery... |
| 35 |
> |
| 36 |
> |
| 37 |
> that is so untrue. bugs.gentoo.org. it's completely transparent. |
| 38 |
|
| 39 |
But doesn't give a complete view of the status of the development. |
| 40 |
|
| 41 |
Pelux |
Archives