I did specifically ask for dancing bears. ;-)
On Apr 22, 2009, at 10:58 AM, Ethan Mallove wrote:
Dancing bears on slide 1. We're off to a good start.
-Ethan
On Wed, Apr/22/2009 09:11:57AM, Jeff Squyres wrote:
> The slides will also be on webex on the call tomorrow. Use the
URL to join
>
Dancing bears on slide 1. We're off to a good start.
-Ethan
On Wed, Apr/22/2009 09:11:57AM, Jeff Squyres wrote:
> The slides will also be on webex on the call tomorrow. Use the URL to join
> the meeting in the email invite that you got. That URL will launch an
> application thingy for the
The slides will also be on webex on the call tomorrow. Use the URL to
join the meeting in the email invite that you got. That URL will
launch an application thingy for the web portion of the meeting, and
it will prompt you for a phone number to call you to join the audio
portion of the
Hello guys,
Here is a small ppt with MTToGDS summary for tomorrow`s meeting.
regards
Mike
On Thu, Apr 16, 2009 at 5:02 PM, Jeff Squyres wrote:
> Will there be dancing bears on the slides? I'll only accept slides with
> dancing bears!
>
> ;-)
>
> (no need to be formal; if
Will there be dancing bears on the slides? I'll only accept slides
with dancing bears!
;-)
(no need to be formal; if slides help, great, otherwise don't make
slides just because we have webex available)
On Apr 16, 2009, at 9:50 AM, Mike Dubman wrote:
I will prepare ppt with summary of
I will prepare ppt with summary of what were discussed and agreed,
milestones, open questions and other thoughts.
regards
Mike
On Thu, Apr 16, 2009 at 2:07 PM, Jeff Squyres wrote:
> Ok, I think we converged on a time: 9am US Eastern / 4pm Israel next
> Thuesday, April 23.
>
Ok, I think we converged on a time: 9am US Eastern / 4pm Israel next
Thuesday, April 23.
I'll send the webex invites in a separate email. Mike: if you have
slides or other electronic material to show during the call, we can
use webex for that. Otherwise, we can just use the telephone
I have been listening in on the thread, but have not had time to
really look at much (which is why I have not been replying). I'm
interested in listening in on the teleconf as well, though if I become
a blocker for finding a time feel free to cut me out.
Best,
Josh
On Apr 14, 2009, at
On Wed, Apr 15, 2009 at 8:50 PM, Jeff Squyres wrote:
> On Apr 15, 2009, at 1:45 PM, Mike Dubman wrote:
>
> yep. correct. We can define only static attributes (which we know for sure
>> should present in every object of given type and leave phase specific
>> attributes to
On Wed, Apr 15, 2009 at 5:23 PM, Jeff Squyres wrote:
> On Apr 15, 2009, at 9:14 AM, Mike Dubman wrote:
>
> Hmm. Ok, so you're saying that we define a "phase object" (for each
>> phase) with all the fields that we expect to have, but if we need to, we can
>> create fields on
On Apr 15, 2009, at 9:14 AM, Mike Dubman wrote:
Hmm. Ok, so you're saying that we define a "phase object" (for each
phase) with all the fields that we expect to have, but if we need
to, we can create fields on the fly, and google will just "do the
right thing" and associate *all* the data
On Wed, Apr 15, 2009 at 3:51 AM, Jeff Squyres wrote:
> On Apr 14, 2009, at 2:27 PM, Mike Dubman wrote:
>
> Ah, good point (python/java not perl). But I think that
>> lib/MTT/Reporter/GoogleDataStore.pm could still be a good thing -- we have
>> invested a lot of time/effort
On Tue, Apr 14, 2009 at 11:50 PM, Ethan Mallove wrote:
> On Tue, Apr/14/2009 09:27:14PM, Mike Dubman wrote:
> >On Tue, Apr 14, 2009 at 5:04 PM, Jeff Squyres
> wrote:
> >
> > On Apr 13, 2009, at 2:08 PM, Mike Dubman wrote:
> >
> >Hello
On Apr 14, 2009, at 2:27 PM, Mike Dubman wrote:
Ah, good point (python/java not perl). But I think that lib/MTT/
Reporter/GoogleDataStore.pm could still be a good thing -- we have
invested a lot of time/effort into getting our particular mtt
clients setup just the way we want them, setting
On Tue, Apr/14/2009 09:27:14PM, Mike Dubman wrote:
>On Tue, Apr 14, 2009 at 5:04 PM, Jeff Squyres wrote:
>
> On Apr 13, 2009, at 2:08 PM, Mike Dubman wrote:
>
>Hello Ethan,
>
> Sorry for joining the discussion late... I was on travel last week and
>
On Tue, Apr 14, 2009 at 5:04 PM, Jeff Squyres wrote:
> On Apr 13, 2009, at 2:08 PM, Mike Dubman wrote:
>
> Hello Ethan,
>>
>
> Sorry for joining the discussion late... I was on travel last week and that
> always makes me waaay behind on my INBOX. :-(
>
> On Mon, Apr 13,
On Apr 13, 2009, at 2:08 PM, Mike Dubman wrote:
Hello Ethan,
Sorry for joining the discussion late... I was on travel last week and
that always makes me waaay behind on my INBOX. :-(
On Mon, Apr 13, 2009 at 5:44 PM, Ethan Mallove
wrote:
Will this translate to
Hello Ethan,
On Mon, Apr 13, 2009 at 5:44 PM, Ethan Mallove wrote:
>
> Will this translate to something like
> lib/MTT/Reporter/GoogleDatabase.pm? If we are to move away from the
> current MTT Postgres database, we want to be able to submit results to
> both the current
On Mon, Apr/13/2009 04:15:23PM, Mike Dubman wrote:
>Hello Guys,
>
>Please comment on the proposed object model and flows. We will have 1-2
>ppl working on this in a 2-3w. Till that moment I would like to finalize
>the scope and flows.
>
>Thanks
>
>Mike.
>
>On Mon,
Hello Guys,
Please comment on the proposed object model and flows. We will have 1-2 ppl
working on this in a 2-3w. Till that moment I would like to finalize the
scope and flows.
Thanks
Mike.
On Mon, Apr 6, 2009 at 4:54 PM, Mike Dubman wrote:
> Hello Guys,
>
> I have
Hello Guys,
I have played a bit with google datastore and here is a proposal for mtt DB
infra and some accompanying tools for submission and querying:
1. Scope and requirements
a. provide storage services for storing test results generated by mtt.
Storage services will be
On Mar 23, 2009, at 9:05 AM, Ethan Mallove wrote:
---+-+--
Resource | Unit| Unit cost
---+-+--
Outgoing Bandwidth | gigabytes | $0.12
Incoming Bandwidth |
I'm playing with google datastore now and will send some proposal and
thoughts.
On Mon, Mar 23, 2009 at 2:33 PM, Jeff Squyres wrote:
> Yes, I think you're right -- making a "schema" for the datastore might be
> quite easy. I'm on travel all this week and likely won't be
The next 2 weeks are pretty tight for me. I'll try to take a look at
the API and send some comments as soon as I am able.
-- Josh
On Mar 23, 2009, at 8:33 AM, Jeff Squyres wrote:
Yes, I think you're right -- making a "schema" for the datastore
might be quite easy. I'm on travel all this
Yes, I think you're right -- making a "schema" for the datastore might
be quite easy. I'm on travel all this week and likely won't be able
to look into this stuff -- can you guys post a proposal and we can
dive into it from that angle?
On Mar 22, 2009, at 6:48 AM, Mike Dubman wrote:
Hello guys,
I`m not sure if we should preserve current DB schema, from one simple reason
- datastore is an object oriented storage and have different rules and
techniques then rdbms.
The basic storage unit in the datastore is an object which can be saved,
loaded and queried.
(hadoop is based on
On Mar 20, 2009, at 10:42 AM, Josh Hursey wrote:
Yeah I think this sounds like a good way to move forward with this
work. The database schema is pretty complex. If you need help on the
database side of things let me know.
To get started, would it be useful to have a meeting over the phone/
Looks like there were 400 applications this year; they selected 150 --
38%. We were in the unlucky 62%. Bummer.
On Mar 18, 2009, at 4:05 PM, Ethan Mallove wrote:
On Wed, Mar/18/2009 03:28:48PM, Josh Hursey wrote:
> So they posted the list of accepted projects and we are -not- on it
> for
On Wed, Mar/18/2009 03:28:48PM, Josh Hursey wrote:
> So they posted the list of accepted projects and we are -not- on it
> for this year:
>
> http://socghop.appspot.com/program/accepted_orgs/google/gsoc2009
>
> Maybe next year. I don't know if they will be sending around a note
> regarding why
So they posted the list of accepted projects and we are -not- on it
for this year:
http://socghop.appspot.com/program/accepted_orgs/google/gsoc2009
Maybe next year. I don't know if they will be sending around a note
regarding why we were not selected to participate. If they do I will
Awesome; many thanks for carrying the baton over the finish line, Josh!
On Mar 13, 2009, at 2:56 PM, Josh Hursey wrote:
The application has been submitted. We find out on March 18 (3 pm) if
we have been accepted. Link to timeline below:
You have to "module load osl merurial" in your shell startup files
somewhere for hg to work on milliways.
On Mar 13, 2009, at 3:15 PM, Ethan Mallove wrote:
On Fri, Mar/13/2009 02:19:24PM, Josh Hursey wrote:
> I just pushed a final draft to the repository. I'll probably plan on
> submitting
The application has been submitted. We find out on March 18 (3 pm) if
we have been accepted. Link to timeline below:
http://socghop.appspot.com/document/show/program/google/gsoc2009/
timeline
Cheers,
Josh
On Mar 13, 2009, at 2:19 PM, Josh Hursey wrote:
I just pushed a final draft to the
I finished a first pass at cleaning up the Ideas page on the Wiki.
All of the ideas were preserved, just some rewording and formatting.
https://svn.open-mpi.org/trac/mtt/wiki/MttNewFeaturesIdeas
If you get a chance, read through this and make sure the text sounds
ok (feel free to clean the
Jeff is going to take the first pass at the application.
I am going to go through the Idea page on the wiki and polish a bit:
https://svn.open-mpi.org/trac/mtt/wiki/MttNewFeaturesIdeas
I'll let folks know when I'm done, and we can start iterating on drafts.
Cheers,
Josh
On Mar 12, 2009, at
I've created a quick-n-dirty hg to collaborate on the GSOC
application. There's a web form to fill out to apply, so let's work
on a .txt file in the hg to get it right.
We have until 3pm US Eastern time tomorrow to submit. Here's the HG:
ssh://www.open-mpi.org/~jsquyres/hg/gsoc/
I've
36 matches
Mail list logo