Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


Hi Anders,

Am 07.02.2012 17:00, schrieb Anders Holbøll:
I wanted to have at look at the source code for the website. But I had a
little trouble finding it. Perhaps a little information should be added
to the wiki or made a little more obvious if it exists.

why?


As far as I can see the code for the CMS is at
https://github.com/tdf/cms-code/ , but it seems that this repository is
not quite up to date

It is updated regularly when the changes applied to the live system work
well and we find enough spare time besides other jobs.


I fixed these locally.
It would be nice if the repository could be updated.

Well feel free to join the website time to improve the situation and the
repos.


It seems that /cms-code/themes/ should be a submodule importing
/cms-themes/ or at least it should be documented what to do.

No it is just another repo containing the themes.
You are also welcome to improve the documentation.   :-)


The file /cms-code/mysite/_config.php seems to have been left out of the
repository because it contains the database-password. But that makes it
harder for a new developer to setup the site 

I do not see the need to publish the configuration for it is mainly
important for people involved and less for attempts to clone our site
for whatever purpose.


since the file probably
also contains a line like "Object::add_extension('SiteTree',
'Translatable');" that isn't in the standard silverstripe _config.

like many other patches applied


Couldn't the password therefore be put in another file, that could be
excluded from git and included in _config.php or just named e.g.
"/cms-code/mysite.secret/_config.php" so silverstripe will find it. The
"install.php" should probably also be included, although I am not sure
it turned out to be needed.

What for? Where do you publish your passwords?  ;-)
Again, if you want to work on the site why not join the team?


Somewhat unrelated, but on the list of "International sites" couldn't
the sites that are not yet ready (those with no link, and also "Lao") be
removed? It doesn't seem very helpfull to list sites that doesn't yet
exist. Also the domain-name-column could probably be removed, since it
probably isn't important/informative to normal users.

You might have recognized that we are an open source community with
members working in their spare time.
Subsites have been requested and set up, still the content has to be
done by the respective language teams in their spare time.

To stress it once more, feel welcome to join the team and discuss your
points of view with us.


Also it seems to me that this file (and the corresponding "rpm" and
"x86_64" files, in total 4 files) are in the wrong folder, since they
are 3.4 release candidate files in the stable 3.3.4 folder.
http://download.documentfoundation.org/libreoffice/stable/3.3.4/deb/x86/LibO-SDK_3.4rc3_Linux_x86_install-deb_en-US.tar.gz

The final RC just gets renamed for releases which sometimes does not
apply to SDKs, the content would not be different.

Cheers
Erich

-- 
Unsubscribe instructions: E-mail to website+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/website/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: 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.