TikiFest is a tradition in the TikiWiki community. A TikiFest is when there is a meeting between at least 2 TikiWiki contributors that don't meet usually. This is an occasion usually for drinking adult beverages, getting laptops out and coding wildly in group sessions, discussing about wiki technology and culture, etc. depending the mood and context. It is a great opportunity for Tiki users and Tiki power users to meet some of the developers and learn more stuff 😀
When
July 9-10-11-12-13 2008 (It's official!)
A few days after RMLL 2008
Participants
Confirmed to be in person at Strasbourg
Pascal Kustner (pkdille) local organizer
Patrice Weber (local)
Stéphane (sept_7) (local)
Jyhem (Jean-Marc) (local)
Marc Laporte arrives Tuesday July 8th 14h, leaves Monday July 14th 15h
Louis-Philippe Huberdeau arrives July 7th at 10h, leaves Monday July 14th 15h
Patrick Allard arrives July 7th at 10h, leaves Monday July 14th 15h
Nelson Ko arrives July 9th in the afternoon, leaves Monday July 14th
Alexander Mette
arrives on 2008-07-09 at 1413 local time (GMT!?) at the main train station
leaves on 2008-07-13 at 1745 local time (GMT!?) from the main train station
luci arrives by car on July 9th, and leaves on the 11th
Franck Martin "will be in Strasbourg 9 and 10 have to leave on 11"
Low hanging fruits for Yslow? incremental things can be done - js compressing, css.
Merge Mozilla patches.
Tiki Core Project (nyloth)
TikiCore
Priority is to re-organize core libs like tikilib.php. This will be done in a way that is backward compatible at first, i.e. the current libs will remain a wrapper for the new lib/core/lib.php. The aim is to provide a more stable, more readable, and better documented core. It should also make the creation of a lightweight API to these functions easily (the lightweight API will be gradually incrementally added on a needs-basis -> the aim is not to architecture a framework but to really focus on making our lives or way of calling these libs easier -> i.e. incremental approach vs. design and build approach).
Reminder: main scripts should not call sql directly.
Unit tests for TikiCore
We need tests - figure out a way to do this at the same time we do this TIkiCore. new TikiCore should be progressively introduced to ensure proper testing framework in in first.
Documented API
Document existing API first --- light API around it will be nice to have.
Smarty functions and blocks to be used in every templates (nyloth)
propagate smarty plugins
Category permissions (what should it do?, what is a bug?)
Revamp perms (and especially for category perms) + perms through tikiobjects discussion
CRM
Workspaces
Security Dashboard presentation
Staging and approval (nkoth)
Prochain TikiFest
Distant participation agenda
(suggest items and add you name next to it if you are interested that this is addressed by the distant participants, as much as they are skilled to and willing to do it)
Done
Linking a tracker to the registration process in tw.o, so that new users in tw.o can decide to join TW Community, beyond being simply registered users at tw.o. (See more information at WhoWhat page):
In favor: xavi, marclaporte
Offering to work on that: xavi
Comments:
http://tikiwiki.org/tiki-register.php allows chosing from plain registered or "TwCommunity" group. If TwCommunity group is chosen, and simple tracker8 is shown for the user to fill it in: a simple checkbox is shown.
Related bugs to be fixed yet:
compulsory checkbox needs to be ensured that it's working (it was not before). See bug report.
some weird duplication of the static text field is shown below.
how to add a tracker on 1.10 to request more information from users at registration time. Rick and Xavi
http://doc.tiki.org/User+Tracker
Improve documentation and usability on trackers (they are very powerful, but new users and power users don't know yet how to use their advanced features) :
how to link information from two trackers (like offers and demands in an exchange network):
Linking Trackers
Improve documentation and usability on trackers (they are very powerful, but new users and power users don't know yet how to use their advanced features) :
improve explanation shown on each tracker filed type at design time. Non coders can't understand the current explanation (which is very hard to understand for non-coders => unusable for new users and power users).
(or making a profile?)
Offering to work on that: xavi
Task:
In favor:
Offering to work on that:
Considering it's not urgent for these TikiFestStrasbourg days:
Should the new message (post-edit wiki page) be changed or removed? MoinMoin fait: Thank you for your changes. Your attention to detail is appreciated. Clear message