[etoys-dev] Bug tracking in Linux
milan.zimmermann at sympatico.ca
Tue Dec 22 23:35:16 EST 2009
On December 21, 2009, Bert Freudenberg wrote:
> On 21.12.2009, at 03:30, Milan Zimmerman (JIRA) wrote:
> > [ http://tracker.squeakland.org/browse/SQ-638 ]
> > Milan Zimmerman commented on SQ-638:
> > ------------------------------------
> > Hi Bert: I see you already discovered this recording problem long time
> > ago. Recording is not a problem on Windows (I tested it today as well),
> > so it seems either Unix VM or XO distribution specific. So maybe we do
> > not need equivalent ticket here...
> Maybe not. But maybe too ;)
> [ As a side note, it's preferable to have those kinds of discussion on the
> mailing list rather than in the bug tracker. It's good practice:
> http://producingoss.com/en/bug-tracker-usage.html ]
yes, I agree :)
> If the Squeakland developers want to know which problems exist with Etoys,
> then we expect the Squeakland bug tracker to be conclusive. So for that
> reason alone I'd think a ticket is warranted.
> The main question is who will see to it this gets fixed. It does sound like
> a VM problem to me. But since Etoys is one of the rare Squeak applications
> recording sound, we should keep track of it. Not necessarily fixing it
> ourselves, but trying to get the right people looking into it.
> So the problem was observed on a XO using the OLPC operating system. So
> dev.laptop.org is the right place to report the bug. But that OS is a
> Fedora derivative, and it uses the Fedora Squeak packages. So the OLPC
> Etoys maintainer should file an upstream bug with Fedora. But Fedora gets
> Etoys and Squeak from somewhere else, so Fedora's Etoys maintainer should
> file an upstream bug with Squeakland. Then someone at Squeakland who feels
> responsible for Linux VM issues with Etoys should file and monitor an
> upstream bug with squeak.org. Once a fix is provided it flows downstream
> from Squeak to Fedora to OLPC.
> (it's even a bit more complicated because
> the VM and Etoys come from different places, but you get the idea)
> Taking short cuts to this longwinded procedure is necessary in the short
> term because Etoys is just now getting established as a regular part of
> Linux distributions. But building that network of maintainers is
> essential. There are just too many ways to get Etoys to be able to track
> it all on our own:
I think you are right - and nice to have the bug lists in one place.
So, in conclusion, for the near future, bugs like
https://dev.laptop.org/ticket/9724 should be also added to
http://tracker.squeakland.org/browse . If you still think so :) , please add
it or let me know and I will add it. At least that is the single bug list
Squeakland observers track, can vote on etc.
> The situation is different on Mac and Windows where so far Squeakland is
> the only "vendor". But IMHO Squeakland cannot and should not try to be the
> vendor for Etoys on Linux. It's a Good Thing (tm) there are no RPMs nor
> DEBs on Squeakland for Etoys 4, because that would interfere with and
> undermine the efforts of maintainers in the distros.
I definitely agree with that. I know you have been helping a lot to engage
> This of course should
> be mentioned on the downloads page, and a tar ball should be provided so
> that packagers know where to start and get new releases from.
We mention a bit about distros here:
But yes, it should be on the download page ... and we should remove the old
versions from the download page, I think. But I don't know what exactly to put
in the tarball. If one of us remembers, let's bring it up on the next dev irc
> - Bert -
> etoys-dev mailing list
> etoys-dev at squeakland.org
More information about the etoys-dev