agree on pico peering agreement while configuring router

[bobster-galore]

During recent beginners workshop on wcw18 it became obvious that there is no easy way to get aware of the pico peering agreement and to accept it.
On our latest Spandau meeting we were discussing it and propose to integrate it into the firmware and ask for acceptance while running a wizard. It should be in english and german.

links to ppa:
https://wiki.freifunk.net/Pico_Peering_Agreement
http://picopeer.net/

[pmelange]

+1

And we could also link to it on the index page of the routers.

[sarumpaet]

The PPA is rather a kind of template than something you just copy and paste as "Terms of Use". Also, it's a bit outdated (do we really want to force node owners to publish their e-mail address?) and uses legalese language for no good reason, and on top of that the German translation isn't very good (English: "service can be scaled back", German: "Der Dienst [...] kann jeder Zeit ohne weitere Erklärung beschränkt [...] werden" - English hints at throttling at best, German sounds like filtering, which the PPA explicitly isn't about).

BUT! It's a good idea. IMO we should take the main points and write those in human-understandable language, in just two or three sentences. Note that the "Notice" in pmelange's screenshot is basically PPA point 3, but in human-understandable words.

We should NOT just link to the PPA text. Everybody hates those "Terms of use" links - why should we impose those on others?

[pmelange]

Actually, I just quickly made a link that goes to"/" just for the screenshot.

What I was thinking is that it would be a link to the internally saved version of the PPA which would also be (hopefully) integrated into the wizard.

[SvenRoederer]

@sarumpaet if you feel bad on the german wording, the official license text should be changed. I think we have to take the text as it is, everything else might cause legal issues.

As of the mentioned possible legal issues and as the license text in only some paragraphs, everyone can read trough, we should include the text is it's complete length.

[bobster-galore]

I am with @SvenRoederer if we want to change the wording, we should do that upstream (http://picopeer.net/) otherwise we should keep the text.

[bobster-galore]

Postpone it or are there good ideas around?

[SvenRoederer]

Some sketch how the page should look like and where we wat to present the text would be a 1st good step

[SvenRoederer]

But as it has no "blocker"-flag I will not call this issue release-critical ...

[bobster-galore]

Probably we make a copy of http://www.picopeer.net/PPA-de.shtml when building the image and include it. For internationalization we put also links to the other languages.

The wizard starts with displaying the picopa and continues with "agree" and stops with "not agree".
"agree" sets ffwizard.settings.picopa="1", so it won't be asked again.

May be we can have that on console als well but no idea how this could work.

not release-critical

[sarumpaet]

See comment number 3. The PPA is outdated and broken and we/the firmware doesn't even comply fully.

I'd rather prefer something based on https://github.com/freifunk/MoU/blob/master/FreifunkMemorandumofUnderstanding_en.md . And, please, no "Agree" or "Disagree" buttons.

not release critical indeed

[bobster-galore]

I do not have any fantasy that someone would do a shorter version of that.
May we use the entire page? ... and a forward button (same as s.o.)
Or just a link to that as proposed by @pmelange ?
In general I think that link should be always on the welcome page.

[akira25]

I think in the wizard should be a page mentioning the idea of Freifunk. BUT, it should be short and easy understandable. Maybe just a few sentences.
Under that there should be links to the PPA and the Freie-Netzwerke e.V. texts. Each with a short explanation about its content.

In my opinion that would be the less "annoying" solution. Seeing a long legal text, most people probably do not get in the mood for reading it.

I agree that those links should always be on the welcome page.