Re: [Rails-devel] rails-package rails.ui.swing SVG revenue

[Erik V. <eri...@hc...>]

IMHO the package name changes (prepending 'rails.')
is worth doing now, better than later.
I don't care about the loss of history, as I'm sure
that the current version is better than anything in the past.
In any case I will make a backup copy of my current project.

The changes to Subversion and the project structure
clearly need more thought and can be postponed, if done at all.

However, I leave the decision to Brett.
One of us should do it, as only the two of us can commit code now.
I'm prepared to do the package name changes next Sunday,
but it's equally fine to me drop the whole issue.

FYI, I'm away from now until Saturday night.

Erik.


> -----Original Message-----
> From: rai...@li... 
> [mailto:rai...@li...] On Behalf 
> Of brett lentz
> Sent: Thursday 18 January 2007 23:34
> To: Development list for Rails: an 18xx game
> Subject: Re: [Rails-devel] rails-package rails.ui.swing SVG revenue
> 
> > With all these proposals, what is most important for me is
> > what all these changes would mean for the way I work with Eclipse.
> > With some trouble I have achieved a working relationship 
> with Eclipse,
> > and I don't really have a picture how that will change with 
> such a new
> > layout.
> >
> 
> 
> Rainer - I think this is the core problem I'm having with many of
> these suggestions. Instead of learning how we've been working, and
> doing it our way for a while, you're suggesting a lot of large,
> drastic changes to accomodate your own preferences.
> 
> I think that we should focus more on reaching our existing goals.  So
> far, I haven't received a patch for the first item you brought up (the
> disclaimer) and now you're moving on to suggesting changing our RCS
> and moving all of our files around and reworking large portions of our
> architecture.
> 
> 
> > As of now, Brett and I don't even use the same .project file
> > (I've put mine in .cvsignore). That may have to change.
> >
> 
> Erik - Yes, this likely needs to find some common working default that
> we can check in to CVS. Perhaps we should compare our .project files
> and see why they're different. I think we might have done this before,
> but I can't remember the results.
> 
> > One minor thing is, that the hierarchy will get a lot deeper,
> > which makes dealing with the (narrow) Navigator view a bit more
> > difficult. But that's no big deal.
> >
> > Perhaps it is all worth a try.
> >
> 
> I don't think it's all worth a try just yet. It seems like many of
> things are big changes with questionable benefit and a definite impact
> on our immediate productivity.  I don't want to stop development to
> undertake any of these big changes just to come out on the other side
> of it with minimal gains.
> 
> I think we're much better off taking smaller steps, and carefully
> selecting which changes we make that either work well with our
> existing methods or provide a definite, tangible benefit.
> 
> ---Brett.
> 
> --------------------------------------------------------------
> -----------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the 
> chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge
&CID=DEVDEV
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel
> 
>