[drupal-devel] CivicSpace development moving to Drupal

[Moshe Weitzman]

Sounds great Chris. Your engineers might want to architect this using 
og.module (organic groups) as their basis for projects and workspaces. 
It supports al lot of what you are going to need 
public/private/moderated groups, group admins, access control, photo 
albums, group blogs, etc. It does not have strict project/ticketing yet. 
I'd be happy to help the SFX team if desired.

-moshe

Chris Messina wrote:
> Dries,
> 
> I'm really excited by this whole list! (I would add forum improvements
> as well, but other than that, it looks good).
> 
> You should know that I'm endeavoring to make a really cool project
> module for Spread Firefox v2 which basically aims to combine
> 43things.com with Basecamp-like workspaces. I think this would be
> extremely useful for Drupal & CivicSpace since it would allow people
> to:
> 
> 1. find new projects
> 2. suggest new projects
> 3. create new projects and get volunteers
> 4. have instant workspaces (blog, forums, issue tracking, member tracking, etc)
> 
> The goal is to imitate SourceForge but do it right and make it very
> simply to get involved or simply track a project. I'll be mockup up
> workflows and UI stuff in the coming week(s). I have 20 or so people
> ready on the SFX side to work on this and are already developing their
> own requirements and ideas. Ideally this could be a really excellent
> project for us to collaborate on.
> 
> If you're interested, you can see some of the very early initial ideas
> for the SFX redesign here:
> 
> http://www.flickr.com/photos/factoryjoe/sets/135075/
> 
> Thoughts & ideas welcome!
> 
> Chris
> 
> 
> On Thu, 24 Mar 2005 13:18:34 +0100, Dries Buytaert <dries at buytaert.net> wrote:
> 
>>On 24 Mar 2005, at 11:40, Gerhard Killesreiter wrote:
>>
>>>Thanks. I'd really like to see the Drupal project advance a bit faster
>>>than it does now.
>>>
>>>Currently, I am often not sure if it is worth my time to work on a
>>>specific bug/feature as I have not much of an idea if (and when!) it
>>>will make it to core. I guess there are more people like me.
>>
>>I'm compiling a detailed list of things I believe are core-worthy and
>>which I'd like to see included or worked on.  I'll share this list as
>>soon as it's ready.  At the top of my head, in no particular order and
>>lacking details:
>>
>>1. Workflow actions (and e-mail subscriptions/notifications in
>>particular)
>>2. Improved node submission form
>>3. Profile fields per role
>>4. Blocks visibility per role
>>5. phpTemplate
>>6. Better link management (node links + menu links)
>>7. Folksonomies and taxonomy improvements
>>8. CCK
>>9. Improved administration structure, visual distinction, intuitive
>>placement of settings
>>10. Improved versioning
>>11. Loose caching
>>12. Better blog.module
>>13. Better archive.module
>>14. Contact module extension to let you contact groups of people.
>>15. USABILITY IMPROVEMENTS
>>16. Improved 'my account' page.
>>17. One node-level permissions scheme (taxonomy-role?)
>>18. Better file handling/serving (permissions)
>>19. Misc. aggregator improvements
>>
>>--
>>Dries Buytaert  ::  http://www.buytaert.net/
>>
>>