Community Plugin - Current State

[Michael Knoll-2]

Hi folks,

after I wrote my last test for this holidays last friday, Lars and I
started to write the first lines of code for the community extension. We
decided to use lib/div although it's really a hard piece of work to get
through the code and to find out how everything works. As Elmar
explained to me, it's still alpha.

We try to set up a basic extension with most of the wishes you posted on
  the wiki.

At the moment we are concentrating on the following functionality:

- User registration (first step is done via fe_user_registration)
- User settings and privacy settings (extending fe_users and creating a
own table for complex privacy settings)
- User search
- Add/Remove Buddies
- Show relations between buddies
- A configurable user list to cope with any kind of user listing
(search-list, buddy-list, group-members-list, ...)

The next step will be to put up groups. We decided to extend
fe_user_groups for that purpose and will put up some functionality that
enables users to join groups or to invite other users into groups etc.

After that, we will put up a messaging system, that enables users to
send messages on public boards as well as on private messaging.

That will be the core of the extension. We are thinking about a kind of
a plugin concept to make the extension work with community-extensions to
get a modular concept, but that will be one of the later points.

We also decided to put up the basic functionality with new extensions
based on lib/div as most of the old extensions are based on pibase. As
soon as there is a example-installation of it, we will send a link to
the list.

So far - regards

Mimi
_______________________________________________
TYPO3-project-community mailing list
TYPO3-project-community@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-project-community

[Paul Blondiaux]

Hi mimi,

We just worked on an extension related to this community concept for a large
client of us, maybe I can send the alpha to you if that can help.
PM me at : paul.blondiaux@...

Regards

Paul Blondiaux


Le 25/09/07 1:02, dans
mailman.1.1190674978.20050.typo3-project-community@...,
« Michael Knoll » <mimi@...> a écrit :

> Hi folks,
>
> after I wrote my last test for this holidays last friday, Lars and I
> started to write the first lines of code for the community extension. We
> decided to use lib/div although it's really a hard piece of work to get
> through the code and to find out how everything works. As Elmar
> explained to me, it's still alpha.
>
> We try to set up a basic extension with most of the wishes you posted on
>   the wiki.
>
> At the moment we are concentrating on the following functionality:
>
> - User registration (first step is done via fe_user_registration)
> - User settings and privacy settings (extending fe_users and creating a
> own table for complex privacy settings)
> - User search
> - Add/Remove Buddies
> - Show relations between buddies
> - A configurable user list to cope with any kind of user listing
> (search-list, buddy-list, group-members-list, ...)
>
> The next step will be to put up groups. We decided to extend
> fe_user_groups for that purpose and will put up some functionality that
> enables users to join groups or to invite other users into groups etc.
>
> After that, we will put up a messaging system, that enables users to
> send messages on public boards as well as on private messaging.
>
> That will be the core of the extension. We are thinking about a kind of
> a plugin concept to make the extension work with community-extensions to
> get a modular concept, but that will be one of the later points.
>
> We also decided to put up the basic functionality with new extensions
> based on lib/div as most of the old extensions are based on pibase. As
> soon as there is a example-installation of it, we will send a link to
> the list.
>
> So far - regards
>
> Mimi

_______________________________________________
TYPO3-project-community mailing list
TYPO3-project-community@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-project-community

[Ingo Renner-2]

Hi all,

I've until now been a silent group watcher. Anyways today I'd like to
give some advice to get the best out of your efforts for the community
and preservinf the "TYPO3 feeling" and best practices...

I really like your idea of having a set of community feature extensions!

typo3.org will soon be getting a lot more community features, which is
just another reason taht makes me interested in your efforts and to team
up with you!


Michael Knoll wrote:

> after I wrote my last test for this holidays last friday, Lars and I
> started to write the first lines of code for the community extension. We
> decided to use lib/div although it's really a hard piece of work to get
> through the code and to find out how everything works. As Elmar
> explained to me, it's still alpha.
>
> We try to set up a basic extension with most of the wishes you posted on
>  the wiki.

To make maintainance easy and smooth I suggest you split things up into
multiple extension like the following:

community or community_core (collecting all base functions for the other
extensions)
community_feuserregister
community_messages
community_buddies

community_whatever ...

History has shown that it really gets hard to maintain a big extension.
I for myself can tell that from TIMTAB, a recent example is commerce and
a rather good example would be DAM (the way features are split into
separate extesions, not the development process ;-)

