Hi Florian, *
Am 29.01.2013 10:38, schrieb Florian Effenberger:
Niklas Johansson wrote on 2013-01-28 20:19:
the way our website interacts with git is unfortunately one of the
major obstacles for me, being totally undocumented.
Erich, do you have more insight here, where to change what in git and
where to push/pull?
Ok, here is my afaik "insight":
Either you have a local checkout of the repository or use the
webinterface to apply changes directly to the respective files. wsadmin
may also use git bash at kermit but I didn't do that yet.
Following this link
you get a view of the file and an 'Edit' button right on top.
So you may apply changes there, comment and commit in one instance.
Git will write your changes into the History next to Edit.
People who lack permissions to do so may send a pull-request email via
git once they committed a patch.
Usually changes find their way into git after they have proven to work,
and not all the files are in git like e.g. _config ;)
Translations of the DownloadSimplePage don't need to prove anything, so
it looks like Rimas just committed all the changes he was aware of.
Except the donate pages there are no other content translations
available via lang_files afaik.
I think you've applied all translations there manually that time, but I
don't even know where. Do not see them in git either.
Ohter locations, except https://github.com/tdf/cms-themes maybe, are of
lesser public interest imo, concerning cms functionality mainly.
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy