Version Control - tips, tricks and good citizenship

Too much theory talk would be useful to have a more hands on talk real world examples.

Presentation was really clear and well delivered.

Overall, a good talk. Does what it says on the tin.

Examples are based on svn, which is still in use but has for the most part fallen out of favor compared to distributed version control systems. I think the talk's relevance could benefit from switching the examples to use a DVCS like git, which is mentioned in the talk and appeared to be used by most of the talk's audience when they were polled by the presenter. That said, many tools are mentioned that assist with the development process and integrate with git. I'm surprised workflows like git-flow didn't seem to get much of a mention.

One relevant subtopic that wasn't covered -- not the fault of the presenter, as I find it's a topic that really doesn't receive enough attention -- is the possibility of scripting proactive searches for merge conflicts between active feature branches and notification of concerned parties, so that merge conflicts aren't discovered late and force potentially hasty or risky resolutions or the exclusion of affected code from time-boxed releases.

PHP_CodeSniffer is covered. A more modern alternative that isn't mentioned is php-cs-fixer: https://github.com/FriendsOfPHP/PHP-CS-Fixer.

Commit message templates are mentioned, though I don't believe Github PR templates are: https://github.com/blog/2111-issue-and-pull-request-templates. Again, not the fault of the presenter, as the feature release was very recent.

In terms of the presentation, a really good first talk. Clearly delivered and decent slides. Good speed and a decent amount of content.

However, most of the audience are using Git and I do appreciate your answers regarding my question about your preference for SVN, but the talk could benefit from discussing the problems solved by using different VCS-es - since you are aiming at an audience that has little prior experience or a dislike for VCS, it would be wise to present current best practice to ensure that people are armed with the best information on which to base their decisions.

Examples were too abstract. For me it would be more descriptive to see real-life examples of conflicts. And most of people are using Git now, so talking about SVN may seems a bit out of date.

Good talk.
I was hoping for more about commit comments, it would have been interesting hearing your option on that as well :-)

This talk was a bit "meh".
'Get a coffee, have a chat.' Was the overarching messgae, which as important as it is it is, is nothing groundbreaking.

Tess, for your first conference you did well. You did not sound nervous, spoke clearly and used pauses well.

I think there might be a tiny bit of preaching to the choir but I know that there will always be someone who wants to know about this stuff or need a refresher. It was good to go back to theory that can be done on any version control and remember there is more to version control than git.

It was easy to get hung on the fact the examples were not in git though considering its popularity.

Maybe adjust the content a little bit if you give this talk again but I do think it delivered on what you set out to do.

This talk wasn't what I expected, in that it lacked for technical detail (I'm fairly new to SVN). That said, it was still a very useful talk and Tess was an enthusiastic and engaging speaker.

Less useful for me, but some great advice in there for people who are not as experienced with version control. I think the main problem was the room full of git-snobs (:) and the basis of the talk being SVN (not the speaker's fault) - it is surprising how many companies do still use SVN, and common sense applies everywhere. All in all, was a clear and well presented topic.

A lot of people, myself included, thought this would be Git related and there was surprise to see Svn used in the examples but the talk was aimed at the overall principles of version control rather than the technicalities. For me I think it could have done with a few more details such as how to write good commit messages and other such things as the overall message of "talk and get a coffee" was a bit flat.

For a first conference talk your delivery was very good and well paced. Well done