[gen] Add community section

[ann0see]

We should discuss everything related to the new section here not in #56

[ann0see]

See comments

[ann0see]

Any updates or ideas on a better name for this?

[ignotus666]

What about just "Community"?

[ann0see]

I'm afraid this might be confused with the forums

[trebmuh]

Agreed, "Community" would be a page I'd go to find a list of communication channels

[ann0see]

Jamulus Guides could be something

[trebmuh]

"Community tips & tricks" or "Community knowledge base" are both fine for what I understand this page is intended for.

[gilgongo]

Maybe just "Knowledge base"? Since that might imply community, but not discussion, and is shorter for the English navigation links at least.

[ann0see]

Yes it would be an option (although it doesn't imply that it's community based in my opinion).

Nevertheless, shall we use that?

[gilgongo]

Looks good to me. I'd prefer not to put too much energy into maintaining this stuff as that's part of the point of "community" really. We can't really expect to keep it all up to date and translated over time, so this is just "seed" content really that we hope people will link to.

[ann0see]

@gilgongo

Next steps on this:

1. Which files should we move here?
2. How do we handle the links in the wiki? Remove them?
3. How do we make contribution easier? As you mentioned in Is it me, or is editing the site content now too difficult? #139 it is a bit difficult to add a new file at the moment.

[gilgongo]

Which files should we move here?

The primary reason (in my mind at least) for the KB is to attract incoming links.

So - interesting, useful, exciting things that people would link to. The topic doesn't have to be related to Jamulus, but should ideally be related to the domain that Jamulus is in (online music jamming playing rehearsing singing, etc.).

In contrast, stuff that is directly related to being able to use Jamulus (like the Onboarding or Server Setup) should NOT be in the KB because we need to reserve our energies for that in keeping it up to date, well written, translated into as many languages as possible, and organised properly over time.

The KB, on the other can be none of those things :-) If somebody wants to write an article about playing Gamelan on the beach in Chinese, and none of us understand it, and it causes outrage in the Gamelan community for factual errors, then that's great because if a Chinese music site links to it - we get a bunch of Chinese people finding us on Google and using Jamulus.

So - of the files here, perhaps move these?

https://jamulus.io/wiki/Linux-Client-Install-Script

https://jamulus.io/wiki/Running-Jamulus-with-Multiple-Audio-Interfaces

https://jamulus.io/wiki/Server-Rpi

https://jamulus.io/wiki/Software-Synth

I'd also say https://jamulus.io/wiki/Sound-Devices if only because that might need to be a community effort anyway.

I can also look for stuff we can grab off the forums too as there are at least a few things there (will ask authors, obviously). We then need to encourage people to move or write content into the KB.

How do we handle the links in the wiki? Remove them?

The links to the pages above you mean? We can link to them if we want I suppose (like the hardware list) but in general wasn't expecting to.

How do we make contribution easier?

Ah - er, how does it work right now? Can people with GH accounts commit straight to it as hoped? We can deal with any spam/vandalism later.

BTW if it's easier, could we set up a new thing on our GH organisation and then have a separate repo for it on a subdomain (knowledgebase.jamulus.io)?

[ann0see]

So - of the files here, perhaps move these? [...]

Yes. I think so. They should already be in the _posts folder.

The only file I'm not sure is the hardware setup.
From your point of view, it will stay part of the wiki? If that's the case, we might need some pictures for this page.

About Sound devices, I think @gegeweb reworked it. I think we could add a big, community maintained list to the KB and put general advise in the wiki (like should have a native ASIO driver on Windows,...). There's already an issue/pr for this.

Can people with GH accounts commit straight to it as hoped? We can deal with any spam/vandalism later.

Unfortunately not. They need to open a PR to release. It's not very user friendly. Not sure if we can solve it with another subdomain + repo?

[gilgongo]

OK, well let's get it out there for now, and if necessary we can think again. As its on our domain we can move it to another setup later if needed without suffering any SEO issues.

[ann0see]

So should we merge it?

[gilgongo]

I think so. We have to start somewhere on this and encourage people to link to it. There's also quite a bit on the forums we can put in if we can get the authors to agree.

BTW I think our lack of visiblity in Google also leads to people "rolling their own" like this which was just posted today.

[ann0see]

I think so. We have to start somewhere on this and encourage people to link to it. There's also quite a bit on the forums we can put in if we can get the authors to agree.

So should we put it on release?

BTW I think our lack of visiblity in Google also leads to people "rolling their own" like this which was just posted today.

There might be problems with our documentation in some ways. I think some of the issues are missing pictures. I can maybe add some?

[gilgongo]

Maybe - maintaining screenshots is quite hard work though which is why I've used them sparingly.

[ann0see]

Let's open a new issue on that and merge this. release or changes?

[gilgongo]

Ok. Let's put it into release I think. It doesn't need to be part of the changes/translation workflow as far as I can see.

[ann0see]

That's quite difficult. If I want to merge it to release it adds some commits from changes, I think.

[gilgongo]

Oh OK. In which case just it on changes and we can add some more pages to it while it's waiting to go into translation (actually translating is optional though)?

[ann0see]

Yes.

[ann0see]

Merged. You can have a look at it locally

[ann0see]

@gilgongo I'm now working on removing the files you mentioned in your comment above in the wiki.

[ann0see]

OK. Didn't remove it but rather added a redirect layout