<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=WordSection1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Jeremy,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Since you already manage an open source project would you be
available to setup and manage an open source public repository for live555. We
could commit the sources as Ross release them since they are of public domain. I
could offer some help if you want. Ross would only need to setup an URL link in
the FAQ section for those people that want an history browsing of the changes
for whatever reason.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Guy<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
live-devel-bounces@ns.live555.com [mailto:live-devel-bounces@ns.live555.com] <b>On
Behalf Of </b>Jeremy Noring<br>
<b>Sent:</b> Thursday, June 24, 2010 11:02<br>
<b>To:</b> LIVE555 Streaming Media - development & use<br>
<b>Subject:</b> Re: [Live-devel] How to contribute code?<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>On Mon, Jun 21, 2010 at 7:50 PM, Ross Finlayson <<a
href="mailto:finlayson@live555.com">finlayson@live555.com</a>> wrote:<o:p></o:p></p>
<div>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-right:0in'>
<p class=MsoNormal>I don't use any revision control system myself. When
I'm developing this code, I use exactly two commands: "emacs" and
"make".<br>
<br>
Each source code release - in "tar.gz" form - is less than 500 kBytes
in size. These days, that's not a significant amount of data to download
in order to get the latest revision, and any bandwidth savings obtained by
downloading from a revision control system instead would be insignificant.
And people should not be using any version of the code other than the
latest one, because that's all that we support.<o:p></o:p></p>
</blockquote>
<div>
<p class=MsoNormal><br>
It's not about bandwidth, it's about having a clear history of all changes made
to the project, and when. It is extraordinarily difficult to isolate
regression without this.<br>
<o:p></o:p></p>
</div>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-right:0in'>
<p class=MsoNormal><br>
I suspect that the real reason why some people want to use a revision control
system is that they want to easily update to the latest version of the code
after they've made custom modifications to it (i.e., without losing their
modifications). I'm sorry, but this is something that I explicitly want to
discourage. People *should not* be making modifications to the released
"LIVE555 Streaming Media" code (i.e., inside the "live"
directory). Instead, they should be leaving that directory as it is, and
instead putting their own code in a separate directory (using subclassing, if
necessary).<o:p></o:p></p>
</blockquote>
<div>
<p class=MsoNormal><br>
This is simply not true--I do not want source control so I can "easily
update to the latest version of the code." I want it so I can easily
have a history of all changes made, readily available diff files, and an easy
way to see when changes have been made.<br>
<br>
Furthermore, most programmers *refuse* to use trunk (this is considered
extraordinarily unwise by every decent program I know), which is basically the
policy you're advocating. The open source project I manage has detailed
download statistics, and the results are clear: people prefer sanctioned
releases as opposed to trunk. So I'm going to have to disagree with you;
I think your hypothesis here is flat-out wrong.<br>
<o:p></o:p></p>
</div>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-right:0in'>
<p class=MsoNormal>If there are parts of the code that make it difficult for
people to customize via subclassing - e.g., some class members that should be
"protected:" instead of "private:", then please let us
know.<o:p></o:p></p>
</blockquote>
<div>
<p class=MsoNormal><br>
Has absolutely nothing to do with this. It's more like, the only way I
can get a diff view of the changes made to the project is to cache away the
various releases you put out on a bi-monthly basis into my source control, so I
can do a compare.<br>
<br>
I don't expect you to find these arguments compelling, and that's fine--I'll
continue to cache away versions of the library so I can roll back to work
around regression introduced in subsequent releases.<o:p></o:p></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
</body>
</html>