Also to make it easy to remember what which plugin does: In commerce and
TIMTAB we did the mistake to put a lot of plugins and mods in one
extension without naming them. The result is pi1...pi6, mod1 .... modX -
now which one does what? In fact xou can choose whatever name you want,
go for it! A good thing which an upcoming version of the kickstarter
will do also is using prefixes: piMessages, modUserAdmin ... so you can
still distinguish between plugins and modules.

It also showed with TIMTAB and DAM already that it's good to have all
extensions start with the same prefix (timtab_, dam_, commerce_). This
makes it easily obvious that the extensions belong together. Also please
  refrain from putting personal initials in front of extensions keys:
http://news.typo3.org/news/article/about-extension-maintainance/news/

> At the moment we are concentrating on the following functionality:
>
> - User registration (first step is done via fe_user_registration)

One note: I couldn't find that extKey in TER, in case you meant
sr_feuser_register, please do not use it because of Franz' update policy.


> - User settings and privacy settings (extending fe_users and creating a
> own table for complex privacy settings)
> - User search

please also reuse functions from "standard" extensions, newloginbox has
a search AFAIR.


> - A configurable user list to cope with any kind of user listing
> (search-list, buddy-list, group-members-list, ...)

For newloginbox I  at least know that it has a listing plugin. This
leads to the next advise: If there's already a "standard" extension, use
it and contribute to it! In case of listing users I also could think of
pulling the function out of newloginbox and moving it to
community_userlisting... f.e. (Robert would talk of "separation of
concerns" in TYPO3 5.0 speak ;-)

> The next step will be to put up groups. We decided to extend
> fe_user_groups for that purpose and will put up some functionality that
> enables users to join groups or to invite other users into groups etc.

great idea, we'll for sure use that for typo3.org!

> That will be the core of the extension. We are thinking about a kind of
> a plugin concept to make the extension work with community-extensions to
> get a modular concept, but that will be one of the later points.

I think if you do it like I suggested you can't do too much wrong here ...

> We also decided to put up the basic functionality with new extensions
> based on lib/div as most of the old extensions are based on pibase. As
> soon as there is a example-installation of it, we will send a link to
> the list.

All cool!

One last thing: With TIMTAB I tried to unite the configuration of the
plugins in a single namspace. That means that the core community
extension would introduce a TS configuratin space
"plugins.tx_community". The messaging options would go into
plugins.tx_community.messages, user settings into
plugins.tx_community.users and so on - even if users and messages are in
different extensions then the core. This makes configuration more easy
and logical.



all the best, have fun!
Ingo


P.S. I think I should put all this stuff in a new version of that
extension maintainance article - what do you think, are those hints
usefull, do they sound good?
_______________________________________________
TYPO3-project-community mailing list
TYPO3-project-community@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-project-community

[Volker Graubaum]

Hi,

> I've until now been a silent group watcher.

Me to ;-)

> I really like your idea of having a set of community feature extensions!
Me to ;-)

> typo3.org will soon be getting a lot more community features, which is
> just another reason taht makes me interested in your efforts and to team
> up with you!

Me to ;-)

> To make maintainance easy and smooth I suggest you split things up into
> multiple extension like the following:
>
> community or community_core (collecting all base functions for the other
> extensions)
> community_feuserregister
> community_messages
> community_buddies
>
> community_whatever ...

Nice Idea, so is there already a wiki page for collecting ideas?
Otherwise we should start one

> History has shown that it really gets hard to maintain a big extension.
> I for myself can tell that from TIMTAB, a recent example is commerce and
> a rather good example would be DAM (the way features are split into
> separate extesions, not the development process ;-)

You're write, so a bigger team would be great, and someone who makes
projectManagement for that, to be sure, that developing goes in the
right way.

> Also to make it easy to remember what which plugin does: In commerce and
> TIMTAB we did the mistake to put a lot of plugins and mods in one
> extension without naming them. The result is pi1...pi6, mod1 .... modX -
> now which one does what? In fact xou can choose whatever name you want,
> go for it! A good thing which an upcoming version of the kickstarter
> will do also is using prefixes: piMessages, modUserAdmin ... so you can
> still distinguish between plugins and modules.

That's right, but here I don't see a big problem, but it would be nicer ;-)

BUT about the number of plugins in

