background preloader

Team Collaboration With GitHub

Team Collaboration With GitHub
GitHub has become the corner stone for all things open source software. Developers love it, collaborate on it and are constantly building awesome projects through it. Apart from hosting our code, GitHub's main attraction is using it as a collaborative tool. In this tutorial, let's explore some of the most useful GitHub features, especially for working in teams, making it all the more efficient, productive and, most importantly, fun! One thing that I find very useful is integrating the Github Wiki into the main source code project. This tutorial assumes that you are already familiar with Git, the open source distributed version control system, created by Linus Torvalds in 2005. In the world of software projects, it is inevitable that we will find ourselves working in a team to deliver a project. If you prefer a screencast for a visual walk-through, hop just below to view it and refer to this tutorial as side notes: There are generally two ways of setting up Github for team collaboration: Related:  Git

A successful Git branching model » nvie.com In this post I present the development model that I’ve introduced for some of my projects (both at work and private) about a year ago, and which has turned out to be very successful. I’ve been meaning to write about it for a while now, but I’ve never really found the time to do so thoroughly, until now. I won’t talk about any of the projects’ details, merely about the branching strategy and release management. Why git? ¶ For a thorough discussion on the pros and cons of Git compared to centralized source code control systems, see the web. But with Git, these actions are extremely cheap and simple, and they are considered one of the core parts of your daily workflow, really. As a consequence of its simplicity and repetitive nature, branching and merging are no longer something to be afraid of. Enough about the tools, let’s head onto the development model. Decentralized but centralized ¶ Each developer pulls and pushes to origin. The main branches ¶ masterdevelop Supporting branches ¶ develop

List of HTTP status codes This is a list of Hypertext Transfer Protocol (HTTP) response status codes. Status codes are issued by a server in response to a client's request made to the server. It includes codes from IETF Request for Comments (RFCs), other specifications, and some additional codes used in some common applications of the Hypertext Transfer Protocol (HTTP). The first digit of the status code specifies one of five standard classes of responses. The message phrases shown are typical, but any human-readable alternative may be provided. Unless otherwise stated, the status code is part of the HTTP/1.1 standard (RFC 7231).[1] The Internet Assigned Numbers Authority (IANA) maintains the official registry of HTTP status codes.[2] Microsoft Internet Information Services (IIS) sometimes uses additional decimal sub-codes for more specific information,[3] however these sub-codes only appear in the response payload and in documentation, not in the place of an actual HTTP status code. 100 Continue 2xx Success[edit]

GNU Assembler the beginning bissel älter das ganze gerade aufm backup wieder gefunden vllt. bringts dem ein oder anderem was So willkommen zu meinem ersten kleinen Assembler tutorial. Zuerst einmal ein paar kurze Informationen über den GNU Assembler und über die Funktionsweiße des Assemblers und der Register. Was ihr hier lernen werdet sind absolute grundlagen in Assembler also den aufbau eines Programmes Sprungadressen den umgang mit variablen die benutzung von macros und abfragen. Was ist der GNU Assembler?(entnommen aus Wiki) Code: The GNU Assembler, commonly known as Gas, is the assembler used by the GNU Project. So los geht’s jungx! Reigster: Register sind das wichtigste in Assembler. Was sind denn Überhaupt reigster? Besondere Register eax – extended accumulator register ebx – extended base register ecx – extended counter register edx – extended data register ebp – extended base pointer esp – extended stack pointer Die ersten 4 allgeminen Register(eax,ebx,ecx,edx) sind in weitere kleinere Register unterteilt.

nvie/gitflow: Git extensions to provide high-level repository operations for Vincent Driessen's branching model. 15 Incredible Sites Built With Twitter Bootstrap Here at Untame we have a special place in our hearts that is only filled by one thing – responsive design and smart design (okay, okay: two things). Twitter Bootstrap is a flexible front end framework that provides developers and designers an incredible set of tools that they can wield in as large or as small a capacity as needed. In any number of uses, there are tons of great sites that benefit from the Twitter Bootstrap framework and we want to highlight just a few! The Pink League Improvely Discoursehq leanix CodrSpace BreweryDB Opencooks NoteSurf Resource Guru Gusta Cup Trek Bagel Hint Percentage Calculator Sweet Soundtrack NameVine Well there you are!

Learn to Code for Free With These 10 Online Resources If Mark Zuckerberg and Bill Gates say so, it must be true: Understanding how to code is the new literacy. Take Zuck and Gates' advice — learn to code. Understanding computer programming will open doors to new jobs and opportunities. But you're probably thinking, where do I even begin? Will code classes drain my money and time? Fortunately for you, there are loads of ways to learn coding online, without paying a thing. We've rounded up 10 places on the web that teach coding through video tutorials, games and quizzes. Homepage image courtesy of iStockphoto, bmcent1

