<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" 
	xmlns:atom="http://www.w3.org/2005/Atom" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/" 
	xmlns:dc="http://purl.org/dc/elements/1.1/" 
	xmlns:georss="http://www.georss.org/georss" 
	xmlns:icbm="http://postneo.com/icbm" 
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/" 
	xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" 
	xmlns:wfw="http://wellformedweb.org/CommentAPI/" >

<channel>
	<title>Source Code Management Interest Group</title>
	<link>http://www.yacs.fr/section-522-source-code-management-interest-group</link>
	<atom:link href="http://www.yacs.fr/section-feed/522"  rel="self" type="application/rss+xml" />
	<description>How do we manage the source code of yacs?</description>
	<language>fr</language>
	<copyright>2002-2010, Paxer Conseil</copyright>
	<managingEditor>bernard.paques@bigfoot.com</managingEditor>
	<webMaster>bernard.paques@bigfoot.com</webMaster>
	<icbm:latitude>40.32</icbm:latitude>
	<icbm:longitude>-111.68</icbm:longitude>
	<georss:point>40.32  -111.68</georss:point>
	<lastBuildDate>Thu, 09 Feb 2012 09:02:51 GMT</lastBuildDate>
	<generator>yacs</generator>
	<docs>http://blogs.law.harvard.edu/tech/rss</docs>
	<ttl>59</ttl>

 <item>
		<title>Convention for commit message</title>
		<link>http://www.yacs.fr/article-7666-convention-for-commit-message</link>
		<guid isPermaLink="true">http://www.yacs.fr/article-7666-convention-for-commit-message</guid>
		<description> Bernard you use several branches to commit your improvements to the sources. For example 'user-interface', 'fixes', 'clean', 'overlays', etc. 
 but as I realized, the rebase mecanism make me loose track of that information when I integrate your contribs to yacs/yacs/master. 
 A solution is to put the name of the branch in the commit message. for example : 
   fix french translation 
 Adding branch name could be done automaticaly by adding a hook in git repository. 
 http://blog.lyrixx.info/web-dev/ajouter-le-nom-de-la-branche-dans-le-message-de-commit-avec-git/ 
 what do you think ? </description>
		<dc:creator>Alexis Raimbault</dc:creator>
		<category>Tools and procedures used in the yacs project</category>
		<pubDate>Tue, 07 Jun 2011 04:23:29 GMT</pubDate>
		<comments>http://www.yacs.fr/section-527-tools-and-procedures-used-in-the-yacs-project#_discussion</comments>
		<slash:comments>9</slash:comments>
		<wfw:comment>http://www.yacs.fr/comments/post.php/article/7666</wfw:comment>
		<wfw:commentRss>http://www.yacs.fr/comments/feed.php/article/7666</wfw:commentRss>
		<trackback:ping>http://www.yacs.fr/links/trackback.php?anchor=article%3A7666</trackback:ping>
	</item>

 <item>
		<title>Sample objects to create github information flows</title>
		<link>http://www.yacs.fr/article-7413-sample-objects-to-create-github-information-flows</link>
		<guid isPermaLink="true">http://www.yacs.fr/article-7413-sample-objects-to-create-github-information-flows</guid>
		<description>The attached file is released according to Creative Commons BY-NC-SA license</description>
		<dc:creator>Bernard Paques</dc:creator>
		<category>Tools and procedures used in the yacs project</category>
		<pubDate>Fri, 22 Oct 2010 06:50:11 GMT</pubDate>
		<comments>http://www.yacs.fr/section-527-tools-and-procedures-used-in-the-yacs-project#_discussion</comments>
		<slash:comments>0</slash:comments>
		<wfw:comment>http://www.yacs.fr/comments/post.php/article/7413</wfw:comment>
		<wfw:commentRss>http://www.yacs.fr/comments/feed.php/article/7413</wfw:commentRss>
		<trackback:ping>http://www.yacs.fr/links/trackback.php?anchor=article%3A7413</trackback:ping>
	</item>

 <item>
		<title>Cloner son fork de Yacs sous Windows</title>
		<link>http://www.yacs.fr/article-7407-cloner-son-fork-de-yacs-sous-windows</link>
		<guid isPermaLink="true">http://www.yacs.fr/article-7407-cloner-son-fork-de-yacs-sous-windows</guid>
		<description> Après avoir pas mal tâtonné (merci Alexis pour les tuyaux), voici comment j'ai créer et cloné mon fork de Yacs sous windows. 
 Créer son compte sur GitHub 
 
 
 Créer son fork de yacs 
