Consider moving development of message* modules back to drupal.org

[jhedstrom]

Now that drupal.org has really good testing infra targeted at Drupal modules, it would be nice to move the message stack back there for development. An added bonus would be author/contributor attribution credit with commits.

We'd also benefit from the nightly builds there which would let us know sooner rather than later when a breaking change is introduced in core.

[amitaibu]

I'm fine with that in general, but maybe we should wait for the PR to land there? The move to GitHub wasn't ideology, it was just the lack of convenient tools.

We'd also benefit from the nightly builds there which would let us know sooner rather than later when a breaking change is introduced in core.

Travis has a "cron" feature for that as-well.

Anyway, @jhedstrom since you are doing all the hard work - it's your call :)

[jhedstrom]

My main thinking for moving back were these two issues:

• We spend a ton of effort mimicking Drupal CI via Travis.
• The attribution credits actually encourages contributions since they play into this listing.

I do like PRs, but one benefit of the patch system is that anybody can pick up and work on an abandoned patch, while re-working a PR in such a way that both authors get commit credit requires the new participant to know how to merge their branch, etc.

[amitaibu]

👍 I'm ok with that.