| 1 |
> The main issue with the current approach is that proposals |
| 2 |
> are forgotten. |
| 3 |
|
| 4 |
Mmm ... are they really forgotten, or is it more a case that they fade away |
| 5 |
because the work to implement them just doesn't get done? If ideas don't |
| 6 |
gather enthusiasm or momentum, then perhaps it is more healthy for them to |
| 7 |
die, than to be half-heartedly implemented by someone working to a 'todo' |
| 8 |
list drawn up by others? |
| 9 |
|
| 10 |
> The case with a management decision is not so much a problem as |
| 11 |
> management also must get the developers along. If it doesn't |
| 12 |
> people walk away and fork |
| 13 |
|
| 14 |
Project forks are typically political, not just technical. They're about |
| 15 |
power and control. |
| 16 |
|
| 17 |
Managers should be there to make it *easier* for developers to do |
| 18 |
development. Managers don't do the work - it's the developers that do. Any |
| 19 |
agenda for a project should be defined by leaders. Management and |
| 20 |
leadership are very different roles! When management insist that only |
| 21 |
*they* can be the leaders, that's when developers start to vote with their |
| 22 |
feet. |
| 23 |
|
| 24 |
Best regards, |
| 25 |
Stu |
| 26 |
-- |
| 27 |
|
| 28 |
|
| 29 |
|
| 30 |
-- |
| 31 |
gentoo-dev@g.o mailing list |
Archives