| 1 |
I'm not a gentoo dev (just a satisfied user), but I lurk on this list. |
| 2 |
|
| 3 |
I was at PyCon last month. I would estimate that about 40% of the |
| 4 |
people there ran linux on their laptops. The most popular distros |
| 5 |
were gentoo and ubuntu. (Not this is not a scientific study, just my |
| 6 |
observations from talking to people there). While I was there the |
| 7 |
person next to me starting hacking the ebuild classes to handles eggs |
| 8 |
(so he could emerge turbogears). I talked to at least 3 others who |
| 9 |
were running gentoo. I asked all of them if they had worked on |
| 10 |
portage. Most said "No, the code is a little scary". (I'll concur |
| 11 |
with that sentiment, as the code doesn't feel very pythonic). |
| 12 |
|
| 13 |
If you want to attract more developers (python people), a few things are needed: |
| 14 |
|
| 15 |
* Portage documentation. How the innards work. There is very little |
| 16 |
docs/comments in the portage code |
| 17 |
* Unittests - without this how do I know that my change to portage |
| 18 |
didn't break someone else's corner case |
| 19 |
* Refactoring into a more pythonic style. Note that this is pretty |
| 20 |
hard without unittests. |
| 21 |
|
| 22 |
Take this as a grain of salt, from an observer, who believes that |
| 23 |
there are a lot of potential users (who know python), and who could |
| 24 |
easily contribute, if the bar was lowered a bit. (Or steps were |
| 25 |
provided to reach a little higher ;)) |
| 26 |
|
| 27 |
-matt |
| 28 |
|
| 29 |
-- |
| 30 |
gentoo-dev@g.o mailing list |
Archives