Hi Scott,
I agree that using the reply box at the bottom of the wave does not work too
well for discussing points in the top blip after many replies are made. I'd
suggest two alternatives:
* Use inline replies, by selecting a location in the top blip then creating
a reply (hit enter, click the bl
James,
Also, I noticed that you added pages, but it didn't look like you added any
navigation links to the new content. Once I test this out I will let you know.
~Michael
On Apr 6, 2011, at 8:40 PM, James Purser wrote:
> Ah that could be why none of the changes I made showed up :)
>
>
> On
Ok, I need to circle back with the infra guys to see how comments are imported.
There might be a way to build out this script that would make the import
easier, if they can tell me the proper import format.
~Michael
On Apr 6, 2011, at 8:40 PM, Soren Lassen wrote:
> FYI, James Purser has writt
Ah that could be why none of the changes I made showed up :)
On Thu, Apr 7, 2011 at 1:34 PM, Soren Lassen wrote:
> That sounds great. Thanks for doing this!
>
> On Thu, Apr 7, 2011 at 1:23 PM, Michael MacFadden
> wrote:
> > All,
> >
> > I have been working with infra to get the new svnpubsub m
FYI, James Purser has written a script:
http://code.google.com/p/wave-protocol/source/browse/issue_exporter.py
which exports the code.google.com/p/wave-protocol issues in a CSV, but
there are some important unresolved shortcomings, including that it
doesn't capture comments, as you say. See the T
That sounds great. Thanks for doing this!
On Thu, Apr 7, 2011 at 1:23 PM, Michael MacFadden
wrote:
> All,
>
> I have been working with infra to get the new svnpubsub mechanism in place on
> the site to avoid having to SSH into people.apache.org and do an "svn up"
> after making changes in the C
All,
I have been working with infra to get the new svnpubsub mechanism in place on
the site to avoid having to SSH into people.apache.org and do an "svn up" after
making changes in the CMS system. This should be in place now. I will be
testing it out this week. I will keep you all posted.
~
All,
I am working with the infra crew to get our Jira issues ported over. The way
we do this is to basically give them a CSV of the current issues. The
question is what do we want to export exactly from the google code project and
does anyone know how we can export them.
From the issue list
Hi Scott,
I'm assuming you're referring to Google Wave and not WIAB. In Google
Wave, you can hit the space bar to go to the next unread blip.
Dan
Στις 7 Απριλίου 2011 12:06 μ.μ., ο χρήστης Scott Mitchell
έγραψε:
> I'm not sure this made a lot of sense. All I'm saying is... when there's
> someth
I'm not sure this made a lot of sense. All I'm saying is... when there's
something important at the top of a wave then it's a pain to scroll very far
to see comments about it. I've noticed that family/friends don't know when
a comment is added and don't scroll down to check.
My favorite thing about wave is the ability to mix document use cases with
informal dialogue.
Here are two use cases:
Use case 1:
A friend and I play correspondence chess. The current game is at the top of
the wave. When games are finished the moves are copied down below the gadget
(in the same
11 matches
Mail list logo
