| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
Cc: debathena@mit.edu Message-Id: <6FAE3C6F-56C9-4033-BA86-382F473C9AC3@mit.edu> From: Jonathan Reed <jdreed@MIT.EDU> To: Greg Price <price@mit.edu> In-Reply-To: <20090313064907.GY25963@mit.edu> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Fri, 13 Mar 2009 09:24:59 -0400 I'm fine with bringing root up to date with /beta, but I'd like to keep /beta a separate site through the end of the term, so that it's a place we can update quickly with information pertinent to the cluster test project. I currently lack bits on the root website and had also assumed that it would not be desirable for the root site to be a place where we do live edits without a chance to preview them. If both of those turn out to be false, then I'm fine with making /beta a symlink. -Jon On Mar 13, 2009, at 2:49 AM, Greg Price wrote: > The websites at http://debathena.mit.edu/ and at > http://debathena.mit.edu/beta are now both complete sites describing > the same software. Thanks to Jon's work, the /beta website is > now substantially clearer and better organized. It'd be good to carry > over those improvements to the front page. > > In particular, I'd like to > > - bring the root site up to date with the /beta site, > probably with git rebase and then git push > > - make the root site and /beta site remain up to date with each other > thereafter by replacing /mit/debathena/web_scripts/beta with a > symlink to website. (We briefly used /beta as a sandbox for > major changes in progress, but today both sites are advertised.) > > Are there objections to, or technical comments on, either of these > steps? > > Greg
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |