fabricius: what we're talking about is the description of an input field. the input is expected in a single format (therefore an international format)
ah thx and sorry chealer - though it was kind of a date shown on a calendar or so
tikiwiki: 03chealer * r37805 10/trunk/templates/admin/include_wiki.tpl: [ENH] wiki_up to database migration tool: clarify feedback
 Info: Tiki 7.2 Now Available - http://info.tiki.org/article175-Tiki-7-2-Now-Available
on ma dit qu'il y avait des francophone.. toute fois on ne ma pas dit qui ici pour celui qui ma envoyer un mail je voudrai plus de détail merci..
polom
sylvieg: +1 to translate the parts of YYYY-MM-DD separately if the format has to be kept intact
good anti-evening luciash
lol
is that a new movement in canada ? :)
good almost-morning chealer :)
hehehe
now, it's just 01:44
I've been much worst, I'm usually at bed these times
yup yup
luciash: it seems my natural schedule fixed itself in the last weeks
luciash: not really a new movement, I just thought it would be geeky
is your time correct ? i have 7:52 synced with time servers
should be 1:52 for you
luciash: hum, it does say 01:53 now. maybe my brain can't handle that time
:D
thanks for caring about my clock
u deserve some rest after the release
hehe, yeah, big stress
polom & good morning tikiverse
hi coaboa 
polom
hi coaboa and luciash 
luciash: I did miss s.th yesterday - was tired and nearly asleep - tracker -item-links links still not working vor anonymous
hi all
is it considered bad to echo paths in error messages around here?
'cause "Header already sent" is kinda useless without file and line information
good morning, together
gaxweb, What tha terror means is you're doing something to the header after page body has been loaded.
and polom to you all! :)
i know. my point is that the error message isn't as helpful as it could be
like: "header already sent in /path/up/to/index.php at line 1"
gaxweb, ok. yes. makes more sense :P
so is echoing paths considered a security hole in the tiki universe?
just checking before i make changes
ah Jens, polom
and Merb, polom you and all aswell
gaxweb, I'd say not in PHP error messages if the error message adheres to the servers settings
gaxweb, you can search for that at doc.tiki.org
:P
harhar
i wonder that, too, for a moment ago
http://twbasics.keycontent.org/Glossary <- here
gaxweb, are you the one who continued work on the perspective binder?
hah there is a fault in there
Merbster: nope
where is a fault?
Merbster: I do some work on perspectiver binder, is it by any chance faster now?
t.smarties
qolom is not existing
it should be moloq
Merbster: -> dodenhoff he is
dodenhoff, The slowness is, at first glance, coming from the SQL query using tikis own lib.
there must be some overhead there that it really doesn't like.
I did not have the time to investigate, I just switched the modified version out with my initial hack.
because the direct sql queries are faster.
I think direct queries are alsways faster, it is the question, do we direct queries or not
also the solution might not scale very well with 1000s of perspectives because those are saved as serialized PHP so checking a pages categories up against a perspective involves deserialization of PHP objects
dodenhoff, I am in doubt there. because at the current speed with tikilib used. it's near unusable.
brb
hmm
merbster: do you have the up-to-date version? for me it is working, but I have just a few perspectives set. Since the db query is done in a loop and within it followed by a loop it creates, of course, a lot of overhead, in particular if the search is not successful. but I cannot think about a way to reduce that, except
we do this loop on an areas admin panel and save the perspectiveids we look for in an array as a property of categories, that way it outputs just the wanted perspectives instead of collecting them everytime you request a page
fabricius, I don't know. If I am going I'll try to get my job to sponsor the trip
Merbster: that would make sense
fabricius: iirc you need perm to view the trackers too
fabricius: anon
luciash: re
luciash: back I am
I have the permission set for Anos to view the tracker and pending items
for open items I did not find a permission
fabricius: there is none
fabricius: open items is tiki_p_view_tracker
fabricius: you said they were closed, so you need perm to view_tracker and to view closed
I seemed to have miss-seen s.th. yesterday night
I have both on: perm pending and perm closed
and perm view ?
yes, and perm view - then items are open in this tracker 
maybe a problem with category perms and tracker?
you have category perms set per the tracker ?
yes
and they are ?
ok, mom I recheck again - some seconds pls
it is category "public" - set for Anos:
tiki_p_tracker_view_attachments - tiki_p_tracker_view_ratings 
tiki_p_view_trackers - tiki_p_view_trackers_closed - tiki_p_view_trackers_pending - tiki_p_watch_trackers
when the tracker item is open, I can see it, but no link - when I switch it to pending or closed it disappears out of the trackerlist
obwohl du das schon gut erklärst
sry
forget that
when I login, I cansee the links
in my point of view it should work
this way
luciash: I made it the opposit way round now: I just added tiki_p_view_tracker in general settings
now it works
somwwhat off topic: does one know if i can use jitsi to call a skype user?
coaboa: it should work in the meantime, but I do not know
I want to try jitsi aswell
first thing I got working is the text chat
coaboa: if you want, I would like to test more aswell
would like to see, if audio/video works between two jitsis
jitsi/skype would be nice asewll
the editor for articles is creating line-breaks instead of paragraphs. i can't find a setting to change that though. is it possible or do i need to modify code?
on jitsi.org they did write something about having integrated a skype protokoll
i'm taking about the generated HTML btw.
gaxweb: wiki paragraph formatting on Admin > Editing & Plugins panel
fabricius: tiki_p_view_tracker global perm shouldn't override object (category) perm
fabricius: it should be the other way around actually ... weird ... what Tiki version ?
fabricius: just read that there is some sort of support for the spype codec but no idea how to configure because jitsy does not offer a "skype" service
codec is just the way how the data is compressed, simply said
luciash:was surprised too . maybe I mixed something
imho the fact that the skype codec is supported would mean one can benefit from its good audio quality when using it in jitsi
that wouldn't mean you can connect to and call skype users though
just my thoughts
but I've found it: the jitsi homepage states: support for skype SILK codec
luciash: yes that could be. If they use the codec. Maybe thats the fact.  I did'nt thought of that option ;-)
luciash: I am wondering for the permission issue aswell
luci but in fact, category perm IS overwriting general perm, as I have a first aid tracker with sensible datas - that i a non-public category and NOT showing the items of that tracker
but luciash: I am thinking about takng out the first aid area into an extra installation anyway
I do not want any risk that somebody else than a tiny few of admins could see or make publc those tracker datas
even if it was not on purpose, just due to wrong categorization
fabricius, you can "auto-categorize" in tracker items now dependant on perspective
You just have to add the category field in the tracker. Set it to for example drop down or listbox and then use pretty tracker to place the category choice in a hidden div. Then it will always categorize in the option picked by the perspective and the user won't have any way of changing it.
fabricius: depends on the version
fabricius: i have most experience with 6.x trackers
Merbster: even not via url param ?
luciash, I haven't tested that, but I would figure most users are not even aware you can pass in parameters that way.
Merbster: yep, but when you say "any way" i get picky ;)
luciash, well they could login to the database and change the categorization there but I see the chance of a user doing that very small. :P
And there is no way they can do it trhough an UI - which in user terms means "no way"
arggl - chromium cannot show the OpenStreetMaps of Tiki
language: I had limited language to english and german, then unlimited and limited to french english and german
but still in the switch menu module I can se only english and german
nofrench
canthis be a bug?
Merbster: be careful of links like tiki-view_tracker_item.php?trackerId=5&cookietab=2&itemId=14&show=view&ins_15[]=4&save=Save
Merbster: ins_15[] is my category dropdown, category Private = 5, category Public = 4
luciash, you'd still need pretty deep knowledge about how tiki is designed and what catIds are assigned to what categories.
also the name of the HTML element
Merbster: view source can mostly easily tell you
luciash, yes, for us blessed with IT knowledge
most users won't know. :P
Merbster: maybe you talk in context of internal Intranet, where ppl cannot do much, but when you take it out to internet... you cannot count on it ppl don't have a clue
*that ppl don't have a clue
luciash, ofcourse not.
if you'd like to build public social site on it, you'd need to take care of every possibility
But my point is, you cannot automaticly categorize an item in wiki
Without using above described workaround
there are some ways... but you mean tracker item or wiki page ?
tracker item
tikiwiki: 03jonnybradley * r37807 10/third_party/jquery/ (5 files in 2 dirs): [FIX] mobile: Update jquery.mobile to 1.0 RC 1
tikiwiki: 03jean-lucnavarro * r37808 10/trunk/lang/fr/language.php: [TRA] more French translations + corrections
Merbster: yup, i am not sure if "Auto create corresponding categories" also assigns that item to that category
luciash, then you just categorize it. I am talking about categorizing an item, depending on what perspective is currently active.
 New Forum Posts: Zur deutschen I18n beitragen - http://tiki.org/tiki-view_forum_thread.php?forumId=10&comments_parentId=42376
