d606c30686
If this file is generated regularly, it becomes easier for translators to keep up with changes to the source code. (Or, at least changes with accompanying gettext calls).
This was generated with:
# for i in `git grep --name-only 'gettext' | grep -v 'pot$'` ; do
# xgettext -j -o ./src/share/locale/en/LC_MESSAGES/OPNsense.pot "${i}"
# done
Signed-off-by: Isaac (.ike) Levy <ike@blackskyresearch.net>
core
OPNsense GUI and system management
The OPNsense® project invites developers to start developing with OPNsense. For your own purpose or even better to join us in creating the best open source firewall available.
The build process has been redesigned to make it lot more straightforward and easy for developers to build OPNsense. Being able to get the sources and build it yourself is one of the key factors of open source software.
Although a lot of the code is still legacy, we try to publish the direction we're taking on our wiki page. The main outline of the new codebase is available there at https://wiki.opnsense.org/index.php/Develop:Architecture Our aim is to gradually evolve to a new codebase instead of using a big bang approach into something new.
Build tools
To create working software like OPNsense you need the sources and the tools to build it. The build tools for OPNsense are freely available. No strings attached.
Notes on how to build OPNsense can be found in the tools repository at https://github.com/opnsense/tools
Contribute
You can contribute to the project in many ways, like testing functionality, sending in bug reports or send us pull requests via github. Any help is always very welcome!
License
OPNsense is and will be available with the simple 2-clause BSD license (http://opensource.org/licenses/BSD-2-Clause). Every contribution made to the project should be available under the same conditions.