Dunno, he sounds over excited yet vague to me but his main point is – social network out of the box or he’s talking about collaborative filtering type stuff.
I might me wrong but I think everyone has a different idea about what a community should be. What the rules of intereaction are. My goal would to allow people to create a huge variety of communities by plugging in a few opensocial modules in plone and configuring them.
Should we do something by aiming big and risk having vaporware or should we get the few people who actually need the code now to sprint or collaborate on a useful start to the architecture? And then publisize it? I think the best projects in the plone world have started with some real code with real needs, like plone4artists or getpaid. Then again, maybe its time to do something different?
Actually the more I read, the more it seems that most of what he wants. Easy to install plugins that play nice in one UI… plone already has. Is Drupal really that backward?
Maybe I’m being closed minded. Plone community has always just done its thing in isolation. Maybe creating a “name” will get the kind of support we need to make this happen quicker.
Is plonesocial the right name? We’re not about creating a new CMS and its about adding more social facilities to plone so seems good to me. But perhaps not sticky enough.
From: plone-socia...@googlegroups.com [mailto:plone-socia...@googlegroups.com] On Behalf Of Nate Aune
Sent: Friday, 28 March 2008 12:38
AM
To: plone-socia...@googlegroups.com
Nate,
You've got the experience with P4A.
My guess would be that usually a buzz is created not so much because
of a manifesto, but because something specific really appeals to
people. A manifesto may attract some people who go for the buzz for a
short while, but then it fizzles. So this guy, whoever he is, may get
the buzz now, but how will that be in 2-3 months from now.
If you can build a team quickly, have clear milestones, such a hype
may work to get funding. Maybe that is his intention.
So.... all of this leads me to believe that if plone social cannot
even create a buzz inside its own plone community, it's difficult to
see how you can attract a buzz outside of it, and even more attract
the coders to build it (which automatically have to come from
within).
I believe, build it and they will come... IF its useful... and if it's not,
then nothing can save it anyway.
Resistance within Plone is from core developers I think is due to requests
to make the core bigger and not solely about being a CMS... and I think that
is great. Focus is everything. That drupal thing won't get far if it
continues with its lack of focused approach.
So whats our focus? Whats a concrete goal we can describe easily?
"Ability to make any Plone site viral" is my first thought. That means
either bringing in new people into a site or bringing in other members into
what your doing on a site.
I propose a virtual sprint on opensocial.invite. I'm in AU which pretty far
from any normal Plone sprint.
> -----Original Message-----
> From: plone-socia...@googlegroups.com [mailto:plone-social-
> netwo...@googlegroups.com] On Behalf Of Patrick
> Sent: Friday, 28 March 2008 11:06 AM
> To: Plone Social Networking
> Subject: Re: Pirillo Starts Large Scale Community CMS Project
>
>
On Fri, Mar 28, 2008 at 1:54 AM, Dylan Jay <dja...@gmail.com> wrote:
>
> Creating buzz is good if you need developers. Which chris does since he's
> not one.
>
> I believe, build it and they will come... IF its useful... and if it's not,
> then nothing can save it anyway.
>
> Resistance within Plone is from core developers I think is due to requests
> to make the core bigger and not solely about being a CMS... and I think that
> is great. Focus is everything. That drupal thing won't get far if it
> continues with its lack of focused approach.
>
> So whats our focus? Whats a concrete goal we can describe easily?
> "Ability to make any Plone site viral" is my first thought. That means
> either bringing in new people into a site or bringing in other members into
> what your doing on a site.
>
> I propose a virtual sprint on opensocial.invite. I'm in AU which pretty far
> from any normal Plone sprint.
+1 for a virtual sprint for getting started on that kind of feature.
Also, if some of you are close to Paris, we can try to get something
done, by combining with virtual attendance, at the coming Paris
sprint.
Cheers,
Kamon
> -----Original Message-----
> From: plone-socia...@googlegroups.com [mailto:plone-social-
> netwo...@googlegroups.com] On Behalf Of Patrick
> Sent: Saturday, 29 March 2008 9:27 AM
> To: Plone Social Networking
> Subject: Re: Pirillo Starts Large Scale Community CMS Project
>
>
> -----Original Message-----
> From: plone-socia...@googlegroups.com [mailto:plone-social-
> netwo...@googlegroups.com] On Behalf Of Patrick
> Sent: Sunday, 30 March 2008 7:46 PM
> To: Plone Social Networking
> Subject: Re: Pirillo Starts Large Scale Community CMS Project
>
>
> -----Original Message-----
> From: plone-socia...@googlegroups.com [mailto:plone-social-
> netwo...@googlegroups.com] On Behalf Of Patrick
> Sent: Saturday, 29 March 2008 6:05 PM
> To: Plone Social Networking
> Subject: Re: Pirillo Starts Large Scale Community CMS Project
>
>
Main focus is Plone, but I think there is a slot for complementary or
othogonal subjects. For example, there will be people working on
adding grok component registration techniques to Plone.
Cheers,
Kamon
+1 for that first use case.
I would be on-site and could coordinate if needed.
-- Kamon
It seems everyone is keep on modeling people, contacts but Plone already has a model of a person, and that’s a plone Member. Yes, it’s a bit simple, but products like ReMember work within that API to add more functionality in terms of better profiles.
My question is, what is we want achieve by some new concept of Person etc separate from Member? If’s a real need, then lets see the usecase.
Otherwise I’d like to try building the whole thing without mucking around with plones existing concept of a member.
Why?
- Means maximum compatibility with other products like PloneBoard etc
- Reduces complexity.
- Means future efforts to improve profile management etc like ReMemeber or plone core stuff don’t collide with our development. I don’t want to great upgrade nitemares like I’ve had with CMFMember.
- Means each of our plonesocial components can work independently without each other, and without having to assume our own Member implementation.
Or am I way off base here?
From: plone-socia...@googlegroups.com [mailto:plone-socia...@googlegroups.com] On Behalf Of Christian Scholz / Tao Takashi
(SL)
Sent: Tuesday, 1 April 2008 4:29
AM
To: plone-socia...@googlegroups.com
Subject: Re: Pirillo Starts Large
Scale Community CMS Project
As said, for me personally it would be more beneficial to work on the underlying data structures and model person, contacts etc. so I can use this to get the standards and formats for Data Portability up and running. But as the structure needed might need some input from use cases it makes sense to collect (more detailed) use cases first anyway.
It seems everyone is keep on modeling people, contacts but Plone already has a model of a person, and that's a plone Member. Yes, it's a bit simple, but products like ReMember work within that API to add more functionality in terms of better profiles.
My question is, what is we want achieve by some new concept of Person etc separate from Member? If's a real need, then lets see the usecase.
Otherwise I'd like to try building the whole thing without mucking around with plones existing concept of a member.
Why?
- Means maximum compatibility with other products like PloneBoard etc
- Reduces complexity.
- Means future efforts to improve profile management etc like ReMemeber or plone core stuff don't collide with our development. I don't want to great upgrade nitemares like I've had with CMFMember.
- Means each of our plonesocial components can work independently without each other, and without having to assume our own Member implementation.
Or am I way off base here?