Documentations update

[ArchangeGabriel]

With 4.0 on track, they are several documentation updates needed around there.

I’ll try to list them here, feel free to add other items. For now I see:

• Update wikis about false/noise errors:
  • Github.com
  • ArchLinux
  • Ubuntu
  • Fedora?
• Update wikis about multi-monitor (especially in link with conf: Change the way we ignore input devices #720):
  • Github.com
  • ArchLinux
  • Ubuntu
  • Fedora?
• Add FAQ entries about Vulkan pointing to [Feature Request] Vulkan support in Bumblebee/Primus #769
• Add FAQ entries about PRIME to explain the differences
• Add FAQ entries about PCIe bottlenecking/rewrite entries about performances
• Update instructions for packagers

Also, we could make use of newer GitHub functions:

• https://github.com/Bumblebee-Project/Bumblebee/wiki/Reporting-Issues could be (partially?) replaced by https://help.github.com/articles/creating-an-issue-template-for-your-repository/.
• https://github.com/Bumblebee-Project/Bumblebee/wiki/Contributing-and-joining-the-team could be similarly replaced by https://help.github.com/articles/setting-guidelines-for-repository-contributors/.

We may change http://bumblebee-project.org/ for bumblebee-project.github.io using https://help.github.com/categories/github-pages-basics/, so that @Thulinma could stop paying for the domain and having to host us.

[gsgatlin]

Here is the section I made about multi monitor on fedora:

https://fedoraproject.org/wiki/Bumblebee#Multi_monitor_setup_with_closed_driver.2C_fedora_22_or_later

I can change whatever in those docs. Just let me know what should be changed.

[Thulinma]

FYI: I'm not actually paying for the domain. I believe that's @Lekensteyn ?
The host is not an issue and can stay up for many more years without problem, but if you want to move it that's fine too of course.

[ArchangeGabriel]

Oh, OK. Yeah, I could host it too without problem, but it was more about the need to pay a domain name for nothing and also have a far easier way to handle site management. ;)

[Lekensteyn]

Yes, I am paying for the .org domain, it is no problem. There was a git repo on the server for the web content, maybe we should put it on Bumblebee-Project/bumblebee-web? A post-commit hook could then somehow ping the server and trigger a pull.

What about the tarballs? I did not check them in when creating the git repo, they are untracked by git, but must still be uploaded for releases.

@Thulinma What is the SSH username? I tried peter, lekensteyn and bumblebee, but the key was rejected.

[bluca]

What about using Github + Travis for the release tarballs? Free hosting and bandwidth, and doing a release is just the matter of pushing a git tag. If you guys want, I can look into it next week.

[Thulinma]

@Lekensteyn I actually think that server doesn't allow logins for the bumblebee data at all right now. I probably forgot to add the user when moving hosts last year. I'll take a look tonight and will check.

[ArchangeGabriel]

@bluca That’s a good idea.

@Lekensteyn We could just use Bumblebee-Project/Bumblebee-Project to get the automated bumblebee-project.github.io website feature like proposed above. Likewise, the hook is really trivial, and with bluca proposal the release tarballs should be an easy thing.

[ArchangeGabriel]

@gsgatlin I’m not sure what is the current status of multi-monitor in fact. The change I was referring to is the changes needed in xorg.conf.nvidia and 10-input-drivers.conf.

[melroy89]

Can somebody upload the website on github of http://bumblebee-project.org/ maybe adding a FAQ?

[Thulinma]

@Danger89 I would upload it all to a organization page, but it appears I don't have the permissions required to create the repo for this.
@ArchangeGabriel Could you either create a bumblebee-project.github.io repo or give me the access needed to do it myself? I'll then upload the webroot to it, so it becomes available at http://bumblebee-project.github.io which the domain can then be redirected to.