Signing the CoC is a pain

Bug #683465 reported by UndiFineD
38
This bug affects 7 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Opinion
Undecided
Unassigned
Ubuntu Code of Conduct
New
Undecided
Unassigned

Bug Description

We should make signing CoC accessible.
50% of the people have dyslexia.
Do we really expect them to read thousands of pages before they can actually sign ?
On the LP website it says you can generate one with the GUI tool,
this is not true as it fails horribly in generating one that is accepted by LP.

There is too much to read and do in this process to finish it.
and most of it is not very accessible.
I had to do this for my wife, as it was simply to much for her.
Only when I found: http://okiebuntu.homelinux.com/okwiki/lesson1overview
I was able to generate a proper key on the eeepc.
Since it has an Atom processor, generating one took more than 10 minutes.
And it requires CLI to do this, which is not suitable for everyone.

The CoC should be available for read
or perhaps have it spoken to you -- video or just audio.
Signing the CoC should be as easy as a check-marker.

Tags: lp-registry
Phill Whiteside (phillw)
Changed in launchpad:
status: New → Confirmed
Revision history for this message
Curtis Hovey (sinzui) wrote :

The CoC is not a trivial document. Launchpad hosts the document for the Ubuntu community and records the digital signatures. The Ubuntu community could provide alternate forms and they are welcome to integrate those into Launchpad.

I use espeak to read me long passages.

affects: launchpad → launchpad-registry
Changed in launchpad-registry:
status: Confirmed → Opinion
Revision history for this message
Phill Whiteside (phillw) wrote : Re: [Bug 683465] Re: Signing the CoC is a pain

Hiyas Curtis,

The reason the bug was filed was that someone with problems could just not
get it to work, it was only after the extra link was found that someone who
has helped out on one of the accessi personas, did it become apparent just
how hard it is https://wiki.ubuntu.com/hajour

Whilst signing the CoC is not something to be undertaken lightly, the fact
that hajour could not even get the existing pgp system to work for her is a
rather damning idictment to the current instructions. I've asked that UBT
include that link as a stop gap measure whilst everyone gets used to the
fact the accessibility is no longer an option, but a requirement.

Her spending 4 frustrating hours, is quite simply, not really acceptable in
the way that Mark Shuttleworth said at the UDS-N.

Please do not take this as a personal insult, but we NEED people like her to
point out accessibility issues that others have long over come, we only get
one pgp key and only sign the CoC once.

My kindest Regards,

Phill.
https://wiki.ubuntu.com/phillw

On 1 December 2010 04:34, Curtis Hovey <email address hidden> wrote:

> The CoC is not a trivial document. Launchpad hosts the document for the
> Ubuntu community and records the digital signatures. The Ubuntu
> community could provide alternate forms and they are welcome to
> integrate those into Launchpad.
>
> I use espeak to read me long passages.
>
> ** Project changed: launchpad => launchpad-registry
>
> ** Changed in: launchpad-registry
> Status: Confirmed => Opinion
>
> --
> Signing the CoC is a pain
> https://bugs.launchpad.net/bugs/683465
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in The Launchpad Registry: Opinion
>
> Bug description:
> We should make signing CoC accessible.
> 50% of the people have dyslexia.
> Do we really expect them to read thousands of pages before they can
> actually sign ?
> On the LP website it says you can generate one with the GUI tool,
> this is not true as it fails horribly in generating one that is accepted by
> LP.
>
> There is too much to read and do in this process to finish it.
> and most of it is not very accessible.
> I had to do this for my wife, as it was simply to much for her.
> Only when I found: http://okiebuntu.homelinux.com/okwiki/lesson1overview
> I was able to generate a proper key on the eeepc.
> Since it has an Atom processor, generating one took more than 10 minutes.
> And it requires CLI to do this, which is not suitable for everyone.
>
> The CoC should be available for read
> or perhaps have it spoken to you -- video or just audio.
> Signing the CoC should be as easy as a check-marker.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/launchpad-registry/+bug/683465/+subscribe
>

Revision history for this message
Duane Hinnen (duanedesign) wrote :

I would love to work on a screencast that shows how to make a key and sign the CoC. The Screencast Team could put it up on screencasts.ubuntu.com and its blip.tv and youtube site. Would this help address some of the accessebility issues?

thank you,
duanedesign

Revision history for this message
Jared Norris (jarednorris) wrote :

I have added that it also affects the project "Ubuntu Code of Conduct" as I believe this is probably a more appropriate project to file the bug against as per Curtis' comments above.

Revision history for this message
Daniel Holbach (dholbach) wrote :

Duane: that'd be awesome.

Are there any other suggestions and ideas?

I'm not sure the ubuntu-codeofconduct project is the right place for this bug, as it just contains the document itself.

Revision history for this message
Paul Tagliamonte (paultag) wrote :

Speaking as someone with dyslexia, as well as someone who volunteers at a center for dyslexia, I don't think that reading two pages of text is a deal-breaker.

The CoC ( run through fmt, to wrap lines sanely ) is 266 lines long.

A level 3 - 4 easy reader children's book is 800 to 1200 words.

While I think making this process easier is a good thing, we still need people to understand what they're doing is as weighty as signing a contract. It's not some useless hoop you have to jump through. The CoC is what really makes this community great.

Revision history for this message
Daniel Holbach (dholbach) wrote :

Paul: I think the problem we're talking about is reading all the pages that explain how GPG works, etc.

Revision history for this message
Paul Tagliamonte (paultag) wrote :

Ahha. I take it back. Thanks, Daniel.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.