Re: OneSocialWeb Project Status
evan
<Daniel.A...@vodafone.com> wrote:
> However, we have limited resources, and we have now taken the decision
to
> concentrate what time we can spend on the federated social Web in the
area
> of protocols and standards. This means we will not be actively updating
the
> code base for OneSocialWeb (server or client), nor will we be adding
> features. We will Continue to work on the protocol, and will support any
> implementers (such as ProcessOne) and collaborate with them to improve
it
> and expand it. Our intention is to contribute the work we have done on
> XMPP
> extensions (e.g. Activity Streams over XMPP) into the relevant XMPP
> technical committees.
Daniel,
Sorry to hear about this, but I think that this kind of change can be
extremely helpful for a project.
-Evan
Simon Tennant (buddycloud)
What I do fear is the one size fits all approach to these frameworks.
All services have some basic elements: activity streams, followers,
following, posts. Beyond that, they have very different business logic
and I've never seen anyone propose a solution and indeed don't think
it's often even possible to find an elegant mashing-together of the
different rules.
How would your framework deal with the different business logic between
sites/codebases?
S.
On 22/06/2011 16:06, ProjectParadigm-ICT-Program wrote:
> Wouldn't a general framework for federating social webs based on what users want instead of a technology make more sense? Combining SIOC standards, OMA standards, SemWeb and open source standards and the enabling technologies should automatically follow.
>
> Milton Ponson
> GSM: +297 747 8280
> PO Box 1154, Oranjestad
> Aruba, Dutch Caribbean
> Project Paradigm: A structured approach to bringing the tools for sustainable development to all stakeholders worldwide by creating ICT tools for NGOs worldwide and: providing online access to web sites and repositories of data and information for sustainable development
>
> This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.
>
>
> --- On Wed, 6/22/11, Appelquist, Daniel, VF-Group <Daniel.A...@vodafone.com> wrote:
>
> From: Appelquist, Daniel, VF-Group <Daniel.A...@vodafone.com>
> Subject: OneSocialWeb Project Status
> To: "W3C Federated Social Web Incubator" <public-xg-fede...@w3.org>
> Cc: federated-...@googlegroups.com, onesoc...@googlegroups.com
> Date: Wednesday, June 22, 2011, 1:11 PM
>
> Hello Federated Social Web peeps -
>
> I'm writing to let you all know what is happening with the OneSocialWeb
> project. As many of you know, this project was originally conceived by
> Laurent Eschenauer and Alard Weisscher in late 2009. Along with Diana Cheng
> (and with some encouragement and cheerleading from myself and others in
> Vodafone R&D) they built the project up as a prototype of what you could do
> with XMPP in the federated social networking space. Unfortunately, due to
> some circumstances out of all of our control, Laurent and Alard had to leave
> Vodafone. At that point, we took the decision to continue the project with
> myself and Diana. During the past year we have kept the project going,
> including adding some new features (e.g. commenting) and we've also seen the
> open source community around OneSocialWeb grow, with a few
> community-developed clients (notably, the iPhone client). We've also
> learned a lot about the federated social networking space both through the
> project and through participation in the burgeoning community.
>
> However, we have limited resources, and we have now taken the decision to
> concentrate what time we can spend on the federated social Web in the area
> of protocols and standards. This means we will not be actively updating the
> code base for OneSocialWeb (server or client), nor will we be adding
> features. We will Continue to work on the protocol, and will support any
> implementers (such as ProcessOne) and collaborate with them to improve it
> and expand it. Our intention is to contribute the work we have done on XMPP
> extensions (e.g. Activity Streams over XMPP) into the relevant XMPP
> technical committees.
>
> Having said all that, all the code that has been produced is up there on
> GitHub. I know that several projects have used the code to develop their
> own prototypes. It's our view that the OneSocialWeb open source community
> has not grown to the point where it can become self-sustaining, but if
> anyone would like to step forward to take ownership of the code-base we
> would be more than happy to discuss this.
>
> As we stated in the summit in Berlin, we are committed to making the FSW
> a reality, and we (Diana and I) will continue actively participating in the
> FSW incubator group and list and will con tribute to all the XMPP social
> specs, and not only OSW. We will also like to be there to facilitate in any
> way we can the work and activities of the FSW community.
>
> Thanks,
> Dan Appelquist
> Vodafone Group R&D
>
--
Simon Tennant
mobile: +49 17 8545 0880
office: +49 89 4209 55854
office: +44 20 7043 6756
xmpp: si...@buddycloud.com
build your own open and federated social network - http://open.buddycloud.com
luca.f...@gmail.com
sorry to hear about that!
I still think that federated social networks is a great idea and I hope we will hear of it more and more in the future.
Regarding OneSocialWeb in particular, I believe we are lacking users: it is difficult not to admit that, after managing a OSW node for a year, having a little more than 10 active users is not such a success!
Nevertheless, I will keep the node up and running still for a while and let's see if any of us will come up with new ideas for developing the project any further
Ciao
Luca
Sent from my BlackBerry® wireless device from WIND
Matěj Cepl
> Regarding OneSocialWeb in particular, I believe we are lacking users:
> it is difficult not to admit that, after managing a OSW node for a
> year, having a little more than 10 active users is not such a success!
I believe the biggest problem OSW (and to some extent Diaspora) has is
its lack of integration with the rest free microblogging world. It sucks
that we have to keep two clients (fortunately in my case integrated into
one Jabber client) for Twitter and Identi.ca (Evan, when is true two-way
integration with TWitter coming to identi.ca? Is it a legal issue or
what?).
To keep even third client (which doesn't exist BTW, so you have to have
opened tab in Firefox on it) which doesn't bring any tangible benefits
comparing to identi.ca (except for the community of all those lovely but
ten people) is just too much.
It is my opinion that if anybody wants to do anything related to
microblogging, integration with the rest of the space should go first.
Or at least some (even quite rudimentary) integration with plain XMPP
clients (see upd...@identi.ca ... yes, I do copy all those numbers to
get reply #76986580 ;)).
So Long, and Thanks for All the Fish
Matěj
@eschnou
Andreas Kuckartz
> It's our view that the OneSocialWeb open source community
> has not grown to the point where it can become self-sustaining, but if
> anyone would like to step forward to take ownership of the code-base we
> would be more than happy to discuss this.
While there is no self-sustaining community around OneSocialWeb there
are other communities which might become interested in
using/integrating/taking over parts of it.
One project I am thinking about is Apache Wave (also using XMPP and
Java) which is currently in the Apache Incubator:
https://incubator.apache.org/wave/
BTW: I noticed that OpenFire since recently (last released version
3.7.0) is also using the Apache Licence 2.0.
Cheers,
Andreas
Ross Gardler
> Am 22.06.2011 15:11, schrieb Appelquist, Daniel, VF-Group:
>
> > It's our view that the OneSocialWeb open source community
> > has not grown to the point where it can become self-sustaining, but if
> > anyone would like to step forward to take ownership of the code-base we
> > would be more than happy to discuss this.
>
> While there is no self-sustaining community around OneSocialWeb there
> are other communities which might become interested in
> using/integrating/taking over parts of it.
>
> One project I am thinking about is Apache Wave (also using XMPP and
> Java) which is currently in the Apache Incubator:https://incubator.apache.org/wave/
Widget specs. One of the additional features it provides is wave
integration to allow widgets to share data (it uses the wave APIs it
does not implement a full Wave application like Apache Wave). There is
also Apache Rave which is a portal framework that uses OpenSocial
gadgets and W3C Widgets as the user interface elements. Both these
projects are incubating projects.
I don't know how much scope there is for bringing the OneSocialWeb
protocols and standards into Apache Wookie, but if anyone wants to
explore it I'd be happy to try and facilitate it.
Ross