Hi,
Le 13 sept. 08 à 03:47, tora - Takamichi Akiyama a écrit :
The point is, that the builds thare are officially released to the
end user are well tested - this has not much to do with the the
question who initially provided the builds.
I have a slightly different idea on that. A point of mine is a
system. IMHO, a software product that will be distributed all over
the world
should be processed by at least certain number of people.
+1
We can trust Maho, but we cannot truly trust the system of current
build system that one person does everything regarding build process.
Exact.
For example, development process of banking system has to be
checked by several colleges and/or auditors. Even they trust each
others, but
they are not able to completely check the inside of the product at
machine code level.
Exact.
So what I would like to suggest here is to devise a way to improve
build system from a type of rely-on-one-person to done-by-a-team.
Here is the point, and I fully agree with you. As a Community
product, the Mac OS X official builds should never be associated to
one people.
Other point: I asked several times Maho to provide us figures about
the number of downloads by locales, and either he refused, or was
never able to provide any.
This is not acceptable, and strict and open rules must be defined.
For *all* builders, including Sun.
Mac OS X Intel by Sun
3.0rc1 en-US da de es fr gl it ja ko nl pl pt-BR ru sl sv vi zh-
CN zh-TW
Mac OS X Intel by Maho
3.0rc1 (all languages)
A set of Sun's builds covers all languages except ga or mk, which
have been released during the era of 2.x.
How can we adapt to the new situation?
Let's proceed as a real Community ? IMHO, it is to the Mac porters
Team to improve the situation, and then the point can be debated
again here afterwards.
FYI, there are weekly Mac port IRC meetings (there is a dedicated
wiki page). Things can be discussed and defined precisely during one
of them. Supposing people will be involved (else, it means the
Community has no credibility, and Sun is the only candidate )
To avoid long discussions, traffic of influence or chaotic situation,
and regarding the number of regular attendees at the Mac porters IRC
meetings, the 10 most regular attendees (whoever they are) max voting
will simplify the things. Indeed, regular contributor to the Mac port
have a right vision of the problem. We can include the candidates for
the vote.
I'm pretty sure, this will not take too much of time, and proceed
like that will add more legitimity to the current candidates.
More precisely Mac port Team (who is not Maho only, but does include
him) will propose rules, validate how Mac OS X builds could be build,
and who can build them during Mac porters IRC meetings.
The minimal rules I see are about :
The Mac porters Team, after a vote, can modify the list, under the
conditions above.
Several people can build the Aqua version: based on "Bus Factor
Effect" , one builder can be replaced. This is the most safe for
vanity, and more.
Note: it is extremely important to keep the door open to new
potential candidates, who will have to convince the Mac port Team to
add him.
The Baseline : currently Tiger (would be a mistake to change )
The architecture : propose (probably cloned), but one solution for
Intel, and one for PowerPC
The required configuration : ( to be defined more precisely )
The build process: I think the script currently used is a good candidate
Which locales can be built: due to limited bandwidth between regions
of the earth, I propose to define default regions, and regional build
Other need: provide OPEN figures and statistics about the downloads,
to help for a strategy, and maybe save disk space on the server.
(propose other ideas)
I seriously think, that once the Mac port will have a better process
to propose, we will progress.
Waiting, I must admit, the community needs to improve its
credibility, and IMHO Sun is a more seious candidate *today* (would
be great to see things change ).
Of course, this proposal can be adapted, amended, modified .. :-)
Opinions ?
Eric Bachard
--
qɔᴉɹə
