Hi,

would anybody like to speak out about the current affairs with OG to give us an orientation?

How is the Organic Groups modul evolving?
What is the state of development?

Besides that from what I can see in the code and changelog - what are the current problems, what is the roadmap, what do you wish to do, what would you like to have done ...

How deep is the implementaion of "groups"? What can a group have / do and what not?

I read in http://drupal.org/node/183245 that there are some issues with privat groups... is there are solution for this on the horizon?

regarding docs i would like to ask: is there a clear definition of what groups should do and what not?

Also I would like to read something about the design related to drupal core, to get an understanding for what will and what will never be possible.

How about experiences with other modules, what are the biggest problems there?

Some more questions:

- can groups have their own (private) taxonomy?
- can groups have private nodes?
- can groups have public nodes?
- how well is this integrated with forums?
- is there anything that enables groups to VOTE for a node to change from private to public?
(is this even possibole with current drupal core implementation?)
- can groups have group calendars with privat and public events?

Also it would be interesting to know, if it is possible to organize groups hierarchically, to be able to generate groups of groups - after a first glance at the code it seems to me that this was not a goal at the design process of OG - anyway will this be possible or is it not possible with the current codebase because xyz...?

Inheritance of group permissions would also be something I would like to ask for... well, it is not really important right now but of course it would be wise to implement that from the beginning to support interesting new applications...

A short overview about OG development and your current headaches would be really very helpful to give us some understanding of OG and help us decide if we can avoid using Plone ;)

THANKS and have a nice day!

Comments

vm’s picture

Let me preface this with , I am not a developer for the OG.module or any of its addons. I've done some limited testing with the module and can answer a few of your questions.

can groups have their own (private) taxonomy?

not that I am aware of. Although I suppose with some inventive testing you could assign a content type that allows freetagging to be assocaited with OG.

- can groups have private nodes?
- can groups have public nodes?

yes and yes

- how well is this integrated with forums?

Not sure what you mean here by integration with forums but, if you employ the og_forums.module groups can have their own forum.

- is there anything that enables groups to VOTE for a node to change from private to public?

not that i can see, though someone may want to test the theory using the actions.module

Inheritance of group permissions would also be something I would like to ask for... well, it is not really important right now but of course it would be wise to implement that from the beginning to support interesting new applications...

drupal uses role based permissions, that being said: you can employ the og_promote.module and when a user joins a group he/she is automagically pushed/pulled to a specific role where permissions are obtained.
_____________________________________________________________________
Confucius says:
"Those who seek drupal answers should use drupal search!" : )

ajayg’s picture

Groups can have their own taxanomy with another contributed module. I have not used,so can't comment further. Most of what you are asking seems to be possible with combination of modules listed here

http://drupal.org/project/Modules/category/90

If you look at the commits you will see OG is one of the most actively developed modules. Having too many issues is not necessarily bad if they are getting resolved. Having too many issues but none submitting patches would be bad but doesn't seem to be case with OG.