In fact, I even like bringing things together, which belongs together
seems to be useful (example DAM, which was splitted in different extensions.

> It also showed with TIMTAB and DAM already that it's good to have all
> extensions start with the same prefix (timtab_, dam_, commerce_). This
> makes it easily obvious that the extensions belong together. Also please
>  refrain from putting personal initials in front of extensions keys:
> http://news.typo3.org/news/article/about-extension-maintainance/news/
>

What's about Elmars idea extension__somehting.
Will this be realy be the future and is it coordinate with the core team?

>> At the moment we are concentrating on the following functionality:
>>
>> - User registration (first step is done via fe_user_registration)
>
> One note: I couldn't find that extKey in TER, in case you meant
> sr_feuser_register, please do not use it because of Franz' update policy.

Right but it has some good concepts from the past. We are adding Ajax
functionallity in the moment and hat to increase only a few methods and
calls. Maybe it's time to create a new extension, add the good things
from sr_feuser_register to it and bring it to the future ;-)

>> - User settings and privacy settings (extending fe_users and creating
>> a own table for complex privacy settings)
>> - User search

> please also reuse functions from "standard" extensions, newloginbox has
> a search AFAIR.

Nicer would be a generall search over all tables.
I like the way XING has improved the search

>> - A configurable user list to cope with any kind of user listing
>> (search-list, buddy-list, group-members-list, ...)
>
> For newloginbox I  at least know that it has a listing plugin. This
> leads to the next advise: If there's already a "standard" extension, use
> it and contribute to it! In case of listing users I also could think of
> pulling the function out of newloginbox and moving it to
> community_userlisting... f.e. (Robert would talk of "separation of
> concerns" in TYPO3 5.0 speak ;-)

Yes, what's about cwt_community ?

>> The next step will be to put up groups. We decided to extend
>> fe_user_groups for that purpose and will put up some functionality
>> that enables users to join groups or to invite other users into groups
>> etc.
>
> great idea, we'll for sure use that for typo3.org!

+1

>> We also decided to put up the basic functionality with new extensions
>> based on lib/div as most of the old extensions are based on pibase. As
>> soon as there is a example-installation of it, we will send a link to
>> the list.
>
> All cool!

:-)

> One last thing: With TIMTAB I tried to unite the configuration of the
> plugins in a single namspace. That means that the core community
> extension would introduce a TS configuratin space
> "plugins.tx_community". The messaging options would go into
> plugins.tx_community.messages, user settings into
> plugins.tx_community.users and so on - even if users and messages are in
> different extensions then the core. This makes configuration more easy
> and logical.

nice idea... :-)

> P.S. I think I should put all this stuff in a new version of that
> extension maintainance article - what do you think, are those hints
> usefull, do they sound good?

+1

Greetings Volker
_______________________________________________
TYPO3-project-community mailing list
TYPO3-project-community@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-project-community

[Ingo Renner-2]

Volker Graubaum wrote:

> What's about Elmars idea extension__somehting.
> Will this be realy be the future and is it coordinate with the core team?

If you like it - use it. I don't like it because the traditional single
underscore works fine as TIMTAB and DAM demonstrate. I just don't see a
reason to reinvent the wheel or to confuse people. Other then that to me
it just looks ugly. Because of theses reasons I'm not going to use
double underscores and won't promote it. The issue also never was
discussed with the core team - at least not that I know of.

> Maybe it's time to create a new extension, add the good things
> from sr_feuser_register to it and bring it to the future ;-)

definitly!

> Nicer would be a generall search over all tables.
> I like the way XING has improved the search

we can do whatever needs to be done...

> Yes, what's about cwt_community ?

never tried it out or had a look at the quality of the code...


Cool you like nearly all of this, too Volker!


all the best
Ingo

_______________________________________________
TYPO3-project-community mailing list
TYPO3-project-community@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-project-community

[Michael Knoll-2]

Hi Ingo,

as far as I know, you live in Karlsruhe... well - me too :) Perhaps we
could both meet, as I face a lot of problems which I can't solve all by
myself. As you seem to be much more into Typo3, it would be great to
meet you.

Just let me know where and when :)

Greez

Mimi



Ingo Renner wrote:

> Hi all,
>
> I've until now been a silent group watcher. Anyways today I'd like to
> give some advice to get the best out of your efforts for the community
> and preservinf the "TYPO3 feeling" and best practices...
>
> I really like your idea of having a set of community feature extensions!
>
> typo3.org will soon be getting a lot more community features, which is
> just another reason taht makes me interested in your efforts and to team
> up with you!
>
>
> Michael Knoll wrote:
>
>> after I wrote my last test for this holidays last friday, Lars and I
>> started to write the first lines of code for the community extension.
>> We decided to use lib/div although it's really a hard piece of work to
>> get through the code and to find out how everything works. As Elmar
>> explained to me, it's still alpha.
>>
>> We try to set up a basic extension with most of the wishes you posted
>> on  the wiki.
>
> To make maintainance easy and smooth I suggest you split things up into
> multiple extension like the following:
>
> community or community_core (collecting all base functions for the other
> extensions)
> community_feuserregister
> community_messages
> community_buddies
>
> community_whatever ...
>
> History has shown that it really gets hard to maintain a big extension.
> I for myself can tell that from TIMTAB, a recent example is commerce and
> a rather good example would be DAM (the way features are split into
> separate extesions, not the development process ;-)
>
> Also to make it easy to remember what which plugin does: In commerce and
> TIMTAB we did the mistake to put a lot of plugins and mods in one
> extension without naming them. The result is pi1...pi6, mod1 .... modX -
> now which one does what? In fact xou can choose whatever name you want,
> go for it! A good thing which an upcoming version of the kickstarter
> will do also is using prefixes: piMessages, modUserAdmin ... so you can
> still distinguish between plugins and modules.
>
> It also showed with TIMTAB and DAM already that it's good to have all
> extensions start with the same prefix (timtab_, dam_, commerce_). This
> makes it easily obvious that the extensions belong together. Also please
>  refrain from putting personal initials in front of extensions keys:
> http://news.typo3.org/news/article/about-extension-maintainance/news/
>
>> At the moment we are concentrating on the following functionality:
>>
>> - User registration (first step is done via fe_user_registration)
>
> One note: I couldn't find that extKey in TER, in case you meant
> sr_feuser_register, please do not use it because of Franz' update policy.
>
>
>> - User settings and privacy settings (extending fe_users and creating
>> a own table for complex privacy settings)
>> - User search
>
> please also reuse functions from "standard" extensions, newloginbox has
> a search AFAIR.
>
>
>> - A configurable user list to cope with any kind of user listing
>> (search-list, buddy-list, group-members-list, ...)
>
> For newloginbox I  at least know that it has a listing plugin. This
> leads to the next advise: If there's already a "standard" extension, use
> it and contribute to it! In case of listing users I also could think of
> pulling the function out of newloginbox and moving it to
> community_userlisting... f.e. (Robert would talk of "separation of
> concerns" in TYPO3 5.0 speak ;-)
>
>> The next step will be to put up groups. We decided to extend
>> fe_user_groups for that purpose and will put up some functionality
>> that enables users to join groups or to invite other users into groups
>> etc.
>
> great idea, we'll for sure use that for typo3.org!
>
>> That will be the core of the extension. We are thinking about a kind
>> of a plugin concept to make the extension work with
>> community-extensions to get a modular concept, but that will be one of
>> the later points.
>
> I think if you do it like I suggested you can't do too much wrong here ...
>
>> We also decided to put up the basic functionality with new extensions
>> based on lib/div as most of the old extensions are based on pibase. As
>> soon as there is a example-installation of it, we will send a link to
>> the list.
>
> All cool!
>
> One last thing: With TIMTAB I tried to unite the configuration of the
> plugins in a single namspace. That means that the core community
> extension would introduce a TS configuratin space
> "plugins.tx_community". The messaging options would go into
> plugins.tx_community.messages, user settings into
> plugins.tx_community.users and so on - even if users and messages are in
> different extensions then the core. This makes configuration more easy
> and logical.
>
>
>
> all the best, have fun!
> Ingo
>
>
> P.S. I think I should put all this stuff in a new version of that
> extension maintainance article - what do you think, are those hints
> usefull, do they sound good?

_______________________________________________
TYPO3-project-community mailing list
TYPO3-project-community@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-project-community

[Michael Knoll-2]

Ingo Renner wrote:

> Hi all,
>
> I've until now been a silent group watcher. Anyways today I'd like to
> give some advice to get the best out of your efforts for the community
> and preservinf the "TYPO3 feeling" and best practices...
>
> I really like your idea of having a set of community feature extensions!
>
> typo3.org will soon be getting a lot more community features, which is
> just another reason taht makes me interested in your efforts and to team
> up with you!
>
>
> Michael Knoll wrote:
>
>> after I wrote my last test for this holidays last friday, Lars and I
>> started to write the first lines of code for the community extension.
>> We decided to use lib/div although it's really a hard piece of work to
>> get through the code and to find out how everything works. As Elmar
>> explained to me, it's still alpha.
>>
>> We try to set up a basic extension with most of the wishes you posted
>> on  the wiki.
>
> To make maintainance easy and smooth I suggest you split things up into
> multiple extension like the following:
>
> community or community_core (collecting all base functions for the other
> extensions)
> community_feuserregister
> community_messages
> community_buddies
>
> community_whatever ...
>

We are already doing that. At the moment we are planning to put up a
community-core package, with all the basic functionality and three
"core-extensions"

community_user
community_group
community_messaging

If you think, that these packages are still "too big" we could discuss
about dividing them.

> History has shown that it really gets hard to maintain a big extension.
> I for myself can tell that from TIMTAB, a recent example is commerce and
> a rather good example would be DAM (the way features are split into
> separate extesions, not the development process ;-)
>
> Also to make it easy to remember what which plugin does: In commerce and
> TIMTAB we did the mistake to put a lot of plugins and mods in one
> extension without naming them. The result is pi1...pi6, mod1 .... modX -
> now which one does what? In fact xou can choose whatever name you want,
> go for it! A good thing which an upcoming version of the kickstarter
> will do also is using prefixes: piMessages, modUserAdmin ... so you can
> still distinguish between plugins and modules.

Think the naming problem got better with lib/div, as you have multiple
controllers, which are self-explaining by their names. But I can see the
problems, I think.
>
> It also showed with TIMTAB and DAM already that it's good to have all
> extensions start with the same prefix (timtab_, dam_, commerce_). This
> makes it easily obvious that the extensions belong together. Also please
>  refrain from putting personal initials in front of extensions keys:
> http://news.typo3.org/news/article/about-extension-maintainance/news/

The prefix is not fixed yet. I didn't want to use a general ext_key like
community, as I only wanted to play arround until we bring up something
that's worth the key :-)
>
>> At the moment we are concentrating on the following functionality:
>>
>> - User registration (first step is done via fe_user_registration)
>
> One note: I couldn't find that extKey in TER, in case you meant
> sr_feuser_register, please do not use it because of Franz' update policy.
>
I was thinking about sr_feuser_register. I only wanted to use that
extension at the beginning, to get the whole thing to work, without
needing so much time. Bit by bit, I want to rewrite all extensions,
which are not based on lib/div.
>
>> - User settings and privacy settings (extending fe_users and creating
>> a own table for complex privacy settings)
>> - User search
>
> please also reuse functions from "standard" extensions, newloginbox has
> a search AFAIR.

Ok - the search I want to implement is a little more complex at the end,
  as I would like to search for users, which have similarities in their
profiles... But I will take a look at newloginbox

>
>
>> - A configurable user list to cope with any kind of user listing
>> (search-list, buddy-list, group-members-list, ...)
>
> For newloginbox I  at least know that it has a listing plugin. This
> leads to the next advise: If there's already a "standard" extension, use
> it and contribute to it! In case of listing users I also could think of
> pulling the function out of newloginbox and moving it to
> community_userlisting... f.e. (Robert would talk of "separation of
> concerns" in TYPO3 5.0 speak ;-)

The same problem as above, as I wanted to make the list as generic as
possible and use it in different places (buddies list, search-result,
group members list... always with a "add" and a "remove" link, if needed.

>
>> The next step will be to put up groups. We decided to extend
>> fe_user_groups for that purpose and will put up some functionality
>> that enables users to join groups or to invite other users into groups
>> etc.
>
> great idea, we'll for sure use that for typo3.org!
>
>> That will be the core of the extension. We are thinking about a kind
>> of a plugin concept to make the extension work with
>> community-extensions to get a modular concept, but that will be one of
>> the later points.
>
> I think if you do it like I suggested you can't do too much wrong here ...
>
>> We also decided to put up the basic functionality with new extensions
>> based on lib/div as most of the old extensions are based on pibase. As
>> soon as there is a example-installation of it, we will send a link to
>> the list.
>
> All cool!
>
> One last thing: With TIMTAB I tried to unite the configuration of the
> plugins in a single namspace. That means that the core community
> extension would introduce a TS configuratin space
> "plugins.tx_community". The messaging options would go into
> plugins.tx_community.messages, user settings into
> plugins.tx_community.users and so on - even if users and messages are in
> different extensions then the core. This makes configuration more easy
> and logical.

Ok - as I started to use timtab a few weeks ago, I took a closer look on
the way, you do the configuration, and I think, I will copy a little :)

>
>
>
> all the best, have fun!
> Ingo
>
>
> P.S. I think I should put all this stuff in a new version of that
> extension maintainance article - what do you think, are those hints
> usefull, do they sound good?

Yes - that would be very helpful. I also started to document all the
steps I made with lib/div, perhaps it is useful for a
"Extension-Writing-with-lib/div-tutorial"

Where can I get the extension-maintainance article from?

Regards

Mimi
_______________________________________________
TYPO3-project-community mailing list
TYPO3-project-community@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-project-community

[Ingo Renner-2]

Michael Knoll wrote:
> Hi Ingo,
>
> as far as I know, you live in Karlsruhe... well - me too :) Perhaps we
> could both meet, as I face a lot of problems which I can't solve all by
> myself. As you seem to be much more into Typo3, it would be great to
> meet you.

this is new to me ;-)

