1:58 a.m.
----- Original Message -----
From: "Robert Middleswarth"
<robert(a)middleswarth.net>
To: infra(a)ovirt.org
Sent: Wednesday, August 15, 2012 3:25:33 AM
Subject: Re: Etherpad instance for ovirt
Sorry about the blank
On 08/14/2012 10:16 AM, Karsten 'quaid' Wade wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 08/07/2012 12:24 PM, Moran Goldboim wrote:
>
>> Love the idea, actually did it just couple of weeks ago on one of
>> our envs here - i used etherpad lite, including table support
>> (very
>> cool - very unstable...). if will get some resources for it - i
>> can
>> bring it up. just to be clear it isn't the most reliable data
>> source (etherpad in general).
> Agreed about data source. I recommend we make it a policy that
> nothing
> "lives" on the Etherpad. When something is finished, the contents
> have
> to be copied to a wiki page for real permanence. (Etherpad doesn't
> seem to have a great content search feature, so if you lose a URL
> you
> might lose the content.)
What useful feature does etherpad provide? The one of two times i
have
used etherpad it cashed and lost data. It seems to be some kind
mult-user data entry system but what makes it better then other
system
designed to for that?
Thanks
Robert
I'll give you my use cases, and I know there are others.
1. Getting ready for a meeting: agenda proposal
You start an agenda for meeting XXX on date YYY.
Then send the link to all participants. Each participant get his/her
entries highlighted in a different color, so people can see who proposed
what. Use inline chat while writing (aka collaboration...).
So you may end up with something like:
http://blog.teachernz.com/files/2009/03/etherpad3.jpg
2. While in meeting
The pad is updated while everyone can see it, add comments if needed.
Think of the previous image with more comments.
3. Other potential case is looking at code snips;
Take a look here: http://www.codingmonkeys.de/subethaedit/images/sessionbig.png
Just one comment WRT Karsten's remark on things which should not "live"
in the pad. I think it would be reasonable to keep pads alive for a day or so,
so people from different time-zones may catchup if needed. But I agree with
the concept that all pads may be deleted within one week from last change.
It's possible to add a default header to each newly created pad, which will
say that the pad will be automatically deleted within a week from last
activity date, so people will be aware of it.
>
> - - Karsten
> - --
> Karsten 'quaid' Wade, Sr. Analyst - Community Growth
> http://TheOpenSourceWay.org .^\ http://community.redhat.com
> @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iD8DBQFQKl3M2ZIOBq0ODEERAhuYAKDFvJFqimvDCo6lsivrvuOP/oKOXQCfZj9s
> 7ICxfVH/axaoY7e1DWT71bk=
> =FyAN
> -----END PGP SIGNATURE-----
>
_______________________________________________
> Infra mailing list
> Infra(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
--
Thanks
Robert Middleswarth
@rmiddle (twitter/IRC)
_______________________________________________
Infra mailing list
Infra(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra