Fluo website does not have obvious link to issue tracker

[sebbASF]

As the subject says: it's not at all obvious how to report bugs and raise enhancement requests.

[ctubbsii]

On the front page (and every page), there is a link in the menu to "How To Contribute". A few sentences down is the statement: "Create an issue that describes the work. Each Fluo repository has its own issue tracker: Fluo, Fluo Recipes, Fluo Website" with links to each issue tracker.

Is this insufficient? Do you have any suggestions to make it more obvious?

[mikewalch]

There are also links to the issue trackers under "User Feedback" at https://fluo.apache.org/getinvolved/

[sebbASF]

It's not at all obvious.

Although technically I suppose reporting a bug or requesting an enhancement is contributing, that's not how I think of it. I suspect others will agree.

The first section implies that the page is all about contributing code.
If I just want to report a bug, obviously the page is not relevant to me. Why should I read further?

And the page buries the links in the Contribution workflow. Do I really have to check out a fork of the repo in order to report a bug? That's what the page implies.

Most other ASF sites have a top-level link to the issue tracker.

[ctubbsii]

@sebbASF I'm concerned about adding a top-level link to the issue tracker, because menus that are too full of options can be bad for usability. It'd be nice to keep things organized. I accept that there's room for improvement. But, do you have a specific change to suggest, which balances the desire to keep things organized without too many top-level menu items, but which doesn't bury the information in a non-obvious way?

[cjmctague]

We could do something like this

Releases	Tour	Community	Contribute	Issue Tracking
Download		Get Involved	How to Contribute	Fluo Issues
API		News Archive	Release Project	Recipe Issues
Docs		People		Website Issues
		Related Projects
		Powered By

[ctubbsii]

Not a big fan of a top level menu item just for issue tracking. That's just one facet of the whole project. If every facet got a top-level menu, that would be quite bloated of a menu. Maybe a "Contact" menu which includes links to mailing lists, IRC, and "Report issues" to the various repos instead?

I've also been thinking that the "Contribute" menu could be consolidated with the "Community" menu, and the "Get Involved" page merged with the "How to Contribute".

[ctubbsii]

Or, maybe we just need one big "How To..." menu? It could have items such as "... get involved", "... contact us", "... view the source code", etc.

[mikewalch]

I've also been thinking that the "Contribute" menu could be consolidated with the "Community" menu, and the "Get Involved" page merged with the "How to Contribute".

+1. I like this idea.

Or, maybe we just need one big "How To..." menu? It could have items such as "... get involved", "... contact us", "... view the source code", etc.

Instead of a new menu, I think we should have a FAQ page under the consolidated "Community" menu with some answers to some of these questions.

[ctubbsii]

FAQ works for me.

[keith-turner]

I opened PR apache/fluo-website#71 to more directly communicate how to open issues. The current documentation is not straightforward.

I agree w/ @sebbASF that a more direct link to issue tracking on the website would be nice for users. You do have to dig a bit to find them. However, I agree with @ctubbsii in that I can not think of a good way to implement it. The main problem seems to be that we have three issue trackers and its hard to concisely link to them w/o adding confusing clutter. That's why I decided to take a crack at cleaning up the get involved page for the short term.