Re: Moving to sourceforge Was: Re: jde-import-kill-extra-imports not working

OK, I get it, you want someone to move JDEE now.  I did express my
willingness to do the dirty work of moving JDEE.  Paul Kinnucan
responded (in this very thread) by saying that it would be best if he
performed the task.  That's where we stand now.  We wait until Paul
gets an opportunity to do the migration, and then we carry on with
patch-applying and such in the new repository.  If Paul were to ask
for someone else to do the work, Paul Landes and I would both be
available.  Out of respect for Paul Kinnucan's great contribution, I
think we should let him call the shots re: the migration of his code.

Carlos Konstanski

At Fri, 14 Dec 2007 12:57:58 +1300,
Len Trigg wrote:
> 
> 
> Hi Carlos,
> 
> You seemed ready, willing, and able to move JDEE to sourceforge.  Can
> you just go ahead and do it please?  It seems that if we continue to
> wait for Paul, we could be waiting indefinitely.  If Paul finds time
> to help in the process that's OK, but we should not further delay the
> move.
> 
> 
> Cheers,
> Len.
> 
> 
> At Mon, 5 Nov 2007 09:47:15 -0500,
> Paul Kinnucan wrote:
> > 
> > Hi Carlos,
> > 
> > I think it would be best if I moved the JDEE myself to Sourceforge. I
> > will have this completed by next weekend.
> > 
> > Paul
> > 
> > > -----Original Message-----
> > > From: Carlos Konstanski [mailto:[email protected]]
> > > Sent: Saturday, November 03, 2007 5:06 PM
> > > To: [email protected]
> > > Subject: Re: jde-import-kill-extra-imports not working
> > > 
> > > At Wed, 31 Oct 2007 11:58:25 +0000,
> > > Phillip Lord wrote:
> > > > I would move to sourceforge or gna.org. This is straightforward
> > enough.
> > > Then
> > > > pull the current cvs into a svn as quite a lot more people are using
> > > this
> > > > nowadays (it's not essential though).
> > > >
> > > > The jobs that need doing are:
> > > >
> > > > 1) checking patches for people without svn/cvs access.
> > > > 2) adding people to svn/cvs where appropriate
> > > > 3) organising a release schedule. In practice, this means doing a
> > new
> > > release
> > > >    when ever enough patches have come in.
> > > > 4) Updating the website with new tarballs, new zips.
> > > >
> > > > As an added extra:
> > > >
> > > > 5) add a top level makefile to build packages for the various
> > linuxes --
> > > rpm,
> > > >    gentoo and the like. Or add autoconf support which should bring
> > the
> > > former
> > > >    nearly for free I think. I'm not a real package expert.
> > > >
> > > > Once the release mechanism is fixed, then use can be made of
> > existing
> > > > patches. This would at least keep JDE ticking over.
> > > >
> > > > I'm afraid I am not volunteering here; I rarely code Java these
> > days, so
> > > I can
> > > > live without. But it would be nice to have the option to use Emacs
> > for
> > > those
> > > > occasions that I do.
> > > >
> > > > Phil
> > > 
> > > OK, the weekend is here and I am ready to do this thing.  First of
> > > all, do we have buyoff from the author/current maintainer to move JDEE
> > > to sourceforge?  I hereby officially ask the individual(s) in charge
> > > if it's all right for me to set up a JDEE sourceforge project and move
> > > the CVS repository there, in accordance with the promises I made
> > > earlier in this thread.