No, seriously... I live close to Frankfurt/M but I actually was at the
T3CON07 of course...


Just drop me some lines with your skype name, we can use that...

Ingo

_______________________________________________
TYPO3-project-community mailing list
TYPO3-project-community@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-project-community

[Ingo Renner-2]

Michael Knoll wrote:

> We are already doing that. At the moment we are planning to put up a
> community-core package, with all the basic functionality and three
> "core-extensions"
>
> community_user
> community_group

I think they belong so close together that they can/need to go into one
extension (users and groups aren't separated in the core either).

> community_messaging

I'm not quite sure whether everybody would need messages, so IMO they
should g into a separate one. Feel free to do what you think fits best.



> Yes - that would be very helpful. I also started to document all the
> steps I made with lib/div, perhaps it is useful for a
> "Extension-Writing-with-lib/div-tutorial"
>
> Where can I get the extension-maintainance article from?

http://news.typo3.org/news/article/about-extension-maintainance/news/


best
Ingo
_______________________________________________
TYPO3-project-community mailing list
TYPO3-project-community@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-project-community

[Alexander Heim]

Hi,

great to see, that there is a development in this process. Sadly i have
had to muich work the last weeks to do something more and to think about
it.

Now i have a big "but"! The idea of this Community-Community ;-) was or
is in my eyes, to work togehter with a lot of people to get the best out
of typo3 for developing community-websites. So I'm wondering, if i miss
some discussions about the plan, how the stuff will be developed. Is
there already a roadmap? Who is doing what? How is the guideline for
developing? I understand, that just starting and writing code is more
fun in the beginning, but without a clear concept, which is published,
the complete idea of an open set of many small community extensions, who
work easily and perfect together will die.

