Mailinglist Archive: opensuse-project (441 mails)

< Previous Next >
Re: [opensuse-project] [openFATE] What should we do for the next step ?
  • From: "Rajko M." <rmatov101@xxxxxxxxxxx>
  • Date: Thu, 19 Mar 2009 08:57:49 -0500
  • Message-id: <200903190857.49746.rmatov101@xxxxxxxxxxx>
On Thursday 19 March 2009 12:17:27 am Satoru Matsumoto wrote:
...
During the meeting, I felt we need to do a brainstorming about what we
should and can do for openFATE and make things much clear. I think I'm
not the only one who don't clearly understand what should be done for now.

I guess, give ideas:
- how to organize screening,
- how to improve interface

For instance where are new entered features?

They need attention (screening) first.
Browse is not word that describes what I see on next screen.
It see advanced search.

Removing all but tag New, I hit first problem in the very first feature
https://features.opensuse.org/100285 .
Full description is in http://bugzilla.suse.de/show_bug.cgi?id=46604 which has
no redirect to Novell bugzilla bug number.

Second, Unconfirmed for new feature and New for screened can be common tag in
bugzilla, but it is far from self explanatory.

For me it would be better that New is new entered, Screened for feature that
someone of screening team have seen, asked requester for additional
explanation if necessary, and it is ready for responsible person in
development team to read and consider for acceptance, or rejection.

Features can't be Unconfirmed, they are not bugs.

Local definition of words, that deflects from standard one in vocabulary, is
common practice in programming, where for sake of brevity, or distinction
from object with similar names, no one should expect strict grammar and word
interpretation. That way should not be used in public interface where
non-coders should understand messages.

The other problem that I hit some days ago was that I couldn't convince search
to give me feature that I was looking at. None of words in title or
description gave that feature as result.

For example, we talked about setting tags to each features. Do we need
some typical keywords for tags, such as installation, update, kernel,
etc. ? Team members can freely and randomly set tags when they have time ?

There are some tags when you come to the main openFATE page.
It would be nice to know how method that selects and prints tags on main page
works.

At the beginning of the meeting, Bryen asked: Are we still only allowing
openSUSE members to enter requests?

I'm also wondering why we have to restrict adding new features only to
Members. Just because lack of human resources ? As long as I can
understand, Members are just kind of contributers who approved by
Board, but not delegates in any sense, because they are *not cosen* by
other contributers and users. There are many contributers who are *not
yet* Members. If they aren't given chances to add new features, IMHO,
openFATE is half-openFATE. I'd like to advocate, even mere users should
be able to add new features, because that is the first step for them to
become contributers. Of cource I don't mean to blame project on that.
What I want to say is: if there are some reasons why we have to
restrict, we should provide convincing explanations.

IMHO, as long as interface is bugzilla like, where inexperienced requesters
can enter many duplicate features and they can't be merged to the first one
and deleted, making browsing nightmare, creating new features should be
restricted. Although, being confirmed openSUSE member is, for sure, not
guarantee that someone has skills to handle bugzilla, or openFATE interface.

Finally, should we discuss such things on this list or prepare the Wiki
page for that ?

IMHO, for now I would keep discussion here, to see what to put on the wiki.

--
Regards, Rajko
--
To unsubscribe, e-mail: opensuse-project+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-project+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups
References