Excerpts from Raniere Silva's message of 2015-03-26 20:45:44 +0100: > > I am very interested in how the workflow to have people make an initial > > empty PR has worked out for you. > > https://gist.github.com/tpoisot/9beac414179518ad10c5#workflow > > Do you find that it helps prevent someone > > coming out of the blue with a lot of work already done? > Maybe. The only problem here is that people could be afraid to contributing > because they need to do a commitment before know if they will get it done.
would not stop me, i just would not make the PR until i had some code, but i can see that it might stop someone. > > Do you have problems with people having a messy history? > I prefer that people rebase their branch to get upstream updates instead of > merging upstream into the branch. i found problems with people not knowing how to do a merge. they would fix conflicts the wrong way and commits that had been rewritten before merging, so it's less about merging a messy history, but making a mess when doing the merge. merging is something i'd only allow experienced developers do. greetings, martin. -- eKita - the online platform for your entire academic life -- chief engineer eKita.co pike programmer pike.lysator.liu.se caudium.net societyserver.org secretary beijinglug.org mentor fossasia.org foresight developer foresightlinux.org realss.com unix sysadmin Martin Bähr working in china http://societyserver.org/mbaehr/ _______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
