+1 on website.  Do that.

On Wed, Jun 22, 2011 at 4:29 PM, Matthew Turk <matthewturk@gmail.com> wrote:
Okay -- let's plan on not having a release before the end of June.  If
I get a chance before I leave I will work a bit on documentation, but
I'd like to take Cameron up on his offer of writing some docs for
Reason and if he and Casey want to coordinate on a screencast of how
to use Reason (in the neighborhood of 30-90 seconds) that would be
awesome.  I've filled out tickets for these items:

https://bitbucket.org/yt_analysis/yt/issue/288/reason-should-be-documented
https://bitbucket.org/yt_analysis/yt/issue/291/reason-screencast

And as a reminder, the open tickets for 2.2 are listed here -- please
feel free to comment or add more information.  Anyone who has push
privs to the repo can update and modify existing tickets, and anyone
can fill out new tickets.

https://bitbucket.org/yt_analysis/yt/issues?status=new&status=open&milestone=2.2

(for the rest: https://bitbucket.org/yt_analysis/yt/issues?status=new&status=open
)

For the website, sounds like it's getting thumbs up, so I'm going to
put it up on the front page sometime before I leave, maybe even later
today.  Speak now or forever ...?

-Matt

On Tue, Jun 21, 2011 at 7:02 AM, Britton Smith <brittonsmith@gmail.com> wrote:
> +1 on the website.
>
> I don't have any time to help out with the yt 2.2 release goals before the
> end of the month.  I could help in July if we want to push the release date
> back.
>
> Britton
>
> On Tue, Jun 21, 2011 at 12:42 AM, Matthew Turk <matthewturk@gmail.com>
> wrote:
>>
>> Hi Stephen,
>>
>> On Mon, Jun 20, 2011 at 2:24 PM, Stephen Skory <s@skory.us> wrote:
>> > Matt,
>> >
>> >> 2) A few of us have created a prototype of a new website:
>> >>
>> >> http://yt.enzotools.org/prototype/
>> >
>> > Just some comments, and then I'll give my opinion on the design.
>> >
>> > I think it's bad form to put shortened URLs on a webpage, in
>> > particular the one for "GET YT". Either put the full URL (which is
>> > long in this case to the install_script.sh) or something descriptive
>> > like 'Download install_script.sh'.
>>
>> I've removed it.  It was also redundant with the "Get yt" section header.
>>
>> >
>> > Having the single-page CSS scrolling is fine, but I don't think the
>> > gaps between the sections are necessary. To some extent, those gaps
>> > assume that the user can see the entire text in each section. When
>> > they can't, they'll start scrolling down, and then they'll discover a
>> > big gap between sections, which is odd. The converse is true too - if
>> > the text is too short, then there's a big gap, which is odd, again.
>>
>> Hmm, I'm not sure about this.  I kind of like it.  If you want to hack
>> away at it, though, feel free.
>>
>> >
>> > Overall I like it, I think it looks pretty sharp.
>>
>> Me too; I think it was the right one to choose.
>>
>> Anybody else have any suggestions on the website?
>>
>> >
>> >> 3) I am going on vacation starting sometime between June 29 and July
>> >> 3, and I will be gone until at least July 23rd.
>> >
>> > Take lots of pictures!
>>
>> I surely will.  :)
>>
>> -Matt
>>
>> >
>> > --
>> > Stephen Skory
>> > s@skory.us
>> > http://stephenskory.com/
>> > 510.621.3687 (google voice)
>> > _______________________________________________
>> > Yt-dev mailing list
>> > Yt-dev@lists.spacepope.org
>> > http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>> >
>> _______________________________________________
>> Yt-dev mailing list
>> Yt-dev@lists.spacepope.org
>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>
>
> _______________________________________________
> Yt-dev mailing list
> Yt-dev@lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>
>
_______________________________________________
Yt-dev mailing list
Yt-dev@lists.spacepope.org
http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org