2.2 release, new website, vacation
Hi all, I'm writing with three points. 1) We had hoped for a release by the end of June. There are three outstanding tickets [ http://hg.enzotools.org/yt/issues?status=new&status=open&milestone=2.2 ]. * Document reason * Fix units for Nyx * Fix field of view for reason slice/proj widget I'm not going to be able to look at these before the end of June. The middle one might get pushed off, as it's blocked on some other developments. So anybody that wants to step up and handle either the field of view or the reason documentation, please do so. Anybody have any thoughts on this? 2) A few of us have created a prototype of a new website: http://yt.enzotools.org/prototype/ to replace the old one. The style was purchased from themeforest.net. I am not yet convinced that this is a good idea, to move to a fancier layout, because I worry that too fancy and it looks unserious. I can't tell if this site crosses that line. I do like how it lays out the community, development, how to get it, and examples. (The examples, I think, are particularly helpful.) +1/-1? The idea was to dump this at the end of the month when 2.2 came out, but if 2.2 is delayed, then this will not happen. Also, I'd be happy to grant write access to the page repo for this; it's private right now because I don't know how the copyright from themeforest works with publicly-viewable repositories, although in theory it's not any additional information that couldn't be gotten from the packages delivered when viewing the page. The images I selected are ... biased towards ones I already had. :) So that might be a place to improve it, among other things ... 3) I am going on vacation starting sometime between June 29 and July 3, and I will be gone until at least July 23rd. During that time I will have very, very limited access to email, and I do not anticipate being able to reply to any yt-users emails or make any software changes. I will be able to reply, in a very limited fashion and with high latency, to direct email inquiries. Thanks, Matt
I can work on documenting some of Reason. Do you think we should still try to push the new version out by the end of June? On 6/20/11 3:59 PM, Matthew Turk wrote:
Hi all,
I'm writing with three points.
1) We had hoped for a release by the end of June. There are three outstanding tickets [ http://hg.enzotools.org/yt/issues?status=new&status=open&milestone=2.2 ].
* Document reason * Fix units for Nyx * Fix field of view for reason slice/proj widget
I'm not going to be able to look at these before the end of June. The middle one might get pushed off, as it's blocked on some other developments. So anybody that wants to step up and handle either the field of view or the reason documentation, please do so. Anybody have any thoughts on this?
2) A few of us have created a prototype of a new website:
http://yt.enzotools.org/prototype/
to replace the old one. The style was purchased from themeforest.net. I am not yet convinced that this is a good idea, to move to a fancier layout, because I worry that too fancy and it looks unserious. I can't tell if this site crosses that line. I do like how it lays out the community, development, how to get it, and examples. (The examples, I think, are particularly helpful.) +1/-1? The idea was to dump this at the end of the month when 2.2 came out, but if 2.2 is delayed, then this will not happen.
Also, I'd be happy to grant write access to the page repo for this; it's private right now because I don't know how the copyright from themeforest works with publicly-viewable repositories, although in theory it's not any additional information that couldn't be gotten from the packages delivered when viewing the page. The images I selected are ... biased towards ones I already had. :) So that might be a place to improve it, among other things ...
3) I am going on vacation starting sometime between June 29 and July 3, and I will be gone until at least July 23rd. During that time I will have very, very limited access to email, and I do not anticipate being able to reply to any yt-users emails or make any software changes. I will be able to reply, in a very limited fashion and with high latency, to direct email inquiries.
Thanks,
Matt _______________________________________________ Yt-dev mailing list Yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
I'd be happy to help you with documenting reason; the reason I was ready to push that one off is that with a paper draft and a grant draft due before I leave, I can't write the whole thing myself. A one-three minute screencast would be awesome, too, I think. If we can close the two reason tickets, I think we should push out a release. All the other major features have either already been documented or require very little documentation, as I recall. (i.e., "yt mapserver") -Matt On Mon, Jun 20, 2011 at 1:05 PM, Cameron Hummels <chummels@astro.columbia.edu> wrote:
I can work on documenting some of Reason. Do you think we should still try to push the new version out by the end of June?
On 6/20/11 3:59 PM, Matthew Turk wrote:
Hi all,
I'm writing with three points.
1) We had hoped for a release by the end of June. There are three outstanding tickets [ http://hg.enzotools.org/yt/issues?status=new&status=open&milestone=2.2 ].
* Document reason * Fix units for Nyx * Fix field of view for reason slice/proj widget
I'm not going to be able to look at these before the end of June. The middle one might get pushed off, as it's blocked on some other developments. So anybody that wants to step up and handle either the field of view or the reason documentation, please do so. Anybody have any thoughts on this?
2) A few of us have created a prototype of a new website:
http://yt.enzotools.org/prototype/
to replace the old one. The style was purchased from themeforest.net. I am not yet convinced that this is a good idea, to move to a fancier layout, because I worry that too fancy and it looks unserious. I can't tell if this site crosses that line. I do like how it lays out the community, development, how to get it, and examples. (The examples, I think, are particularly helpful.) +1/-1? The idea was to dump this at the end of the month when 2.2 came out, but if 2.2 is delayed, then this will not happen.
Also, I'd be happy to grant write access to the page repo for this; it's private right now because I don't know how the copyright from themeforest works with publicly-viewable repositories, although in theory it's not any additional information that couldn't be gotten from the packages delivered when viewing the page. The images I selected are ... biased towards ones I already had. :) So that might be a place to improve it, among other things ...
3) I am going on vacation starting sometime between June 29 and July 3, and I will be gone until at least July 23rd. During that time I will have very, very limited access to email, and I do not anticipate being able to reply to any yt-users emails or make any software changes. I will be able to reply, in a very limited fashion and with high latency, to direct email inquiries.
Thanks,
Matt _______________________________________________ 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
I love making screencasts. Any requests? On Mon, Jun 20, 2011 at 2:08 PM, Matthew Turk <matthewturk@gmail.com> wrote:
I'd be happy to help you with documenting reason; the reason I was ready to push that one off is that with a paper draft and a grant draft due before I leave, I can't write the whole thing myself. A one-three minute screencast would be awesome, too, I think.
If we can close the two reason tickets, I think we should push out a release. All the other major features have either already been documented or require very little documentation, as I recall. (i.e., "yt mapserver")
-Matt
I can work on documenting some of Reason. Do you think we should still
On Mon, Jun 20, 2011 at 1:05 PM, Cameron Hummels <chummels@astro.columbia.edu> wrote: try
to push the new version out by the end of June?
On 6/20/11 3:59 PM, Matthew Turk wrote:
Hi all,
I'm writing with three points.
1) We had hoped for a release by the end of June. There are three outstanding tickets [ http://hg.enzotools.org/yt/issues?status=new&status=open&milestone=2.2 ].
* Document reason * Fix units for Nyx * Fix field of view for reason slice/proj widget
I'm not going to be able to look at these before the end of June. The middle one might get pushed off, as it's blocked on some other developments. So anybody that wants to step up and handle either the field of view or the reason documentation, please do so. Anybody have any thoughts on this?
2) A few of us have created a prototype of a new website:
http://yt.enzotools.org/prototype/
to replace the old one. The style was purchased from themeforest.net. I am not yet convinced that this is a good idea, to move to a fancier layout, because I worry that too fancy and it looks unserious. I can't tell if this site crosses that line. I do like how it lays out the community, development, how to get it, and examples. (The examples, I think, are particularly helpful.) +1/-1? The idea was to dump this at the end of the month when 2.2 came out, but if 2.2 is delayed, then this will not happen.
Also, I'd be happy to grant write access to the page repo for this; it's private right now because I don't know how the copyright from themeforest works with publicly-viewable repositories, although in theory it's not any additional information that couldn't be gotten from the packages delivered when viewing the page. The images I selected are ... biased towards ones I already had. :) So that might be a place to improve it, among other things ...
3) I am going on vacation starting sometime between June 29 and July 3, and I will be gone until at least July 23rd. During that time I will have very, very limited access to email, and I do not anticipate being able to reply to any yt-users emails or make any software changes. I will be able to reply, in a very limited fashion and with high latency, to direct email inquiries.
Thanks,
Matt _______________________________________________ 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
Matt,
2) A few of us have created a prototype of a new website:
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'. 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. Overall I like it, I think it looks pretty sharp.
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! -- Stephen Skory s@skory.us http://stephenskory.com/ 510.621.3687 (google voice)
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:
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
+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:
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
+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:
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
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:
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
+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
+1 on the website.
I don't have any time to help out with the yt 2.2 release goals before
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:
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
On Tue, Jun 21, 2011 at 7:02 AM, Britton Smith <brittonsmith@gmail.com> wrote: the 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
agreed. +1. it is great. On 6/22/11 11:39 AM, Britton Smith wrote:
+1 on website. Do that.
On Wed, Jun 22, 2011 at 4:29 PM, Matthew Turk <matthewturk@gmail.com <mailto: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 <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 <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 <mailto: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 <mailto:matthewturk@gmail.com>> > wrote: >> >> Hi Stephen, >> >> On Mon, Jun 20, 2011 at 2:24 PM, Stephen Skory <s@skory.us <mailto: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 <mailto:s@skory.us> >> > http://stephenskory.com/ >> > 510.621.3687 <tel:510.621.3687> (google voice) >> > _______________________________________________ >> > Yt-dev mailing list >> > Yt-dev@lists.spacepope.org <mailto:Yt-dev@lists.spacepope.org> >> > http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org >> > >> _______________________________________________ >> Yt-dev mailing list >> Yt-dev@lists.spacepope.org <mailto:Yt-dev@lists.spacepope.org> >> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org > > > _______________________________________________ > Yt-dev mailing list > Yt-dev@lists.spacepope.org <mailto:Yt-dev@lists.spacepope.org> > http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org > > _______________________________________________ Yt-dev mailing list Yt-dev@lists.spacepope.org <mailto: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
The website looks great. +1 I do have a little bit of worry along the lines of Stephen's: the gaps can be a bit annoying/confusing if you are viewing the page on a smaller screen. For example, I first looked at the new page on my phone, and it looked like a terrible waste of space if I were just to scroll through it. Then again, if someone is seriously considering using this piece of software they probably aren't viewing the webpage on a mobile device... Not sure what can be done about this outside of moving to separate pages. It's only a minor quibble, so probably not worth the trouble. Chris On Jun 22, 2011 11:49am, Cameron Hummels <chummels@astro.columbia.edu> wrote:
agreed. +1. it is great.
On 6/22/11 11:39 AM, Britton Smith wrote: +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:
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
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
_______________________________________________ Yt-dev mailing list Yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
Hi Chris et al, Yes ... the space between sections is annoying. I'm not sure how to fix that, but feel free to play with the repo and see if you can work it out. I don't really mind having it be mobile friendly. :) (I recently added a few things to reason to make it more mobile friendly, for what that's worth ...) I've gone ahead and deployed. Thanks for the thumbs up, everybody! I am really pleased with how it's looking, too. Hopefully this will help attract contributors as well as put our best foot forward. -Matt On Wed, Jun 22, 2011 at 8:55 AM, <chris.m.malone@gmail.com> wrote:
The website looks great. +1
I do have a little bit of worry along the lines of Stephen's: the gaps can be a bit annoying/confusing if you are viewing the page on a smaller screen. For example, I first looked at the new page on my phone, and it looked like a terrible waste of space if I were just to scroll through it. Then again, if someone is seriously considering using this piece of software they probably aren't viewing the webpage on a mobile device... Not sure what can be done about this outside of moving to separate pages. It's only a minor quibble, so probably not worth the trouble.
Chris
On Jun 22, 2011 11:49am, Cameron Hummels <chummels@astro.columbia.edu> wrote:
agreed. +1. it is great.
On 6/22/11 11:39 AM, Britton Smith wrote: +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:
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
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
_______________________________________________ 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
participants (6)
-
Britton Smith -
Cameron Hummels -
Casey W. Stark -
chris.m.malone＠gmail.com -
Matthew Turk -
Stephen Skory