1 |
Hi, |
2 |
|
3 |
The Xbox2 is rumored to be powered by 3 IBM 980 cpu's (dual core G5), |
4 |
same goes for the Playstation III. The current PS2 has a MIPS-SMP |
5 |
architecture. The current Xbox has on a slightly modified Intel |
6 |
architecture microprocessor. |
7 |
All of them have very advanced GPU. |
8 |
|
9 |
On 24 May 2004, at 19:48, Jon Portnoy wrote: |
10 |
|
11 |
> I'm looking for comments on what, exactly, constitutes a platform worth |
12 |
> recruiting developers for. |
13 |
|
14 |
Historically we've used architecture/platform words in the following |
15 |
contexts: |
16 |
|
17 |
- architecture: intel, ppc, power, mips, sparc, ... 32bit/64bit |
18 |
|
19 |
- platform: windows, linux, bsd, cygwin, OS X, Solaris... |
20 |
|
21 |
For the game consoles mentioned above, the question whether or not |
22 |
devrel can reject devs specifically for work on a game console, depends |
23 |
on whether the architecture in question supports the game console. |
24 |
Devrel should be able to impose extra requirements (in coordination |
25 |
with the mentor!!!) when the area of responsibility for the new dev |
26 |
includes only supporting the niche (or just one ebuild... things like |
27 |
that). The management is responsible for taking care of new |
28 |
architectures/platforms. |
29 |
|
30 |
My opinion is that if there are people wanting to work on something |
31 |
that is legal to support, and that already may be supported by other |
32 |
distributions, why not? ( A new arch/platform needs to be discussed by |
33 |
the management. gentoo-alt provides help during the first |
34 |
days/weeks/months for new archs/platforms wanting the help ) Devrel |
35 |
should decide whether just supporting a niche market is enough to |
36 |
qualify as a new dev (needs to happen in coordination with the mentor). |
37 |
|
38 |
I'm personally inclined not to support Xbox officially for legal |
39 |
reasons: It's not because you can't prove that something is not legal, |
40 |
that it is legal. |
41 |
|
42 |
> I like to be extremely careful when selecting |
43 |
> new developers both to keep the bar set high for developer status and |
44 |
> for security reasons (every new account is a potential attack vector, |
45 |
> especially when you consider that a developer's box could be |
46 |
> compromised |
47 |
> and used to get in), so I'm very inclined to reject requests for new |
48 |
> developers |
49 |
|
50 |
A QA team/tool monitoring contributions would help alot. |
51 |
|
52 |
We already support a huge amount of niche markets. I don't believe the |
53 |
argument that 'devs for a niche market get rejected per definition' |
54 |
argument holds. I do agree that devrel can impose extra requirement for |
55 |
applications when the area of resp. for a new dev is too narrow (or too |
56 |
ambitious). All of this should happen in coordination with the mentor |
57 |
of course. |
58 |
|
59 |
The security argument doesn't hold either (cfr. below). |
60 |
|
61 |
> who will only be working on a very small niche like XBox |
62 |
> support (especially when it's really just embedded x86 and it seems |
63 |
> like there wouldn't be too much maintainance work involved). I would |
64 |
> also be inclined to reject developers for, say, m68k. |
65 |
|
66 |
Well, I have m68k machines in my basement. I doubt that a lot of m68k |
67 |
users would be interested in a from source approach. The only thing we |
68 |
need to support m68k users is a modified bootloader (floppy), and maybe |
69 |
some patched kernel ebuild. If somebody wishes to maintain that and do |
70 |
some ppc work as well, he's welcome. |
71 |
|
72 |
I think that people with AMD64 machines allowing half the world to work |
73 |
on their fast machines pose a bigger security risk than one user |
74 |
ambitious enough to install gentoo on his favorite 33mhz 68K machine |
75 |
loaded with 24M ram and (maybe) a 512M hard disk. |
76 |
|
77 |
Kindest regards, |
78 |
|
79 |
Pieter Van den Abeele |
80 |
|
81 |
|
82 |
-- |
83 |
gentoo-dev@g.o mailing list |