talk.manageiq.org integration

[garrett]

Quoting @dneary, from gitlab:

Developer and user forums will go through Discourse, on the subsite talk.manageiq.org

We need to:

• Add a "Forums" block to the front page, community page, and page footer to ensure people can find them
• Expose the website to Jeff Atwood at a point where it's sufficiently advanced that he can theme the Discourse site to fit in
• Ensure that developer discussion happens on the forum ASAP (so that at launch it's not empty)

[garrett]

Forum is located @ http://talk.manageiq.org/

[garrett]

Front page inclusion

• What should the "forums" block be like?
• What should it contain?
• Is it possible to embed the forum?
• Does it even make sense to embed the forum?
• What should be shown if embedded?

Atwood et al

Have we shown the site recently to Jeff Atwood and his crew?

Developer discussion

What sort of developer discussion should happen there? Forums should be set up and topics should be suggested. While this is important, it is actually outside the scope of this issue (integration). But it would be nice to have some live data on the site to see how things work.

[dneary]

Hi,

On 05/22/2014 04:48 AM, Garrett LeSage wrote:

Front page inclusion

• What should the "forums" block be like?
• What should it contain?
• Is it possible to embed the forum?
• Does it even make sense to embed the forum?
• What should be shown if embedded?

I think it looks reasonable now - talk is "talk to the developers", ask
is "get help with your problems". Do you feel we need to differentiate more?

Atwood et al

Have we shown the site recently to Jeff Atwood and his crew?

No, not recently.

Developer discussion

What sort of developer discussion should happen there? Forums should be
set up and topics should be suggested. While this is important, it is
actually outside the scope of this issue (integration). But it would be
nice to have some live data on the site to see how things work.

The developers working on ManageIQ hate mailing lists, and did not want
them. My suggestion is to use Discourse for technical discussion,
announcements, conversations related to blog entries (comments etc) and
general "getting stuff done" which requires interaction. It's where our
users get to know the team behind the project.

Dave.

Dave Neary - Community Action and Impact
Open Source and Standards, Red Hat - http://community.redhat.com
Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13

[garrett]

The developers working on ManageIQ hate mailing lists, and did not want them.

I strongly agree with the developers of ManageIQ on this subject. (I also like their decision to use github issues over bugzilla too.) 😄

@dneary, you and I may understand the difference, but we (you, me, @johnmark, and others) need to make sure to effectively communicate these differences via the website. This is why I opened up a separate issue (#31) on exactly this topic.

If the website is murky in meaning, then it would drive the wrong type of content to the wrong place. This is what I'd like for the website to avoid.

[garrett]

In issue #32 and pull request #40 (merged in commit eec93ef), there's an integration point with talk.manageiq.org to use it to power the comments on blog posts. It has been added.

Also, it is linked from the social link area of the footer (in git commit 171a748 & pull request #39).

[garrett]

I still do not like the inclusion of the forum and Q&A site on the front page. But that isn't "integration" though.

I've integrated it in the comments on blog posts and also in the footer, so I consider "integration" to be solved. Closing this bug.

[garrett]

(Also, the talk website resembles ManageIQ enough for now.)