\subsection{How to contribute}
-OpenWrt is constantly being improved. We'd like as many people to contribute
+LibreWRT is constantly being improved. We'd like as many people to contribute
to this as we can get. If you find a change useful, by all means try to get
-it incorporated into the project. This should improve OpenWrt and it should
+it incorporated into the project. This should improve LibreWRT and it should
help carry your changes forward into future versions
This section tries to lay out a procedure to enable people to submit patches
\begin{itemize}
\item google to find things related to your problem
- \item Mailing lists: \href{http://lists.openwrt.org/}{http://lists.openwrt.org/}
- \item Wiki: check the wiki: \href{http://wiki.openwrt.org/OpenWrtDocs}{http://wiki.openwrt.org/OpenWrtDocs}
- \item Forum: \href{http://forum.openwrt.org/}{http://forum.openwrt.org/}
- \item IRC: \texttt{irc.freenode.net}, channels \texttt{\#openwrt} and
- \texttt{\#openwrt-devel}
- \item TRAC: \href{https://dev.openwrt.org/}{https://dev.openwrt.org/} the issue/bug/change tracking system
+ \item Mailing lists: \href{http://lists.librewrt.org/}{http://lists.librewrt.org/}
+ \item Wiki: check the wiki: \href{http://librewrt.org/}{http://librewrt.org/}
+ \item IRC: \texttt{irc.freenode.net}, channels \texttt{\#librewrt}
\end{itemize}
It is often best to document what you are doing before you do it. The process
\begin{enumerate}
\item Use git or svn to create a patch. Creating patches manually with
\textit{diff -urN} also works, but is usually unnecessary.
- \item Send a mail to openwrt-devel@lists.openwrt.org with the following contents:
+ \item Send a mail to dev@lists.librewrt.org with the following contents:
\begin{enumerate}
\item \texttt{[PATCH] <short description>} in the Subject, followed by:
\item (optional) a longer description of your patch in the message body