Maybe i missed some discussions somewhere. I thought, that we wanted to
meet. But strange, this thread died. So whats up? Where? When?

I do not want to be negative, but i leaded and developed some big
software projects and i just know all the problems which will come, if
there is no clear concept before.


But maybe someone can send me a document with the concept and i read it
and say: perfect! everything is thoughtful and i'm happy :-)



Greetz
Alex


Michael Knoll schrieb:

> Hi folks,
>
> after I wrote my last test for this holidays last friday, Lars and I
> started to write the first lines of code for the community extension. We
> decided to use lib/div although it's really a hard piece of work to get
> through the code and to find out how everything works. As Elmar
> explained to me, it's still alpha.
>
> We try to set up a basic extension with most of the wishes you posted on
>  the wiki.
>
> At the moment we are concentrating on the following functionality:
>
> - User registration (first step is done via fe_user_registration)
> - User settings and privacy settings (extending fe_users and creating a
> own table for complex privacy settings)
> - User search
> - Add/Remove Buddies
> - Show relations between buddies
> - A configurable user list to cope with any kind of user listing
> (search-list, buddy-list, group-members-list, ...)
>
> The next step will be to put up groups. We decided to extend
> fe_user_groups for that purpose and will put up some functionality that
> enables users to join groups or to invite other users into groups etc.
>
> After that, we will put up a messaging system, that enables users to
> send messages on public boards as well as on private messaging.
>
> That will be the core of the extension. We are thinking about a kind of
> a plugin concept to make the extension work with community-extensions to
> get a modular concept, but that will be one of the later points.
>
> We also decided to put up the basic functionality with new extensions
> based on lib/div as most of the old extensions are based on pibase. As
> soon as there is a example-installation of it, we will send a link to
> the list.
>
> So far - regards
>
> Mimi

_______________________________________________
TYPO3-project-community mailing list
TYPO3-project-community@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-project-community

[Michael Knoll-2]

Hi Alexander,

let me give you some answers to the questions and "buts" in your mail. A
friend and me wanted or want to build a community (as many people want
to do these days I suppose) and as I did some pages with typo3 and
started to write my own extensions recently, we had the plan to do this
with Typo3.

