Is this still being maintained from the upstream head?
ethank opened this issue · comments
It seems to have stalled out a month ago?
Discourse is proving to be a very hard project to track, even with the simple Heroku-compatibility additions made here. Git conflicts are a-plenty.
Given their (the Discourse maintainer's) preference to not have forks, I'm considering shutting this one down.
Happy to hear other thoughts.
I'm working on a rebase with upstream and yes. It's really hard.
Could we consider dropping the fork and having an up to date guide instead?
The upstream actually offer docs for heroku.
Regards.
El feb 19, 2014 5:25 PM, "Ryan Daigle" notifications@github.com escribió:
Discourse is proving to be a very hard project to track, even with the
simple Heroku-compatibility additions made here. Git conflicts are a-plenty.Given their (the Discourse maintainer's) preference to not have forks, I'm
considering shutting this one down.Happy to hear other thoughts.
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/11#issuecomment-35554064
.
I just saw that Heroku is maintaining a fork: https://github.com/heroku/discussion
@ethank I wouldn't consider that a fork. It's much more like a heavily modified version of Discourse specifically for https://discussion.heroku.com/