On 3/19/06, Joe Kramer <cckramer gmail.com> wrote:
> Usable Mantis is fork of Mantis based on 1.0.1 release
code.
I assume that, since yours is the Usable Mantis, we are all
working on
the "Unusable" one. Maybe we should all consider
switching...
> The main scope of the project is Making Mantis usable
by wider audience,
> non-IT, non-technical users. As well as fixing many
bugs and making other
> improvements along the way.
What exactly prevents you from just participating to the
regular
Mantis development?
Moreover, exactly which fixed bugs are you referring to ?
>
> Of course forking is not so good and both projects
would benefit if we merge
> our code into Mantis core and join Mantis project.
Again, if you recognize this, WHY did you started such
effort in the
first place?
> Problem is, among our improvements we added the Issue
Type attribute to
> Mantis. We can't live without Issue Type and Mantis
define all issues as
> just "Issue". We needed adding Bug, Change
Request, Feature request, etc.
Considering the "Feature" type is already listed
among the Severity
values, I think a more natural place for this customization
would have
been there. I'm sure that, if you bothered to ask in the
list before,
someone else would have suggested something even better.
> issue types. We had to reuse "Priority"
which wasn't used by our projects
> and rename it to "Issue Type" adding
different values and such.
So, if I switch to your mantis I could not correctly
prioritize my tasks.
> We could gladly join our UI changes and bugfixes with
Mantis core
That would be very kind of you...
>
> So our questions are:
>
> Will Mantis have "Issue Type" attribute?
And who decide that?
I think this question should have been asked _before_
forking. Now,
_you_ decide what you want in your forked mantis, so why
bother who
decide?
>
> What is the standing on usability/UI improvements?
Currently we are working
> on simplifying the issue list screen and making
non-advanced Issue screens
> more simpler and readable. We also working on joining
"Main" screen and "My
> view" into one. (Having both screens is kind of a
waste and main menu exceed
> usability limit for number of menu items.)
Not that I do not appreciate a work on improving usability
but, who
set this "usability limit" on the number of
menu items? Moreover, the
two pages have very different purposes, so a merge give us
huge pages;
look for example at http://bugs.ma
ntisbt.org/main_page.php and
http:
//www.mantisbt.org/mantis/view.php?id=5410
http:
//www.mantisbt.org/mantis/view.php?id=4181
http:
//www.mantisbt.org/mantis/view.php?id=6470
are good candidates.
Cheers
Gianluca
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking
scripting language
that extends applications into web and mobile media. Attend
the live webcast
and join the prime developer group breaking into this new
coding territory!
http:
//sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$
1720&dat1642
_______________________________________________
Mantisbt-dev mailing list
Mantisbt-dev lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mantisbt-d
ev
|