Aller sur http://github.com/yacs/yacs 
  
 Clé SSH 
Créer ou récupérer la clé SSH avec GitGUI : 
 
 
Définir sa clé SSH dans GitHub : 
 
 
 Adresse du fork  ... more   </description>
		<dc:creator>Jmarc</dc:creator>
		<category>Tools and procedures used in the yacs project</category>
		<pubDate>Mon, 18 Oct 2010 22:08:21 GMT</pubDate>
		<comments>http://www.yacs.fr/section-527-tools-and-procedures-used-in-the-yacs-project#_discussion</comments>
		<slash:comments>3</slash:comments>
		<wfw:comment>http://www.yacs.fr/comments/post.php/article/7407</wfw:comment>
		<wfw:commentRss>http://www.yacs.fr/comments/feed.php/article/7407</wfw:commentRss>
		<trackback:ping>http://www.yacs.fr/links/trackback.php?anchor=article%3A7407</trackback:ping>
	</item>

 <item>
		<title>Git sur Windows</title>
		<link>http://www.yacs.fr/article-7384-git-sur-windows</link>
		<guid isPermaLink="true">http://www.yacs.fr/article-7384-git-sur-windows</guid>
		<description>Premiers pas sur Windows avec Git</description>
		<dc:creator>Jmarc</dc:creator>
		<category>Tools and procedures used in the yacs project</category>
		<pubDate>Sat, 16 Oct 2010 16:58:43 GMT</pubDate>
		<comments>http://www.yacs.fr/section-527-tools-and-procedures-used-in-the-yacs-project#_discussion</comments>
		<slash:comments>3</slash:comments>
		<wfw:comment>http://www.yacs.fr/comments/post.php/article/7384</wfw:comment>
		<wfw:commentRss>http://www.yacs.fr/comments/feed.php/article/7384</wfw:commentRss>
		<trackback:ping>http://www.yacs.fr/links/trackback.php?anchor=article%3A7384</trackback:ping>
	</item>

 <item>
		<title>Mettre à jour son Yacs &quot;customisé&quot; avec SmartGit</title>
		<link>http://www.yacs.fr/article-7402-mettre-a-jour-son-yacs-customise-avec-smartgit</link>
		<guid isPermaLink="true">http://www.yacs.fr/article-7402-mettre-a-jour-son-yacs-customise-avec-smartgit</guid>
		<description>Voici une méthode illustrée permettant, à l'aide de SmartGit, de simuler la mise à jour d'une version &quot;customisé&quot; de Yacs en l'upgradant avec les nouvelles versions de Yacs</description>
		<dc:creator>Jmarc</dc:creator>
		<category>Tools and procedures used in the yacs project</category>
		<pubDate>Fri, 15 Oct 2010 12:43:40 GMT</pubDate>
		<comments>http://www.yacs.fr/section-527-tools-and-procedures-used-in-the-yacs-project#_discussion</comments>
		<slash:comments>2</slash:comments>
		<wfw:comment>http://www.yacs.fr/comments/post.php/article/7402</wfw:comment>
		<wfw:commentRss>http://www.yacs.fr/comments/feed.php/article/7402</wfw:commentRss>
		<trackback:ping>http://www.yacs.fr/links/trackback.php?anchor=article%3A7402</trackback:ping>
	</item>

 <item>
		<title>How to contribute to yacs core software?</title>
		<link>http://www.yacs.fr/article-7398-how-to-contribute-to-yacs-core-software</link>
		<guid isPermaLink="true">http://www.yacs.fr/article-7398-how-to-contribute-to-yacs-core-software</guid>
		<description>A bird-eye view of the workflow supported at Github</description>
		<dc:creator>Bernard Paques</dc:creator>
		<category>Tools and procedures used in the yacs project</category>
		<pubDate>Fri, 15 Oct 2010 12:02:42 GMT</pubDate>
		<comments>http://www.yacs.fr/section-527-tools-and-procedures-used-in-the-yacs-project#_discussion</comments>
		<slash:comments>2</slash:comments>
		<wfw:comment>http://www.yacs.fr/comments/post.php/article/7398</wfw:comment>
		<wfw:commentRss>http://www.yacs.fr/comments/feed.php/article/7398</wfw:commentRss>
		<trackback:ping>http://www.yacs.fr/links/trackback.php?anchor=article%3A7398</trackback:ping>
	</item>

 <item>
		<title>History of source code management in the yacs project</title>
		<link>http://www.yacs.fr/article-7025-history-of-source-code-management-in-the-yacs-project</link>
		<guid isPermaLink="true">http://www.yacs.fr/article-7025-history-of-source-code-management-in-the-yacs-project</guid>
		<description>Early days 
 Initially the project was simply uploaded in  .zip  archive files. 
