[ECLIPSE] Vote for project management solution

[Pantelis Koukousoulas]

Hi!

I 'd just like to do some explaining since there seems to be a slight
misunderstanding here.
The vote is about which *bugtracker* to use. I.e., the interface on
which we will file tasks,
assign things to ourselves and keep track of who is working on what.

Since we all have very limited free time, having a web / bugzilla-like
interface for this task
seems much better since you can just assign something that is orphan
to yourself while you are
working on it and just orphan it again if you see you can not afford
to work on this again for the
forseeable future, leaving things open for someone else to continue
where you left off.

It is also nice for keeping track of what % of the task is done, etc.

This has absolutely *nothing* to do with the distribution we are
developing for (which is of course
debian in the sense that the dependencies etc are all assumed to be
what is in debian sid or
explicitely stated otherwise).

It has also nothing to do with the vcs we are using which I propose to
be whatever everyone likes
(e.g., I 'm planning to use git because I really like and understand
it and expose it perhaps through
gitorious or something). In the end, I 'd expect all communication to
be through plain-old patches
in this mailing list (to facilitate peer review) and Andreas and
whoever else wants commit rights
to commit agreed-upon work to pkg-java svn.

So please base your decision on the technical merits of each solution
alone, i.e., which one
is faster, less annoying, more familiar to you to work with etc.,

> I'm with Andreas here: I'd feel a lot more comfortable with an Alioth
> project since I'm already familiar with it and we really should keep
> things in Debian, so other downstreams can profit; Ubuntu is just one of
> them. I do not totally object to Launchpad but I feel a little uneasy
> about using the same infrastructure as Debian already provides; also, it
> raises the barrier for DDs to work on Eclipse.

I don't see how the barrier is raised for DDs as long as the pkg-java
repo is the authoritative
source for agreed upon work. Are DDs more familiar with the alioth
(gforge) bugtracker?

> I also wonder if we really need to split things out. The packaging was
> going on the Java packaging repository, we can also just that and get it
> into shape. We can also add a new mailing list for packaging issues in
> the Java packaging scope, if that seems needed. Not every package has to
> have it's own Alioth project, IMHO.

I feel we need to have a place of our own for tracking tasks for 2 reasons:

     * Not create unnecessary traffic on this list of the type
"[ECLIPSE] task #1 is now assigned to Pantelis"
        that other java maintainers might not care about.

     * To make it easy to manage since keeping track of emails takes a
long time, that is just not available

I expect we have about 50 tasks to complete until the package is ready
but from the perspective of this list
there is only one task: "upgrade eclipse" :-)

Btw, if you have some totally different bugtracking interface that you
like better, are faster with,
it would be fair game too, please say so :-)

The reason I didn't just choose alioth is that the underlying platform
(Gforge) seems to be a little
sucky bugtracking-wise (but don't quote me on that)

Hope things are a little clearer now,
Cheers,
Pantelis