http://www.assembla.com/flows/flow/drupalcpp Gnomepal (from Assembla Breakout) en-us 60 http://www.ubercart.org should really be looked at as another excellent example. Drigg is a smaller number of people. CiviCRM is.....a bolt on bit of code that has full time people working on it, so not as good of an example, I don't think. 2008-04-02 c3rixaamar3zuHabIlDkbG http://www.assembla.com/flows/show/c3rixaamar3zuHabIlDkbG Why not just add this info to the profile information requested at the gnomepal.org site? People can fill out their profile and even tag themselves with skills, etc. 2008-04-02 antvugamar3z3DabIlDkbG http://www.assembla.com/flows/show/antvugamar3z3DabIlDkbG Great job! Some questions/comments: #1 Basic Member - A site visitor who has completed the administration and profile process and been granted access by the site's adminstrators. ## 1 Notes Does this statement infer that the site administrator has to approve/authorize all new members? Or does this mean that the site administrator will have the capability to define what the requirements are for people becoming members of the community? From an IA pov, I assume the latter, but I thought I'd ask. #2 Scenarios - this concept is not really a scenario, however it is something we discussed and should likely be captured somewhere as it likely requires some backend plumbing to make it work. The concept revolves around keeping track of what the member views (aka, activity stream), make an attempt to figure out what they like, and then show them relevant content based on what the community determines they may like. Another component to this could be to allow the member to see this as recommended content, but add in a capability similar to what Pandora offers for music where you let them know that you like what they recommend or that you do not. Then the system continually "learns" by your input and the recommended content gets more precise. If the same member is a participant in multiple communities, see if there are opportunities to leverage their view habits across communities to make their experience within each community richer. #3 Setup Wizard - Offer a "skip this step" as well as "skip wizard". Ensure the Wizard offers context aware help throughout the process, so the person setting up the community can try to better understand what the step is for (or provide examples). 2008-04-01 b5TCNcaaer3A2fabIlDkbG http://www.assembla.com/flows/show/b5TCNcaaer3A2fabIlDkbG - Groups of users. Plenty of uses, but one example is a user could be part of certain groups, or, for example, on a Tech Support community, "areas of expertise." Users would be appropriately ranked on their content or comments "answering" questions based on their groups. - Desktop integration. While what "Gnomepal" strives to be is a form of a web application, bringing desktop integration in the future is definitely something to think about. For a lot of things on the web, I don't even launch a browser. To twitter I use a Vista sidebar gadget. To upload photos to Flickr, I use Live Photo Gallery (kudos to Microsoft for adding out-of-the-box support). Or to write a new blog post, Live Writer. While desktop apps could be developed by third-parties, adding the APIs necessary in the web-application at this point in time is something to think about. - When I insert a photo or video into new content, automatically upload it to my Flickr or Youtube account. I don't want that photo/video to have already pre-existed on my account. - A standard login system for all installations and possibly a central relational database. What I mean is that not only would you be able to see the activity of one person's profile in a single community, but see whatactivity they have on other communities as well. Have they created content with the same tags in another community? Have they commented on similar content? etc The issue with this is technical limitations. - API for web-based mobile support. When I take a photo with my Treo or iPhone, I want to be able to upload it to Flickr, create a new blog post about it, and Twitter it all in one go. - Sharing content between communities. Have APIs in place where I can easily click a button and share content on one community with another one that I'm a part of. Because of copyright or duplicating content with advertising income concerns, not only would it be an option to allow for easily copying certain amounts of content, but creating new content of your own which redirects the reader to another community. All appropriate tags, photos, or videos should be pulled as well. - Take this into the gaming community. What if I could add an Xbox Live Gamertag to my profile and automatically have any of my Xbox Live friends which happen to be a part of the community or even OTHER communities added? That would be absolutely great... - The same thing for social networks such as Myspace or Facebook friends. - Tools or services for "serious" media producers. Comparatively, YouTube has lower quality video than what video producers would want. Certainly, content should be put on YouTube for sheer distribution and to get the stuff out there, but also for other video services. The same thing for music artists, not only with Myspace Music or last.fm, but music-specific services for startup bands. Members of a community could then easily discovery other's members interests in music including these startups. - Possibly storefront integration for these artists? I know I saw a Drupal storefront module somewhere... - What about if I own/run multiple communities and want to push out content to all of them at the same time? - Integration between forums and the content. Have an option to not only push content to the main page, but also a specific forum. This would be great to work the other way around. I create a new forum post with an announcement, it gets pushed to the main page. I post a forum "sticky" topic about common questions which are asked, it gets sent to the appropriate page or a manually selected page within the community. I look forward to the other systems being put in place to facilitate suggestions and discussion. - Adam http://www.adamreyher.com 2008-03-30 aQRac4_Qir3itWabIlDkbG http://www.assembla.com/flows/show/aQRac4_Qir3itWabIlDkbG I think the system should have the ability to differentiate between the possibility of editor-originated content and user-generated content, and have moderation/promotion rules for both. 2008-03-30 a-YmoK_ICr3lchabIlDkbG http://www.assembla.com/flows/show/a-YmoK_ICr3lchabIlDkbG There are a few key features that are important when setting up a community I thought I might add. My personal projects include a podcast network and an artist site that allows artists to share writing, images, audio, and video recordings. These two community sites are entirely different, and will have different needs. Of all the features I have jotted down these 5 seem to ring out as being baseline necessities. 1. Allow the admin the ability to select "featured" posts and content from within the community to share on the main page, while also providing an "autopilot" that would give the admin the option to have the top 5 or so most active threads, items, or posts from within the community automatically set on the front page as featured articles. If the admin so chooses, the system could provide them as "suggestions" for featured status bringing these hot topics to the admin's attention before feature status is granted. 2. Create or allow for the creation of separate RSS feeds for each category of content that a profile adds to the community. For example, if user A posts 50 of their photographs and 5 of their audio recordings, they should have a gallery separate from their music, podcasts, whatever. This would allow someone to direct their fans/followers to their art gallery without having their audio tracks jumbled in the mix. Having a different RSS feed would allow someone to subscribe to user's videos without getting every little twitter update summary, photo upload, etc. 3. It would be nice to have an interoperability built in with multiple forms of implementation. For example, if someone has an OpenID site running gnomepal, their users should be able to fairly easily shake hands with and import profiles from their other gnomepal accounts on other active sites. For admins that chose to opt out of OpenID, a primitive import/export could be made possible allowing users the ability to shake hands and set themselves up in the new community without having to re-enter all the information. Other possibilities using RSS, for example, could be possible pulling someone's profile from multiple sources into their Gnomepal community profile. 4. An admin should have a blanket ability to block certain strings in cases where a community is being barraged by outside interference. Let's say for example, that your site revolves around users sharing poetry. If you have the ability to block out phrases like "sucks" or "stupid" or other less polite nonsense, while allowing original posters the ability to keep those phrases in their posts, if for whatever reason their story has that term in it. One problem I'm seeing with community sites like Youtube for example, is that the site can't become a place of honest critique and idea sharing beyond the initial contribution when half of the comments made are unreasonable and unnecessary trolling. This one was hard to put into words, so forgive me if it doesn't make sense. 5. Users should have the ability to make the rights they chose to have on their content visible and present. Flickr has a great rights management program, and when you view a post from a user you know what license that user has selected to give their peers. This is missing from so many community sites out there and deserves a place in Gnomepal. Thanks very much, MR 2008-03-29 a3aFPM_Eqr3kqmabIlDkbG http://www.assembla.com/flows/show/a3aFPM_Eqr3kqmabIlDkbG Posted today about the project (slow news day) http://hansacross.wordpress.com/2008/03/28/large-scale-community-cms-project-started-caveats-explored/ Main points: 1. Do not fork Drupal (agreed) 2. Forgo Glory. Instead make Drupal better. Where you can, involve and empower the existing Drupal Development Community. 3. Sure, creating an easier technical install (the ftp-way) is important, but also create a wordpress.org / .com ecology. The easiest install is a one click install. (I volunteer, just say the word). 4. One of the greatest barriers for a nice Drupal site is not the availability of modules or even installing them. It is the integration of different modules though css/dhtml/javascript/ajaxy wizardy (which completely eludes me too). We need to create great looking cool themes - NOT for a standard empty drupal install - but for completely configured and installed applied community concepts. A nice font, some colors and a sexy image header will NOT do. 5. Understand that any code you create needs to be maintained. New modules should be kept to a minimum, kept as granular as possible (to enable yet newer, as yet unenvisioned possibilities) and pushed into their own maintenance projects. 6. Google is also a big fan of Drupal. Can we do something with Google’s summer of code 7. Find other sponsors, big and small. 8. On the project site it is currently stated that ‘The hope is to integrate OpenSocial, OAuth, and OpenID.’ It is my opinion that these things are absolutely essential for a futureproof Community project. It could finally lead to being completely in charge of your own community profile through our project / Drupal. Let’s be ambitious here. 2008-03-28 aLsIqa_nir3lhbabIlDkbG http://www.assembla.com/flows/show/aLsIqa_nir3lhbabIlDkbG Choose the wysiwyg editor for us! There are like 10 contrib modules and counting. It's confusing. Starter content, kinda like Joomla! 1.5. Real content (not Lorem Ipsum), as in pages and stories that explains Drupal and help a new users get started. Perhaps some getting started videos on the "welcome to your new Drupal site" page. Kind of like Flight Simulator's Learning Center, if anyone's familiar with that. 2008-03-28 csTqCG_jWr3lhbabIlDkbG http://www.assembla.com/flows/show/csTqCG_jWr3lhbabIlDkbG