Hi Edward.
I am happy, that you think it is a good idea.
1) Porting/safety download of the wiki
There will be two things you need to safety download.
From the FTP and the MYSQL database.
The FTP contains the LocalSettings.php, which provide the settings for the wiki
The FTP also contain the images that is uploaded to the wiki.
The wiki entries are written to a MYSQL database, which is the important one to
backup.
For safety reasons, I suggest a model where you get the passwords to the FTP and the
MYSQL database. If you then can make a backup script that on a weekly/daily basis
make a dump of the FTP and the MYSQL database, and make that available external,
I think that is the best model. I would be insecure about sharing the passwords for other
than trusted people.
I see that it is working, but there is a DNS problem, which prevent user creation,
log in/out and editing.
According to my brother you need to tweak your DNS provider. You have
record and point to IP 217.116.232.203.
Let's take this off-list.
3) Scripts for the wiki
I was part of migrating all the scripts at the pymolwiki into a shared pymol-script-repo
at Github. The advantages are many. Read here for reference.
I wrote all these entries at the pymol wiki.
For the wiki, Thomas Holder made a "wiki box". (A dynamic page thing)
One just write in the wiki entry:
{{Infobox script-repo
|type = script
|filename = propka.py
|author = [[User:Tlinnet|Troels E. Linnet]]
|license = BSD
}}
You can for example see it here:
If one in the top-right click 'propka.py', you are
redirected to the "raw" view at github.
There is color and raw view available
I suggest we setup up a similar system.
Creating an "organisation" at at gihub, for the merged scripts.
Developers can then fork, modify, and make a "pull request" from their
repo to the organisation repo.
Note, that the traffic is "quite" low.
But one could make tutorials, analysing scripts, matplot lib plotting.
Etc etc.
The good thing with this, is that this will provide a "fast track" development for
users. Making it more "fun" for new NMR people, with script background.
Users do not need to "care" to much about backwards compatibility.
If the wiki pages have a large hit-rate, the functionality could then be considered
to be official implemented in the relax source code.
4) Graphic icon
Sure ! I already stole one icon from the repo. Can you point out which one?
With the FTP access, you can also do it ourself. :-)
Upload it to: /skins/common/images
And modify LocalSettings.php at the entry:
$wgLogo = "$wgStylePath/common/images/ulysses.png";
5) Name: relax
I have modified the name, and will try to remember forwards.
Note, that you can create a user, and do it your self. :-)
I suggest you create two users.
I will grant one admin rights, and in the daily, I suggest logging
in with the "plain" user, to prevent accidentally clicking one of the "power" buttons.
6) Organisation.
You can change the title/pages/categories, as you find fit. :-)
As for organisation of pages/categories, I agree that we should have that in mind.
But before we/I use to much energy, I think we should wait a "little" to let the information
grow. Then we can take a "cleaning/organisation" round.
I for example, will only cover material/tutorials/install instructions that is directly usable for
"our" group, which is dynamics in us time scale. I "hope" that groups which will benefit
for detailed instructions on their type of analysis, will provide the entries needed.
7) License
The License is in LocalSettings.php
## For attaching licensing metadata to pages, and displaying an
## appropriate copyright notice / icon. GNU Free Documentation
## License and Creative Commons licenses are supported so far.
$wgRightsPage = ""; # Set to the title of a wiki page that describes your license/copyright
$wgRightsText = "Creative Commons Attribution Share Alike";
$wgRightsIcon = "{$wgStylePath}/common/images/cc-by-sa.png";
I have made a License page, and protected it for admins only modification:
I made these changes
$wgRightsPage = "License"; # Set to the title of a wiki page that describes your license/copyright
$wgRightsText = "GNU General Public License, version 3 (GPL-3.0)";
$wgRightsIcon = "{$wgStylePath}/common/images/62px31px-GNU_General_Public_License_3_Logo.png";
Best
2013/6/24 Edward d'Auvergne
<edward@xxxxxxxxxxxxx>
Hi Troels,
This is a really good idea! I would have started this a long time ago
but, because the Gna! infrastructure does not support PHP, a wiki was
never possible. It would be possible to set this up but for an open
source project we will have to first make the wiki migratable.
Therefore I would suggest first writing a script to be added to the
devel_scripts directory which will make a mirror copy of the backend
of the wiki. That way a subset of the relax developers could set up a
cronjob with this script, just as is down with the relax subversion
repository and the relax mailing lists (see the backup_repository and
backup_mailing_lists scripts). This backup would need to be
sufficient to set up the wiki on another server. This is simply part
of the strategy for having all parts of relax survive forever,
independent of who comes and goes from the project (including myself).
The URL http://wiki.nmr-relax.com/ is a good idea. I have paid for
the http://www.nmr-relax.com/ domain name myself, through Godaddy, and
I am able to set up this subdomain. I will set this up for testing
but to be permanent the backup script for easy migration will be
needed. Ok, it is now activated.
I also have a few suggestions/questions for the wiki design:
- I was wondering if you thought it would be possible for users to
upload scripts to such a wiki? If so, how would this be implemented?
- You can use one of the relax icons with a transparent background
from the graphics/ directory rather than the current one with a white
background.
- The project is called simply 'relax' and not 'NMR relax'. The
reason I had to use http://www.nmr-relax.com is that the relax.com
domain name was not available. I have used it in a few other places,
again because the name 'relax' was not available (for example at
https://www.ohloh.net/p/nmr-relax and
http://freecode.com/projects/nmr-relax).
- The title will need modification as relax supports almost all NMR
dynamics analysis types. Relaxation dispersion is only a small subset
of what relax can do. Therefore it might be good to have an
organisation around the different analysis types.
- We should discuss the licence for the content. Would it be possible
to use the same licence as the relax website
(http://www.nmr-relax.com/fdl.html)?
Cheers,
Edward
On 24 June 2013 13:16, Troels Emtekær Linnet <
tlinnet@xxxxxxxxx> wrote:
> Dear relax developers.
>
> I felt the need to create a wiki, to document my own progress into the relax
> use.
>
> Much in the same way the pymol wiki serves an excellent resource of
> information.
>
> I was noting information down in our internal lab wiki about relax, but
> found it more useful if more
> users could take advantage of this information.
>
> At the moment, it is located at my brothers domain:
>
http://nmr-relax.kimlinnet.dk
>
> I hope when it has matured, and after a little discussion of format, it can
> be moved to:
>
http://www.wiki.nmr-relax.com/
>
> My most strong motivation, was that I last year made a tutorial at the pymol
> wiki, for
> a course in biochemistry. Returning the following year with teaching in the
> same course,
> I noticed over 8000 views. Not bad.
>
> I see a wiki as an excellent possibility for "quickly" noting and improving
> information, which is
> not readily available in the manual or other "places"
>
> I try to make links to the relax online manual and API, and then improving
> with contents I myself
> would find useful, or that I find answers to.
>
> If some pages has a large "hit-rate" it could be considered valuable to
> "rewrite / port" the information into
> the relax manual? And with the text "kind-of" available, it should not take
> to long time to "copy/paste/modify" it.
>
> Best
> Troels Emtekær Linnet
> PhD student
> SBiNLab, Copenhagen
>
> relax (http://www.nmr-relax.com)
>
> This is the relax-devel mailing list
> relax-devel@xxxxxxx
>
> To unsubscribe from this list, get a password
> reminder, or change your subscription options,
> visit the list information page at
> https://mail.gna.org/listinfo/relax-devel
>
Re: Creation of a relax wiki