After evaluating the extension currently available, we missed a lot of
features and after taking a closer look on the code we came to the
conclusion that they are not really useful for our purposes. After
deciding to build our own extension, I found this mail-listing and
posted some of our ideas and wanted to collect some more ideas. We put
up a wiki page on which we tried to collect wish-lists and set up a roadmap.

One goal - which was not only our's but a common wish - was to use
lib/div as a basis and no longer to use pi_base.

After some weeks of planning and talking about the whole thing, I wanted
to start, as we would like to start our website about February next
year. So the "many people work together" approach was - let's say
corrupted by me simply starting to put up some of the functionality that
was on everybody's wishlist.

The biggest problem at the moment seems to be the quick changes in
lib/div, as it is still alpha and you can't be sure that the
functionality you use at the moment is still available with the same
interfaces some weeks later.

As soon as a little core of what we want to create is running, I will
publicate it on TER or t3xdev so that everybody can help making a good
piece of code out of it. At the moment I see no chance to coordinate
more than the two of us (Lars and me) to do the programming stuff. If
you have a better idea or can tell me how to coordinate a team managing
the task, I'd be very thankful if you let me know how to do that.

The plugins we write at the moment are very small and quite
community-low-level, so that I think we can reuse them, no matter how
the whole-big-thing will look like one day.

Hope this explains a little of my problems and my thoughts.

Regards

Mimi



Alexander Heim wrote:

> Hi,
>
> great to see, that there is a development in this process. Sadly i have
> had to muich work the last weeks to do something more and to think about
> it.
>
> Now i have a big "but"! The idea of this Community-Community ;-) was or
> is in my eyes, to work togehter with a lot of people to get the best out
> of typo3 for developing community-websites. So I'm wondering, if i miss
> some discussions about the plan, how the stuff will be developed. Is
> there already a roadmap? Who is doing what? How is the guideline for
> developing? I understand, that just starting and writing code is more
> fun in the beginning, but without a clear concept, which is published,
> the complete idea of an open set of many small community extensions, who
> work easily and perfect together will die.
>
> Maybe i missed some discussions somewhere. I thought, that we wanted to
> meet. But strange, this thread died. So whats up? Where? When?
>
> I do not want to be negative, but i leaded and developed some big
> software projects and i just know all the problems which will come, if
> there is no clear concept before.
>
>
> But maybe someone can send me a document with the concept and i read it
> and say: perfect! everything is thoughtful and i'm happy :-)
>
>
>
> Greetz
> Alex
>
>
> Michael Knoll schrieb:
>> Hi folks,
>>
>> after I wrote my last test for this holidays last friday, Lars and I
>> started to write the first lines of code for the community extension. We
>> decided to use lib/div although it's really a hard piece of work to get
>> through the code and to find out how everything works. As Elmar
>> explained to me, it's still alpha.
>>
>> We try to set up a basic extension with most of the wishes you posted on
>>  the wiki.
>>
>> At the moment we are concentrating on the following functionality:
>>
>> - User registration (first step is done via fe_user_registration)
>> - User settings and privacy settings (extending fe_users and creating a
>> own table for complex privacy settings)
>> - User search
>> - Add/Remove Buddies
>> - Show relations between buddies
>> - A configurable user list to cope with any kind of user listing
>> (search-list, buddy-list, group-members-list, ...)
>>
>> The next step will be to put up groups. We decided to extend
>> fe_user_groups for that purpose and will put up some functionality that
>> enables users to join groups or to invite other users into groups etc.
>>
>> After that, we will put up a messaging system, that enables users to
>> send messages on public boards as well as on private messaging.
>>
>> That will be the core of the extension. We are thinking about a kind of
>> a plugin concept to make the extension work with community-extensions to
>> get a modular concept, but that will be one of the later points.
>>
>> We also decided to put up the basic functionality with new extensions
>> based on lib/div as most of the old extensions are based on pibase. As
>> soon as there is a example-installation of it, we will send a link to
>> the list.
>>
>> So far - regards
>>
>> Mimi

_______________________________________________
TYPO3-project-community mailing list
TYPO3-project-community@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-project-community

[Alexander Heim]

Hi Mimi,

:-) hope you both are still working on your plugin. Anything new? How is the state?

Damn that currently I'm so full packed with other projects, that after 60 hours
a week i have no space in my brain anymore :-(.

Greetz from Berlin and a lot of energy and nice ideas :-)
Alex



Michael Knoll schrieb:

