Updated readme.md & Added few keyboard shortcuts

[mebinthattil]

The readme lacked few critical links such as :

• trying sugar online
• experience sugar page
• sugar wiki

Also changed the download link to now directly point to the download page of the speak activity. Before it pointed to a page where you would have to search for the speak activity and then download it.

---

Added few keyboard shortcuts for common actions such as:

• speaking the text
• switching to speak mode
• switching to chatbot mode
• adjusting pitch
• cycling through mouth types

[quozl]

Please never close a pull request unnecessarily. You have split away from the other discussion, and it looks like you are trying to hide it. Of course you aren't, but there's no reason to have closed. You could have reset your branch to ec299b7 and pushed it and your other pull request would be updated.

The older pull request #35

Our guidance on branching you have not followed;

• https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#branching

Our guidance on commit messages you have not followed;

• https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#making-commits

GitHub correctly abbreviates your ec299b7 commit message when rendering the pull request pages. The ellipsis shows you have not kept to common commit message formatting, which our guidance reinforces.

Please fix the commit messages.

[mebinthattil]

Going forward I shall make sure to strictly abide by the contribution docs. The contribution docs mention that I need to create a separate branch and create a PR from that to the master branch of the speak repo.

But since this current PR is on the master branch of my fork does that mean that I have to close this PR and create another PR from a separate branch? Is there a way I can change the source branch for a PR?

I apologize for any inconvenience caused and assure you that I will take steps to prevent such mistakes from occurring in the future.

[quozl]

I've never had to do it, because I always get it right. 😀

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request looks interesting.

[mebinthattil]

That article mentions how the base repository can be changed, but in my case I want to change the source repo (which I think cannot be edited).

Changing base repo would mean that I could merge this PR into another fork from the sugar speak repo.

But what I need to do is to merge this PR to the master of speak repo, but from a branch on my fork.

So does this leave me with no other option other than closing this PR? Again sorry for this, will make sure not to make these mistakes again.

[quozl]

Hmm, thanks, let me know what you find.

[mebinthattil]

I see no other option other than closing this PR and creating another one. May I proceed?

[quozl]

You should learn how to rewrite your commits and then force push, that way only this pull request is updated.