Hi Kristis,
On 10.01.2007 00:15, Kristis Makris wrote:
>
>
> I wouldn't oppose converting it to Python. Just don't expect *me* to do
> it! Or at least yet. Real life keeps getting in the way plenty already.
>
After a discussion here, some kind of re-implementing scmbug
in Python (with or without change of the underlying software architecture)
is probably a nice student project. scmbug has functionality and
(more important) generality, that our approach is missing currently.
I'm already going to find an interested student for that...
I'm wondering if you might contribute to that re-implementation?
Either in writing code or in intellectual support?
>
>
> I just hate the duplication of effort, you know...
>
Yes, of course, duplication of effort should be avoided.
I just think that one of the major problems in many software
developments is the poor maintainability of code, which results in
plenty of wokr and wastes a lot of time. Me, as well as many
other people I know, consider Perl code as unmaintainable and
a clean re-implementation in a language like Python safes time
(and costs) at the end. Of course, I don't want to affront you
and your code in particular, its just a general argumentation.
Best,
Andreas
>
> On Tue, 2007-01-09 at 23:05 +0100, Andreas Schreiber wrote:
> > Hi Kristis,
> >
> > we already had a look at scmbug a year ago, when we integrated our
> > Subversion
> > repository with our issue tracking (Mantis). At that time, we were
> > migrating from
> > CVS to Subversion and we just didn't wanted to extend and maintain our
> > long-grown
> > CVS hook scripts any more.
> >
> > To be honest, we have a really strong aversion against Perl. We are
> > definitely
> > not going to run software written in Perl, that is probably to be
> > changed by us.
> > We have discovered in various occasions, that it is a lot easier to
> > re-design
> > and re-implement a certain piece of software in Python than maintaining
> > Perl code
> > (of course, this is also true for a couple of other languages...).
> >
> > Mmh, so last year we implemented the "svnchecker" scripts, which
> > fulfilled
> > our requirements at the German Aerospace Center. We didn't plan to
> release
> > it under an Open Source license at the beginning. This came up the last
> > couple
> > of days, after some former colleagues urged us to make it available to
> > the public.
> > In general, developing Open Source software wasn't favored and not
> allowed
> > in our research lab. I'm currently trying to change that a bit...
> >
> > Are you sticked to Perl? Is that a must or requirement?
> >
> > Best regards,
> > Andreas
> >
> > On 09.01.2007 21:34, Kristis Makris wrote:
> > > Hi Andreas,
> > >
> > > I just so your posting on freshmeat about SVNChecker. What are the
> > > chances of getting your work merged in Scmbug
> > > http://freshmeat.net/projects/scmbug/ so that your checks become SCM
> > > agnostic instead of depending strictly on Subversion ? For example, we
> > > already implement some checks:
> > >
> > >
> http://files.mkgnu.net/files/scmbug/SCMBUG_RELEASE_0-19-7/manual/html-single/manual.html#VERIFICATION-CHECKS
> > >
> > > One immediate issue I see is that your work is implemented in Python
> > > while we use Perl (we are not proud of that) .I'd hate for your to
> > > reimplement some logic, especially since Scmbug is trying to solve the
> > > integration problem once and for all and you are addressing already
> > > issues we haven't.
> > >
> > > Thanks,
> > > Kristis
> > >
> > >
> >
> >
>
--
Andreas Schreiber
Leiter Abt. Verteilte Systeme und Komponentensoftware
Deutsches Zentrum fuer Luft- und Raumfahrt e.V. (DLR)
Simulations- und Softwaretechnik (SISTEC) Koeln-Porz
Tel: (02203) 601-2485 http://www.dlr.de/sc
Fax: (02203) 601-3070 mailto:[EMAIL PROTECTED]
Mobile: (0173) 5231013 ICQ# 324185855
http://www.xing.com/go/invite/4232700.edbeba
_______________________________________________
scmbug-users mailing list
[email protected]
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
