1. @open_atrium

2. Open Atrium
Building a product with Drupal and the Power of
Decentralized Features

3. This presentation
How Development Seed uses Atrium.
How Atrium can be extended.
How we can collaborate to improve Atrium.
How collaboration could get easier.

4. Ian Cairns
Dangerous with Aegir

18. casetracker.module
drupal.org/project/casetracker

19. Turn it on and it works
srsly.

20. How?
It depends on things, and has some defaults.

21. Hey, Atrium is like that!

22. Feature: collection of
Drupal parts that do
something specific.

27. How do I share a
feature?
(...this is where it gets tricky)

28. Drupal + Hot Sauce

29. Core + Contrib + Hot Sauce

30. Drupal core lives at
drupal.org

31. Drupal “contrib” lives at
drupal.org

32. Atrium’s “hot sauce”...
$hot_sauce = $install_profile + $custom_modules;

33. ; $Id: default.info,v 1.4 2009/08/30 06:02:08 dries Exp $
name = Drupal
description = Create a Drupal site with the most commonly used
features pre-installed.
version = VERSION
core = 7.x
dependencies[] = block
dependencies[] = color
dependencies[] = comment
dependencies[] = help
dependencies[] = image
dependencies[] = menu
dependencies[] = path
dependencies[] = taxonomy
dependencies[] = dblog
dependencies[] = search
dependencies[] = toolbar
dependencies[] = field_ui
dependencies[] = file
files[] = default.profile

35. Atrium lives on Github
Core + Contrib + Hot Sauce

36. Atrium’s rules

37. works out of the box.

38. works with Aegir.

39. doesn’t hack core,
or contrib*.
*except occasionally.

40. doesn’t do everything.

41. ...but can be extended.

42. Atrium collaboration
(present)

43. Report a bug.

44. Bug gets flagged:
‘upstream’

45. Quickly fixed on d.o

46. Packaged into a release
on d.o

47. ...d.o release is added to
Atrium

48. Atrium beta X is
released!

49. ...and downloaded

50. 7 Steps
1. Report a bug.
2. Bug gets flagged: ‘upstream’
3. Quickly fixed on d.o
4. Packaged into a release on d.o
5. ...d.o release is added to Atrium
6. Atrium beta X is released!
7. ...and downloaded

51. Atrium collaboration
(ideal)

52. report a bug.

53. fixed by maintainer.

54. released

55. ...and downloaded

56. 4 Steps
1. Report a bug.
2. Bug gets flagged: ‘upstream’
3. Quickly fixed on d.o
4. Packaged into a release on d.o
5. ...d.o release is added to Atrium
6. Atrium beta X is released!
7. ...and downloaded

60. Drush Make
http://drupal.org/project/drush_make

61. <?php
$projects = array(
'drupal' => array(
'version' => '6.13',
'directory_name' => 'featureserver',
),
// Drupal.org hosted projects
'admin',
'cck',
'context',
'features',
'filefield',
'views',
// Projects hosted elsewhere
'fserver' => array('location' => 'http://code.ds.org/fserver'),
'singular' => array('location' => 'http://code.ds.org/fserver'),
'tao' => array('location' => 'http://code.ds.org/fserver'),
);

62. Packaging improvements
on Drupal.org
(or so a little birdy told me)

63. How do I share a
feature?
(I told you it was tricky)

64. Multiple feature servers,

65. distributing ownership

66. ...some using something
that isn’t cvs,

67. ...publishing modules
details in XML
...like what the update module uses.

68. which is aggregated by a
central hub.
...like drupal.org

70. What will this mean for
Atrium?

71. What will this mean for
install profiles?

72. Pull from public and
private sources...

73. ...using standard tools.
(like drush & aegir)

74. This could change how
we all work.

75. Get Started
Play with Atrium
http://openatrium.com/
Play with the features module
http://drupal.org/project/features
Play with drush make
http://drupal.org/project/drush_make

76. Questions?
@open_atrium