Merbster: i understand what you mean :) i just pointed out i wouldn't 100% rely on this workaround but rather see something implemented in trackers code
tikiwiki: 03jonnybradley * r37809 10/third_party/mobileESP/mdetect.php: [FIX] mobile: Update mobile esp library
why can anonymous users see unpublished articles on /tiki-list_articles.php?
that's a bug, right?
gaxweb, I guess that would depend on the permissions you gave
hmm, couldn't find any
in that direction
for articles , anonymous only has read_article, read_topic and rate_article
gaxweb: well, i would say it is rather missing permission to view the articles list
luciash: but i want them to see the list, just not which articles haven't been published yet
gaxweb: it depends if you want your anonymous users view the articles list at all, or you want them view only list with published
ok, and where can i set "view only list with published"
gaxweb: i would rather file a bug report that there is no permission tiki_p_list_articles
i see. thanks for the help though.
gaxweb: as a workaround you could delete the script tiki-list_articles.php and send your users to a wiki page with articles wikiplugin instead where you can list only published
my actual problem is that tiki-view_articles.php can't be sorted by users
that's a good idea luciash, thanks
unless you can't sort there either :)
heh, not sure if you can
there's Article List plugin too
ah, that's the one
mkay, so many places to go :]
the other one inserts article content, ok
nah, won't help unfortunately - no custom sorting. it seems to invoke the view template. :/
tikiwiki: 03jonnybradley * r37810 10/trunk/templates/tracker_validator.tpl: [ENH] trackers: Disable submit buttons on tracker forms after the form is submitted. Will stop duplicate items being added - requires feature_jquery_validation (thanks Xavi)
tikiwiki: 03jonnybradley * r37811 10/trunk/templates/admin/include_features.tpl: [MOD] admin/features: Move mobile prefs below non-experimental ajax & jquery ones
gaxweb: i see. other option for you is to mdify the template of tiki-list_articles
gaxweb: go to templates/ and make a copy of tiki-list_articles.tpl
yes, doing it myself usually works ;)
gaxweb: then edit the line where the section loop starts
gaxweb: with {section name=changes loop=$listpages}
add after: {if $listpages[changes].ispublished eq 'y'}
but then nobody would see unpublished articles anymore, right?
then you need to close this condition on line before {sectionelse}
using {/if}
yep, unless you add: or $user neq '' (to the condition)
aha!
means OR $user is empty (which is anonymous)
tikiwiki: 03jonnybradley * r37812 10/trunk/lib/headerlib.php: [FIX] headerlib: Missing var in set_metatags (seemingly unused function?) and missing global in add_map
gaxweb: remember this is still a workaround... there should really be new permission check instead
gaxweb: you could also use: or $tiki_p_admin
gaxweb: if you want only users with admin perms view the unpublished ones
$tiki_p_admin eq 'y'
gotta run, c u later
thanks!
{if $listpages[changes].ispublished eq 'n' and $user eq ''}{else} did it
gaxweb, clever! :P
not really, but thanks ;)
you got access to the beta?
or is it released?
sure
it's open now. anyone can play.
ah nice :)
Well I am planning to buy Gears of War 3 today.
a good choice as well
I am wondering if I should postpone it.
why?
because I don't think it will bring anything new or wonderful. It's just the end of a story. "more of the same" even though more of Gears is not necesarrily a bad thing
that's probably true, but isn't that the same for most sequels?
more of the same?
yes ofcourse. I want it, what I question is, do I really want to pay 66€ for it
http://jsfiddle.net/T4GwL/ <- what is wrong here? . why is the first "Rediger" button not alerting what I have pressed?
well, money is a different story :)
gotta go now. cya.
have a nice weekend gaxweb 
you too
I found out.
forgot to give the button an ID. it only had a name
tikiwiki: 03robertplummer * r37813 10/trunk/templates/fgal_context_menu.tpl: [FIX] Context menu feature checks for sheet, draw, and docs
tikiwiki: 03oeversetten * r37814 10/trunk/lib/perspective_binder.php: [FIX] decomment if in else case again, so it does not redirects on any found categid
are people using tiki to send html newsletters?
sylvieg: I am just starting to use HTML newsletters
fabricius: is it working well? - I suppose you have to put absolute url for image..
sylvieg: we are still testing - not with much time, cause we have several different tasks - but yes, image seems to be a problem
If I remember right, I had to use the absolute url
I can have a look
mom sylvieg - got a phonecall
polom
sylvieg: yes, I did send a few testnewsletters - I recieved the image with absolute url - had to tell the browser to open external source (I think that is a normal local setting and not controlable by the webmaster)
sylvieg: I have to go for a while - will come back to you later on - OK?
polom chealer
bbl
tikiwiki: 03lphuberdeau * r37815 10/trunk/lib/wiki-plugins/wikiplugin_code.php: [MOD] Removing all legacy highlight and options, using codemirror for everything, eliminate ishtml and wiki parsing because they open undesired code paths leading to XSS, removing cpy which is no longer needed
 New Forum Posts: How to export semantic links from Tiki or database? - http://tiki.org/tiki-view_forum_thread.php?forumId=4&comments_parentId=42381
