Davidson Rodrigues Paulo <davidsonpaulo(a)gmail.com> wrote:
Education is a task for documentation, not software.
I disagree. But, ironically, the CLI addresses that today. ;)
When people follow CLA instructions they need to be educated
in PGP keys, not when they are creating the keys.
Now I'm confused. How does this make everything "easier"?
And are you advocating them creating the keys _then_ understanding?
I'm not talking about GUI building, wizards or user education.
From the start:
* There is a GUI that works in a way it need to work, and it's so
"educational" than the CLI;
I didn't understand that statement, and I'm still scratching my head
on what you mean by "works in a way it need to work"?
* Using GUI, we can sign a file, but it's not possible finish a
validation signing the file this way because the file is signed as
in "gpg -b --sign [file]", and the Fedora Account System is
configured to recognized files signed as in "gpg -a --sign [file]";
That's a simple binary v. ASCII aspect. I'm still confused here.
Is there not the option radio button to change this already?
Or are you talking about changing defaults in GUI programs?
* Making some modifications in the GUI that allow users to sign a
file in a way that is compatible with Fedora Account System will
give them a new way to create their CLA without modifying
absolutely nothing in the process (just in _one tool_ used to
acomplish _two steps_ of the process);
Is that, nothing else.
I'm still utterly confused here. I guess I'm just clueless.
Bryan J. Smith Professional, Technical Annoyance
Fission Power: An Inconvenient Solution