> Hi Alexander,
>
> let me give you some answers to the questions and "buts" in your mail. A
> friend and me wanted or want to build a community (as many people want
> to do these days I suppose) and as I did some pages with typo3 and
> started to write my own extensions recently, we had the plan to do this
> with Typo3.
>
> After evaluating the extension currently available, we missed a lot of
> features and after taking a closer look on the code we came to the
> conclusion that they are not really useful for our purposes. After
> deciding to build our own extension, I found this mail-listing and
> posted some of our ideas and wanted to collect some more ideas. We put
> up a wiki page on which we tried to collect wish-lists and set up a
> roadmap.
>
> One goal - which was not only our's but a common wish - was to use
> lib/div as a basis and no longer to use pi_base.
>
> After some weeks of planning and talking about the whole thing, I wanted
> to start, as we would like to start our website about February next
> year. So the "many people work together" approach was - let's say
> corrupted by me simply starting to put up some of the functionality that
> was on everybody's wishlist.
>
> The biggest problem at the moment seems to be the quick changes in
> lib/div, as it is still alpha and you can't be sure that the
> functionality you use at the moment is still available with the same
> interfaces some weeks later.
>
> As soon as a little core of what we want to create is running, I will
> publicate it on TER or t3xdev so that everybody can help making a good
> piece of code out of it. At the moment I see no chance to coordinate
> more than the two of us (Lars and me) to do the programming stuff. If
> you have a better idea or can tell me how to coordinate a team managing
> the task, I'd be very thankful if you let me know how to do that.
>
> The plugins we write at the moment are very small and quite
> community-low-level, so that I think we can reuse them, no matter how
> the whole-big-thing will look like one day.
>
> Hope this explains a little of my problems and my thoughts.
>
> Regards
>
> Mimi
>
>
>
> Alexander Heim wrote:
>> Hi,
>>
>> great to see, that there is a development in this process. Sadly i have
>> had to muich work the last weeks to do something more and to think about
>> it.
>>
>> Now i have a big "but"! The idea of this Community-Community ;-) was or
>> is in my eyes, to work togehter with a lot of people to get the best out
>> of typo3 for developing community-websites. So I'm wondering, if i miss
>> some discussions about the plan, how the stuff will be developed. Is
>> there already a roadmap? Who is doing what? How is the guideline for
>> developing? I understand, that just starting and writing code is more
>> fun in the beginning, but without a clear concept, which is published,
>> the complete idea of an open set of many small community extensions, who
>> work easily and perfect together will die.
>>
>> Maybe i missed some discussions somewhere. I thought, that we wanted to
>> meet. But strange, this thread died. So whats up? Where? When?
>>
>> I do not want to be negative, but i leaded and developed some big
>> software projects and i just know all the problems which will come, if
>> there is no clear concept before.
>>
>>
>> But maybe someone can send me a document with the concept and i read it
>> and say: perfect! everything is thoughtful and i'm happy :-)
>>
>>
>>
>> Greetz
>> Alex
>>
>>
>> Michael Knoll schrieb:
>>> Hi folks,
>>>
>>> after I wrote my last test for this holidays last friday, Lars and I
>>> started to write the first lines of code for the community extension. We
>>> decided to use lib/div although it's really a hard piece of work to get
>>> through the code and to find out how everything works. As Elmar
>>> explained to me, it's still alpha.
>>>
>>> We try to set up a basic extension with most of the wishes you posted on
>>>  the wiki.
>>>
>>> At the moment we are concentrating on the following functionality:
>>>
>>> - User registration (first step is done via fe_user_registration)
>>> - User settings and privacy settings (extending fe_users and creating a
>>> own table for complex privacy settings)
>>> - User search
>>> - Add/Remove Buddies
>>> - Show relations between buddies
>>> - A configurable user list to cope with any kind of user listing
>>> (search-list, buddy-list, group-members-list, ...)
>>>
>>> The next step will be to put up groups. We decided to extend
>>> fe_user_groups for that purpose and will put up some functionality that
>>> enables users to join groups or to invite other users into groups etc.
>>>
>>> After that, we will put up a messaging system, that enables users to
>>> send messages on public boards as well as on private messaging.
>>>
>>> That will be the core of the extension. We are thinking about a kind of
>>> a plugin concept to make the extension work with community-extensions to
>>> get a modular concept, but that will be one of the later points.
>>>
>>> We also decided to put up the basic functionality with new extensions
>>> based on lib/div as most of the old extensions are based on pibase. As
>>> soon as there is a example-installation of it, we will send a link to
>>> the list.
>>>
>>> So far - regards
>>>
>>> Mimi

_______________________________________________
TYPO3-project-community mailing list
TYPO3-project-community@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-project-community