[9fans] central list of bugs

Hello,

is there any central place, where there is a list of known
bugs/potential bugs that sould be corrected/thought about?

During my short play with plan9 I encountered several bugs/bug-like
cases. They were marginally discussed in this forum, too, amongs those
are:

-- an obvious bug with selecting an already closed hiden window in a rio menu
-- questionable behaviour of acme/sam not scrolling in the case 'Edit
/old/c/new/'

Maybe some others.
For me it'd be interesting to see such a list.

Ruda

i think it was something like /dev/null :D

On Mon, Oct 27, 2008 at 9:39 AM, Rudolf Sykora <rudolf.sykora@gmail.com> wrote:[color=blue]
> Hello,
>
> is there any central place, where there is a list of known
> bugs/potential bugs that sould be corrected/thought about?
>
> During my short play with plan9 I encountered several bugs/bug-like
> cases. They were marginally discussed in this forum, too, amongs those
> are:
>
> -- an obvious bug with selecting an already closed hiden window in a rio menu
> -- questionable behaviour of acme/sam not scrolling in the case 'Edit
> /old/c/new/'
>
> Maybe some others.
> For me it'd be interesting to see such a list.
>
> Ruda
>
>[/color]

There is an errata page on the wiki, however
I doubt there is anyone looking at this and fixing
the bugs.

The bottom line is if you discover a bug, and it anoys you,
fix it (you have the source). If you are feeling friendly
submit a patch.

Sorry if this seems harsh, but there is no support team behind
Plan9. I am sure we would all be delighted if somone was willing
to spend their time doing arbitary plan9 bug fixes, but I don't
know of such a person.

-Steve

* Rudolf Sykora <rudolf.sykora@gmail.com> wrote:

Hi folks,
[color=blue]
> is there any central place, where there is a list of known
> bugs/potential bugs that sould be corrected/thought about?[/color]

A bug tracker would be fine.
If the community's interested, I could setup some issue tracker
(bugzilla ? trac ?)


cu
--
----------------------------------------------------------------------
Enrico Weigelt, metux IT service -- [url]http://www.metux.de/[/url]

cellphone: +49 174 7066481 email: [email]info@metux.de[/email] skype: nekrad666
----------------------------------------------------------------------
Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------

The 'community' (whatever that is) is not interested.

uriel

On Thu, Oct 30, 2008 at 4:51 PM, Enrico Weigelt <weigelt@metux.de> wrote:[color=blue]
> * Rudolf Sykora <rudolf.sykora@gmail.com> wrote:
>
> Hi folks,
>[color=green]
>> is there any central place, where there is a list of known
>> bugs/potential bugs that sould be corrected/thought about?[/color]
>
> A bug tracker would be fine.
> If the community's interested, I could setup some issue tracker
> (bugzilla ? trac ?)
>
>
> cu
> --
> ----------------------------------------------------------------------
> Enrico Weigelt, metux IT service -- [url]http://www.metux.de/[/url]
>
> cellphone: +49 174 7066481 email: [email]info@metux.de[/email] skype: nekrad666
> ----------------------------------------------------------------------
> Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
> ----------------------------------------------------------------------
>
>[/color]

> The 'community' (whatever that is) is not interested.[color=blue]
>
> uriel[/color]

How can this man talk for others?!
Ruda

I have a strong believe that without some central bug-tracking (so
that anybody can know about where there is a bug) this project will
only stay where it is.

On Fri, Oct 31, 2008 at 21:24, Rudolf Sykora <rudolf.sykora@gmail.com> wrote:[color=blue][color=green]
>> The 'community' (whatever that is) is not interested.
>>
>> uriel[/color]
>
> How can this man talk for others?![/color]

it's a tradition.
Or he might be making an attempt at a (bad) joke, pretending to be the only
member of the community. Or he was just grumpy. having not had his
morning coffee. Go figure.

[color=blue]
> I have a strong believe that without some central bug-tracking (so
> that anybody can know about where there is a bug) this project will
> only stay where it is.[/color]

unfortunately, I am afraid you might most probably be right.

My recommendation would be that if you want to do it, then just do it.
Fire up the issue tracker, and give the link to the tracker here.
If some people use it, then it's great. If they don't, at least you tried.

Plan 9 fans are either really reactive and enthusiastic, or really dull and
annoying. (sorry folks. Though I rarely interact on this list, I used to
have a great time reading it. But the past year has seen it be crippled by
useless and childish bashing, shadowing half of the interesting threads.
my hats off to the people who are helpful around here, and not only by
means of their technical expertise).
Just don't let the latter take your motivation away, and don't hold your
breath when you expect a reaction.

Thanks for suggesting something constructive.

--
Laurent Malvert [laurent.malvert@gmail.com]

On Thu, Oct 30, 2008 at 10:51 AM, Enrico Weigelt <weigelt@metux.de> wrote:[color=blue]
> * Rudolf Sykora <rudolf.sykora@gmail.com> wrote:
>
> Hi folks,
>[color=green]
>> is there any central place, where there is a list of known
>> bugs/potential bugs that sould be corrected/thought about?[/color]
>
> A bug tracker would be fine.
> If the community's interested, I could setup some issue tracker
> (bugzilla ? trac ?)
>[/color]

I think its a great idea. Folks seem to make good use of the
inferno-os bug tracker. I took the initiative and setup a google code
project to serve this purpose:

[url]http://code.google.com/p/plan9-os[/url]

-eric

* Eric Van Hensbergen <ericvh@gmail.com> wrote:
[color=blue]
> I think its a great idea. Folks seem to make good use of the
> inferno-os bug tracker. I took the initiative and setup a google code
> project to serve this purpose:
>
> [url]http://code.google.com/p/plan9-os[/url][/color]

Great. Perhaps you could add separate categories for several
projects, eg. v9fs, libmixp, etc.

For some strange reason, I can't create tickets - it always wants
me to re-login endlessly (even I am already logged-in) :(


cu
--
----------------------------------------------------------------------
Enrico Weigelt, metux IT service -- [url]http://www.metux.de/[/url]

cellphone: +49 174 7066481 email: [email]info@metux.de[/email] skype: nekrad666
----------------------------------------------------------------------
Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------

On Sat, Nov 1, 2008 at 1:57 PM, Enrico Weigelt <weigelt@metux.de> wrote:[color=blue]
> * Eric Van Hensbergen <ericvh@gmail.com> wrote:
>[color=green]
>> I think its a great idea. Folks seem to make good use of the
>> inferno-os bug tracker. I took the initiative and setup a google code
>> project to serve this purpose:
>>
>> [url]http://code.google.com/p/plan9-os[/url][/color]
>
> Great. Perhaps you could add separate categories for several
> projects, eg. v9fs, libmixp, etc.
>[/color]

Ah - well, that's sort of a different topic. v9fs for instance, has
its own bug-tracking as part of kernel.org. I'm uncertain of whether
the various server/client implementations maintain their own tracker.
It does make some sense to have some sort of central repository for
such bugs as in many cases the symptom of the problem can't be
isolated to a component (v9fs versus the server for instance) very
easily. I'm less sure of how to deal with this in an appropriate
fashion though... Suggestions welcome, I suppose we could include a
category for such outside tools in plan9-os, but I was thinking it was
more of a Plan 9 proper bug reporting facility.
[color=blue]
> For some strange reason, I can't create tickets - it always wants
> me to re-login endlessly (even I am already logged-in) :([/color]

Weird, I didn't have a problem -- I'll verify that permissions are
setup to let anyone post issues. Anyone wanting access to the project
just email me and I'll be happy to add you.

-eric