TikiFest2009-London-2-GSOC

Between Open Translation Tools 2009, Amsterdam, The Netherlands (22-23-24 June) and the Tenth Libre Software Meeting / 10e Rencontres Mondiales du Logiciel Libre (RMLL), Nantes, France (7-8-9-10-11 July)

Some Tiki community will probably participate to the two other events (Rodrigo, Marc, Olaf, etc.)

It is true, all the cheap flights only get near to London!

Return tickets are for both ways there and back.

From Gatwick Airport you can get a train in to London,

• There is a bus/coach 1 every hour for 13.50 GBP each return, it takes 1.5 hours if the traffic is good.
• The cheapest train is with "First Capital Connect" 17.00 GBP each return (this goes to London Bridge station). 3-4 and hour and it takes 30 mins.
• There is another service "Gatwick Express" which is 28.80 GBP each return, and is only 3 minutes faster! (this goes to Victoria station). It is a very reliable, it is best if you can afford it and have limited time.

Both trains get you on to the tube lines so it is easy from there on. So ask for "London Bridge" station not just "London" they will sell you an express ticket if you do!

From Luton

• Get a short shuttle bus (5 mins) to the train station then a train "First Capital Connect" for 22.50 GBP (This goes to St Pancras station) 6 times an hour and it take 35 mins.
• Or a coach direct from the airport 14.50 GBP return each, but it takes 75 miuntes if the traffic is good. This goes to Victoria station)

From Stanstead

• The train is 26.80 GBP each return the are 4 an hour and you get to Liverpool Street station.
• The coach takes at least 60 mins but it can get badly delayed by traffic so leave lots of time on the way back to the airport. It is only 14 GBP each return.

So welcome to the problems of having 4 main airports and competition on the trains!

Once you are on the Tube network it is easy to get around.

The Tube/Bus network you will need to get a "Oyster" card each. This requires a 3 GBP deposit which you get back as you leave. Then you put money on it and use it for all your travel. 1 GBP for each bus ride and 6.50 GBP for the whole day on the tube. Without this card it is twice as expensive! The card is clever and will charge you less if you don't need to pay for the whole day. You can get a card at any Tube station ticket office.

See more about this card at http://www.tfl.gov.uk/tickets/oysteronline/2732.aspx

This is about the features admin pages. This is not about the Admin Home section, which is a mess, but it's our mess, so it needs to be correted, but it is not as urgent. The features admin pages are the pages which our customers use to administer the features we activate for them. The UI of these pages ranges from horrible to good, and the lack of consistency is an issue all by itself. These reflect directly on people's opinion on Tiki, and we have to do something about it as soon as possible.
As an illustration, compare :

• Edit blog
• Edit forums
• Admin users

Everyone present (and remote) agrees that this is not good and more consistency and usability would be welcome. This means we have to agree on what would be a good admin interface.
We compare two interfaces which are actually usable :

1. First approach: Admin trackers

tiki-admin_trackers.php
Plus: Nicer.
Minus: Not everything can be seen. More clicking.

1. Second approach: myTiki admin contacts

tiki-contacts.php
Plus: It's just an improvement on what we have (Forums).
Minus: It's not obvious what does what, and usability is lost on new users.

Opinions

It seems that the admin trackers approach (aka first approach) would give the best results but give more work. Also, most people present feel the workload is more than they can spare.
Since PKdille (absent) seems to have given it some thought and is willing to start working on implementing the first approach (like he already did for titles, search boxes, buttons), everybody agrees to encourage him and also maybe give him a hand when possible.

Work to do

1.1.1.1.1.1. We should merge files like

• tiki-admin_forums.php
• tiki-forums.php

Into a single tiki-forums.php which displays appropriate tabs.
This way: less files, less duplicated code.

1.1.1.1.1.2. Creation of appropriate smarty tags

PKdille is currently working on {tabset} and {tab}. At first, these would control display of tabs with no change in functionality.

1.1.1.1.1.3. Time scale

This would happen in trunk.
It is unlikely to be finished for 4.0, but starting with the major features will still make it great.

This was more of a conversation than a presentation (nothing was actually shown).
Wysiwyg was introduced by CoE by integrating FCKeditor (Nyloth), contracting FCK for fixing a list of 20 bugs, helping integrate it more (Sept). CoE is far from using it on all its Tiki sites.
The general consensus is, it is not yet production-ready. A lot of people present selling Tiki consultancy agree on this.
There is some discussion on the relative merits of FCKeditor and TinyMCE. It seems that one or the other is ahead, depending on releases. The consensus is that switching to tinyMCE did not seem to be a good move, as it is not consistenly better, and we would waste our FCKeditor experience.
Sept and Nyloth have reached the conclusion that storing HTML makes things easy at first, but make complicated issues unsolvable. So Sept has started a new FCKeditor integration based of the FCKeditor fork the FCKeditor project made for Mediawiki. This version stores Tiki syntax.
This has advantages such as allowing switching from Tikisyntax to Wysiwyg and back.
This is a different discussion from allowing HTML code in Tikisyntax pages. It would still be optionally allowed for those who need it just like now. The discussion is only about the page storage format.
What to do about CKeditor 3 was not decided (we use FCKeditor 2), and needs to be discussed among involved developpers.
This work is pretty muc advanced in COE experimental branch. Any interested developpers are welcome in COE branch for wysiwyg improvement work, and contact Sept for discussing the relevant issues. The name of the branch is not meant to refrain anyone from using and improving the branch.

Check out the recent talk: