<h3>How to subscribe?</h3>
-<p>The easiest way to subscribe to the list is through the web interface at <a href="http://lists.samba.org/">http://lists.samba.org/</a>. Please read this note on <b><a href="/samba/ml-etiquette.html">mailing list etiquette</a></b> before posting.</p>
+<p>The easiest way to subscribe to the list is through the web interface at <a href="https://lists.samba.org/">https://lists.samba.org/</a>. Please read this note on <b><a href="/samba/ml-etiquette.html">mailing list etiquette</a></b> before posting.</p>
<p>If you do not have web access, you may subscribe over email by sending a blank email to <i>listname</i><tt>-request@lists.samba.org</tt> with the word 'help' in the subject line.</p>
<th>Name</th><th>Description</th>
</tr>
<tr>
- <td><a href="http://lists.samba.org/pipermail/samba/">samba</a></td>
+ <td><a href="https://lists.samba.org/pipermail/samba/">samba</a></td>
<td> The Samba SMB fileserver</td>
</tr>
<tr>
- <td><a href="http://lists.samba.org/pipermail/samba-announce/">samba-announce</a></td>
+ <td><a href="https://lists.samba.org/pipermail/samba-announce/">samba-announce</a></td>
<td>Samba Announcements</td>
</tr>
<tr>
- <td><a href="http://lists.samba.org/pipermail/samba-vms/">samba-vms</a></td>
+ <td><a href="https://lists.samba.org/pipermail/samba-vms/">samba-vms</a></td>
<td>Samba for the VMS operating system</td>
</tr>
<tr>
- <td><a href="http://lists.samba.org/pipermail/samba-cvs/">samba-cvs</a></td>
+ <td><a href="https://lists.samba.org/pipermail/samba-cvs/">samba-cvs</a></td>
<td>Samba CVS, Subversion and Git commit messages</td>
</tr>
<tr>
- <td><a href="http://lists.samba.org/pipermail/samba-docs/">samba-docs</a></td>
+ <td><a href="https://lists.samba.org/pipermail/samba-docs/">samba-docs</a></td>
<td><em>Discontinued </em>list about Samba documentation</td>
</tr>
<tr>
- <td><a href="http://lists.samba.org/pipermail/samba-binaries/">samba-binaries</a></td>
+ <td><a href="https://lists.samba.org/pipermail/samba-binaries/">samba-binaries</a></td>
<td><em>Discontinued</em> Developer discussions about Samba binary distributions</td>
</tr>
<tr>
- <td><a href="http://lists.samba.org/pipermail/samba-technical/">samba-technical</a></td>
+ <td><a href="https://lists.samba.org/pipermail/samba-technical/">samba-technical</a></td>
<td>Developer discussions about Samba internals</td>
</tr>
<tr>
- <td><a href="http://lists.samba.org/pipermail/samba-ntdom/">samba-ntdom</a></td>
+ <td><a href="https://lists.samba.org/pipermail/samba-ntdom/">samba-ntdom</a></td>
<td><em>Discontinued</em> list about NT Domain support</td>
</tr>
<tr>
- <td><a href="http://lists.samba.org/pipermail/mirrors/">mirrors</a></td>
+ <td><a href="https://lists.samba.org/pipermail/mirrors/">mirrors</a></td>
<td>for sites mirroring samba.org</td>
</tr>
</table>
<h3>Coding Projects</h3>
-<p>All coding work needs to be coordinated with a <a href="/samba/team/">Samba Team member</a>, at the very least, on the <a href="http://lists.samba.org/listinfo/samba-technical">samba-technical mailing list</a> or on the #samba-technical IRC channel (irc.freenode.net). Don't just start coding and expect patches to automatically be integrated in. Obviously, projects by specific team members -- winbind, for example -- need to be coordinated with those team members in charge.</p>
+<p>All coding work needs to be coordinated with a <a href="/samba/team/">Samba Team member</a>, at the very least, on the <a href="https://lists.samba.org/listinfo/samba-technical">samba-technical mailing list</a> or on the #samba-technical IRC channel (irc.freenode.net). Don't just start coding and expect patches to automatically be integrated in. Obviously, projects by specific team members -- winbind, for example -- need to be coordinated with those team members in charge.</p>
<p>For those without Git write access (non-team members), patches should be
incremental and in the form of context diffs (attached diff -u output or better
<p>If you want to code, you should know how to get the source branches via anonymous Git. See our <a href="http://wiki.samba.org/index.php/Using_Git_for_Samba_Development">Git instructions</a> for details.</p>
-<p>Anyone interested in actively participating in Samba development probably should also subscribe to the <a href="http://lists.samba.org/listinfo/samba-cvs">samba-cvs mailing list</a> in order to follow Git commit log messages.</p>
+<p>Anyone interested in actively participating in Samba development probably should also subscribe to the <a href="https://lists.samba.org/listinfo/samba-cvs">samba-cvs mailing list</a> in order to follow Git commit log messages.</p>
<ul>
<li>(Priority - MEDIUM, Status - ACTIVE) Implement ACL support for currently unsupported platforms.</li>
<p>Please coordinate all development efforts on the
<a href="mailto:samba-technical@samba.org">samba-technical</a> mailing
list. For more information about the list, or to join the list, go to the
-<a href="http://lists.samba.org/mailman/listinfo/samba-technical">samba technical mailing list</a>
+<a href="https://lists.samba.org/mailman/listinfo/samba-technical">samba technical mailing list</a>
page. The main samba development channel on IRC is <i>#samba-technical</i>, server <i>irc.freenode.net</i>.
Please don't ask user questions in this channel (users see <i>#samba</i>).
Channel logs are available <a href="http://irclog.samba.org/">here</a>.</p>