[openi18n-im:01305] Re: Communications & Tools for the project

On Tuesday 22 March 2005 17:49, Lawrence Lim wrote:
> My vote goes to Option 2. Normal Wiki + Bugzilla.
>
> In addition to the rich feaures found in Bugzilla, the main reason for
> my decision is because with Option 2, bug information can be exchanged
> using xml-rpc between Red Hat Bugzilla and openi18n Bugzilla, so both
> sites will be kept up-to-date at all times. At the moment, im-sdk bug
> activity is more active than openi18n bug tracker, it will be really
> nice to have both sites synchronized.

I can see your point on this benefit to other vendors/contributors. In general 
point of view, I think the main idea to help user to learn less system and 
able to submit their bug, and I think bugzilla may able to help that.

>
> If it is agreed by all, I am happy to volunteer myself for the initial
> scoping, determine how much work is involved, and participate in the
> migration of the bug tracking system.

Wonderful. Thanks Lawrence!

Cheers,
Leon

>
>
>
> Thanks,
> Lawrence
>
> On Mon, 2005-03-21 at 18:37, Leon Ho wrote:
> > As we want to ease the contributions of information, here are some of the
> > options of tool that we can migrate:
> >
> > 1. Trac (mentioned by tagoh-san) http://www.edgewall.com/trac/
> >   Features:
> >   - Wiki
> >   - Issue tracking (bug tracking system)
> >   - Interface to svn
> >   - Timeline tracking
> >   - Roadmap tracking (number of features/fixes within version; A clean
> > way to track features through this way)
> >
> >   Comment: Admin probably need less resource than number two as it is all
> > integrated within one solution. It maybe less powerful than bugzilla as
> > bug tracking.
> >
> > 2. Normal Wiki (MoinMoin?) + Bugzilla
> >   - Wiki
> >   - Most of the large open source projects uses bugzilla. So to minimize
> > the barrier of entry for user to post bugs
> >   - Features tracking can be track through reporting and system in
> > bugzilla and link to Wiki
> >
> >   Comment: Going to be needing higher resources. However MoinMoin can
> > spawn into couple copies for different sub-groups within openi18n.org if
> > other groups are desired on a collaboration tool.
> >
> > Let me know what are the other options and how do you like these options.
> >
> > Regards,
> > Leon
> >
> > On Friday 04 March 2005 12:37, Jens Petersen wrote:
> > > Leon Ho wrote:
> > > > Inwards communication accelerates our development.
> > > > Outwards communication increases wider adoption of the project.
> > >
> > > Yes, this is the key point. :-)
> > >
> > > > Web page for IIIMF. Any improvement on this area? Is it an info
> > > > riching area, and does it allow you to request/add information
> > > > easily?
> > >
> > > I don't know how to log into the website,
> > > so I'm not able to contribute to it.  I haven't used
> > > postnuke much either I'm not really in position to judge
> > > how well it fits our needs.  It would be good to revamp
> > > in the near future though IMHO, and try to improve the layout
> > > and organisation of information.
> > >
> > > Currently the website is not very actively maintained - for lack
> > > of time by the core developers understandably. :)  I think
> > > we need to share the maintenance of the website better;
> > > with delegation I'm sure we can improve it significantly.
> > >
> > > > Should we use tool like like Wiki? How much information on IIIMF you
> > > > want to share but there aren't any place for it?
> > >
> > > As the project is growing and gathering a userbase and community
> > > for this project to flourish we really need a dynamic Wiki site
> > > where the community and developers can work together on notes,
> > > project plans, support information, faq's, and so on.
> > >
> > > > Bug Tracking system. This is important because it is a central place
> > > > for user/QA/Developers to exchange information. Have we used it well
> > > > enough? If not what is the obstacle that prevent you using it?
> > >
> > > Again I'm not able to access my account here: so having never
> > > used mantis I can't really judge its capabilities or ease of use.
> > > I wonder if we wouldn't be better off using bugzilla, which is being
> > > used widely by many FOSS projects these days.
> > >
> > > Without good issue tracking, we're not going to see a significant
> > > improvement in quality of iiim.  Up to now we've basically been using
> > > our own Bugzilla system to track bugs, but we really need to track them
> > > at the project level for maximum leverage for everybody.
> > >
> > > Jens

-- 
 Leon Ho                       <llch at redhat.com>
 Supervisor, I18N Engineering  Red Hat Asia-Pacific
 Legal:           http://apac.redhat.com/disclaimer