Home

Welcome to the developing wiki! These wiki pages are part of the main wiki documentation of retebuonvivere project.

---

Since building profiles has much to do with all the developing workflow (soft/hard configuration, makefile, distributions, ...), this wiki will be the main wiki for all developing stuff.

Documentation

Let's start with documentation on building profiles:

• We can start from this article: How to Write a Drupal 7 Installation Profile.
• Or from Developing installation profiles and distributions, the main drupal documentation on distributions.
  • A part of the main doc is Installation Profile Utilities page, with links - among others - to:
    • How to Create a Drupal Installation Profile with Profiler and Profiler Builder
    • Distribution profiles drupal discussion group.
• Installation Profiles as a development tool presentation by Florian Lorétan at Drupal Developer Days Brussels 2011 (slides and video).

Further doc on code drive development:

• Code driven development: using Features effectively in Drupal 6 and 7 slides by nuvole (from page 47).
• BUILDING AND MAINTAINING A DISTRIBUTION IN DRUPAL 7 WITH FEATURES (slides and vide) also explains very well the points.
• Coding For Config: Install Profile Development Using Features - this has a lot of example code.
• First Steps in Drupal Code Driven Development.

Distribution

Retebuonvivere.org could become a new drupal distribution (allowing other networks to use it besides Verona's).

If we go for this choice, above there are sone links to specific documentation for working with distros to start with.

Another choise is to work on top of one of the social distributions out there, e.g. Open Atrium 2 and Drupal Commons 3, or on top of a base distribution as Panopoly.

Both Open Atrium 2 and Drupal Commons 3 are great, rich, powerful barebone social networks. This implies that they highten system requirements (php memory limit, apache solr, ...). I(miro)'m not an expert but I think this can be a problem because we want to stay light, making it easy and cheaper to find a hosting solution). It could probably be possible to remove some funcionalities (but this implies a certain amount of re-configuration).

There is also another important point: both of them are aimed at levereging an online community. They are full of superb funcionalities for messaging other users, following contents, managing user dashboards, sharing content... Perfect for an intranet, for instance.

Retebuonvivere.org is slightly different:

• it aims at being a (self)representation and cooperation tool for a community which is fragmented and whose members already use a pletory of different tools:
  • web-based (emails, mailing-lists, online groups, instant messaging, social networks, ...);
  • non web-based tools (telephones, faxes, notice boards, notebooks,...);
  • in-presence modes (direct face-to-face talking, conferences, meetings, sociable events, ...);
• each member use a cobination of these tools and modes in a personal, unique ways.
• member's organizations (most of them) also have a propretary (main) website.
• They «don't need a "new social network"». For these reasons we:
• do not implement messaging funcionalities;
• focus on tools with a network scope (see feature documentation) such as:
  • the graph, which allows to see all the network of relations between organizations. This should produce fill the gap of consciousness of being part of a whole; should produce an understanding of the complexity at place.
  • shared calendar.
  • discussion forum and the wiki.
• and then working on connecting other websites, with functionalities like:
  • importing content (from RSS links, from social networks like facebook, wiser.org, zoes.it, from calendars,...);
  • feeding other websites with content created in retebuonvivere.org (connecting with facebook API...).