[pythonvis] Re: NVDA app module tract: Sound Forge repo now available

  • From: "Joseph Lee" <joseph.lee22590@xxxxxxxxx>
  • To: <pythonvis@xxxxxxxxxxxxx>
  • Date: Sun, 14 Dec 2014 14:44:19 -0800

Hi,
For those, this is where we use add-ons mailing list to alert the add-on/ 
readme authors about this.
For Bitbucket, similar processes are taken, but for add-ons repos, we use email 
versions of those: a potential reviewer will work on a branch, commits it and 
others comment on the commit. Then the add-on author will merge branches. Even 
for my own code, I work from topic branches, and after testing it, merge the 
branch into master.
Cheers,
Joseph

-----Original Message-----
From: pythonvis-bounce@xxxxxxxxxxxxx [mailto:pythonvis-bounce@xxxxxxxxxxxxx] On 
Behalf Of Andre Polykanine
Sent: Sunday, December 14, 2014 2:36 PM
To: Joseph Lee
Subject: [pythonvis] Re: NVDA app module tract: Sound Forge repo now available

Hello Joseph,

So,  for  example,  if I found a couple typos in readme.md, there's no way to 
let you know and allow to merge my corrections in?
I've forked the repo, btw.
Sorry  for  mentioning  Github so often but it's too popular and there are 
quite a number of projects where I collaborate or pull request.
So,  at  Github,  the most common way of operating is the following: a person  
forks  the  repo  he or she wants to contribute to, then makes his/her  changes 
 (in the forked Master branch or in a separate branch for  each  feature),  
then he/she submits a pull requests that is then merged  either  by  the  owner 
 or  by one of the collaborators of the original repository.
I thought you have something alike...


--
With best regards from Ukraine,
Andre
Skype: Francophile
Twitter: @m_elensule; Facebook: menelion My blog: http://menelion.oire.org/


------------ Original message ------------
From: Joseph Lee <joseph.lee22590@xxxxxxxxx>
To: pythonvis@xxxxxxxxxxxxx
Date created: , 12:22:36 AM
Subject: [pythonvis] Re: NVDA app module tract: Sound Forge repo now available


      Hi,
As far as our add-ons processes go, anyone in our team can work on any add-on, 
with the condition being that people need to work on separate branches. Once 
the branches are done, the developer would write to the add-ons list for code 
review, at which point the add-on author will review the branch code and do a 
follow-up such as asking questions and merging the branches into master.
Cheers,
Joseph

-----Original Message-----
From: pythonvis-bounce@xxxxxxxxxxxxx [mailto:pythonvis-bounce@xxxxxxxxxxxxx] On 
Behalf Of Andre Polykanine
Sent: Sunday, December 14, 2014 2:19 PM
To: Joseph Lee
Subject: [pythonvis] Re: NVDA app module tract: Sound Forge repo now available

Hello Joseph,

This is great and neat, but there is no instructions about how to pull request  
in  an accessible way. It says "Click the pull request button in the top right 
corner". Great, but not really helpful.
Don't  you  use pull requests in the add-ons developers team? Or it is just 
our, I mean, Github users modus operandi?..
Thanks!


--
With best regards from Ukraine,
Andre
Skype: Francophile
Twitter: @m_elensule; Facebook: menelion My blog: http://menelion.oire.org/


------------ Original message ------------
From: Joseph Lee <joseph.lee22590@xxxxxxxxx>
To: pythonvis@xxxxxxxxxxxxx
Date created: , 11:52:08 PM
Subject: [pythonvis] Re: NVDA app module tract: Sound Forge repo now available


      Hi,
Hopefully, this tutorial should help:
https://www.atlassian.com/git/tutorials/making-a-pull-request/
Cheers,
Joseph

