> >>> * I suggest we leave it at the old URL as well, and not remove it. For ppl
> >>> coming in from old links. It can still be community section, and it can
> >>> still have a different title, though
> >> This should be a redirect, which I can put in place with PHP. We should
> >> not duplicate content like that.
> >
> > It's not really duplicate. Just add two rows in the dispatcher.
>
> If it presents the same content under /developers as under /community it
> is duplicate and that is dumb. I would agree that having a redirect is
> appropriate.
Matter of definition. Data exists once and is presented twice. Kinda like normalisation :-P
> >>> * Let's not delete the old developer.php file and create a new identical
> >>> one. Modify the one that's there instead. Filenames don't have to match,
> >>> that's what the dispatcher takes care of.
> >> That would be inconsistent with the rest of the portal layout.
> >
> > that'sjust temporary. The system is set up so you can do this stuff without kiling version control, by using the
dispatcher.Please do so.
>
> Exactly how are we killing version control? Subversion handles removal
> of files just fine.
Bad choice of words. But if your patch is applied, I can't see a diff of your changes. And it's still logged as one ad
andone remove. so I can't easily diff between tomorrows version and one two steps back.
And since there really is no gain, imnsho, I see no reason to take away that ability.
> >>> * You added a new template, but didn't remove the old one. My suggestion -
> >>> keep the old one, don't add the new one.
> >> I should remove the old one. I must of missed it, sorry.
> >>
> > No, you should *use* the old one...
> >
>
> Disagreements are the heart of open source.
Indeed :)
/Magnus
