Hi Noelia,
Thank you so much. I'll copy this into my git cheat sheet.
Jim
==========
Jim Homme,
Team Lead and Accessibility Consultant,
Bender HighTest Accessibility Team
Bender Consulting Services, Inc.,
412-787-8567,
jhomme@xxxxxxxxxxxxxxxxx
http://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions
E+R=O
-----Original Message-----
From: nvda-addons-bounce@xxxxxxxxxxxxx
[mailto:nvda-addons-bounce@xxxxxxxxxxxxx] On Behalf Of Noelia
Sent: Thursday, December 22, 2016 1:23 PM
To: nvda-addons@xxxxxxxxxxxxx
Subject: [nvda-addons] Re: Request review for Emoticons 5.0 add-on
I suggest you to do the following:
- git checkout 5.0 # Change to 5.0 branch
- git merge upstream/5.0 # Ensure that the branch is updated with last changes
done in the upstream remote.
- git checkout -b doc # Create a new branch based on 5.0, and switch to this
branch.
- Make changes.
- git push origin doc # Push changes to your doc branch.
- Go to your GitHub repo and open a pull request based on the doc branch.
Thanks.
El 22/12/2016 a las 19:15, Jim Homme escribió:
Hi,----------------------------------------------------------------
I tried to look in the Pro Git book before I asked all of this. Here
is what I did so far. I’m lacking confidence, so thank you for your patience.
I forked the repository, so that it has the same name, but under my
user name, which is jhomme.
Then here are the commands I typed next.
Git remote add upstream <url>
Where <url> was the original, not my repository.
Git remote -v
This showed me both repositories.
Git fetch upstream
This told me that it got all of the branches.
Git fetch origin
Origin represents my repository. It did more stuff.
Now this is where I am not quite sure of what to do. I was going to
type git checkout, and the name of a branch. I was thinking that I
should say something like git checkout 5.0, which is the branch under
development, but then I was wavering, because I was thinking maybe I
should type git checkout docs and creat my own, separate branch. Is
this series of commands what I should have done, and all that stuff?
Thanks.
Jim
==========
Jim Homme,
Team Lead and Accessibility Consultant,
Bender HighTest Accessibility Team
Bender Consulting Services, Inc.,
412-787-8567,
jhomme@xxxxxxxxxxxxxxxxx
http://www.benderconsult.com/our%20services/hightest-accessible-techno
logy-solutions
E+R=O
*From:*nvda-addons-bounce@xxxxxxxxxxxxx
[mailto:nvda-addons-bounce@xxxxxxxxxxxxx] *On Behalf Of *derek riemer
*Sent:* Thursday, December 22, 2016 1:02 PM
*To:* nvda-addons@xxxxxxxxxxxxx
*Subject:* [nvda-addons] Re: Request review for Emoticons 5.0 add-on
This is why we need a page with a list of addons and where the source is.
On 12/22/2016 10:49 AM, Noelia wrote:
Hi, I think not, since the automated translations system uses
Bitbucket, an each author can use either Github, Bitbucket or other
hosting, or several of them, for add-ons maintenance.
I prefer GitHub since its intarface seems more comfortable, even to
attach binaries to releases.
Thanks.
El 22/12/2016 a las 16:55, Jim Homme escribió:
Hi,
Here is why I got confused. I followed the link at the bottom of
an e-mail to this group to the Community site. I clicked on the
link for add-ons under development. That took me to BitBucket.
Do we need to alter the Community page so that the link for
add-ons under development goes to GitHub?
Thanks.
Jim
==========
Jim Homme,
Team Lead and Accessibility Consultant,
Bender HighTest Accessibility Team
Bender Consulting Services, Inc.,
412-787-8567,
jhomme@xxxxxxxxxxxxxxxxx <mailto:jhomme@xxxxxxxxxxxxxxxxx>
http://www.benderconsult.com/our%20services/hightest-accessible-techno
logy-solutions
E+R=O
-----Original Message-----
From: nvda-addons-bounce@xxxxxxxxxxxxx
<mailto:nvda-addons-bounce@xxxxxxxxxxxxx>
[mailto:nvda-addons-bounce@xxxxxxxxxxxxx] On Behalf Of Noelia
Sent: Thursday, December 22, 2016 10:27 AM
To: nvda-addons@xxxxxxxxxxxxx <mailto:nvda-addons@xxxxxxxxxxxxx>
Subject: [nvda-addons] Re: Request review for Emoticons 5.0
add-on
The development is been done on Github. The Bitbucket repo is
just for the automatic translation system.
Thanks.
El 22/12/2016 a las 16:23, Jim Homme escribió:
Hi,
I'm a little confused about how to set this up. The add-on
is on GitHub, but the team repository is on BitBucket. Do I
fork a copy on GitHub or BitBucket?
Thanks.
Jim
==========
Jim Homme,
Team Lead and Accessibility Consultant, Bender HighTest
Accessibility
Team Bender Consulting Services, Inc., 412-787-8567,
jhomme@xxxxxxxxxxxxxxxxx <mailto:jhomme@xxxxxxxxxxxxxxxxx>
http://www.benderconsult.com/our%20services/hightest-accessible-techno
logy-solutions
E+R=O
-----Original Message-----
From: nvda-addons-bounce@xxxxxxxxxxxxx
<mailto:nvda-addons-bounce@xxxxxxxxxxxxx>
[mailto:nvda-addons-bounce@xxxxxxxxxxxxx] On Behalf Of Noelia
Sent: Thursday, December 22, 2016 10:14 AM
To: nvda-addons@xxxxxxxxxxxxx
<mailto:nvda-addons@xxxxxxxxxxxxx>
Subject: [nvda-addons] Re: Request review for Emoticons 5.0
add-on
Yes, please.
Thanks.
El 22/12/2016 a las 15:49, Jim Homme escribió:
Hi,
I was thinking of reviewing the documentation. Do you
want me to fork the repository and submit pull requests
if I change the documentation?
==========
Jim Homme,
Team Lead and Accessibility Consultant, Bender HighTest
Accessibility
Team Bender Consulting Services, Inc., 412-787-8567,
jhomme@xxxxxxxxxxxxxxxxx <mailto:jhomme@xxxxxxxxxxxxxxxxx>
http://www.benderconsult.com/our%20services/hightest-accessible-techn
o
logy-solutions
E+R=O
-----Original Message-----
From: nvda-addons-bounce@xxxxxxxxxxxxx
<mailto:nvda-addons-bounce@xxxxxxxxxxxxx>
[mailto:nvda-addons-bounce@xxxxxxxxxxxxx] On Behalf Of
Noelia
Sent: Wednesday, December 21, 2016 4:51 PM
To: nvda-addons@xxxxxxxxxxxxx
<mailto:nvda-addons@xxxxxxxxxxxxx>
Subject: [nvda-addons] Request review for Emoticons 5.0
add-on
Hi, I'm pleased to announce the availability of a 5.0
branch for the Emoticons add-on, whose main author is
Chris Leo, also contributed by Mesar Hameed, a new
author named Francisco Javier Estrada Martínez and myself.
This new branch contains features that could be
available for the next major version (5.0). These are
the changes mentioned in the add-on guide:
Changes for 5.0
• Added support for emojis.
• Improvements for Insert Emoticon dialog with a filter
field and radio buttons to choose displayed emoticons.
• Using guiHelper for Activation settings dialog and
Insert Emoticon
dialog: requires NVDA 2016.4 or higher versions
I'd like to request:
- Basic review for the add-on.
- Indept review for the guide, taking care on possible
grammar errors or language improvements.
- Any feed-back that you want to provide.
If pass, we will post the 5.0-dev version on the
community add-ons website, and about two week later, the
version could become stable.
Please, note that the new 5.0 branch is located at
https://github.com/nvdaes/emoticons
You can clone this repo or add this remote, and review
diffs against master:
git checkout 5.0
git diff master
Thanks to users, reviewers and the other authors of this
great add-on.
Cheers.
----------------------------------------------------------------
NVDA add-ons: A list to discuss add-on code enhancements
and for reporting bugs.
Community addons are available from:
http://addons.nvda-project.org
To send a message to the list: nvda-addons@xxxxxxxxxxxxx
<mailto:nvda-addons@xxxxxxxxxxxxx> To change
your list settings/unsubscribe:
//www.freelists.org/list/nvda-addons
To contact list moderators:
nvda-addons-moderators@xxxxxxxxxxxxx
<mailto:nvda-addons-moderators@xxxxxxxxxxxxx>
5P i h % m جr ,i h y jw‑ ~ z + ) n ,
x ɧ] { j)ZnW ] {' ֩ r + :,zwZ ,j
^ +- Zi h y b ( r 쨺 b ‑ ا ˛ m m
祊 l ? +- { i ] { ' - +- ^ h u v 욇^ h y b (rg==
----------------------------------------------------------------
NVDA add-ons: A list to discuss add-on code enhancements and
for reporting bugs.
Community addons are available from:
http://addons.nvda-project.org To
send a message to the list: nvda-addons@xxxxxxxxxxxxx
<mailto:nvda-addons@xxxxxxxxxxxxx> To change your
list settings/unsubscribe:
//www.freelists.org/list/nvda-addons
To contact list moderators:
nvda-addons-moderators@xxxxxxxxxxxxx
<mailto:nvda-addons-moderators@xxxxxxxxxxxxx>
5P i h % m جr ,i h y jw‑ ~ z + ) n ,
x ɧ] { j)ZnW ] {' ֩ r + :,zwZ ,j
^ +- Zi h y b ( r 쨺 b ‑ ا ˛ m m
祊 l ? +- { i ] { ' - +- ^ h u v 욇^ h y b (rg==
----------------------------------------------------------------
NVDA add-ons: A list to discuss add-on code enhancements and for
reporting bugs.
Community addons are available from:
http://addons.nvda-project.org To send a message to the list:
nvda-addons@xxxxxxxxxxxxx <mailto:nvda-addons@xxxxxxxxxxxxx> To
change your list settings/unsubscribe:
//www.freelists.org/list/nvda-addons
To contact list moderators: nvda-addons-moderators@xxxxxxxxxxxxx
<mailto:nvda-addons-moderators@xxxxxxxxxxxxx>
5P i h % m جr ,i h y jw‑ ~ z + ) n ,
x ɧ] { j)ZnW ] {' ֩ r + :,zwZ ,j ^ +-
Zi h y b ( r 쨺 b ‑ ا ˛ m m
祊 l ? +- { i ] { ' - +- ^ h u v 욇^ h y b (rg==
----------------------------------------------------------------
NVDA add-ons: A list to discuss add-on code enhancements and for
reporting bugs.
Community addons are available from: http://addons.nvda-project.org
To send a message to the list: nvda-addons@xxxxxxxxxxxxx
<mailto:nvda-addons@xxxxxxxxxxxxx>
To change your list settings/unsubscribe:
//www.freelists.org/list/nvda-addons
To contact list moderators: nvda-addons-moderators@xxxxxxxxxxxxx
<mailto:nvda-addons-moderators@xxxxxxxxxxxxx>
--
----------------------------------------------------------------------
--
Derek Riemer
· Department of computer science, third year undergraduate student.
· Proud user of the NVDA screen reader.
· Open source enthusiast.
· Member of Bridge Cu
· Avid skiier.
Websites:
Honors portfolio <http://derekriemer.com> Awesome little hand built
weather app!
<http://django.derekriemer.com/weather/>
email me at derek.riemer@xxxxxxxxxxxx
<mailto:derek.riemer@xxxxxxxxxxxx>
Phone: (303) 906-2194