Using git-flow to automate your git branching workflow If you need tagged and versioned releases, you can use git-flow’s release branches to start a new branch when you’re ready to deploy a new version to production. Like everything else in git-flow, you don’t have to use release branches if you don’t want to. Prefer to manually git merge --no-ff develop into master without tagging? $ git flow release start 0.1.0 Switched to a new branch 'release/0.1.0' Summary of actions: - A new branch 'release/0.1.0' was created, based on 'develop' - You are now on branch 'release/0.1.0' Follow-up actions: - Bump the version number now! Bump the version number and do everything that’s required to release your project in the release branch. $ git flow release finish 0.1.0 Switched to branch 'master' Merge made by the 'recursive' strategy. authentication.txt | 1 + 1 file changed, 1 insertion(+) create mode 100644 authentication.txt Deleted branch release/0.1.0 (was 1b26f7c).

dafont.com MikeOS - simple x86 assembly language operating system x86 operating system MikeOS is an operating system for x86 PCs, written in assembly language. It is a learning tool to show how simple 16-bit, real-mode OSes work, with well-commented code and extensive documentation. Features: A text-mode dialog and menu-driven interface Boots from a floppy disk, CD-ROM or USB key Over 60 system calls for use by third-party programs File manager, text editor, image viewer, games... The code is completely open source (under a BSD-like license), and is written by Mike Saunders and other developers. News 28 Oct 2013: MikeOS mouse library released -- Joshua Beck has implemented his TachyonOS mouse code as a MikeOS library. Downloads The link below contains the source code (see the source and programs directories), along with disk images for floppies/USB keys and CD-Rs in the disk_images folder. You can write the images to a floppy disk, USB key or CD-R and boot your PC from them to test -- or use a PC emulator such as QEMU, VirtualBox or VMware. Images Handbooks

Paris JUG : Improve your sex life with Git | In Fine blog Mardi soir se tenait une session consacrée entièrement à Git au Paris JUG qui a été sponsorisée par In Fine. Elle a rencontré un énorme succès, les places ont été prises d’assaut en moins de 4h. Néanmoins beaucoup de gens se sont fait recaler à l’entrée. La polémique des inscriptions Certains ont accusé JUG Events pour ce désastre au niveau des inscriptions. Quiz et Mac Book In Fine, sponsor du JUG a voulu pour cette soirée créer une animation différente : des boîtiers ont été distribués à chaque participant afin de participer à un quiz portant sur Git et Java principalement, présenté par Antoine Ramponi. Sébastien Douche, en habitué, est venu présenté Git en 2 parties : la première théorique est la deuxième avec des cas plus pratiques. Mais avant d’attaquer le vif du sujet, rappelons qui est Sébastien Douche. A première vue, Git peut sembler complexe, pourtant il est fait de concepts simples. Git peut être vu de 2 points de vue : backend et frontend. Cliquer pour agrandir Bien commencer

Getting Started - Google Maps JavaScript API v3 Audience This documentation is designed for people familiar with JavaScript programming and object-oriented programming concepts. You should also be familiar with Google Maps from a user's point of view. This conceptual documentation is designed to let you quickly start exploring and developing applications with the Google Maps API. Obtaining an API Key All Maps API applications* should load the Maps API using an API key. * Google Maps API for Business developers must not include a key in their requests. To create your API key: Visit the APIs Console at and log in with your Google Account. By default, a key can be used on any site. Hello, World The easiest way to start learning about the Google Maps API is to see a simple example. View example (map-simple.html) Even in this simple example, there are a few things to note: We declare the application as HTML5 using the <! These steps are explained below. Declaring Your Application as HTML5 HTTPS or HTTP

Git dans la pratique (2/2) Dans une première partie, nous avons abordé la notion d’index et la différence entre une branche locale et une branche distante. Une fois les notions d’index et de branches locales et distantes bien comprises, il est possible d’aborder des fonctionnalités plus avancées de Git. Oui, Git est efficace et flexible Mettre de côté des modifications Régulièrement, on se retrouve avec des modifications en cours sur notre copie de travail quand vient une tâche plus prioritaire. Pour reprendre le travail commencé et rangé il est possible de le récupérer de 2 façons différentes : soit nous avons la possibilité de créer une branche sur laquelle nous pourrons créer autant de commits que nécessaire, de basculer entre cette tâche que l’on peut faire avancer au rythme souhaité si elle n’est plus prioritaire. Cherry-picking Il est classique d’utiliser des branches pour gérer les différentes versions des différents environnements où est déployée l’application. Merge vs Rebase Exemple Cas d’un merge Conclusion

Modeling IT Systems Modeling is the foundation for successful development and implementation of new IT systems. A correct and complete model ensures that, in the end, users get the IT system they need. Figure 4.1 Different views of a system In this chapter, we show how a conceptual model of an IT system can be developed with the help of UML. Taking into consideration the 80:20 rule, we do not use all the features of UML. The IT system model consists of four different views, each of which emphasizes certain aspects and which are closely related to each other. Figure 4.2 Different views of an IT system External View—Use case diagram and use case sequence diagram Structural View—Class diagram Interaction View—Sequence diagram and communication diagram Behavioral View—Statechart diagram Each of these views emphasizes certain aspects, and thus, disregards all others. The external view shows the use cases of the IT system in the form of UML use case diagrams and an interface prototype.

Related: