paciorek
commented
8 years ago Sounds like a good idea to me. 10/2 and 10/9 both work though I teach 2-3:30.
On Mon, Sep 21, 2015 at 7:45 AM, Aaron Culich notifications@github.com wrote:
After various discussions I've had with @davclark https://github.com/davclark , @paciorek https://github.com/paciorek , @ck37 https://github.com/ck37 , and @ryanlovett https://github.com/ryanlovett , I wonder if it's time to have a BCE HackDay ahead of doing a Fall release? Is there a day (or half day or even just 2 hours) that we could get together in the next couple of weeks? Preferably before the Oct 15th Cloud WG topic which is: BCE on AWS?
Maybe Friday 10/2 or Friday 10/9?
I'll start triaging all the issues we have here https://github.com/ucberkeley/bce/issues and in the documentation issues https://github.com/ucberkeley/bce/issues ahead of that HackDay.
I'd like to address issues like this one that Dav and I discussed on the uc-juptyer slack https://uc-jupyter.slack.com/messages/general/:
aculich [6:49 PM] @davlab https://github.com/davlab Is anaconda the approach used in http://bce.berkeley.edu ?
aculich [6:49 PM] Whatever the approach, I wonder if we ought to include a short description in the https://github.com/ucberkeley/bce/blob/dev/README.md of the high-level decisions and reasons for making them so that:
aculich [6:49 PM]
- folks can (without looking at the build scripts) see what our approach is; and
aculich [6:49 PM]
- can see our rationale (which won’t necessarily be obvious when looking at the build scripts) NEW MESSAGES
----- Yesterday September 20th, 2015 -----
davlab [7:42 PM] @aculich https://github.com/aculich: yes, we use anaconda now. We aren’t using it as well as we could (i.e., I’d like to enable conda install bce=fall-2015 for at least arbitrary-ish unix). Such a thing is not hard, we just haven’t gotten to it.
davlab [7:43 PM] I think a great first step would be simply documenting the choices we made even without the rationale! I’ve been meaning to do this, and I think we should explain how to install most of the major tools - like PyCharm, RStudio, anaconda, etc.
— Reply to this email directly or view it on GitHub https://github.com/ucberkeley/bce/issues/65.
ck37
ryanlovett
aculich
davclark
After various discussions I've had with @davclark , @paciorek , @ck37 , and @ryanlovett , I wonder if it's time to have a BCE HackDay ahead of doing a Fall release? Is there a day (or half day or even just 2 hours) that we could get together in the next couple of weeks? Preferably before the Oct 15th Cloud WG topic which is: BCE on AWS?
Maybe Friday 10/2 or Friday 10/9?
I'll start triaging all the issues we have here and in the documentation issues ahead of that HackDay.
I'd like to address issues like this one that Dav and I discussed on the uc-juptyer slack:
aculich [6:49 PM] @davlab Is anaconda the approach used in http://bce.berkeley.edu ?
aculich [6:49 PM] Whatever the approach, I wonder if we ought to include a short description in the https://github.com/ucberkeley/bce/blob/dev/README.md of the high-level decisions and reasons for making them so that:
aculich [6:49 PM]
aculich [6:49 PM]
----- Yesterday September 20th, 2015 -----
davlab [7:42 PM] @aculich: yes, we use anaconda now. We aren’t using it as well as we could (i.e., I’d like to enable
conda install bce=fall-2015for at least arbitrary-ish unix). Such a thing is not hard, we just haven’t gotten to it.davlab [7:43 PM] I think a great first step would be simply documenting the choices we made even without the rationale! I’ve been meaning to do this, and I think we should explain how to install most of the major tools - like PyCharm, RStudio, anaconda, etc.