-----Original Message-----
From: pythonvis-bounce@xxxxxxxxxxxxx [mailto:pythonvis-bounce@xxxxxxxxxxxxx] On 
Behalf Of Andre Polykanine
Sent: Sunday, December 14, 2014 1:42 PM
To: Joseph Lee
Subject: [pythonvis] Re: NVDA app module tract: Sound Forge repo now available

Hello Joseph,

And  what  about  pull requests on Bitbucket? Is there any solution? A direct 
URL maybe?


--
With best regards from Ukraine,
Andre
Skype: Francophile
Twitter: @m_elensule; Facebook: menelion My blog: http://menelion.oire.org/


------------ Original message ------------
From: Joseph Lee <joseph.lee22590@xxxxxxxxx>
To: pythonvis@xxxxxxxxxxxxx
Date created: , 11:11:41 PM
Subject: [pythonvis] Re: NVDA app module tract: Sound Forge repo now available


      Hi,
I used Bitbucket to highlight the fact that the add-on is written by other 
contributors, as this is what we use. However, if people genuinely want Github, 
I'll create a mirror repo over there under my name (which actually defeats the 
collaborative process).
Cheers,
Joseph

-----Original Message-----
From: pythonvis-bounce@xxxxxxxxxxxxx [mailto:pythonvis-bounce@xxxxxxxxxxxxx] On 
Behalf Of Andre Polykanine
Sent: Sunday, December 14, 2014 1:09 PM
To: Joseph Lee
Subject: [pythonvis] Re: NVDA app module tract: Sound Forge repo now available

Hello Joseph,

Just  of  curiosity:  why  Bitbucket  and  not Github? I mean, for all add-ons, 
 not  for  you  only?  Github  is  far  more  accessible than BitBucket.
For  instance,  I've been searching for a quarter of an hour and can't find a 
way to submit a pull request.
Thanks.


--
With best regards from Ukraine,
Andre
Skype: Francophile
Twitter: @m_elensule; Facebook: menelion My blog: http://menelion.oire.org/


------------ Original message ------------
From: Joseph Lee <joseph.lee22590@xxxxxxxxx>
To: pythonvis@xxxxxxxxxxxxx
Date created: , 10:42:19 PM
Subject: [pythonvis] NVDA app module tract: Sound Forge repo now available


      Hi,

For our app module tract participants: Sound Forge repo is now available at:

https://bitbucket.org/nvdaaddonteam/soundforge/

The repo uses Git, so you need to have Git on your computer. Good luck.

Cheers,

Joseph

List web page is 
//www.freelists.org/webpage/pythonvis

To unsubscribe, send email to 
pythonvis-request@xxxxxxxxxxxxx with "unsubscribe" in the Subject field.

List web page is 
//www.freelists.org/webpage/pythonvis

To unsubscribe, send email to 
pythonvis-request@xxxxxxxxxxxxx with "unsubscribe" in the Subject field.

List web page is 
//www.freelists.org/webpage/pythonvis

To unsubscribe, send email to 
pythonvis-request@xxxxxxxxxxxxx with "unsubscribe" in the Subject field.

List web page is 
//www.freelists.org/webpage/pythonvis

To unsubscribe, send email to 
pythonvis-request@xxxxxxxxxxxxx with "unsubscribe" in the Subject field.

List web page is 
//www.freelists.org/webpage/pythonvis

To unsubscribe, send email to 
pythonvis-request@xxxxxxxxxxxxx with "unsubscribe" in the Subject field.

List web page is 
//www.freelists.org/webpage/pythonvis

To unsubscribe, send email to 
pythonvis-request@xxxxxxxxxxxxx with "unsubscribe" in the Subject field.

List web page is 
//www.freelists.org/webpage/pythonvis

To unsubscribe, send email to 
pythonvis-request@xxxxxxxxxxxxx with "unsubscribe" in the Subject field.

List web page is
//www.freelists.org/webpage/pythonvis

To unsubscribe, send email to
pythonvis-request@xxxxxxxxxxxxx with "unsubscribe" in the Subject field.

Other related posts: