28 Mar
2009
28 Mar
'09
9:33 p.m.
Hi all.
I would like to participate GSoC and work by XWiki. I am interested in idea
"XWiki Jabber, Google Talk, Skype Integration".
Main aim of described idea is to use some kind of chat rooms. Those chat
rooms should be used for discuss editions and log this discussions to
wiki(please correct me if I am wrong).
What I propose is publish-subscribe mechanism, it is part of
XMPP(Jabber/GTalk) standard. It allows to create messages categorized by
nodes. When message is add, modify or delete from node there is notification
sent to all subscribers (like RSS or ATOM). Main advantage of this solution
is that users may use their jabber accounts for subscribe discussion or
publish something in it.
Here is small comparison:
chat logging:
* To be at home in subject someone have to read all chat log.
pubsub:
* You may subscribe only nodes you are interested in and ignore
uninteresting.
chat logging:
* Chat has specific convention, there is a lot of short messages, statements
are not well-thought-out, there are a lot of misunderstandings and
explanations of it
* After logged all chat. It may be necessary to moderate discussion. We have
to create special tool for this and someone have to do the work.
pubsub:
* When people publish some "post" they have more time to think about it. It
is possible to modify posted unclear statements. Author can even delete
unnecessary own posts (in both situations all subscribers will be notify).
Main disadvantage of pubsub is that it will be more difficult to port this
for Skype and other closed protocols. But users can always use expected
built-in XWiki pubsub client.
Plese give me feedback about this idea.
Jan J. Roman
30 Mar
30 Mar
5:33 p.m.
Hi Jan,
On Sat, Mar 28, 2009 at 9:33 PM, Jan J. Roman <poczta(a)jjroman.net> wrote:
Hi all.
I would like to participate GSoC and work by XWiki. I am interested in idea
"XWiki Jabber, Google Talk, Skype Integration".
Main aim of described idea is to use some kind of chat rooms. Those chat
rooms should be used for discuss editions and log this discussions to
wiki(please correct me if I am wrong).
What I propose is publish-subscribe mechanism, it is part of
XMPP(Jabber/GTalk) standard. It allows to create messages categorized by
nodes. When message is add, modify or delete from node there is
notification
sent to all subscribers (like RSS or ATOM). Main advantage of this solution
is that users may use their jabber accounts for subscribe discussion or
publish something in it.
Here is small comparison:
chat logging:
* To be at home in subject someone have to read all chat log.
pubsub:
* You may subscribe only nodes you are interested in and ignore
uninteresting.
chat logging:
* Chat has specific convention, there is a lot of short messages,
statements
are not well-thought-out, there are a lot of misunderstandings and
explanations of it
* After logged all chat. It may be necessary to moderate discussion. We
have
to create special tool for this and someone have to do the work.
pubsub:
* When people publish some "post" they have more time to think about it. It
is possible to modify posted unclear statements. Author can even delete
unnecessary own posts (in both situations all subscribers will be notify).
Main disadvantage of pubsub is that it will be more difficult to port this
for Skype and other closed protocols. But users can always use expected
built-in XWiki pubsub client.
Plese give me feedback about this idea.
If I understand well, your idea is about building a system where people will
be able to exchange messages through a mix of chat client + wiki + RSS /
ATOM. This seems somewhat similar to building a forum where you would add
replies through an XMPP interface rather than through a web one. It would
have the following steps:
1. Create a new discussion on the wiki
2. Send messages to that discussion through Jabber
3. Be notified of new messages via RSS
This looks complex to me. 2 remarks:
- The initial proposal aims at addressing 2 needs:
- *Storing content from chat discussions in the wiki to archive them
and make them searchable*. The aim is to not get in the way of chat
users but rather provide them with a public searchable archive.
This is an
important part of the project and does not seem to be addressed by your
proposal.
- *Letting users chat right into the wiki. *This means letting people
exchange messages together while working on a page for instance. The use
case described here is for real-time communication while your proposal is
not.
- The overall description of your project makes it look complex. However,
it might be integrated with other projects. for instance, it might be
interesting to follow posts in a bulletin board through your chat client.
However these are improvements to another application and as such don't
warrant a full GSoC project spot.
The best advice I can give to you is either to give a second look at the
project description and update your GSoC application form with ideas that
match it more closely or to choose another project from the list (there are
plenty to choose from on
http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/ :-)
You can also build your Publication / Subscription system on your own and
contribute it to the project outside the frame of the GSoC if that's what
you absolutely want to create ;-)
Hope this will help you make your application successful,
Guillaume
Jan J. Roman
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Guillaume Lerouge
Product Manager - XWiki
Skype ID : wikibc
http://guillaumelerouge.com/
6:22 p.m.
Hi,
If I understand well, your idea is about building a system where people
will
be able to exchange messages through a mix of chat client + wiki + RSS /
ATOM. This seems somewhat similar to building a forum where you would add
replies through an XMPP interface rather than through a web one. It would
have the following steps:
1. Create a new discussion on the wiki
2. Send messages to that discussion through Jabber
3. Be notified of new messages via RSS
Ad. 3 I would rather said that user will be notified by something like RSS.
This something is part of XMPP. It makes this solution real-time one.
Notifications are not standard messages, client should rather display it as
a change in subscribed node.
This looks complex to me. 2 remarks:
- The initial proposal aims at addressing 2 needs:
- *Storing content from chat discussions in the wiki to archive them
and make them searchable*. The aim is to not get in the way of chat
users but rather provide them with a public searchable archive.
This is an
important part of the project and does not seem to be addressed by
your
proposal.
I don't know did you look into my application but I already proposed some
store mechanism so bind it with search engine shouldn't be very difficult
but rather a obvious issue.
- *Letting users chat right into the wiki. *This means letting people
exchange messages together while working on a
page for instance. The
use
case described here is for real-time communication while your proposal
is
not.
As I said my proposal is not real chat but it is real-time. I mentioned
disadvantages of chat logging in my last mail.
Thank you for your advices and review. I would rather change my proposal and
describe other solution instead change picked up idea. IMs are my branch so
I would like to work with them, I am also keen on cross technologies
services ... so this idea is created for me. I saw that some other student
is working on this case but GSoC is a competition.
Jan J. Roman
5649
days inactive
5651
days old
2 comments
2 participants
participants (2)
-
Guillaume Lerouge -
Jan J. Roman