tikiwiki: 03lphuberdeau * r37816 10/trunk/lib/wiki-plugins/wikiplugin_code.php: [FIX] Missing semi-colon
tikiwiki: 03nkoth * r37817 10/trunk/lib/wiki-plugins/wikiplugin_tracker.php: [FIX] Allow showing of fields when creating new tracker item while registering even without create item perm) because you don't want to actually give the create item perm that will allow access to create item screen
tikiwiki: 03nkoth * r37818 10/trunk/lib/wiki-plugins/wikiplugin_tracker.php: [FIX] Allow categorization of user tracker item while registration even without all the required perms which is real troublesome to setup
tikiwiki: 03lphuberdeau * r37819 10/trunk/ (5 files in 5 dirs): [MOD] Introducing the transaction concept, which does not handle database transactions for now, but limits the amounts of commits on unified index (which is the same scope)
tikiwiki: 03sampaioprimo * r37820 10/trunk/lib/test/editlib/ (ParseToWiki_TextTest.php ParseToWysiwyg_TextTest.php): restore preference default state to fix testWikiParser() test
tikiwiki: 03sampaioprimo * r37821 10/trunk/lib/test/phpunit.php: wraper file to make it possible to debug the test suite using Xdebug/Aptana
tikiwiki: 03sampaioprimo * r37822 10/trunk/lib/wiki-plugins/wikiplugin_code.php: check if $colors variable is defined
tikiwiki: 03sampaioprimo * r37823 10/trunk/lib/test/wiki-plugins/ (. CodeTest.php): very basic test for wikiplugin_code()
hi changi|Zend
nkoth|nelson: when would you be available to discuss Tiki 8?
chealer,i just finished lunch
hi all
hi all
id advanced rating working for forum? or do we have rating in forum?
the doc says comments...
well, forums are just comments with a different UI
I haven't tried it but it should work unless some objecttype confusion happened causing it to break
is there another doc than http://doc.tiki.org/Advanced+Rating - checking the feature advance rating is not enough to show rating bar in forum
polom
hi marclaporte
sylvieg: I think there is a "posts can be rated" check box in individual forum setting
lphuberdeau: I'm working on a new preference that when enabled will add more behavior to UsersLib::add_user(). instead of adding it directly to the function, I'm considering using the new events mechanism. creating something like tiki.user.save and bind it to tiki.save. but tiki.save already have plugged in some functionally that is exclusive to tiki objects (like plugin_post_save_actions). what do you think of moving everything that is binded to
hi marclaporte
I think nkoth|nelson, changi|Zend are here so we can start on that Tiki 8 scheduele
yep
I wanted to start asking how the server migration was going, but changi|Zend just told me it's complete :-)
rogrigo_sampaio, makes sense, since tiki.save is never triggered directly, all that binding is quite local
however, what do you expect would be common between objects and users?
first, do we is it realistic to release by November? and at the same time, how available will you be in October changi|Zend? we need to upgrade almost all sites, plus package at least 2 releases.
should be fine
and trunkdoc and trunkdev will help a lot
so end Octobei-ish?
lphuberdeau: I can't think of anything now that is common between them. But I like the idea of leaving this possibility open in case something appears.
changi|Zend: great. absolutely, {trunk,legacy}{doc,dev} will be so facilitating
lphuberdeau: but I trust your judgment if you think it is better to have two independent chains, one for objects and other for users.
nkoth|nelson: the current draft says Halloween :-) http://dev.tiki.org/Tiki8
nkoth|nelson: thanks I have it now
halloween is fine for me
rodrigo_sampaio: we can always change the chain later if we see it's needed
i can provide a trunkinfo too
changi|Zend: oh. are we going to upgrade info to 8?
rodrigo_sampaio: it's not hard to do now, and it won't be much harder in the future either
rodrigo_sampaio: but there is a need for tiki.user.update and tiki.user.create, with a common tiki.user.save
chealer: maybe on day, it will be usefull to have our 3 most popular website with a trunk view
even if we don't upgrade it now
lphuberdeau: ok, now I only need tiki.user.create. but if it is easy to deploy, which is likely to be the case, I will do tiki.user.update and tiki.user.save as well
changi|Zend: OK, yes in that sense it would be useful, and if upgrading it takes little time, we would need it for 9 anyway
so does anyone think it's too late for October 31st or have a different target release date to suggest?
chealer: I'm quite optimistic about the stability of trunk right now
lphuberdeau: cool
OK lphuberdeau. let's go with that
that gives us a nice 31 days to release
there has been much more people testing on trunk than in any past releases, so I believe we're already past alpha
even late-beta quality, but I guess only branching and getting random people testing will show that
next question, when do we branch?
as soon as possible
I already feel limited in the changes I can make
tomorrow?
I mean in the list of people who said they had things to add, are there any outstanding?
it's not like branching meant complete freeze
I agree with ASAP
well, fixes are ok, but given that we have 1 month it will be quite strictly just fixes
but I have a wave of changes to make in trackers, and I can't do it anywhere now
I'm also holding some changes waiting for branching
so I agree with branching as soon as possible
that means we should have branched a week ago
nkoth|nelson: only Jonny and Robert said they had things IIRC. Robert explicitly asked not to freeze yesterday. I told him to add his plans on the radar but he didn't yet.
there will be auto-merge for a long while, so no big issue
how about Monday? and who can branch?
branching takes a few seconds
sunday evening so next week can start clean?
no freeze during "normal working hours"
OK, is everyone good with branching Sunday?
+1
I think it is fine. If jonny has any thing he needs to commit when he gets back Tuesday we can make an exception for him
chealer: +1
let's do sunday
good. next question, number of prereleases. we currently have 2 betas and 1 RC scheduled. how about just 1 beta and one RC?
if anything, I would rather do 1 beta and 2 RC than the other way around
RC is a different signal
Tiki 7 had 2 betas and 1 RC
it depends on how many commits there are
1 beta and 2 RC will be fine for me
(but over a 2+ months freeze)
1 package per week is fine
not more
but 1 beta and 2 RC sounds about right, unless we discover some things that blandside us
but a lot of bugs have been fix already imo
I would rather avoid *planning* several RCs, I think a release candidate should actually be something we think could be released as-is
chealer: many people just don't test if it says beta
chealer: I see what you are saying
but people are more likely to test RC?
probably
that's for sure
1 beta, 1 RC, and leave time for a second one if needed
first RC 3rd week of october?
or 2nd even
pretty much
is everyone OK with lphuberdeau's suggestion?
yes for me.
ok
good, next, is any step missing from http://dev.tiki.org/Tiki8#Schedule ?
dates?
yeah, if no step is missing, we get to dates
good, now for pre-release dates, we have a beta and an RC.
I would target release before 31
chealer: some website are missing
I should write an email
but nothing critical
that way, if we're a bit late, we can still manage for 31
changi|Zend: OK, then please add them, we get to those in a moment
lphuberdeau: OK, let's make sure we agree on that first
does have a different target release date to suggest?
anyone...
well  not sure if it matters but I will be quite precoocupied from Oct 21 - 29
I'm hesitant to target significantly before October 31st. I consider it as just a tentative date, I don't really mind delayed a bit to November if necessary.
so from my perspective setting 31 is fine
I think it would be awesome to hit the release schedule once ;)
it is sort of industry standard not to hit those things lol
nkoth, if you're going to be busy the last week, we might as well try to release before it while you're not ;)
worse beore
I'd say 31 is a good date
good chance of hitting and even if we miss it'll be just a few days
OK, let's stick with October 31st then.
how about 29, which is a saturday
I'm OK with October 29th if it's a better weekday
nkoth|nelson?
I'm indifferent between both
I might be mistaken, but I think week-end is better for changi
I'm presenting at an open source conference on the 29 I think
don't you think it would be nice to have the 8 package pop-up during your presentation? :)
lphuberdeau is highly convincing
hehe
so you release while I present?
hahaha
chealer ^ :)
if others don't mind, I'm OK with that
tikiwiki: 03changi67 * r37824 10/trunk/ (27 files in 2 dirs): [ENH] Zend Code Styling - quality.tiki.org
I guess we'll go with October 29th then
ok
changed. are we all satisfied with what we decided so far?
ok for me
great. back to pre-release dates, I suggest beta October 11th and RC October 22nd.
beta should be earlier I think
October 11th is 9 days after branching
i can do it next thursday
October 10th is a the Monday of thanksgiving
6th
so the 6th would be 4 days after branching
!help
You can get a more complete list of commands that work with this bot at http://tiki.org/TikiBot .
nkoth|nelson: would you prefer October 6th to 11th?
yes
OK. I have no strong opinion
is everyone OK with RC October 22nd?
+1
ok
on 20 would be easier for me
Thursday is the best day for me
Thusday then
changi|Zend: could you take beta 1 in charge? I can be here and announce to -devel.
I'm OK with RC October 20th
http://tiki.org/TikiFestFrankfurt8 can be a good time to test
bye marclaporte, thanks for your quiet watch ;-)
marclaporte: to test RC or 8.x in general?
test in general
OK
so we need as many *.tiki.org sites on 8.x as soon as possible
chealer: yes i can
I agree
marclaporte: i think i can create doc8 dev8 and info8 as soos as the branches/8.x is create
thanks changi|Zend.
s/soos/soon
isn't info staying on LTS?
yeah, I think the plan was to keep info on Tiki 6
so is everyone good with the beta on October 6th and RC 1 on October 20th?
as i explain before it's only for testing purpose
chealer: yes
changi|Zend: oh, "info8", I see
didn't think about that
if thursday is best for changi, I would even push the release to 27
good
changi|Zend: would you prefer releasing October 27th to 29th?
27, would be better
or if someone else want to release the 29, feel free :)
nkoth|nelson: can you make your audience swallow that Tiki 8 is being released live if it was only released 2 days before?
lol chealer
even better if it is already released actually
I find October 27th early, but I'm not thrilled to package
tikiwiki: 03changi67 * r37825 10/trunk/lib/profilelib/installlib.php: [ENH] Zend Code Styling - quality.tiki.org
OK, so no problem moving the target release date to October 27th?
tikiwiki: 03changi67 * r37826 10/trunk/lib/test/ (phpunit.php wiki-plugins/CodeTest.php): [user:changi:FIX] SVN Keywords + Copyright
OK, 8.0 target date moved. do we stick with what we decided so far, plus beta October 6th and RC 1 October 22nd?
I agree
wasn't RC1 on the 20th?
yes on 20
I think we are aiming for thursdays
thursday releases
I think it looks like a sane release
tikiwiki: 03sampaioprimo * r37827 10/trunk/lib/ (setup/events.php userslib.php): deploying tiki.user.save, tiki.user.create and tiki.user.update events
tikiwiki: 03sampaioprimo * r37828 10/trunk/ (5 files in 4 dirs): 
tikiwiki: [ENH] new preference to make daily reports the default option for new
tikiwiki: users
sorry, indeed, so we stick with what we decided. are we good with beta October 6th and RC 1 October 20th?
yes
tikiwiki: 03changi67 * r37829 10/trunk/lib/prefs/dailyreports.php: [user:changi:FIX] SVN Keywords
changi|Zend: thanks for the site additions
chealer: no problem
OK, pre-release dates set. next, order of site upgrades
3 weeks release sprint is a lot more sustainable than the last 3-month marathon
i think doc should be upgrade after dev
I agree
I put community somewhere random BTW, it depends on Oliver
I moved up dev
for code and mods I don't really care
hi RobertPlummer
code and mods will be done after doc
chealer: polom
OK. I'll contact Oliver regarding community
if we're good with the order, let's set dates for themes, tv, dev, doc and profiles (in that order)
tikiwiki: 03nkoth * r37830 10/trunk/lib/wiki-plugins/wikiplugin_iframe.php: [FIX] Prevent parsing of iframe contents leading to it not showing
changi|Zend: let's say profiles should be between October 20th and October 27th at your convenience, ideally not too late?
ok
just after the release
changi|Zend: Saturday the 8th a good day for you? for themes and tv
tikiwiki: 03changi67 * r37831 10/trunk/tiki-calendar.php: [ENH] Zend Code Styling - http://quality.tiki.org/job/Tikitrunk/violations/file/svn/tiki-calendar.php
tikiwiki: 03sampaioprimo * r37832 10/branches/7.x/ (6 files in 4 dirs): [bp/37828][ENH] new preference to make daily reports the default option for new users (at Xavi's request)
Sunday will be better
so themes and tv Sunday the 9th. when can we do dev then, Tuesday the 11th?
yep
OK, that would leave doc somewhere between the 11th and the 20th
13 ?
changi|Zend: that could be intense, but we can try
we would have themes and tv on the 9th, dev on the 11th and doc on the 13th
tikiwiki: 03sampaioprimo * r37833 10/branches/proposals/6.x/ (9 files in 5 dirs): [bp/37828][ENH] new preference to make daily reports the default option for new users (at Xavi's request)
so we would have themes and tv on the 9th, dev on the 11th, doc on the 13th and then profiles a bit after the 20th. community to be discussed with Oliver.
should we try that?
yes
OK, main site upgrades dates set
do we have a plugin to display a wmv video
How does the schedule look now?
chealer: as short as firefox's one :)
lol
not as short as chrome?
aggressive but good. worst case one more RC we should be good
changi|Zend: hahaha
allright, is this our final Tiki 8 schedule? http://dev.tiki.org/Tiki8#Schedule
nkoth|nelson: were you volunteering to tell tikiwiki-devel about our conclusions?
Hey guys, how do you obtain a page as a variable?
Like what is already been created from memory?
I've seen some varialbe that have to do with clean, or something, is that right?
Is it ob_start();?
chealer: yes, just link to the page and a reminder that it's last call for non-fixes, and also that already developers are holding back large commits till after the branch
I was about to write it
RobertPlummer, ob_whatever is the whole output buffer thing in php
not sure if that is what you are looking for
thanks nkoth|nelson
I guess we can call that our final schedule.
sorry for running long, thanks everyone
chealer: can i send my email to devel about infrastructure ? 
changi|Zend: oh, sorry, I meant to comment on it... I know it's already late for you
changi|Zend: I'll have some comments in 15 minutes if you can wait, otherwise, I'll just reply
you'll reply :)
see ya all
OK changi|ffa, thanks again
nice coordination chealer and nkoth|nelson 
RobertPlummer: ob_start() returns a boolean. ob_get_contents() could give you something, but it depends on the context
chealer: Thanks buddy.
RobertPlummer: maybe having more context would help
chealer: It isn't tiki related, just a general questions.
RobertPlummer: oh, OK. because in Tiki Smarty limits the role of ob* 
tikiwiki: 03changi67 * r37834 10/trunk/ (6 files): [ENH] Zend Code Styling - http://quality.tiki.org/job/Tikitrunk/violations
tikiwiki: 03robertplummer * r37835 10/trunk/lib/logs/logsquerylib.php: 
tikiwiki: [FIX] Fixed syntax
tikiwiki: [ENH] Added ability to set attribute to narrow by user
tikiwiki: 03changi67 * r37837 10/trunk/ (165 files): [REF] Zend Code Styling - http://quality.tiki.org/job/Tikitrunk/violations
polom
re marclaporte
we should have discussed 7.x. are we going to release a 7.3?
I suspect we will
but maybe better not promise it
 6.5 is more important
the problem is developers won't know if they should/need to backport to 7.x
7.x branch dies in a month
when 8 is released
realistically, we're not going to have an other release in that timespan
unless there is a critical security fix, imo, there is no need to release another 7.x
7.2 wasn't even expected
lphuberdeau: what is the most memory efficient way to get a file from a url and save to a temp file on disk in tiki?
(in case the file is large)
actually, nm, I don't need this anymore, but might be good to know anyway
well, fopen and writing as it comes in I guess
but there is still buffering going on
wget has to be efficient to do it
but that's not from PHP
tikiwiki: 03sylvieg * r37838 10/third_party/jquery/jquery.media.js: [ENH]jquery.media update to the latest