[Foresight-devel] Re: 2.0.4 lite installation woes...

Martin Bähr mbaehr at email.archlab.tuwien.ac.at
Mon Aug 18 10:01:29 EDT 2008


On Mon, Aug 18, 2008 at 07:55:13AM -0400, Jayson Rowe wrote:
> We DO care actually - all feedback is very important.
> 
> I would recommend however, to ensure that your issues are addressed,
> please enter issues into JIRA (https://issues.foresightlinux.org) so
> that these problems can be tested and verified by others in the
> community. A mailing list is appropriate for asking questions, and
> having discussions, but not for reporting issues.

well, i am implicitly asking the question: which of these issues should
i report first? there are to many to report all of them. i'd be busy all
day just with reporting. i don't have that time, so i am sending them
here so they don't get completely lost. 

> I've read through your posts to the mailing lists, and while some may
> be legitimate issues, others may be configuration issues, or problems
> with your profile.

well, see, figuring out which are legitimate issues would be useful,
then i could focus on reporting those.

> One thing you report, for example is that
> "GNOME-Do" doesn't do "anything" when selected from the menu - it
> probably does, it just starts hidden and you bring it up by the key
> combintation <super>+<space>.

and i am supposed to know that from where?
a user who sees gnome-do for the first time has no chance of knowing
this.

any click anywhere should generally provide feedback. and if it is only
a message telling the user: gnome-do has been started, here is how you
use it:...

if gnome-do is actually a daemon then it should not even be in the menu.
beagle is not in the menu either, is it?
but on the other hand there is no reason why certain actions should only
be available through a keyboard shortcut. why not have a menu entry too?

> Also, filing separate issues in JIRA will help folks help you by
> breaking your problems out one by one - when you list so many problems
> in a single email, it makes it harder to follow.

oh, i don't mean them to be followed, just a quick going over like you
are doing to indicate which are the bits worthy to work with and report.

> Any issues you file, will help other (new) users of Foresight as well.

that's actually my main motivation for bringing these issues up in the
first place, for myself most of those issues are just annoyances that i
can work around somehow. and once i have a workaround i tend to forget
the problem, that's why it is important to write it down right away
without having to go through the effort of filing a proper report.

greetings, martin.
-- 
cooperative communication with sTeam      -     caudium, pike, roxen and unix
offering: programming, training and administration   -  anywhere in the world
--
pike programmer   working in china                      community.gotpike.org
unix system-      iaeste.(tuwien.ac|or).at                     open-steam.org
administrator     caudium.org                                    is.schon.org
Martin Bähr       http://www.iaeste.or.at/~mbaehr/


More information about the Foresight-devel mailing list