Re: GPE bugtracker and SCM

Hi,

Paul Sokolovsky wrote:
>      Here, I would like to indeed constrain discussion to techinal
> aspects only: whatever the home GPE will have, how to improve it, to
> ease maintenance burden, and streamline user/developer support.

okay - sounds like we are back to our core competence :-)

>   I hope, even more "hardcore" options like Monotone/GIT/whatever are
> not considered ;-). SVN should be indeed good compromise between
> advanced features and ease to learn, already experienced user base,
> and ease of maintenance. SVN would improve work process for different
> participant roles - core developers, contributors, occasional patch

No chance for Monotone and GIT - my experience with Monotone used for
OpenEmbedded is that even the latest versions can cause major trouble
if you are not really careful. Apart from the fact that i don't see a
reason what we would gain from a distributed SCM.

> submitters, just users. As a note, it would be nice to have SVN via
> HTTP/WebDAV (vs SSH), as that would help people behind heavy
> firewalls (so far I see LTG offers svn/svn+ssh protocols).

Yes right, we need to make this work too.

>     GForge tracker is similar to SourceForge.net's, and I guess many
> users might try it already. AFAI can see, it's pretty basic, for good,
> or bad. One thing which is good with GForge tracker is that it is
> consistent for all projects - once people know how to use it (and
> for users, submit is pretty easy), they can use it in any hosted
> project.

That's the most important advantage.

>     But now that you mention Trac, I can only passionately second this
> choice. For development, Trac+SVN combo just screams. Maybe its just
> me, but Trac offers just the best SCM viewer - it's always easy to
> find what you're looking for, and it shows result just the very
> natural and comfortable way (ViewVC (ex-ViewCVS) is second in its
> usability IMHO, and current Mtn/GIT viewer are just bare). It has
> pretty good tracker and wiki. And all this can be easily cross-linked
> via easy wiki syntax. Summing up, it would let developers to do their
> job comfortably, being able to easily maintain and visualize project
> history, and let contributors/users to has good insight into the
> latter, lowering participation threshold and alleviating support burden.

That's definitely something to think about. What i currently lack is the
knowledge how it integrates mailinglists... One missing thing is support for
shell user management.

Feeding a new bugtracker with data about the GPE bits and all the released
versions seems to be no too complicated. With some help (i'm not that familiar
with any scripting language) i was able to write a script creating a useful
Bugzilla database, but i guess its not more complicated for other bug trackers.

Greetings

Florian

-- 
The dream of yesterday                  Florian Boor
is the hope of today                    Tel: +49 271-771091-14
and the reality of tomorrow.            Fax: +49 271-771091-19
[Robert Hutchings Goddard, 1904]        [email protected]

1D78 2D4D 6C53 1CA4 5588  D07B A8E7 940C 25B7 9A76