X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Message-ID: <569A9AD3.9060306@iee.org>
Date: Sat, 16 Jan 2016 19:32:35 +0000
From: "M. J. Everitt (m DOT j DOT everitt AT iee DOT org) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] LP1532611 (modular fie formats) fixes
References: <CAC4O8c8tTutWKvXFA-nfcmUiUGYbOY1_5171Vf3WDk09Tmx3yw AT mail DOT gmail DOT com> <56982D5A DOT 1020706 AT prochac DOT sk> <CAC4O8c93jC=qRPAHnzBCrVYONGnyvQ55qv5yQ-vor8es-0_meg AT mail DOT gmail DOT com> <569A2DAC DOT 9070200 AT prochac DOT sk> <569A3280 DOT 3030704 AT iee DOT org> <201601161912 DOT u0GJC8Fs025943 AT envy DOT delorie DOT com>
In-Reply-To: <201601161912.u0GJC8Fs025943@envy.delorie.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:FEMt/BNLdlSGr279xoo3MFcKNbeoY/9Ec9GYiXXxmI3bLj9EenK
 fJbO3GrZk6oode0rdTYieBxE0EqiEYcdUmVUX1VDaIiN4IrVjJbFuMRGxb9xubxBDaOixIv
 4xLSPBexB9y4pgZpypT64EW9SjhcridUeOg0wZjIerMjPMUSioEXW6kgDb54Iw4GG/RigwH
 A2n5zVOOODs0bchN13c6g==
X-UI-Out-Filterresults: notjunk:1;V01:K0:igkz7gZ4RwE=:RlOTY69UX2G+9uI6v+2N+Z
 bla0eAP6OiYofY0jiUBVMDfOvbtDGWoScWydDSWRYwto9m1lxGfDKwZamHGF2uiHGHvJ2WoYL
 8hD9kXoYhPe9FO3Cy/+L+K6RulLE55yUBkUeXK+aqaWas5mITp6zvQaMcs/tGkeljVG3zaZWa
 hhEtx4sDj9aIFTVx3CNfds+JFY1BwXP/CGB/gjbQ/4l0YPAeCooRjiL/VNZvkqfYg6sgNkJEg
 XeU8PN8ES0rBVhJN7O5P9/L7myEl8fm8CB5xFvAHP+Ck0kbJKFgEbqNq/+MpwDVCPvmU07J1S
 g0c3E49xaSRC8QLrhnoJ+TuT4CLVonRMexTzf4Rp++9d/C9KfFqlBcPTCktNK0YEnTcfQ6l8N
 Y+U57zurVbq7XFjpF1uvzlyIYKDuX8ltF2LEBlAPiV/tuRqeQ1mdBy8KoJBr+TAWm2oP2bj1Y
 53eGDgEOlnFAGQINcR33DrnP9fcuH3czjN4Ye/24XGICgEtfUQeoxgDWcO3ZWSA+gWhouhioZ
 7u5dN5bnvRm2B3L+zsFfDwX+1a0zGrwzUdJzyOmjAsizCg75kvJ+dAE6N6SEYJKgdBBK03L/c
 2b9McVHYZTUIMWqEsXprdA1GVgCHc1Y2D6oVmtpPHhJRU2SX0x3mglh18K8Y+9slKb/28DKQQ
 aOOdO4gGeDsY4MgoJdjtLbzJIyI4Nqz2BuSvQpQSqFFMMTGBp/fmDuaNs+qHvST9l01KQyDxb
 NR30yfGIuTT3G3AR
Reply-To: geda-user AT delorie DOT com


On 16/01/16 19:12, DJ Delorie wrote:
>> http://blog.scottlowe.org/2015/01/27/using-fork-branch-git-workflow/ .
> We used that flow before.  Pull requests got lost, a lot of the work
> done in forks got forgotten, etc.  We use the same basic flow now
> (branch-n-merge instead of fork-n-pull) but having all the "things to
> be reviewed" in one spot makes it easier to keep track of it all.
But from where I'm sitting/standing .. where IS that one spot? I see
several .. sprinkled all over your git and user's "invisible" home repos
(now I'm sure if I got a user account, I could clone these just as
easily as the next dude, but that's not my point). For anyone to be able
to review other's code .. it needs to be easily accessible, nay ..
blatantly obvious, even. I'm not sure (correct me if I'm wrong, of
course) that that is the case currently...
> There's nothing stopping you from using the fork model still, as some
> of us do.  Just keep in mind that it's your responsibility to keep
> your work from being forgotten.
Of course. That's reasonably academic, but also illustrates the point
above about code being freely accessible to others.

I'll take the opportunity to clarify here .. I know people are
particular about their code and features, coding standards and what-not.
The idea is not to create a platform for people to rail against one
another, its to see what other people are working on, how they achieve
their goals, and generally open up the coding effort that's currently
going on. Perhaps with a little bit of friendly 'review' we can all
suggest improvements, and collectively improve? Also, its transparent
how to merge A's work with B and C and so forth .. at least in my eyes ..
>> I'm pretty sure this workflow is not unique to Github, it's just become
>> popular because of it.
> The details are, though:
>
> "Forking a repository is really straightforward:
>     1. Make sure you’re logged into GitHub with your account."
>
> "GitHub makes this part incredibly easy. Once you push a new branch up
>  to your repository, GitHub will prompt you to create a pull request"
Yes, this is what I mean about not being unique to GitHub, but partially
becoming popular because of it. As I say, I'm still a relative newbie to
both git and github, but I can really see the power of it, and its
interface, although no reason why the command-line git tools don't
complement it either. As it's free to use, and I have nothing to hide,
this would obviously be my platform of choice (either GH or bitbucket
I've used) for my code development (and already is in a couple of cases).

MJE