[6232] in Release_7.7_team

home help back first fref pref prev next nref lref last post

Re: publicity

daemon@ATHENA.MIT.EDU (Jonathan Reed)
Thu Feb 26 18:46:19 2009

Cc: release-team@mit.edu
Message-Id: <5CFE2B73-2972-4965-A46C-C763B8CD77E4@mit.edu>
From: Jonathan Reed <jdreed@MIT.EDU>
To: William Cattey <wdc@mit.edu>
In-Reply-To: <3CA58D3C-7D44-4473-96A4-DCCED68C8234@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: Thu, 26 Feb 2009 18:45:33 -0500
X-Spam-Flag: NO
X-Spam-Score: 0.00

I'll send out revised publicity tomorrow, note that I am also out of  
the office tomorrow.

Are we calling it "Athena 10" or not?   And what URL should I put on  
the publicity?  athena10.mit.edu?  debathena.mit.edu/beta/?  (I prefer  
the latter).

Wednesday morning would be ideal for installs, I think.  I realize  
it's two additional days, but:
- we will have met at release-team the day before and sanity-checked  
everything
- OLC meets on Wednesday afternoons for training, meaning the  
consultants will only have a few hours of deployment before training,  
vs two days if we install on Monday.
- We have more time to settle on the URL
- Rather than scramble to deal on Monday morning, I think we should  
take two extra days and ensure that we do this right.

Whatever we do, installing on Friday afternoon is definitely not a  
good idea.

-Jon


On Feb 26, 2009, at 5:02 PM, William Cattey wrote:

> Inasmuch as we closed the last Early Blocker moments ago, this is  
> now the next task on the critical path to installing some early  
> systems. (PXE is back up.)
>
> I agree with tabbott that we should add "Beta" for expectation  
> setting.
>
> How about changing the first sign to say,
>
> "This cluster contains workstations running a Beta test of the new  
> Athena 10 release"
>
> and changing second sign to read:
>
> 		Athena 10
> 		Beta Test
> 		Workstation
>
> Inasmuch as other publicity also points people at athena10.mit.edu,  
> leaving that URL as-is is fine.
>
> Jon,
>
> Can you cook up an update, and then maybe you and I can go install  
> some systems?  Ordinarily I'd jump on it and say Friday, but maybe  
> we want to do it Monday afternoon so that we can make site visits  
> during business hours if they break.
>
> -Bill
>
>
>
> On Feb 25, 2009, at 10:05 AM, Jonathan Reed wrote:
>
>> Here's a first draft at publicity.  athena10-workstation.pdf is  
>> designed to be taped to the table next to the workstation.    
>> athena10-cluster.pdf has two things - the top half will be taped to  
>> the cluster door, the bottom half will be taped on top of every  
>> athena 10 workstation display, probably folded somehow and printed  
>> on cardstock (I'm not concerned with those logistics at the moment)
>>
>> Please review the docs and let me know what you think.  Yes, I know  
>> some of them say "Debathena" and others say "Athena 10".  I think  
>> we probably do want to standardize on "Debathena", however the  
>> problem is I don't yet have a URL to print on them, since my  
>> changes to the Debathena pages aren't yet ready, and I don't want  
>> cluster installs to block on that.  athena10.mit.edu was a fine URL  
>> to print on there, since we can point it wherever.  But perhaps we  
>> don't want to do that if we're going to merge the two sites, and we  
>> don't want the URL to say "Athena10" when everything else says  
>> Debathena.
>>
>> I've thought too much about this already, so I'm going to pass the  
>> buck to someone else to make the final decision.   As a last  
>> resort, we could create web.mit.edu/newathena/ as a temporary  
>> redirect and point it wherever.
>>
>>
>>
>> <athena10-cluster-door.pdf>
>>
>>
>> <athena10-workstation.pdf>
>


home help back first fref pref prev next nref lref last post