Vincent van Ravesteijn wrote: > I don't really get this. When used to it, I don't think it is > technically a very difficult workflow.
do you know the story about the guy who didn't step into the development for several month/years? because it was difficult to setup win compilation process for lyx? i think his name was Vincent and once used to, it was pice of cake :) think of newbies or people who for example want to add something to documentation. such people needed to 'svn up' and 'svn diff' up to now. we should keep things on a similar level of simplicity. many people around are not software developers at all and they won't spend one week for studying git philosophy or hacks. some complicated structure of branches or merge processes can easily repell them. >Second, does that mean > that the less skilled developers are only allowed to do small > things and refrain from the larger features because they don't > know how to use the branches ? well, my point is that git fancy features shouldn't be hindrance for non-git people to contribute. it should generally remain simple despite all the hell i'm able to do with git on my box. > > Very good point. I don't think that's wanted, and I think it would not > > harm if any new workflow wouldn't deviate _needlessly_ from what seemed > > to have worked reasonably well for the project in the past. So even if > > there are new bells and whistles in a potential new tool there is no > > need to require their use on a "but we can!" base. > > I don't propose this based on a "because it can" base. I saw > that even a lot of small commits, were either corrected adjusted > etc. several times. How are we gonna decide which feature deserves > a branch and which doesn't ? intuitively? up to now i commited locally bigger things and small glitches commited directly. to create branch and care about some merging/tagging for every piece of code/comment/doc around looks somewhat annoying and it may make me think twice whether i really want to fix some typo ;) for all my comments i dont understand what exact workflow you have in mind until i see some clear guidelines/ git commands so my opinion may change when i see them... pavel
