Re: Getting Gnome Accessibility in Garnome
- From: David Bolter <david bolter utoronto ca>
- To: Bill Haneman <bill haneman sun com>
- Cc: Jeff Waugh <jdub perkypants org>, Rodd Clarkson <r-list clarkson id au>, Gnome Accessibility List <gnome-accessibility-list gnome org>, List Garnome <garnome-list gnome org>
- Subject: Re: Getting Gnome Accessibility in Garnome
- Date: Mon, 31 Mar 2003 08:34:48 -0500
Bill Haneman wrote:
Hi David:
Sorry Simon/David, slip of the fingers. Simon Bates and David Bolter
are the maintainers.
Yes, Simon Bolter is our borg name.
I think there is a misunderstanding about releases and announcements
here; these releases are primarily for the development community and a
few early-adopters, and are eventually used by distros if they believe
that quality and utility warrant.
Releases _do_ need to be announced, but only to aliases read primarily
by the GNOME developer community. There is no implication of
"readiness" nor suitability in such announcements. On the other hand,
it's generally not considered appropriate to release or bundle projects
(via distros or "stable" community releases like 2.2.0 and 2.4.0) that
have not already gone through several such internal 'releases'.
David, can we get the go-ahead to make a GOK tarball for (GNOME's
definition of) such a release? I think it's important to do this now if
we want GOK to be considered part of GNOME at any point in the near
future.
Understood and yes please! Fortunately, Simon has already done the
build configuration for 'make dist'. I would be more comfortable if he
was involved with at least the first few releases.
(BTW we need to update gok's version numbers. What is the rule of thumb
here?)
cheers,
David
- Bill
On Mon, 2003-03-31 at 14:10, David Bolter wrote:
Jeff Waugh wrote:
<quote who="Bill Haneman">
Up until now, the gok team has been reluctant to make any actual
'releases' (though GOK itself is working reasonably well). However in
recent conversations with Simon Bolter of the University of Toronto,
co-maintainer of GOK, it sounded as though they could be persuaded to
start making releases.
ObligatoryReleaseTeamComment: Making releases is a really good habit to get
into, 'release early, release often', etc. :-) If you've got code out in
wide use, you can prioritise your fixes more easily - 'real' feedback really
helps.
Just a quick note to say that we agree with making frequent "releases"
to the gnome community. We wanted to wait on making a wider
announcement until gok is really solid. Oh, and that is "Simon Bates"
you probably spoke with :-)
cheers,
David Bolter
The same goes for the gnopernicus team; Draghi, Adi, are you guys ready to
start uploading tarballs (i.e. "make dist") to ftp.gnome.org?
Just a recommendation - it's worth making sure your module distchecks before
you make a release. Sometimes painful, but worth it in the end.
As for the rest of the accessibility stack, it should be ready for GARNOME
now as far as I know. I would include the 'at-poke' module also, in the
developer platform tarballs (not desktop), (at-poke was largely written by
Michael M) since it's very useful as a testing and diagnostic tool for the
developer platform.
Cool, I'll add at-poke.
Thanks,
- Jeff
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]