[liblouis-liblouisxml] Re: Doing fork from CLI

  • From: Mesar Hameed <mesar.hameed@xxxxxxxxx>
  • To: liblouis-liblouisxml@xxxxxxxxxxxxx
  • Date: Thu, 4 Sep 2014 15:16:13 +0100

Hi Christian,

On Thu 04/09/14,14:10, Christian Egli wrote:
> Hi all
> 
> On 09/04/2014 12:36 PM, Mesar Hameed wrote:
> >github only allows for a very strict workflow with git,  which may not
> >be suitable for all people or all projects.
> 
> It might be strict and simple but it makes it easy and efficient for me. I
> can not sink endless amount of time into liblouis and using the github
> workflow makes it very efficient for me.

It might be efficient for sighted developers, but if it rules out blind
developers or contributors then I think this is not really a tenable
position, especially considering the nature of the project.

> If the patches come in via pull request I will look at them. If
> they are hidden on some branch with no pull request they will be forgotten

$ git branch -r

will show remote branches, and is accessible. this is not hidden.

There are some good online git resources if you need to be more
comfortable with the git command line client.

> just like in the last release.

It was our first release as the new team, and things can always be
improved. These are teething problems while we settle with git and our
new responsibilities.

> > We can apply your patches in seperate branches until they are ready,
> > much like we have with tables/ueb, hammera_hu etc.
> 
> To be honest I'd prefer if this stuff was in a separate repo with pull
> requests.

Idealy yes, but remember that the screenreader user has very little
power in getting github to make their product more accessible.
So we should not add additional burden for those that are
screen reader users, especially since this doesn't give us any real benefits.

thanks,
Mesar

Attachment: signature.asc
Description: Digital signature

Other related posts: