| 1 |
Arun Raghavan <ford_prefect@g.o> posted |
| 2 |
48A71F65.1080908@g.o, excerpted below, on Sun, 17 Aug 2008 |
| 3 |
00:11:41 +0530: |
| 4 |
|
| 5 |
> And then there's the sunrise overlay [1]. |
| 6 |
|
| 7 |
Yes, but sunrise doesn't (didn't?) take any packages already in the |
| 8 |
tree. If it's not getting updated in-tree, however, and the only block |
| 9 |
from it being in sunrise is that it's in-tree already (that is, there's |
| 10 |
someone already actively willing to work with it in sunrise, and only |
| 11 |
can't because it's in-tree), then that could be support for removing it |
| 12 |
from the tree. |
| 13 |
|
| 14 |
But better than that would be finding a dev to proxy-maintain it in the |
| 15 |
tree, since the above assumes a user already willing to do the real |
| 16 |
work. The difference is in-tree with a named proxy-maintainer, or in- |
| 17 |
sunrise with the sunrise devs acting as proxies. Since in-tree is higher |
| 18 |
visibility and availability, that's definitely preferred, and if it's |
| 19 |
already in-tree, the only blocker is then finding someone to be that |
| 20 |
named proxy-maintainer. |
| 21 |
|
| 22 |
-- |
| 23 |
Duncan - List replies preferred. No HTML msgs. |
| 24 |
"Every nonfree program has a lord, a master -- |
| 25 |
and if you use the program, he is your master." Richard Stallman |
Archives