CVS at SourceForge 
 Then we built a repository at SourceForge, and managed changes with TortoiseCVS. For the first time all of yacs code was exposed, and not only the content of installation archives. 
SVN at Google Code 
 On March 2008 the code repository has been moved from CVS at SourceForge to SVN at Google Code, and changed were managed with TortoiseSVN, then with svnX. SVN is far more powerful than CVS, yet we never attempted to move to true collaborative development. Merges seem to be so challenging!  ... more   </description>
		<dc:creator>Bernard Paques</dc:creator>
		<category>Tools and procedures used in the yacs project</category>
		<pubDate>Tue, 12 Oct 2010 21:37:37 GMT</pubDate>
		<comments>http://www.yacs.fr/section-527-tools-and-procedures-used-in-the-yacs-project#_discussion</comments>
		<slash:comments>0</slash:comments>
		<wfw:comment>http://www.yacs.fr/comments/post.php/article/7025</wfw:comment>
		<wfw:commentRss>http://www.yacs.fr/comments/feed.php/article/7025</wfw:commentRss>
		<trackback:ping>http://www.yacs.fr/links/trackback.php?anchor=article%3A7025</trackback:ping>
	</item>

 <item>
		<title>GIT on MSwindows</title>
		<link>http://www.yacs.fr/article-7249-git-on-mswindows</link>
		<guid isPermaLink="true">http://www.yacs.fr/article-7249-git-on-mswindows</guid>
		<description>3 exe</description>
		<dc:creator>Alexis Raimbault</dc:creator>
		<category>Tools and procedures used in the yacs project</category>
		<pubDate>Wed, 06 Oct 2010 08:43:40 GMT</pubDate>
		<comments>http://www.yacs.fr/section-527-tools-and-procedures-used-in-the-yacs-project#_discussion</comments>
		<slash:comments>2</slash:comments>
		<wfw:comment>http://www.yacs.fr/comments/post.php/article/7249</wfw:comment>
		<wfw:commentRss>http://www.yacs.fr/comments/feed.php/article/7249</wfw:commentRss>
		<trackback:ping>http://www.yacs.fr/links/trackback.php?anchor=article%3A7249</trackback:ping>
	</item>

 <item>
		<title>Putting more files in the blessed repository</title>
		<link>http://www.yacs.fr/article-7388-putting-more-files-in-the-blessed-repository</link>
		<guid isPermaLink="true">http://www.yacs.fr/article-7388-putting-more-files-in-the-blessed-repository</guid>
		<description>We are committed to expose all source files to the community</description>
		<dc:creator>Bernard Paques</dc:creator>
		<category>Announcements</category>
		<pubDate>Wed, 06 Oct 2010 08:08:53 GMT</pubDate>
		<comments>http://www.yacs.fr/section-570-announcements#_discussion</comments>
		<slash:comments>1</slash:comments>
		<wfw:comment>http://www.yacs.fr/comments/post.php/article/7388</wfw:comment>
		<wfw:commentRss>http://www.yacs.fr/comments/feed.php/article/7388</wfw:commentRss>
		<trackback:ping>http://www.yacs.fr/links/trackback.php?anchor=article%3A7388</trackback:ping>
	</item>

 <item>
		<title>Les bases Git avec SmartGit</title>
		<link>http://www.yacs.fr/article-7387-les-bases-git-avec-smartgit</link>
		<guid isPermaLink="true">http://www.yacs.fr/article-7387-les-bases-git-avec-smartgit</guid>
		<description> Pour apprendre à utiliser Git via SmartGit (sous Windows), j'ai fait l'exercice de reprendre ci-dessous le didacticiel réalisé par Alexis et consultable sur Cybermédium : http://www.cybermedium.info/article-48-utilisez-git-pour-maintenir-vos-scripts-yacs 
 Initialisation du répertoire de travail 
 Lancer SmartGit. Une fenêtre d'accueil propose de créer un nouvel arbre de travail local Git: 
  
 Sélectionner le répertoire de travail : 
  
 Confirmer l'initialisation de l'arbre de travail : 
  
 Indiquer le nom du projet géré par Git : 
   ... more   </description>
		<dc:creator>Jmarc</dc:creator>
		<category>Tools and procedures used in the yacs project</category>
		<pubDate>Wed, 06 Oct 2010 07:57:40 GMT</pubDate>
		<comments>http://www.yacs.fr/section-527-tools-and-procedures-used-in-the-yacs-project#_discussion</comments>
		<slash:comments>1</slash:comments>
		<wfw:comment>http://www.yacs.fr/comments/post.php/article/7387</wfw:comment>
		<wfw:commentRss>http://www.yacs.fr/comments/feed.php/article/7387</wfw:commentRss>
		<trackback:ping>http://www.yacs.fr/links/trackback.php?anchor=article%3A7387</trackback:ping>
	</item>

 <item>
		<title>Collaborative development models on githubs </title>
		<link>http://www.yacs.fr/article-7355-collaborative-development-models-on-githubs</link>
		<guid isPermaLink="true">http://www.yacs.fr/article-7355-collaborative-development-models-on-githubs</guid>
		<description>Quick note
 &quot;  There are two popular models of collaborative development on GitHub: 
 
 
 The Fork + Pull Model lets anyone fork an existing  repository and push changes to their personal fork without requiring  access be granted to the source repository. The changes must then be  pulled into the source repository by the project maintainer. This model  reduces the amount of friction for new contributors and is popular with  open source projects because it allows people to work independently  without upfront coordination. 
 
 
 The Shared Repository Model is more prevalent with small  teams and organizations collaborating on private projects. Everyone is  granted push access to a single shared repository and topic branches are  used to isolate changes. 
 
 
 Pull requests are especially useful in the Fork + Pull Model because they provide a way to notify project maintainers about changes in your fork. However, they're also useful in the Shared Repository Model where they're used to initiate code review and general discussion about  a set of changes before being merged into a mainline branch.  &quot;  ... more   </description>
		<dc:creator>Alexis Raimbault</dc:creator>
		<category>Announcements</category>
		<pubDate>Tue, 05 Oct 2010 20:52:54 GMT</pubDate>
		<comments>http://www.yacs.fr/section-570-announcements#_discussion</comments>
		<slash:comments>2</slash:comments>
		<wfw:comment>http://www.yacs.fr/comments/post.php/article/7355</wfw:comment>
		<wfw:commentRss>http://www.yacs.fr/comments/feed.php/article/7355</wfw:commentRss>
		<trackback:ping>http://www.yacs.fr/links/trackback.php?anchor=article%3A7355</trackback:ping>
	</item>

 <item>
		<title>Why should we move from SVN to Git?</title>
		<link>http://www.yacs.fr/article-7027-why-should-we-move-from-svn-to-git</link>
		<guid isPermaLink="true">http://www.yacs.fr/article-7027-why-should-we-move-from-svn-to-git</guid>
		<description> There are at least four reasons to use Git: 
   Linus Torwald recommends to do it in a famous Google Talk video   
   We have decided to branch development of yacs, and experts says that merging is painful with SVN   
   We want powerful developers to benefit from powerful tools to manage code at their powerful computers   
   We want to embrace parallel development on a large scale, instead of discussing &quot;who is allowed to commit?&quot;   
   
 Maybe you would like to add your own reason for using Git instead of SVN or CVS?  ... more   </description>
		<dc:creator>Bernard Paques</dc:creator>
		<category>Announcements</category>
		<pubDate>Tue, 05 Oct 2010 20:44:50 GMT</pubDate>
		<comments>http://www.yacs.fr/section-570-announcements#_discussion</comments>
		<slash:comments>2</slash:comments>
		<wfw:comment>http://www.yacs.fr/comments/post.php/article/7027</wfw:comment>
		<wfw:commentRss>http://www.yacs.fr/comments/feed.php/article/7027</wfw:commentRss>
		<trackback:ping>http://www.yacs.fr/links/trackback.php?anchor=article%3A7027</trackback:ping>
	</item>

 <item>
		<title>Where should we host our software repository?</title>
		<link>http://www.yacs.fr/article-7029-where-should-we-host-our-software-repository</link>
		<guid isPermaLink="true">http://www.yacs.fr/article-7029-where-should-we-host-our-software-repository</guid>
		<description> Some requirements: 
   ensure that the community has full control on stored content   
   be entirely based on open-source software   
   prefer open hosting over closed hosting, if possible   
   technology should allow the community to host its own repository in the future   
   ensure consistent usage across various operating systems (namely, Windows, Mac OSX and Linux)   
   be provided at no cost for the community   
   
 What else? </description>
		<dc:creator>Bernard Paques</dc:creator>
		<category>Announcements</category>
		<pubDate>Tue, 05 Oct 2010 20:41:05 GMT</pubDate>
		<comments>http://www.yacs.fr/section-570-announcements#_discussion</comments>
		<slash:comments>4</slash:comments>
		<wfw:comment>http://www.yacs.fr/comments/post.php/article/7029</wfw:comment>
		<wfw:commentRss>http://www.yacs.fr/comments/feed.php/article/7029</wfw:commentRss>
		<trackback:ping>http://www.yacs.fr/links/trackback.php?anchor=article%3A7029</trackback:ping>
	</item>

 <item>
		<title>Created yacs/yacs repository</title>
		<link>http://www.yacs.fr/article-7353-created-yacs-yacs-repository</link>
		<guid isPermaLink="true">http://www.yacs.fr/article-7353-created-yacs-yacs-repository</guid>
		<description> 
 I created the yacs acount with yacs repository, for testing purpose, and maybe it will become the official repository for yacs on github.
 
 
 http://github.com/yacs/yacs 
 
 I added Bernard (bernard357), Christophe (cbattarel) and myself (rair) as collaborator on this project. So we are able to commit in this repository 
 but the administration of this project must be done with yacs account (like adding new collaborators). This account could be shared by trusted members. 
 
 
 contributing 
 
 to contribute, everyone can register on github, and fork the project by pressing one button. 
 that will be I think the way we will contribute : Bernard, Christophe and I, will fork the yacs/yacs project, and put our public works on yacs in ours own repositories, available for test.
 
 After being tested and reviewed, jobs would be integrated in the official repo. 
  ... more   </description>
		<dc:creator>Alexis Raimbault</dc:creator>
		<category>Announcements</category>
		<pubDate>Sun, 12 Sep 2010 21:23:39 GMT</pubDate>
		<comments>http://www.yacs.fr/section-570-announcements#_discussion</comments>
		<slash:comments>1</slash:comments>
		<wfw:comment>http://www.yacs.fr/comments/post.php/article/7353</wfw:comment>
		<wfw:commentRss>http://www.yacs.fr/comments/feed.php/article/7353</wfw:commentRss>
		<trackback:ping>http://www.yacs.fr/links/trackback.php?anchor=article%3A7353</trackback:ping>
	</item>

 <item>
		<title>proposal of a policy for managing yacs sources with git</title>
		<link>http://www.yacs.fr/article-7282-proposal-of-a-policy-for-managing-yacs-sources-with-git</link>
		<guid isPermaLink="true">http://www.yacs.fr/article-7282-proposal-of-a-policy-for-managing-yacs-sources-with-git</guid>
		<description> where to host ? 
 what branches ? 
 what workflow ? 
   </description>
		<dc:creator>Alexis Raimbault</dc:creator>
		<category>Announcements</category>
		<pubDate>Wed, 30 Jun 2010 15:22:19 GMT</pubDate>
		<comments>http://www.yacs.fr/section-570-announcements#_discussion</comments>
		<slash:comments>0</slash:comments>
		<wfw:comment>http://www.yacs.fr/comments/post.php/article/7282</wfw:comment>
		<wfw:commentRss>http://www.yacs.fr/comments/feed.php/article/7282</wfw:commentRss>
		<trackback:ping>http://www.yacs.fr/links/trackback.php?anchor=article%3A7282</trackback:ping>
	</item>

 <item>
		<title>gitignore file for indexing a running yacs server</title>
		<link>http://www.yacs.fr/article-7263-gitignore-file-for-indexing-a-running-yacs-server</link>
		<guid isPermaLink="true">http://www.yacs.fr/article-7263-gitignore-file-for-indexing-a-running-yacs-server</guid>
		<description>proposal of a set of rules for this mecanism</description>
		<dc:creator>Alexis Raimbault</dc:creator>
		<category>Tools and procedures used in the yacs project</category>
		<pubDate>Wed, 23 Jun 2010 13:53:14 GMT</pubDate>
		<comments>http://www.yacs.fr/section-527-tools-and-procedures-used-in-the-yacs-project#_discussion</comments>
		<slash:comments>0</slash:comments>
		<wfw:comment>http://www.yacs.fr/comments/post.php/article/7263</wfw:comment>
		<wfw:commentRss>http://www.yacs.fr/comments/feed.php/article/7263</wfw:commentRss>
		<trackback:ping>http://www.yacs.fr/links/trackback.php?anchor=article%3A7263</trackback:ping>
	</item>

 <item>
		<title>  Utilisez GIT pour maintenir vos scripts YACS</title>
		<link>http://www.yacs.fr/article-7214-tutorial-utilisez-git-pour-maintenir-vos-scripts-yacs</link>
		<guid isPermaLink="true">http://www.yacs.fr/article-7214-tutorial-utilisez-git-pour-maintenir-vos-scripts-yacs</guid>
		<description>Un système de gestion de version appliqué à yacs, chez soi</description>
		<dc:creator>Alexis Raimbault</dc:creator>
		<category>Tools and procedures used in the yacs project</category>
		<pubDate>Wed, 23 Jun 2010 13:31:54 GMT</pubDate>
		<comments>http://www.yacs.fr/section-527-tools-and-procedures-used-in-the-yacs-project#_discussion</comments>
		<slash:comments>1</slash:comments>
		<wfw:comment>http://www.yacs.fr/comments/post.php/article/7214</wfw:comment>
		<wfw:commentRss>http://www.yacs.fr/comments/feed.php/article/7214</wfw:commentRss>
		<trackback:ping>http://www.yacs.fr/links/trackback.php?anchor=article%3A7214</trackback:ping>
	</item>

 <item>
		<title>2 good websites for learning GIT</title>
		<link>http://www.yacs.fr/article-7251-2-good-websites-for-learning-git</link>
		<guid isPermaLink="true">http://www.yacs.fr/article-7251-2-good-websites-for-learning-git</guid>
		<description>1 for beginners and the other for more advanced purpose</description>
		<dc:creator>Alexis Raimbault</dc:creator>
		<category>Discussion board</category>
		<pubDate>Wed, 16 Jun 2010 20:10:44 GMT</pubDate>
		<comments>http://www.yacs.fr/section-523-discussion-board#_discussion</comments>
		<slash:comments>0</slash:comments>
		<wfw:comment>http://www.yacs.fr/comments/post.php/article/7251</wfw:comment>
		<wfw:commentRss>http://www.yacs.fr/comments/feed.php/article/7251</wfw:commentRss>
		<trackback:ping>http://www.yacs.fr/links/trackback.php?anchor=article%3A7251</trackback:ping>
	</item>

 <item>
		<title>Everyday GIT With 20 Commands Or So</title>
		<link>http://www.yacs.fr/article-7250-everyday-git-with-20-commands-or-so</link>
		<guid isPermaLink="true">http://www.yacs.fr/article-7250-everyday-git-with-20-commands-or-so</guid>
		<description> a summary for using git : 
 http://www.kernel.org/pub/software/scm/git/docs/everyday.html </description>
		<dc:creator>Alexis Raimbault</dc:creator>
		<category>Discussion board</category>
		<pubDate>Wed, 16 Jun 2010 09:27:33 GMT</pubDate>
		<comments>http://www.yacs.fr/section-523-discussion-board#_discussion</comments>
		<slash:comments>0</slash:comments>
		<wfw:comment>http://www.yacs.fr/comments/post.php/article/7250</wfw:comment>
		<wfw:commentRss>http://www.yacs.fr/comments/feed.php/article/7250</wfw:commentRss>
		<trackback:ping>http://www.yacs.fr/links/trackback.php?anchor=article%3A7250</trackback:ping>
	</item>

 <item>
		<title>Choosing a workflow</title>
		<link>http://www.yacs.fr/article-7147-choosing-a-workflow</link>
		<guid isPermaLink="true">http://www.yacs.fr/article-7147-choosing-a-workflow</guid>
		<description> there are differents way to collaborate with GIT. We have to choose one. 
 read http://www.kernel.org/pub/soft...tworkflows.html </description>
		<dc:creator>Alexis Raimbault</dc:creator>
		<category>Announcements</category>
		<pubDate>Mon, 07 Jun 2010 20:07:07 GMT</pubDate>
		<comments>http://www.yacs.fr/section-570-announcements#_discussion</comments>
		<slash:comments>3</slash:comments>
		<wfw:comment>http://www.yacs.fr/comments/post.php/article/7147</wfw:comment>
		<wfw:commentRss>http://www.yacs.fr/comments/feed.php/article/7147</wfw:commentRss>
		<trackback:ping>http://www.yacs.fr/links/trackback.php?anchor=article%3A7147</trackback:ping>
	</item>

</channel>
</rss>
