OpenAtrium profile page reports a link to download it from an external site

@kiamlaluno I'm obviously biased but please try to understand that providing a link to the full drupal distro code only helps makes those distribution more popular
and widely used not only in drupal community but worldwide, especially to less technical folks.

I understand that there should be a suggestion somewhere for not allowing link to code outside drupal.org. Can we change that ? What are pros / cons ?

Drupal install profiles are currently not mature enough to support complex distributions such as openatrium / openscholar. Drush make is a huge improvement but it's currently
a developer tool (what about those Windows users ? ).

Thanks !

It is only a recommendation, not a requirement:

See http://drupal.org/node/7765

Contributors are strongly encouraged to host at drupal.org rather than elsewhere

The advantages are described at http://drupal.org/node/648898

However, these are recommendations, not requirements.

In short, there's nothing to see here.

This issue, and the accompanying issue re OpenScholar, should be closed.

There are well documented reasons why profiles like Open Atrium do not have fully packaged downloads currently hosted on Drupal.org. For Open Atrium this is purely a pragmatic decision based on the current state of our installation profile packaging infrastructure. As the maintainer of the project I view this as a temporary decision while the larger Drupal community irons out the details of how the sticker point of automated packages will work.

This issues is not, of itself, actionable. I think it should be closed.

See here.

Agreed with @jmiccolis, Open Atrium uses the drupal.org infrastructure, see http://drupalcode.org/viewvc/drupal/contributions/profiles/openatrium/ so the quote from @kiamlaluno does not apply. Unfortunately the d.o infrastructure does not yet allow the building of packages as required by some complex install profiles like Open Atrium. I think we should celebrate that its being hosted here in terms of CVS commits, issues, etc. since it allows us to use many of the advantages of d.o projects (eg. delegation of issues). That drupal.org is not yet ready to package complex distributions yet is a weakness of drupal.org and projects should not be denied access to otherwise integrate themselves with the community just for our weakness.

This is currently by design, the underlying infrastructure is in the process of being solved elsewhere.