From mark at the-howards.net Sun Jun 1 14:47:56 2008 From: mark at the-howards.net (Mark Howard) Date: Sun, 1 Jun 2008 14:47:56 -0400 Subject: [geeklog-devel] Interesting reading ... Message-ID: <065901c8c418$021e79b0$065b6d10$@net> As long as this were used with a local configuration opt-out, the following would seem to be a useful thing to consider as we head towards an expanded use of Ajax in the presentation layer . http://ajaxian.com/archives/announcing-ajax-libraries-api-speed-up-your-ajax -apps-with-googles-infrastructure -m -------------- next part -------------- An HTML attachment was scrubbed... URL: From ironmax at spacequad.com Sun Jun 1 16:45:20 2008 From: ironmax at spacequad.com (Michael Brusletten) Date: Sun, 1 Jun 2008 16:45:20 -0400 Subject: [geeklog-devel] Configuration GUI References: Message-ID: <000d01c8c428$6a271020$fe00a8c0@ns2.spacequad.com> I have a question about the configuration. How does a person know what the defaults are for the listings in the GUI for items like the TimeZone? Example: Timezone (?) Restore In the database it reads for the value as "unset" and the default is Etc/GMT-6 once you click on the restore. Now my real quetion is, how does someone reset the field back to original setting? The reset is not working as one would think it should. Is it not supposed to pull the values from the default_value column of the database? Same holds true for many of the other options that have restore next to the options. In orser for the option to go back to the original setting from setup. I had to look in the database with what the values were and set them. Try it and change the values around and then try hitting the reset...and nothing really happens to reset the values. Michael From devel at portalparts.com Sun Jun 1 17:27:32 2008 From: devel at portalparts.com (Blaine Lang) Date: Sun, 01 Jun 2008 17:27:32 -0400 Subject: [geeklog-devel] Interesting reading ... In-Reply-To: <065901c8c418$021e79b0$065b6d10$@net> References: <065901c8c418$021e79b0$065b6d10$@net> Message-ID: Hi Howard, Noticed this earlier this week and is nice of google and noticed that Yahoo was not on the list but that is likely because Yahoo announced this service in early last year. It's nice because we can release our plugins without distributing these libraries or requiring a user to copy/install the files. http://yuiblog.com/blog/2007/02/22/free-yui-hosting Blaine Mark Howard wrote: > > As long as this were used with a local configuration opt-out, the > following would seem to be a useful thing to consider as we head > towards an expanded use of Ajax in the presentation layer ? > > http://ajaxian.com/archives/announcing-ajax-libraries-api-speed-up-your-ajax-apps-with-googles-infrastructure > > -m > > ------------------------------------------------------------------------ > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > From mark at the-howards.net Sun Jun 1 20:25:15 2008 From: mark at the-howards.net (Mark Howard) Date: Sun, 1 Jun 2008 20:25:15 -0400 Subject: [geeklog-devel] Interesting reading ... In-Reply-To: References: <065901c8c418$021e79b0$065b6d10$@net> Message-ID: <004b01c8c447$21ec1020$65c43060$@net> :^) I think the primary difference here is that Google is offering to host multiple libraries, even libraries not of their creation - except of course YUI, a product of their competitor. That coupled with Google's slightly more extensive hosting infrastructure might count this as a one-up (don't get me wrong - I'm not a Google stockholder, employee or irrational zealot). Anyway - not surprising that they took the opportunity to try to best YaHoo at it's own game, and I guess it's win-win, and it's just a matter of determining the correct source based upon what libraries you have selected for your use. -Mark -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Blaine Lang Sent: Sunday, June 01, 2008 5:28 PM To: Geeklog Development Subject: Re: [geeklog-devel] Interesting reading ... Hi Howard, Noticed this earlier this week and is nice of google and noticed that Yahoo was not on the list but that is likely because Yahoo announced this service in early last year. It's nice because we can release our plugins without distributing these libraries or requiring a user to copy/install the files. http://yuiblog.com/blog/2007/02/22/free-yui-hosting Blaine Mark Howard wrote: > > As long as this were used with a local configuration opt-out, the > following would seem to be a useful thing to consider as we head > towards an expanded use of Ajax in the presentation layer . > > http://ajaxian.com/archives/announcing-ajax-libraries-api-speed-up-your-ajax -apps-with-googles-infrastructure > > -m > > ------------------------------------------------------------------------ > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From devel at portalparts.com Sun Jun 1 22:47:23 2008 From: devel at portalparts.com (Blaine Lang) Date: Sun, 01 Jun 2008 22:47:23 -0400 Subject: [geeklog-devel] Interesting reading ... In-Reply-To: <004b01c8c447$21ec1020$65c43060$@net> References: <065901c8c418$021e79b0$065b6d10$@net> <004b01c8c447$21ec1020$65c43060$@net> Message-ID: Likely Yahoo would not allow Google to host the YUI libraries albeit Yahoo has a very liberal licensing strategy but it still may be political as to why Google did not announce with YUI support from the outset. I have been using the YUI libraries on projects for the past 2 years and it's a very impressive library that is growing every few months. I'd like to see Google host the EXT library as we use that on projects and my latest plugin that used EXT extensively was a bit of a hog initially loading 1Meg of JS. Some of the other libraries have neat features specially jquery but one has to be careful loading too many of these libraries and I've been very pleased with the decision to use YUI. It's also beneficial that YUI has compressed min versions of their libraries and hosting on their CDN really can reduce any noticeable initial load. Additionally, they have a feature to load libraries on page load so their is even less or no initial page render delay. Blaine Mark Howard wrote: > :^) > > I think the primary difference here is that Google is offering to host > multiple libraries, even libraries not of their creation - except of course > YUI, a product of their competitor. That coupled with Google's slightly > more extensive hosting infrastructure might count this as a one-up (don't > get me wrong - I'm not a Google stockholder, employee or irrational zealot). > > Anyway - not surprising that they took the opportunity to try to best YaHoo > at it's own game, and I guess it's win-win, and it's just a matter of > determining the correct source based upon what libraries you have selected > for your use. > > -Mark > > -----Original Message----- > From: geeklog-devel-bounces at lists.geeklog.net > [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Blaine Lang > Sent: Sunday, June 01, 2008 5:28 PM > To: Geeklog Development > Subject: Re: [geeklog-devel] Interesting reading ... > > Hi Howard, > > Noticed this earlier this week and is nice of google and noticed that > Yahoo was not on the list but that is likely because Yahoo announced > this service in early last year. > It's nice because we can release our plugins without distributing these > libraries or requiring a user to copy/install the files. > > http://yuiblog.com/blog/2007/02/22/free-yui-hosting > > Blaine > > Mark Howard wrote: > >> As long as this were used with a local configuration opt-out, the >> following would seem to be a useful thing to consider as we head >> towards an expanded use of Ajax in the presentation layer . >> >> >> > http://ajaxian.com/archives/announcing-ajax-libraries-api-speed-up-your-ajax > -apps-with-googles-infrastructure > >> -m >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> geeklog-devel mailing list >> geeklog-devel at lists.geeklog.net >> http://eight.pairlist.net/mailman/listinfo/geeklog-devel >> >> > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > From geeklog at mystral-kk.net Wed Jun 4 09:41:06 2008 From: geeklog at mystral-kk.net (geeklog at mystral-kk.net) Date: Wed, 4 Jun 2008 22:41:06 +0900 (JST) Subject: [geeklog-devel] Custom email localization Message-ID: <41372.192.168.1.22.1212586866.squirrel@www.s215.xrea.com> Hi all, it might be too late for GL-1.5.0, but I'd like to point out a possible problem in sending an email with GL. This has exsited since GL-1.4.1. As of GL-1.5.0 in CVS, if you have defined CUSTOM_mail() function, it will be used instead of COM_mail(). However, since neither CUSTOM_formatEmailAddress() nor CUSTOM_emailEscape() is suppoted, you'll immediately face a problem when the charset of your GL site is UTF-8 _AND_ you want to send an email in a charset OTHER THAN UTF-8. So, how about supporting CUSTOM_formatEmailAddress() and CUSTOM_emailEscape()? I think this will need a minimum of code change in lib-common.php as follows: ========== before ========== function COM_emailEscape( $string ) { global $_CONF; $charset = COM_getCharset(); ========== after =========== function COM_emailEscape( $string ) { global $_CONF; if (function_exists('CUSTOM_emailEscape')) { return CUSTOM_emailEscape($string); } $charset = COM_getCharset(); ============================ ========== before ========== function COM_formatEmailAddress( $name, $address ) { $formatted_name = COM_emailEscape( $name ); ========== after =========== function COM_formatEmailAddress( $name, $address ) { if (function_exists('CUSTOM_formatEmailAddress')) { return CUSTOM_formatEmailAddress($name, $address); } $formatted_name = COM_emailEscape( $name ); ============================ -- mystral-kk geeklog at mystral-kk.net http://mystral-kk.net From mjervis at gmail.com Thu Jun 5 03:52:31 2008 From: mjervis at gmail.com (Michael Jervis) Date: Thu, 5 Jun 2008 08:52:31 +0100 Subject: [geeklog-devel] GSoC - Comments - Edit - Permissions Message-ID: <7b42e7470806050052o4acdfbfas9d31ef0084765eb8@mail.gmail.com> Jared and I are discussing permissions to edit comments in Geeklog for the GSoC work he's doing. Firstly, I beleive the requirement is for users to be able to edit their own comments, and for administrators to be able to edit users comments subject to security permissions. So, I've said the following: >> Geeklog uses unix style permissions. Everything with permissions on it >> has an owner and a group. Then there are permissions for owner, group >> and anonymous users. >> >> A comment should be saved with the owner_id being the id of the user >> who created it, if authenticated. I don't think we already have one, >> but a group of comment moderators or something might be needed. >> Comments would then be saved with perm_owner allowing edits and >> perm_group allowing edits. Then administrators can be given edit >> permissions to comments by assigning them the comment moderator group, >> and users can edit their own comments. Anonymous should just have read >> permissions of course. Jared's response: > Does this mean add these rows to the comment table and save this default > data each time a comment is submitted? I think the answer to this is yes, comments will now need to have the standard permissions columns which will have to be set when a comment is saved by a user automatically. > Are there instances where individual > comment permissions would change? But, would we want the administrator to be able to change the permissions mask as they can with stories? So, if a user edits a comment, a moderator edits a piece out and the user edits it back in, the administrator can change it such that the user can no longer edit it? (Perm_owner read only) And I would assume we'd default existing comments on mature sites to owner_id of the user who posted the comment, or root if it was anonymous, and perm_owner to read only as with perm_group and perm_anon? > Currently I have something like this this > with the comment moderator group having rights to the feature 'comment.edit' > : > > if ( $_USER['uid'] == $A['uid'] && $_CONF['comment_edit'] == 1 > && (time() - $A['nice_date']) < $_CONF['comment_edittime']) { > $edit_option = true; > } else if (SEC_hasRights( 'comment.edit' ) ) { > $edit_option = true; > } else { > $edit_option = false; > } Having seen this from Jared, I'm half re-canting my earlier comment: >> Then administrators can be given edit >> permissions to comments by assigning them the comment moderator group, I guess the group would actually be the group of the user who posted the comment (logged in users most likely) and the group permission would be read only. And Jared is right, Administrators/Moderators would need the comment.edit permission to edit a users comment, which would include the editing of the permissions mask to prevent the owner re-editing the comment (assuming that owner wasn't a comment.edit user too of course). Does that make sense and cover all the use-cases people can see? Where are the obvious glaring gaps I've left in as a deliberate mistake? ;-) Cheers, Mike -- Michael Jervis mjervis at gmail.com 504B03041400000008008F846431E3543A820800000006000000060000007765 62676F642B4F4D4ACF4F0100504B010214001400000008008F846431E3543A82 0800000006000000060000000000000000002000000000000000776562676F64 504B05060000000001000100340000002C0000000000 From devel at portalparts.com Thu Jun 5 07:27:43 2008 From: devel at portalparts.com (Blaine Lang) Date: Thu, 05 Jun 2008 07:27:43 -0400 Subject: [geeklog-devel] GSoC - Comments - Edit - Permissions In-Reply-To: <7b42e7470806050052o4acdfbfas9d31ef0084765eb8@mail.gmail.com> References: <7b42e7470806050052o4acdfbfas9d31ef0084765eb8@mail.gmail.com> Message-ID: Michael, Why not use the topic perms as the test if a member can edit/delete the comments? - User posting the comments can edit/delete for a configurable timelimit and not after that. - if SEC_inGroup('Root') or SEC_inGroup('Topic_Group_Edit') or SEC_inGroup(Topic_Owner) then edit/delete I would think that we would not need a comment admin and a topic admin. If comments are not in a topic,then they are part of a plugin which we call a PLG_checkCommentAdminRights() where the plugin author can have basic perm tests or more complex as need. Even for stories - maybe use a wrapper function that could later be appended if the topicAdmin perm is not sufficient. Then you don't need to store gorup perms per comment - just comment_owner_uid Blaine Michael Jervis wrote: > Jared and I are discussing permissions to edit comments in Geeklog for > the GSoC work he's doing. > > Firstly, I beleive the requirement is for users to be able to edit > their own comments, and for administrators to be able to edit users > comments subject to security permissions. > > So, I've said the following: > > >>> Geeklog uses unix style permissions. Everything with permissions on it >>> has an owner and a group. Then there are permissions for owner, group >>> and anonymous users. >>> >>> A comment should be saved with the owner_id being the id of the user >>> who created it, if authenticated. I don't think we already have one, >>> but a group of comment moderators or something might be needed. >>> Comments would then be saved with perm_owner allowing edits and >>> perm_group allowing edits. Then administrators can be given edit >>> permissions to comments by assigning them the comment moderator group, >>> and users can edit their own comments. Anonymous should just have read >>> permissions of course. >>> > > Jared's response: > > >> Does this mean add these rows to the comment table and save this default >> data each time a comment is submitted? >> > > I think the answer to this is yes, comments will now need to have the > standard permissions columns which will have to be set when a comment > is saved by a user automatically. > > >> Are there instances where individual >> comment permissions would change? >> > > But, would we want the administrator to be able to change the > permissions mask as they can with stories? So, if a user edits a > comment, a moderator edits a piece out and the user edits it back in, > the administrator can change it such that the user can no longer edit > it? (Perm_owner read only) > > And I would assume we'd default existing comments on mature sites to > owner_id of the user who posted the comment, or root if it was > anonymous, and perm_owner to read only as with perm_group and > perm_anon? > > >> Currently I have something like this this >> with the comment moderator group having rights to the feature 'comment.edit' >> : >> >> if ( $_USER['uid'] == $A['uid'] && $_CONF['comment_edit'] == 1 >> && (time() - $A['nice_date']) < $_CONF['comment_edittime']) { >> $edit_option = true; >> } else if (SEC_hasRights( 'comment.edit' ) ) { >> $edit_option = true; >> } else { >> $edit_option = false; >> } >> > > Having seen this from Jared, I'm half re-canting my earlier comment: > > >>> Then administrators can be given edit >>> permissions to comments by assigning them the comment moderator group, >>> > > I guess the group would actually be the group of the user who posted > the comment (logged in users most likely) and the group permission > would be read only. And Jared is right, Administrators/Moderators > would need the comment.edit permission to edit a users comment, which > would include the editing of the permissions mask to prevent the owner > re-editing the comment (assuming that owner wasn't a comment.edit user > too of course). > > Does that make sense and cover all the use-cases people can see? Where > are the obvious glaring gaps I've left in as a deliberate mistake? ;-) > > Cheers, > > Mike > > From mjervis at gmail.com Thu Jun 5 07:57:54 2008 From: mjervis at gmail.com (Michael Jervis) Date: Thu, 5 Jun 2008 12:57:54 +0100 Subject: [geeklog-devel] GSoC - Comments - Edit - Permissions In-Reply-To: References: <7b42e7470806050052o4acdfbfas9d31ef0084765eb8@mail.gmail.com> Message-ID: <7b42e7470806050457m2cea3d90v828fc6a875122e3c@mail.gmail.com> > Why not use the topic perms as the test if a member can edit/delete the > comments? For administrative edit of users comments, that might be good, but, what if you want to have "Moderators" who can only edit comments. So if you have a big site, with editors/authors writing the main posts, but community moderators editing/deleting the dodgy comments out? > I would think that we would not need a comment admin and a topic admin. > If comments are not in a topic,then they are part of a plugin which we call > a PLG_checkCommentAdminRights() where the plugin author can have basic perm > tests or more complex as need. Yes, would need to implement that either way, because you might not want comment.edit to apply globally to comments in plugins. > Then you don't need to store gorup perms per comment - just > comment_owner_uid But to allow a user to edit their comment, don't you also need comment_owner_perm so that you can have a system that allows users to edit their comments and one that doesn't. And if you have "comment aging" on the editability (i.e. you can edit for the first 20 minutes) it that perm can be expired by time also? Mike From devel at portalparts.com Thu Jun 5 09:33:04 2008 From: devel at portalparts.com (Blaine Lang) Date: Thu, 05 Jun 2008 09:33:04 -0400 Subject: [geeklog-devel] GSoC - Comments - Edit - Permissions In-Reply-To: <7b42e7470806050457m2cea3d90v828fc6a875122e3c@mail.gmail.com> References: <7b42e7470806050052o4acdfbfas9d31ef0084765eb8@mail.gmail.com> <7b42e7470806050457m2cea3d90v828fc6a875122e3c@mail.gmail.com> Message-ID: Michael Jervis wrote: > For administrative edit of users comments, that might be good, but, what if you want to have "Moderators" who can only edit comments. So if you have a big site, with editors/authors writing the main posts, but community moderators editing/deleting the dodgy comments out? Do we need that? Maybe we need to look at what if storyEditor was a plugin. I would probably add a comment moderator right to a topic. So topics could be extended to have comment moderator permission. Atleast this way we don't need to be checking or storing perms for each comment record. > But to allow a user to edit their comment, don't you also need comment_owner_perm so that you can have a system that allows users to edit their comments and one that doesn't. And if you have "comment aging" on the editability (i.e. you can edit for the first 20 minutes) it that perm can be expired by time also? I think we were saying the same think. Just need to store comment owner UID and if the owner and within the allowable edit window then the edit/delete link appears. The forum does that now for example. Blaine From dirk at haun-online.de Thu Jun 5 15:15:27 2008 From: dirk at haun-online.de (Dirk Haun) Date: Thu, 5 Jun 2008 21:15:27 +0200 Subject: [geeklog-devel] GSoC - Comments - Edit - Permissions In-Reply-To: References: <7b42e7470806050052o4acdfbfas9d31ef0084765eb8@mail.gmail.com> <7b42e7470806050457m2cea3d90v828fc6a875122e3c@mail.gmail.com> Message-ID: <20080605191527.1866676738@smtp.haun-online.de> Blaine Lang wrote: >>what if you want to have "Moderators" who can only edit comments. >Do we need that? I guess sites with a lot of comments would love that. Think Groklaw. >>And if you have "comment >>aging" on the editability (i.e. you can edit for the first 20 minutes) >>it that perm can be expired by time also? If there was such a permission, I wouldn't change it but always check against the time. Makes it easier to disable/extend the "edit window" later. bye, Dirk -- http://www.haun-online.de/ http://spam.tinyweb.net/ From dirk at haun-online.de Thu Jun 5 15:22:14 2008 From: dirk at haun-online.de (Dirk Haun) Date: Thu, 5 Jun 2008 21:22:14 +0200 Subject: [geeklog-devel] GSoC - Comments - Edit - Permissions In-Reply-To: <7b42e7470806050052o4acdfbfas9d31ef0084765eb8@mail.gmail.com> References: <7b42e7470806050052o4acdfbfas9d31ef0084765eb8@mail.gmail.com> Message-ID: <20080605192214.129720873@smtp.haun-online.de> Michael Jervis wrote: >>> I don't think we already have one, >>> but a group of comment moderators or something might be needed. Currently, if you have edit permissions for the story, you can also edit (well, delete) the comments. But I agree, a Comment Moderator role would be cleaner. >I think the answer to this is yes, comments will now need to have the >standard permissions columns which will have to be set when a comment >is saved by a user automatically. Wouldn't all comments have the same permissions? Or, to put it the other way around: How would you end up with two comments under the same story having different permissions? >But, would we want the administrator to be able to change the >permissions mask as they can with stories? So, if a user edits a >comment, a moderator edits a piece out and the user edits it back in, >the administrator can change it such that the user can no longer edit >it? (Perm_owner read only) Edit wars? Phew, hadn't thought of that. I guess Wikipedia shows that there's no good solution to that ... bye, Dirk -- http://www.haun-online.de/accu/ From eakwarren at gmail.com Thu Jun 5 17:33:32 2008 From: eakwarren at gmail.com (Eric Warren) Date: Thu, 5 Jun 2008 15:33:32 -0600 Subject: [geeklog-devel] Topic Admin inconsistencies Message-ID: I've noticed that most of the Admin screens render with a "centerblock" of sorts with an icon and Create New and Admin Home links, and a description in them. Below that box is bold text, for example Calendar Manager, Group Manager, Link Manager, Plugin List, etc. and then whatever config or administration options according to that section. However, the Topics Admin block is inconsistent, rendering the bold text Topic Manager on top, and then the "centerblock" below it. I've looked in admin/topic.php and in layout/professional/admin/topic/ but can't seem to find where to fix it. I'm probably missing something obvious though. Can this layout inconsistency be fixed in CVS? Thx! Eric -------------- next part -------------- An HTML attachment was scrubbed... URL: From dirk at haun-online.de Fri Jun 6 01:56:28 2008 From: dirk at haun-online.de (Dirk Haun) Date: Fri, 6 Jun 2008 07:56:28 +0200 Subject: [geeklog-devel] Topic Admin inconsistencies In-Reply-To: References: Message-ID: <20080606055628.99891075@smtp.haun-online.de> Eric Warren wrote: >However, the Topics Admin block is inconsistent, rendering the bold text >Topic Manager on top, and then the "centerblock" below it. bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ From dirk at haun-online.de Mon Jun 9 15:27:35 2008 From: dirk at haun-online.de (Dirk Haun) Date: Mon, 9 Jun 2008 21:27:35 +0200 Subject: [geeklog-devel] Mercurial, first impressions Message-ID: <20080609192735.271175183@smtp.haun-online.de> On the topic of using a DVCS for the SoC (and possibly later, as a replacement for CVS): I've started playing around with Mercurial. I converted a copy of the 1.5.0rc2 CVS repository to a Mercurial repository, which was painless (apart from getting to install a few Ruby extensions that the converter needed). Mercurial (and DVCS in general) really has some nice ideas built in: - The repository and working copy are all in one directory and its all selfcontained. So you can move it around, check things in without an internet connection, create more clones from your local copy. Then, later, push your changes back to the main repository (if there is such a thing - doesn't have to). - Mercurial at least has a webserver built in. Run "hg serve" and you have a simple equivalent of the CVS viewer we're using. - As with the webserver, you can easily and temporarily share your repository. Just tell someone how the get to your repository and they can clone it. Works via http and ssh. - Pushing changes back requires an account and ssh. I think this would work really well for the SoC. A mentor could pull the changes directly from a student. Students can show off what they have at any time: Hop on IRC, give temp. URL of repository, let mentor or someone else pull things from there. Note that I haven't really done too much real work with it yet. I did the conversion yesterday, pulled a copy from my machine at home to the one at work today, made a change there and pushed it back. This only involved http and ssh connections and worked through a firewall. No fancy running of a daemon on some port. Still need to wrap my head around some of the concepts, but so far I'm impressed. I'll keep you posted ... bye, Dirk -- http://www.haun-online.de/ http://spam.tinyweb.net/ From tony at tonybibbs.com Thu Jun 12 12:37:06 2008 From: tony at tonybibbs.com (Tony Bibbs) Date: Thu, 12 Jun 2008 09:37:06 -0700 (PDT) Subject: [geeklog-devel] Time to rebrand 2.x Message-ID: <808725.74572.qm@web702.biz.mail.mud.yahoo.com> Following the discussion on the challenges with the Geeklog "brand" from a few weeks ago it was pretty much decided not to do anything with 1.x and if we were going to rename things do it for 2.x. To prevent a bunch of back-and-forth on it some of us GL2 devs have been tossing around ideas on a name and landed on Aptitude. Surely any name we'd come up with be liked by some, hated by others. As we prepare for this alpha we are going to go through the process of rebranding everything to use that name. This has zero impact on 1.x but quite a bit on 2.x (domains, URL's, class name changes, etc). When we do release the alpha we'll want to dig into gl.net and make changes accordingly (I'm fine owning this). I just wanted to float this out to give you all plenty of time to chew on it and submit any grievances. To that end the trac site and wiki for it has already been setup at: http://www.apteno.net/aptitude/trac --Tony From macosx at rocteur.cc Thu Jun 12 12:41:35 2008 From: macosx at rocteur.cc (Jerry Rocteur) Date: Thu, 12 Jun 2008 18:41:35 +0200 Subject: [geeklog-devel] Time to rebrand 2.x In-Reply-To: <808725.74572.qm@web702.biz.mail.mud.yahoo.com> References: <808725.74572.qm@web702.biz.mail.mud.yahoo.com> Message-ID: <20080612164134.GA20000@incc-g5.telenet.be> * Tony Bibbs [2008-06-12 18:38]: > Following the discussion on the challenges with the Geeklog "brand" from a few weeks ago it was pretty much decided not to do anything with 1.x and if we were going to rename things do it for 2.x. To prevent a bunch of back-and-forth on it some of us GL2 devs have been tossing around ideas on a name and landed on Aptitude. Surely any name we'd come up with be liked by some, hated by others. As we prepare for this alpha we are going to go through the process of rebranding everything to use that name. This has zero impact on 1.x but quite a bit on 2.x (domains, URL's, class name changes, etc). > > When we do release the alpha we'll want to dig into gl.net and make changes accordingly (I'm fine owning this). I just wanted to float this out to give you all plenty of time to chew on it and submit any grievances. > > To that end the trac site and wiki for it has already been setup at: > > http://www.apteno.net/aptitude/trac > > --Tony Hi, Are you sure you want to call it something that is already well known to Linux people ? http://en.wikipedia.org/wiki/Aptitude_(program) -- _ Jerry Rocteur MACosX at rocteur.CC _|_|_ http://www.rocteur.cc (0 0) MSN macosx at rocteur.cc ooO--(_)--Ooo Jabber jerry at jabber.rocteur.cc _________________________________________________ [06:23:57 rocteur.cc /Users/jerry] From tony at tonybibbs.com Thu Jun 12 12:47:35 2008 From: tony at tonybibbs.com (Tony Bibbs) Date: Thu, 12 Jun 2008 09:47:35 -0700 (PDT) Subject: [geeklog-devel] Time to rebrand 2.x Message-ID: <423947.11989.qm@web704.biz.mail.mud.yahoo.com> Yep, as long as we don't call it "apt" and market the launch with "apt-get". --Tony ----- Original Message ---- From: Jerry Rocteur To: Geeklog Development Sent: Thursday, June 12, 2008 11:41:35 AM Subject: Re: [geeklog-devel] Time to rebrand 2.x * Tony Bibbs [2008-06-12 18:38]: > Following the discussion on the challenges with the Geeklog "brand" from a few weeks ago it was pretty much decided not to do anything with 1.x and if we were going to rename things do it for 2.x. To prevent a bunch of back-and-forth on it some of us GL2 devs have been tossing around ideas on a name and landed on Aptitude. Surely any name we'd come up with be liked by some, hated by others. As we prepare for this alpha we are going to go through the process of rebranding everything to use that name. This has zero impact on 1.x but quite a bit on 2.x (domains, URL's, class name changes, etc). > > When we do release the alpha we'll want to dig into gl.net and make changes accordingly (I'm fine owning this). I just wanted to float this out to give you all plenty of time to chew on it and submit any grievances. > > To that end the trac site and wiki for it has already been setup at: > > http://www.apteno.net/aptitude/trac > > --Tony Hi, Are you sure you want to call it something that is already well known to Linux people ? http://en.wikipedia.org/wiki/Aptitude_(program) -- _ Jerry Rocteur MACosX at rocteur.CC _|_|_ http://www.rocteur.cc (0 0) MSN macosx at rocteur.cc ooO--(_)--Ooo Jabber jerry at jabber.rocteur.cc _________________________________________________ [06:23:57 rocteur.cc /Users/jerry] _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From dracul01 at gmail.com Thu Jun 12 15:12:44 2008 From: dracul01 at gmail.com (Damien Hodgkin) Date: Thu, 12 Jun 2008 15:12:44 -0400 Subject: [geeklog-devel] Time to rebrand 2.x In-Reply-To: <423947.11989.qm@web704.biz.mail.mud.yahoo.com> References: <423947.11989.qm@web704.biz.mail.mud.yahoo.com> Message-ID: <200806121512.48469.dracul01@gmail.com> On Thursday 12 June 2008 12:47:35 pm Tony Bibbs wrote: > Yep, as long as we don't call it "apt" and market the launch with > "apt-get". > > --Tony > > ----- Original Message ---- > From: Jerry Rocteur > To: Geeklog Development > Sent: Thursday, June 12, 2008 11:41:35 AM > Subject: Re: [geeklog-devel] Time to rebrand 2.x > > * Tony Bibbs [2008-06-12 18:38]: > > Following the discussion on the challenges with the Geeklog "brand" from > > a few weeks ago it was pretty much decided not to do anything with 1.x > > and if we were going to rename things do it for 2.x. To prevent a bunch > > of back-and-forth on it some of us GL2 devs have been tossing around > > ideas on a name and landed on Aptitude. Surely any name we'd come up > > with be liked by some, hated by others. As we prepare for this alpha we > > are going to go through the process of rebranding everything to use that > > name. This has zero impact on 1.x but quite a bit on 2.x (domains, > > URL's, class name changes, etc). > > > > When we do release the alpha we'll want to dig into gl.net and make > > changes accordingly (I'm fine owning this). I just wanted to float this > > out to give you all plenty of time to chew on it and submit any > > grievances. > > > > To that end the trac site and wiki for it has already been setup at: > > > > http://www.apteno.net/aptitude/trac > > > > --Tony > > Hi, > > Are you sure you want to call it something that is already well known to > Linux people ? > > http://en.wikipedia.org/wiki/Aptitude_(program) I myself feel the rebranding of 2.x has been long overdue. And it will open up all new possibilities for it. The fact that 2.x shares absolutely no code with GL1.x makes the rebranding much easier. And also allows for GL1.x to progress toward it's *own* 2.x release. -- Best Regards, Damien ------------- "To see the world in a grain of sand, and to see heaven in a wild flower, hold infinity in the palm of your hands, and eternity in an hour." - William Blake -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 194 bytes Desc: This is a digitally signed message part. URL: From macosx at rocteur.cc Thu Jun 12 16:10:57 2008 From: macosx at rocteur.cc (@ Rocteur CC) Date: Thu, 12 Jun 2008 22:10:57 +0200 Subject: [geeklog-devel] Time to rebrand 2.x In-Reply-To: <200806121512.48469.dracul01@gmail.com> References: <423947.11989.qm@web704.biz.mail.mud.yahoo.com> <200806121512.48469.dracul01@gmail.com> Message-ID: <11E32CF9-5C0F-4919-A4B4-BE805A9340C4@rocteur.cc> On 12 Jun 2008, at 21:12, Damien Hodgkin wrote: > On Thursday 12 June 2008 12:47:35 pm Tony Bibbs wrote: >> Yep, as long as we don't call it "apt" and market the launch with >> "apt-get". >> >> --Tony >> >> ----- Original Message ---- >> From: Jerry Rocteur >> To: Geeklog Development >> Sent: Thursday, June 12, 2008 11:41:35 AM >> Subject: Re: [geeklog-devel] Time to rebrand 2.x >> >> * Tony Bibbs [2008-06-12 18:38]: >>> Following the discussion on the challenges with the Geeklog >>> "brand" from >>> a few weeks ago it was pretty much decided not to do anything >>> with 1.x >>> and if we were going to rename things do it for 2.x. To prevent >>> a bunch >>> of back-and-forth on it some of us GL2 devs have been tossing around >>> ideas on a name and landed on Aptitude. Surely any name we'd >>> come up >>> with be liked by some, hated by others. As we prepare for this >>> alpha we >>> are going to go through the process of rebranding everything to >>> use that >>> name. This has zero impact on 1.x but quite a bit on 2.x (domains, >>> URL's, class name changes, etc). >>> >>> When we do release the alpha we'll want to dig into gl.net and make >>> changes accordingly (I'm fine owning this). I just wanted to >>> float this >>> out to give you all plenty of time to chew on it and submit any >>> grievances. >>> >>> To that end the trac site and wiki for it has already been setup at: >>> >>> http://www.apteno.net/aptitude/trac >>> >>> --Tony >> >> Hi, >> >> Are you sure you want to call it something that is already well >> known to >> Linux people ? >> >> http://en.wikipedia.org/wiki/Aptitude_(program) > > I myself feel the rebranding of 2.x has been long overdue. And it > will open up > all new possibilities for it. > > The fact that 2.x shares absolutely no code with GL1.x makes the > rebranding > much easier. And also allows for GL1.x to progress toward it's > *own* 2.x > release. > I agree, I just don't agree that aptitude is a good name and I think Tony's answer is as funny as he is! Cheers, Jerry -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2417 bytes Desc: not available URL: From tony at tonybibbs.com Thu Jun 12 16:33:55 2008 From: tony at tonybibbs.com (Tony Bibbs) Date: Thu, 12 Jun 2008 13:33:55 -0700 (PDT) Subject: [geeklog-devel] Time to rebrand 2.x Message-ID: <171908.96723.qm@web703.biz.mail.mud.yahoo.com> Yeah, the name thing would be akin to UI/CSS design discussions we've all been in where we can't make everybody happy because one person wants padding-left to be 3px and someone else prefers 8px. That said the people working with it everyday agreed it was a good name. In the end you can find something wrong with every name you come up with...nothing is original. Google reminds me of that everyday. --Tony ----- Original Message ---- From: "@ Rocteur CC" To: Geeklog Development Sent: Thursday, June 12, 2008 3:10:57 PM Subject: Re: [geeklog-devel] Time to rebrand 2.x On 12 Jun 2008, at 21:12, Damien Hodgkin wrote: > On Thursday 12 June 2008 12:47:35 pm Tony Bibbs wrote: >> Yep, as long as we don't call it "apt" and market the launch with >> "apt-get". >> >> --Tony >> >> ----- Original Message ---- >> From: Jerry Rocteur >> To: Geeklog Development >> Sent: Thursday, June 12, 2008 11:41:35 AM >> Subject: Re: [geeklog-devel] Time to rebrand 2.x >> >> * Tony Bibbs [2008-06-12 18:38]: >>> Following the discussion on the challenges with the Geeklog >>> "brand" from >>> a few weeks ago it was pretty much decided not to do anything >>> with 1.x >>> and if we were going to rename things do it for 2.x. To prevent >>> a bunch >>> of back-and-forth on it some of us GL2 devs have been tossing around >>> ideas on a name and landed on Aptitude. Surely any name we'd >>> come up >>> with be liked by some, hated by others. As we prepare for this >>> alpha we >>> are going to go through the process of rebranding everything to >>> use that >>> name. This has zero impact on 1.x but quite a bit on 2.x (domains, >>> URL's, class name changes, etc). >>> >>> When we do release the alpha we'll want to dig into gl.net and make >>> changes accordingly (I'm fine owning this). I just wanted to >>> float this >>> out to give you all plenty of time to chew on it and submit any >>> grievances. >>> >>> To that end the trac site and wiki for it has already been setup at: >>> >>> http://www.apteno.net/aptitude/trac >>> >>> --Tony >> >> Hi, >> >> Are you sure you want to call it something that is already well >> known to >> Linux people ? >> >> http://en.wikipedia.org/wiki/Aptitude_(program) > > I myself feel the rebranding of 2.x has been long overdue. And it > will open up > all new possibilities for it. > > The fact that 2.x shares absolutely no code with GL1.x makes the > rebranding > much easier. And also allows for GL1.x to progress toward it's > *own* 2.x > release. > I agree, I just don't agree that aptitude is a good name and I think Tony's answer is as funny as he is! Cheers, Jerry From nick at nick-andrew.net Thu Jun 12 21:55:47 2008 From: nick at nick-andrew.net (Nick Andrew) Date: Fri, 13 Jun 2008 11:55:47 +1000 Subject: [geeklog-devel] Time to rebrand 2.x In-Reply-To: <171908.96723.qm@web703.biz.mail.mud.yahoo.com> References: <171908.96723.qm@web703.biz.mail.mud.yahoo.com> Message-ID: <20080613015547.GA16600@tull.net> On Thu, Jun 12, 2008 at 01:33:55PM -0700, Tony Bibbs wrote: > Yeah, the name thing would be akin to UI/CSS design discussions > we've all been in where we can't make everybody happy because one > person wants padding-left to be 3px and someone else prefers 8px. > That said the people working with it everyday agreed it was a > good name. In the end you can find something wrong with every > name you come up with...nothing is original. Google reminds me of > that everyday. If you call it 'a p t i g e e k' (without the spaces), that would be unique. Zero hits on it in google, compared to over 1 million for 'aptitude'. And it's still only 8 letters long. And the .com/.net/.org domain names are available. Nick. -- PGP Key ID = 0x418487E7 http://www.nick-andrew.net/ PGP Key fingerprint = B3ED 6894 8E49 1770 C24A 67E3 6266 6EB9 4184 87E7 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From dirk at haun-online.de Fri Jun 13 01:56:04 2008 From: dirk at haun-online.de (Dirk Haun) Date: Fri, 13 Jun 2008 07:56:04 +0200 Subject: [geeklog-devel] Time to rebrand 2.x In-Reply-To: <20080613015547.GA16600@tull.net> References: <171908.96723.qm@web703.biz.mail.mud.yahoo.com> <20080613015547.GA16600@tull.net> Message-ID: <20080613055604.81241993@smtp.haun-online.de> Nick Andrew wrote: >Zero hits on it in google, compared to over 1 million for >'aptitude'. Trying to get rid of the "geek" bit was actually one of the goals of the renaming attempt, if I remember the previous discussions correctly. The current trend seems to be to go with African names. For example, the CMS formerly known as PostNuke has just been renamed to Zikula. bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ From tony at tonybibbs.com Fri Jun 13 09:19:24 2008 From: tony at tonybibbs.com (Tony Bibbs) Date: Fri, 13 Jun 2008 06:19:24 -0700 (PDT) Subject: [geeklog-devel] Time to rebrand 2.x Message-ID: <43282.5668.qm@web701.biz.mail.mud.yahoo.com> Sorry, let me be a bit more clear. We chose a name for this exact reason...to avoid a bunch of subjective back-and-forth that will only assuredly result in a case where it will be impossible to make everyone happy. My original note was simply to inform everybody of the name chosen and look for any violent disagreement. Short of that we'll proceed with the new name. Thanks, --Tony ----- Original Message ---- From: Nick Andrew To: Geeklog Development Sent: Thursday, June 12, 2008 8:55:47 PM Subject: Re: [geeklog-devel] Time to rebrand 2.x On Thu, Jun 12, 2008 at 01:33:55PM -0700, Tony Bibbs wrote: > Yeah, the name thing would be akin to UI/CSS design discussions > we've all been in where we can't make everybody happy because one > person wants padding-left to be 3px and someone else prefers 8px. > That said the people working with it everyday agreed it was a > good name. In the end you can find something wrong with every > name you come up with...nothing is original. Google reminds me of > that everyday. If you call it 'a p t i g e e k' (without the spaces), that would be unique. Zero hits on it in google, compared to over 1 million for 'aptitude'. And it's still only 8 letters long. And the .com/.net/.org domain names are available. Nick. -- PGP Key ID = 0x418487E7 http://www.nick-andrew.net/ PGP Key fingerprint = B3ED 6894 8E49 1770 C24A 67E3 6266 6EB9 4184 87E7 From mevans at ecsnet.com Sat Jun 14 23:56:52 2008 From: mevans at ecsnet.com (Mark R. Evans) Date: Sat, 14 Jun 2008 22:56:52 -0500 Subject: [geeklog-devel] Multi Language Support in 1.5 Message-ID: <48549304.10608@ecsnet.com> I was reading the wiki on multi-language support and I can't see how it is supported in v1.5... The wiki states: If you're using the ISO abbreviation 'de' for German, then you could have the following in your site's config.php: $_CONF['date'] = '%A, %B %d %Y @ %I:%M %p %Z'; $_CONF['date_de'] = '%A, %d. %B %Y, %R Uhr'; With these two lines, Geeklog would use the 'date_de' formatting when displaying content in German, and the 'date' formatting for all the other languages. Actually, for this to work properly, you will also have to set |$_CONF['locale']| and |$_CONF['locale_de']| accordingly, since some of the date formatting (localized day and month names) requires the correct locale to be set: $_CONF['locale'] = 'en_GB'; $_CONF['locale_de'] = 'de_DE'; How do you define the _de versions of date and locale using the new online configuration? Or will these entries have to go into the siteconfig.php? Thanks! Mark From mjervis at gmail.com Sun Jun 15 03:38:01 2008 From: mjervis at gmail.com (Michael Jervis) Date: Sun, 15 Jun 2008 08:38:01 +0100 Subject: [geeklog-devel] Mercurial, first impressions In-Reply-To: <20080609192735.271175183@smtp.haun-online.de> References: <20080609192735.271175183@smtp.haun-online.de> Message-ID: <7b42e7470806150038n24f33b07x59bea6ae6a6077ed@mail.gmail.com> > I'll keep you posted ... Sounds great. Can you point me at any stuff you read to enable you to do this? I'm thinking of trying it to solve some issues at work, where we do not permit a commit to the repository without full testing and Change Control sign off. Which is causing a problem due to the scale of some of our new feature developments meaning there's huge merge issues when they're ready to commit. By the time they've sorted the merge, it all needs to go through testing again... From dirk at haun-online.de Sun Jun 15 03:54:52 2008 From: dirk at haun-online.de (Dirk Haun) Date: Sun, 15 Jun 2008 09:54:52 +0200 Subject: [geeklog-devel] Multi Language Support in 1.5 In-Reply-To: <48549304.10608@ecsnet.com> References: <48549304.10608@ecsnet.com> Message-ID: <20080615075452.1587606564@smtp.haun-online.de> Mark R. Evans wrote: >I was reading the wiki on multi-language support and I can't see how it >is supported in v1.5... Right, thanks for the reminder. I've only discovered this myself on Friday and promptly forgot about it again ... Big fat oversight, no other way of putting it. >How do you define the _de versions of date and locale using the new >online configuration? You can't. >Or will these entries have to go into the siteconfig.php? Yep, that's what you will have to do for now. Oh well, another item on the to-do list for 1.5.1. bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ From dirk at haun-online.de Sun Jun 15 04:31:45 2008 From: dirk at haun-online.de (Dirk Haun) Date: Sun, 15 Jun 2008 10:31:45 +0200 Subject: [geeklog-devel] Mercurial, first impressions In-Reply-To: <7b42e7470806150038n24f33b07x59bea6ae6a6077ed@mail.gmail.com> References: <20080609192735.271175183@smtp.haun-online.de> <7b42e7470806150038n24f33b07x59bea6ae6a6077ed@mail.gmail.com> Message-ID: <20080615083145.1671857219@smtp.haun-online.de> Michael Jervis wrote: >Sounds great. Can you point me at any stuff you read to enable you to do this? The Mercurial wiki has quite a few How-To articles (some of them are a bit hidden - try going through the FAQ, TipsAndTricks, and HOWTO pages). http://www.selenic.com/mercurial/wiki/ >By the time they've sorted the merge, it all >needs to go through testing again... Is that even solvable? Strictly speaking, you would have to go through testing again after every change to the software, as it could have side effects. Unless you can demonstrate that the changes are truly separate, which is mostly determined by your architecture. And any VCS can be used to get a list of the changes to compare against that architecture. Or maybe I didn't understand what you're after ... bye, Dirk -- http://www.haun-online.de/accu/ From tony at tonybibbs.com Sun Jun 15 16:32:59 2008 From: tony at tonybibbs.com (Tony Bibbs) Date: Sun, 15 Jun 2008 13:32:59 -0700 (PDT) Subject: [geeklog-devel] FYI Message-ID: <3725.94473.qm@web706.biz.mail.mud.yahoo.com> Just in case some of you have been living under a rock, here in Iowa we are dealing with severe floods. Geeklog is getting some good press as we setup a new Geeklog 1.4 site that was featured today at the following press conference: mms://video.flood2008.iowa.gov/flood2008/080615_update.wmv For those who can't view .wmv's the site is http://flood2008.iowa.gov. --Tony From trinity93 at gmail.com Sun Jun 15 23:00:26 2008 From: trinity93 at gmail.com (Trinity) Date: Sun, 15 Jun 2008 22:00:26 -0500 Subject: [geeklog-devel] FYI In-Reply-To: <3725.94473.qm@web706.biz.mail.mud.yahoo.com> References: <3725.94473.qm@web706.biz.mail.mud.yahoo.com> Message-ID: would be nice if the site said it was running on geeklog On Sun, Jun 15, 2008 at 3:32 PM, Tony Bibbs wrote: > Just in case some of you have been living under a rock, here in Iowa we are dealing with severe floods. Geeklog is getting some good press as we setup a new Geeklog 1.4 site that was featured today at the following press conference: > > mms://video.flood2008.iowa.gov/flood2008/080615_update.wmv > > For those who can't view .wmv's the site is http://flood2008.iowa.gov. > > --Tony > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > From mjervis at gmail.com Mon Jun 16 04:02:18 2008 From: mjervis at gmail.com (Michael Jervis) Date: Mon, 16 Jun 2008 09:02:18 +0100 Subject: [geeklog-devel] FYI In-Reply-To: <3725.94473.qm@web706.biz.mail.mud.yahoo.com> References: <3725.94473.qm@web706.biz.mail.mud.yahoo.com> Message-ID: <7b42e7470806160102p228dff4dhafba0d5841ac6284@mail.gmail.com> > Just in case some of you have been living under a rock, Or perhaps in another country... From dirk at haun-online.de Mon Jun 16 13:44:39 2008 From: dirk at haun-online.de (Dirk Haun) Date: Mon, 16 Jun 2008 19:44:39 +0200 Subject: [geeklog-devel] Server upgrades, part 1 Message-ID: <20080616174439.77235538@smtp.haun-online.de> So the first round of the planned server upgrades is done. Let me know if anything on www.geeklog.net or the project site isn't working as expected. The bugtracker isn't running at the moment - this is already being looked into. Anything else? bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ From dirk at haun-online.de Mon Jun 16 16:56:20 2008 From: dirk at haun-online.de (Dirk Haun) Date: Mon, 16 Jun 2008 22:56:20 +0200 Subject: [geeklog-devel] Server upgrades, part 1 In-Reply-To: <20080616174439.77235538@smtp.haun-online.de> References: <20080616174439.77235538@smtp.haun-online.de> Message-ID: <20080616205620.937521267@smtp.haun-online.de> Dirk Haun wrote: >The bugtracker isn't running at the moment It's back up. Everything else seems to be working fine too, from what I can see. Let me know if you find anything. I've also activated the Webservices now on geeklog.net. Although it seems that only 5 people (those with Story Admin or Static Pages Admin rights) will actually be able to use it ... bye, Dirk -- http://www.haun-online.de/ http://spam.tinyweb.net/ From dirk at haun-online.de Tue Jun 17 12:45:12 2008 From: dirk at haun-online.de (Dirk Haun) Date: Tue, 17 Jun 2008 18:45:12 +0200 Subject: [geeklog-devel] Server upgrades, part 2 In-Reply-To: <20080616174439.77235538@smtp.haun-online.de> References: <20080616174439.77235538@smtp.haun-online.de> Message-ID: <20080617164512.1787125625@smtp.haun-online.de> Second round of server maintenance is also done. Anyone notice any differences? bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ From mark at the-howards.net Tue Jun 17 14:01:14 2008 From: mark at the-howards.net (Mark Howard) Date: Tue, 17 Jun 2008 14:01:14 -0400 Subject: [geeklog-devel] Server upgrades, part 2 In-Reply-To: <20080617164512.1787125625@smtp.haun-online.de> References: <20080616174439.77235538@smtp.haun-online.de> <20080617164512.1787125625@smtp.haun-online.de> Message-ID: <14ff01c8d0a4$22fb07f0$68f117d0$@net> Yes - it seems to be a bit quicker ... -m -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Dirk Haun Sent: Tuesday, June 17, 2008 12:45 PM To: geeklog-devel Subject: Re: [geeklog-devel] Server upgrades, part 2 Second round of server maintenance is also done. Anyone notice any differences? bye, Dirk From devel at portalparts.com Tue Jun 17 14:04:01 2008 From: devel at portalparts.com (Blaine Lang) Date: Tue, 17 Jun 2008 14:04:01 -0400 Subject: [geeklog-devel] Server upgrades, part 2 In-Reply-To: <20080617164512.1787125625@smtp.haun-online.de> References: <20080616174439.77235538@smtp.haun-online.de> <20080617164512.1787125625@smtp.haun-online.de> Message-ID: Yes - much faster! Blaine Dirk Haun wrote: > Second round of server maintenance is also done. Anyone notice any > differences? > > bye, Dirk > > > From dirk at haun-online.de Tue Jun 17 16:49:39 2008 From: dirk at haun-online.de (Dirk Haun) Date: Tue, 17 Jun 2008 22:49:39 +0200 Subject: [geeklog-devel] Server upgrades, part 2 In-Reply-To: References: <20080616174439.77235538@smtp.haun-online.de> <20080617164512.1787125625@smtp.haun-online.de> Message-ID: <20080617204939.1545774060@smtp.haun-online.de> Blaine Lang wrote: >Yes - much faster! Good, that's what I wanted to hear :) bye, Dirk -- http://www.haun-online.de/ http://geeklog.info/ From dirk at haun-online.de Wed Jun 18 14:07:50 2008 From: dirk at haun-online.de (Dirk Haun) Date: Wed, 18 Jun 2008 20:07:50 +0200 Subject: [geeklog-devel] Bug when approving story submissions? Message-ID: <20080618180750.673610409@smtp.haun-online.de> Interesting effect: I just approved two story submissions on geeklog.net. In both cases, I edited the story. One of the stories left a duplicate in the submission queue. For the other story, it worked as expected. Not sure what the difference was between the two. First one to come up with a reproducible case, please submit a bug report ... bye, Dirk -- http://www.haun-online.de/accu/ From mevans at ecsnet.com Wed Jun 18 15:48:05 2008 From: mevans at ecsnet.com (Mark R. Evans) Date: Wed, 18 Jun 2008 14:48:05 -0500 Subject: [geeklog-devel] Bug when approving story submissions? In-Reply-To: <20080618180750.673610409@smtp.haun-online.de> References: <20080618180750.673610409@smtp.haun-online.de> Message-ID: <50aae8730806181248v5cdb3654ude62777af7c28004@mail.gmail.com> Dirk, Did you change the story id on one of the stories? Looking at story.class.php, near line 667, you have: if ($this->type == 'submission') { /* there might be a submission, clean it up */ DB_delete($_TABLES['storysubmission'], 'sid', $checksid); } I think part of the problem is that $checksid is only set when the original SID doesn't match the new SID (around line 584), so if you don't change the story ID, the entire submission queue could be deleted (since checksid = ''). How are edits in the submission queue supposed to work. It looks like now when you edit and save, it approves the story automatically. I don't recall how it worked in previous versions, but it would seem that the edit should save back to the submission table. Not sure what the proper method is... Thanks! Mark On Wed, Jun 18, 2008 at 1:07 PM, Dirk Haun wrote: > Interesting effect: I just approved two story submissions on > geeklog.net. In both cases, I edited the story. One of the stories left > a duplicate in the submission queue. For the other story, it worked as > expected. > > Not sure what the difference was between the two. > > First one to come up with a reproducible case, please submit a bug report > ... > > bye, Dirk > > > -- > http://www.haun-online.de/accu/ > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dirk at haun-online.de Wed Jun 18 17:02:28 2008 From: dirk at haun-online.de (Dirk Haun) Date: Wed, 18 Jun 2008 23:02:28 +0200 Subject: [geeklog-devel] Bug when approving story submissions? In-Reply-To: <50aae8730806181248v5cdb3654ude62777af7c28004@mail.gmail.com> References: <20080618180750.673610409@smtp.haun-online.de> <50aae8730806181248v5cdb3654ude62777af7c28004@mail.gmail.com> Message-ID: <20080618210228.501660619@smtp.haun-online.de> Mark R. Evans wrote: >Did you change the story id on one of the stories? That's probably it. I changed the sid on the glFusion article and it was properly deleted from the submission queue. I did not change the sid on the other article and it was duplicated. >How are edits in the submission queue supposed to work. It looks like now >when you edit and save, it approves the story automatically. That's how it's supposed to work (and it did for the last couple of years). If you don't want to publish the story just yet, use the draft flag. In the absence of a multi-stage approval process, that's the closest you can get to a "workflow" of sorts. Removing it from the submission queue at least shows that somebody has looked at the article already. bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ From dirk at haun-online.de Sat Jun 21 18:56:43 2008 From: dirk at haun-online.de (Dirk Haun) Date: Sun, 22 Jun 2008 00:56:43 +0200 Subject: [geeklog-devel] Time to rebrand 2.x In-Reply-To: <43282.5668.qm@web701.biz.mail.mud.yahoo.com> References: <43282.5668.qm@web701.biz.mail.mud.yahoo.com> Message-ID: <20080621225643.68443088@smtp.haun-online.de> Tony Bibbs wrote: >My original note was simply to inform everybody of the name >chosen and look for any violent disagreement. I'm still wondering if it isn't bad karma to knowingly choose the name of another open source project, even if that other project is mostly know by it's short name. I was just reminded of this when this post showed up in my feed reader: (via planet-soc.com) bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ From dirk at haun-online.de Sun Jun 22 14:25:08 2008 From: dirk at haun-online.de (Dirk Haun) Date: Sun, 22 Jun 2008 20:25:08 +0200 Subject: [geeklog-devel] The road ahead - post 1.5.0 Message-ID: <20080622182508.45447649@smtp.haun-online.de> Looking at the first bug reports that came in for 1.5.0, it's time to think about how we go from here. Here are my suggestions: I think for Geeklog 1.5.1 we should concentrate on fixing all those rough edges that we left in while rushing to push out 1.5.0. The addition of new features should be kept to a minimum. Something like should be part of 1.5.1. It's a lot of work with little immediate gain, but will make using Geeklog smoother and less of a hassle in places. If you look at the list of open bugs, there are quite a few that fall into this category. With the introduction of OpenID support, the various minor issues with Remote User accounts will also become more obvious and need to be cleaned up. In parallel, we should work on a strictly bugfixes-only release, Geeklog 1.5.0-1, and make sure that it can be installed with a minimum of hassle. I.e., no changes in the database, the themes, or the language files unless we absolutely have to. Timeframe: Geeklog 1.5.0-1: Second half of July, Geeklog 1.5.1: Somewhere near the end of the Summer of Code, e.g. early to mid September. After that, a version integrating the results from the Summer of Code (and possibly other new features) could be released by the end of this / beginning of next year. Comments? bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ From vfuria at gmail.com Sun Jun 22 17:57:48 2008 From: vfuria at gmail.com (Vincent Furia) Date: Sun, 22 Jun 2008 15:57:48 -0600 Subject: [geeklog-devel] The road ahead - post 1.5.0 In-Reply-To: <20080622182508.45447649@smtp.haun-online.de> References: <20080622182508.45447649@smtp.haun-online.de> Message-ID: <8319e2d60806221457u7b1cf658i8c825d41064d5a23@mail.gmail.com> I also think we need to include the template caching upgrade into 1.5.1. It's finished. It has proven itself on several websites, and will not require a lot of work on our part. In fact, we could release a story (maybe ask Joe to do it), advising plugin authors that it is coming in the next x months and they should start to prepare their plugins now. -Vinny On Sun, Jun 22, 2008 at 12:25 PM, Dirk Haun wrote: > Looking at the first bug reports that came in for 1.5.0, it's time to > think about how we go from here. Here are my suggestions: > > I think for Geeklog 1.5.1 we should concentrate on fixing all those > rough edges that we left in while rushing to push out 1.5.0. The > addition of new features should be kept to a minimum. > > Something like > should be part of 1.5.1. It's a lot of work with little immediate gain, > but will make using Geeklog smoother and less of a hassle in places. If > you look at the list of open bugs, there are quite a few that fall into > this category. With the introduction of OpenID support, the various > minor issues with Remote User accounts will also become more obvious and > need to be cleaned up. > > > In parallel, we should work on a strictly bugfixes-only release, Geeklog > 1.5.0-1, and make sure that it can be installed with a minimum of > hassle. I.e., no changes in the database, the themes, or the language > files unless we absolutely have to. > > > Timeframe: > > Geeklog 1.5.0-1: Second half of July, > Geeklog 1.5.1: Somewhere near the end of the Summer of Code, e.g. early > to mid September. > > After that, a version integrating the results from the Summer of Code > (and possibly other new features) could be released by the end of this / > beginning of next year. > > Comments? > > bye, Dirk > > > -- > http://www.geeklog.net/ > http://geeklog.info/ > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From devel at portalparts.com Sun Jun 22 18:30:27 2008 From: devel at portalparts.com (Blaine Lang) Date: Sun, 22 Jun 2008 18:30:27 -0400 Subject: [geeklog-devel] The road ahead - post 1.5.0 In-Reply-To: <8319e2d60806221457u7b1cf658i8c825d41064d5a23@mail.gmail.com> References: <20080622182508.45447649@smtp.haun-online.de> <8319e2d60806221457u7b1cf658i8c825d41064d5a23@mail.gmail.com> Message-ID: Since this next couple months have the core dev's pretty busy with SOC, I agree that we can't take on too much net new and therefore, your idea of focusing on bugs that don't require any major code changes makes sense. We also should open up the floor to new ideas for post 1.5.1 (assuming thats a minor release). Last years SOC GL config manager was focused on moving the GL config to be table driven and our initial online config manager needs to be improved as it was not the focus of the initial project. While the online config manager is usable it's not as intuitive as it needs to be. We had hoped to make that a SOC project for this year but we did not have enough mentors and suitable students that wanted that project. Additionally items that I would like to raise for post 1.5 are: - SESSIONS support - Improved Core filtering class to better handle filtering hostile data, html filtering, censoring and handling the various modes program need: > Filtering for re-presentation to application > Filtering for DB insert/update > Filering for AJAX server-side use which can include DB + formated Web presentation - Fresh new theme/look ( I believe we had a nice offer a few months ago and hope offer is still available) - Review CTL for inclusion, as Vinny noted and has my vote as well - I also would like to see us decide that PHP5 and possibly MySQL 4+ are the minimal requirements and evolve our code to use a more PHP5 OO design. - Agree that javascript is here to stay :) and start to actively use AJAX in our Admin and User core components. - Expect that we will need time to refine and fully implement the SOC project code Blaine Vincent Furia wrote: > I also think we need to include the template caching upgrade into > 1.5.1. It's finished. It has proven itself on > several websites, and will not require a lot of work on our part. In > fact, we could release a story (maybe ask Joe to do it), advising > plugin authors that it is coming in the next x months and they should > start to prepare their plugins now. > > -Vinny > > On Sun, Jun 22, 2008 at 12:25 PM, Dirk Haun > wrote: > > Looking at the first bug reports that came in for 1.5.0, it's time to > think about how we go from here. Here are my suggestions: > > I think for Geeklog 1.5.1 we should concentrate on fixing all those > rough edges that we left in while rushing to push out 1.5.0. > The > addition of new features should be kept to a minimum. > > Something like > should be part of 1.5.1. It's a lot of work with > little immediate gain, > but will make using Geeklog smoother and less of a hassle in > places. If > you look at the list of open bugs, there are quite a few that fall > into > this category. With the introduction of OpenID support, the various > minor issues with Remote User accounts will also become more > obvious and > need to be cleaned up. > > > In parallel, we should work on a strictly bugfixes-only release, > Geeklog > 1.5.0-1, and make sure that it can be installed with a minimum of > hassle. I.e., no changes in the database, the themes, or the language > files unless we absolutely have to. > > > Timeframe: > > Geeklog 1.5.0-1: Second half of July, > Geeklog 1.5.1: Somewhere near the end of the Summer of Code, e.g. > early > to mid September. > > After that, a version integrating the results from the Summer of Code > (and possibly other new features) could be released by the end of > this / > beginning of next year. > > Comments? > > bye, Dirk > > > -- > http://www.geeklog.net/ > http://geeklog.info/ > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > > ------------------------------------------------------------------------ > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > From mjervis at gmail.com Mon Jun 23 07:43:24 2008 From: mjervis at gmail.com (Michael Jervis) Date: Mon, 23 Jun 2008 12:43:24 +0100 Subject: [geeklog-devel] The road ahead - post 1.5.0 In-Reply-To: <20080622182508.45447649@smtp.haun-online.de> References: <20080622182508.45447649@smtp.haun-online.de> Message-ID: <7b42e7470806230443o6876fdf4t1c9c1ba97c97c5c@mail.gmail.com> > I think for Geeklog 1.5.1 we should concentrate on fixing all those > rough edges that we left in while rushing to push out 1.5.0. The > addition of new features should be kept to a minimum. > In parallel, we should work on a strictly bugfixes-only release, Geeklog > 1.5.0-1, and make sure that it can be installed with a minimum of > hassle. I.e., no changes in the database, the themes, or the language > files unless we absolutely have to. I would like to propose an alternative, ever so slightly radical approach. I think we should have a roadmap, and we should stick to set time releases. I think we should aim to have Geeklog 1.5.1 out by the end of July, it should have a specific set of items in it. 1) Bug fixes 2) Community contributed ready-to-go patches (CTL and any others). We should have a beta release mid-July, final release 31st July. We need to make steps in the rift between community submissions and core team submissions. We should have a plan for doing so, and the work in getting the release ready should be shared. i.e. Dirk shouldn't be left holding the baby. Remaining summer effort from core team should involve getting the GSoC ready for a release not too long after the end of pencil's down. Instead of taking a year to get it integrated post pencils down Plus bug fixing and tidying up stuff. Maybe the new theme? Replacing KSES? Changing in baselines supported? etc. Housework. PLUS planning for 1.6, with a road map and time scales and defined features. It'll just make us more credible. If we have defined windows for getting things done with cut offs etc, and keep the community up-to-date it'll make it easier for the community to contribute also. Personally, I'm quite happy to take a defined role resolving community patches and fixing bugs and aiding community/core communication and trying REALLY hard to keep my hands off trying to build the big cool things I'm really interested in doing, if it enables us to move forward better. I'm not running a business on geeklog (unlike others), and so making those big changes is less important to me, and I'm more likely to slip anything big due to time and life. But I think we need to be more structured so anyone running a big site or proper business based on Geeklog can keep doing so, and our platform, community and team can grow. Cheers, Mike From dirk at haun-online.de Mon Jun 23 14:50:31 2008 From: dirk at haun-online.de (Dirk Haun) Date: Mon, 23 Jun 2008 20:50:31 +0200 Subject: [geeklog-devel] The road ahead - post 1.5.0 In-Reply-To: References: <20080622182508.45447649@smtp.haun-online.de> <8319e2d60806221457u7b1cf658i8c825d41064d5a23@mail.gmail.com> Message-ID: <20080623185031.847465509@smtp.haun-online.de> Blaine Lang wrote: >- I also would like to see us decide that PHP5 and possibly MySQL 4+ are >the minimal requirements and evolve our code to use a more PHP5 OO design. We owe our users a bugfixed 1.5.0 that still works on PHP 4 (I did actually see someone mentioning they were on PHP 4.1.2 or something equally ancient in the forums just today or yesterday). But for 1.5.1 and later it doesn't make sense any more to insist on compatibility with PHP 4. Not sure where to draw the line with MySQL. Official support for MySQL 3.23 ended quite a while ago. What does MySQL 4 buy us over 3.23? What about 4.1? >- Agree that javascript is here to stay :) and start to actively use >AJAX in our Admin and User core components. Just the other day I saved someone's day when I pointed out that he could switch off JavaScript for "My Account" and it would still work. I'm a bit miffed, actually, that the Configuration requires JavaScript for - to me at least - no obvious reason. Didn't notice it in time, so I didn't say anything. Nothing wrong with jazzing things up a bit (or a lot). But the basic, minimal functionality should still work without JS. Yeah, I'm old- fashioned ... >- Review CTL for inclusion, as Vinny noted and has my vote as well Did anyone ever do some performance tests with this thing? How does it help on small sites vs. large sites (aka does it scale)? Also, from what I understand, it's translating the templates to PHP. What about security? >- Fresh new theme/look ( I believe we had a nice offer a few months ago >and hope offer is still available) Haven't heard anything since. bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ From ironmax at spacequad.com Mon Jun 23 15:14:06 2008 From: ironmax at spacequad.com (Michael Brusletten) Date: Mon, 23 Jun 2008 15:14:06 -0400 Subject: [geeklog-devel] geeklog-devel Digest, Vol 16, Issue 14 References: Message-ID: <002501c8d565$4e9cc810$fe00a8c0@ns2.spacequad.com> I agree, CTL should be placed in the core as I myself have been stalled on a project that is going to require Marks Media Gallery. Until this is done, geeklog users will have to install the CTL seperately into the core. I have found that there are more users out there that don't really know what they are doing when it comes to PHP and have messed up therir installs or configurations because they wanted to run this. I myself need it because of the project I'm working on. Its a Family Tree intigration plugin thats not going to use the Gallery2, but rather the Media Gallery. I have no time frame on this yet, as some details have to be worked out. Michael ----- Original Message ----- > Message: 2 > Date: Sun, 22 Jun 2008 15:57:48 -0600 > From: "Vincent Furia" > Subject: Re: [geeklog-devel] The road ahead - post 1.5.0 > To: "Geeklog Development" > Message-ID: > <8319e2d60806221457u7b1cf658i8c825d41064d5a23 at mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > I also think we need to include the template caching upgrade into 1.5.1. > It's finished. It has proven itself on several websites, and will not > require a lot of work on our part. In fact, we could release a story (maybe > ask Joe to do it), advising plugin authors that it is coming in the next x > months and they should start to prepare their plugins now. > > -Vinny > > On Sun, Jun 22, 2008 at 12:25 PM, Dirk Haun wrote: > > > Looking at the first bug reports that came in for 1.5.0, it's time to > > think about how we go from here. Here are my suggestions: > > > > I think for Geeklog 1.5.1 we should concentrate on fixing all those > > rough edges that we left in while rushing to push out 1.5.0. The > > addition of new features should be kept to a minimum. > > > > Something like > > should be part of 1.5.1. It's a lot of work with little immediate gain, > > but will make using Geeklog smoother and less of a hassle in places. If > > you look at the list of open bugs, there are quite a few that fall into > > this category. With the introduction of OpenID support, the various > > minor issues with Remote User accounts will also become more obvious and > > need to be cleaned up. > > > > > > In parallel, we should work on a strictly bugfixes-only release, Geeklog > > 1.5.0-1, and make sure that it can be installed with a minimum of > > hassle. I.e., no changes in the database, the themes, or the language > > files unless we absolutely have to. > > > > > > Timeframe: > > > > Geeklog 1.5.0-1: Second half of July, > > Geeklog 1.5.1: Somewhere near the end of the Summer of Code, e.g. early > > to mid September. > > > > After that, a version integrating the results from the Summer of Code > > (and possibly other new features) could be released by the end of this / > > beginning of next year. > > > > Comments? > > > > bye, Dirk > > From tony at tonybibbs.com Mon Jun 23 15:41:03 2008 From: tony at tonybibbs.com (Tony Bibbs) Date: Mon, 23 Jun 2008 12:41:03 -0700 (PDT) Subject: [geeklog-devel] Time to rebrand 2.x Message-ID: <165648.82682.qm@web706.biz.mail.mud.yahoo.com> Karma? Maybe I should care more. But seriously, the name and all has been in use for like 2 weeks and we're already one of the first links on Google. http://tinyurl.com/3rrkvw --Tony ----- Original Message ---- From: Dirk Haun To: geeklog-devel Sent: Saturday, June 21, 2008 5:56:43 PM Subject: Re: [geeklog-devel] Time to rebrand 2.x Tony Bibbs wrote: >My original note was simply to inform everybody of the name >chosen and look for any violent disagreement. I'm still wondering if it isn't bad karma to knowingly choose the name of another open source project, even if that other project is mostly know by it's short name. I was just reminded of this when this post showed up in my feed reader: (via planet-soc.com) bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From dirk at haun-online.de Mon Jun 23 15:55:57 2008 From: dirk at haun-online.de (Dirk Haun) Date: Mon, 23 Jun 2008 21:55:57 +0200 Subject: [geeklog-devel] The road ahead - post 1.5.0 In-Reply-To: <7b42e7470806230443o6876fdf4t1c9c1ba97c97c5c@mail.gmail.com> References: <20080622182508.45447649@smtp.haun-online.de> <7b42e7470806230443o6876fdf4t1c9c1ba97c97c5c@mail.gmail.com> Message-ID: <20080623195557.511773626@smtp.haun-online.de> Michael Jervis wrote: >I would like to propose an alternative, ever so slightly radical approach. > >I think we should have a roadmap, and we should stick to set time releases. > >I think we should aim to have Geeklog 1.5.1 out by the end of July And here I thought my proposed schedule was radical ... I've said on more than one occassion that I think our release cycles are too long (1.5.0 was just an extreme case) and that I'd prefer something like 2 releases per year. But are you sure we can pull this off? If this were a full-time project, I'd say sure, no problem. But we're all doing this in our spare time. We have jobs, family, other commitments and interests. I can only see this working with some very, very strict restrictions on what and what not to add. >I think we should aim to have Geeklog 1.5.1 out by the end of July, it >should have a specific set of items in it. > >1) Bug fixes >2) Community contributed ready-to-go patches (CTL and any others). That would be 5 weeks then? Not sure if the CTL is "ready to go". It may work as the hack that it is, but a proper integration requires more work, starting with an integration into the Configuration panel, the resulting DB and language file changes. Speaking of language file changes: There's also the issue of translations - those take time. Just sayin' ... bye, Dirk -- http://www.haun-online.de/accu/ From furiousdog at gmail.com Mon Jun 23 17:30:48 2008 From: furiousdog at gmail.com (Sami Barakat) Date: Mon, 23 Jun 2008 22:30:48 +0100 Subject: [geeklog-devel] The road ahead - post 1.5.0 In-Reply-To: <20080623185031.847465509@smtp.haun-online.de> References: <20080622182508.45447649@smtp.haun-online.de> <8319e2d60806221457u7b1cf658i8c825d41064d5a23@mail.gmail.com> <20080623185031.847465509@smtp.haun-online.de> Message-ID: <609505460806231430h4ea2ba2bw13740d3b080e33be@mail.gmail.com> 2008/6/23 Dirk Haun : > Blaine Lang wrote: > > >- I also would like to see us decide that PHP5 and possibly MySQL 4+ are > >the minimal requirements and evolve our code to use a more PHP5 OO design. > > We owe our users a bugfixed 1.5.0 that still works on PHP 4 (I did > actually see someone mentioning they were on PHP 4.1.2 or something > equally ancient in the forums just today or yesterday). But for 1.5.1 > and later it doesn't make sense any more to insist on compatibility with > PHP 4. > > Not sure where to draw the line with MySQL. Official support for MySQL > 3.23 ended quite a while ago. What does MySQL 4 buy us over 3.23? What > about 4.1? > > One bonus of MySQL 4.0 is allowing Full-Text searches to be done using boolean operators. As you may know, as part of my GSoC project, I plan to implement Full-Text indexing on databases that want it, commonly very large sites. The admin will decide if they want it enabled when installing/upgrading. The advantage of Full-Text is it allows searching to be done in a fraction of the time it currently takes. Full-Text was introduced in 3.23. If the minimum requirements was set at 4.0 it could go a step further and allow users to search for items in boolean mode, meaning terms like "+apple +juice -tree" will return results that contain both "apple" and "juice" but not "tree". It might be a pointless feature on some sites but its relatively simple to implement. >From what I have heard there have been numerous changes to the Full-Text feature in MySQL between the versions 3.23 - 4.0 - 4.1. I have also herd reports that it doesn't scale well, but I am not sure how true this is. I will be doing tests to find out how it performs on the different versions. Maybe you can take this into consideration when deciding the minimum requirements. Full-Text is also available on Microsoft SQL Server 2000, will this minimum requirement stay the same? There have been some performance improvments done in SQL Server 2005. ref: http://dev.mysql.com/doc/refman/4.1/en/fulltext-boolean.html Sami -------------- next part -------------- An HTML attachment was scrubbed... URL: From dirk at haun-online.de Tue Jun 24 01:02:23 2008 From: dirk at haun-online.de (Dirk Haun) Date: Tue, 24 Jun 2008 07:02:23 +0200 Subject: [geeklog-devel] MS SQL (was: The road ahead - post 1.5.0) In-Reply-To: <609505460806231430h4ea2ba2bw13740d3b080e33be@mail.gmail.com> References: <20080622182508.45447649@smtp.haun-online.de> <8319e2d60806221457u7b1cf658i8c825d41064d5a23@mail.gmail.com> <20080623185031.847465509@smtp.haun-online.de> <609505460806231430h4ea2ba2bw13740d3b080e33be@mail.gmail.com> Message-ID: <20080624050223.1735821764@smtp.haun-online.de> Sami Barakat wrote: >Full-Text is also available on Microsoft SQL Server 2000, will this minimum >requirement stay the same? There have been some performance improvments done >in SQL Server 2005. Speaking of which: Now would be a good time to look at the new MS SQL driver again. Kevin, are you still with us? bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ From mjervis at gmail.com Tue Jun 24 02:51:14 2008 From: mjervis at gmail.com (Michael Jervis) Date: Tue, 24 Jun 2008 07:51:14 +0100 Subject: [geeklog-devel] The road ahead - post 1.5.0 In-Reply-To: <20080623195557.511773626@smtp.haun-online.de> References: <20080622182508.45447649@smtp.haun-online.de> <7b42e7470806230443o6876fdf4t1c9c1ba97c97c5c@mail.gmail.com> <20080623195557.511773626@smtp.haun-online.de> Message-ID: <7b42e7470806232351r36503e17x5a91bcce54ff9b46@mail.gmail.com> > I've said on more than one occassion that I think our release cycles are > too long (1.5.0 was just an extreme case) and that I'd prefer something > like 2 releases per year. Maybe we should aim for 1 big release per year, with a plan to follow that in quick succession with 1-3 minor releases with bug fixes and minor new features. > But are you sure we can pull this off? If this were a full-time project, > I'd say sure, no problem. But we're all doing this in our spare time. We > have jobs, family, other commitments and interests. Well, depends what we do. What is involved in a release? If we do a minor release in 5 weeks with bug fixes and community contribs that are ready to go (debate what later). That's pretty do-able. Then we plan to have a dead line for a 1.5.2/1.6 with the GSoC contributions in. And aim for it with a plan instead of a "We want to release by", but figure out what we need to do, how to do it and when it needs to be done. The problem is we are part time, but we don't try and deal with that. We just drift. If we have a date to aim for and milestones on the way we can track progress, manage expectations and change the plan, but we should at least /have/ a plan to get the GSoC contributions out in a timely fashion this year. And plan for the next timely releases. > I can only see this working with some very, very strict restrictions on > what and what not to add. Well if we did that, the plan would be to have a cut off at a certain date, so GSoC's big bits will be in by x, anything else by y, then a plan to get that to a releaseable state. Then you just do the same. As I said, we just drift. Code freezes start when we can, not when they are planned to and sometimes we break them. If we're a little more planned in advance, then people who are working part-time round other commitments (all of us?) know what's going on and won't accidentally delay the next release by months because they start to commit parts of a big development. >>I think we should aim to have Geeklog 1.5.1 out by the end of July, it >>should have a specific set of items in it. > That would be 5 weeks then? Yes, but, 1.5.1 is what 1.5.0-1 was in your email in my opinion. Sub-version numbers work ok for urgent security releases, but 1.5.1 is really the first bug fix release of 1.5 at least in my head. > Not sure if the CTL is "ready to go". It may work as the hack that it > is, but a proper integration requires more work, starting with an > integration into the Configuration panel, the resulting DB and language > file changes. Ah yes, good points, but, maybe we can get Joe/whoever to crack that off so that it can be rolled in with the GSoC then? > Speaking of language file changes: There's also the issue of > translations - those take time. How quickly/readily do we get contributed translations? Do they necessarily prevent a release? Can we provide language file updates via Geeklog.net post-release? Cheers, Mike From dirk at haun-online.de Tue Jun 24 15:32:29 2008 From: dirk at haun-online.de (Dirk Haun) Date: Tue, 24 Jun 2008 21:32:29 +0200 Subject: [geeklog-devel] The road ahead - post 1.5.0 In-Reply-To: <7b42e7470806232351r36503e17x5a91bcce54ff9b46@mail.gmail.com> References: <20080622182508.45447649@smtp.haun-online.de> <7b42e7470806230443o6876fdf4t1c9c1ba97c97c5c@mail.gmail.com> <20080623195557.511773626@smtp.haun-online.de> <7b42e7470806232351r36503e17x5a91bcce54ff9b46@mail.gmail.com> Message-ID: <20080624193229.692187427@smtp.haun-online.de> Michael Jervis wrote: >Maybe we should aim for 1 big release per year, with a plan to follow >that in quick succession with 1-3 minor releases with bug fixes and >minor new features. Sounds good to me. If we may be so bold as to assume that we get into GSoC again, we may want to sync the major release with that then. >The problem is we are part time, but we don't try and deal with that. >We just drift. Yep. >Code freezes start when we can, not when they are planned to and >sometimes we break them. If we're a little more planned in advance, >then people who are working part-time round other commitments (all of >us?) know what's going on and won't accidentally delay the next >release by months because they start to commit parts of a big >development. For starters, we should start using the bugtracker more. Mantis has a few features that we may want to use, e.g. subprojects, custom fields, and filters. Ideally, you should be able to see, at a glance, what is being worked on for the next release. That should be doable with proper tagging and defining a filter for it. >Yes, but, 1.5.1 is what 1.5.0-1 was in your email in my opinion. >Sub-version numbers work ok for urgent security releases, but 1.5.1 is >really the first bug fix release of 1.5 at least in my head. One problem with this: So far, our stance was that we would be supporting the last two versions (current and previous release), and that was usually easy to understand from the version numbers. If there's, say, a 1.5.2 in December, we probably don't want to drop support for 1.5.0 already by then. But providing, say, a security fix for 3 versions would mean having to provide at least 4 tarballs (fix for each version + a new complete tarball, plus possibly up to another 3 "combo" updates, in case there were earlier security fixes). That's way too much to handle. Of course, if we go forward in smaller steps, our users may be less reluctant to upgrading ... >How quickly/readily do we get contributed translations? Depends. Some are very fast, others are only updated every other release. >Do they necessarily prevent a release? Depends, again. If there's a new feature with a user interface, we should at least give the translators a chance. >Can we provide language file updates >via Geeklog.net post-release? Sure - look at our download section. It tends to get cluttered up, though, and some people may miss them. bye, Dirk -- http://www.haun-online.de/ http://geeklog.info/ From dirk at haun-online.de Tue Jun 24 16:04:52 2008 From: dirk at haun-online.de (Dirk Haun) Date: Tue, 24 Jun 2008 22:04:52 +0200 Subject: [geeklog-devel] Hmm ... Message-ID: <20080624200452.503559630@smtp.haun-online.de> Long version: From thomas at koch.ro Tue Jun 24 16:23:26 2008 From: thomas at koch.ro (Thomas Koch) Date: Tue, 24 Jun 2008 22:23:26 +0200 Subject: [geeklog-devel] Awesome GIT slides and talk Message-ID: <200806242223.27018.thomas@koch.ro> I've seen, that you started discussing about a DVCS to choose. Therefor I'd like to recommend an awesome talk given at Railsconf 2008 some weeks ago. http://www.gitcasts.com/git-talk There is a movie of the slides with voiceover and the slides as PDF. I recommend you this one, because it is very nice made and the best introduction to GIT that I've seen so far. Best regards, -- Thomas Koch, Software Developer http://www.koch.ro From dirk at haun-online.de Wed Jun 25 12:44:12 2008 From: dirk at haun-online.de (Dirk Haun) Date: Wed, 25 Jun 2008 18:44:12 +0200 Subject: [geeklog-devel] Awesome GIT slides and talk In-Reply-To: <200806242223.27018.thomas@koch.ro> References: <200806242223.27018.thomas@koch.ro> Message-ID: <20080625164412.1987642209@smtp.haun-online.de> Thomas Koch wrote: >http://www.gitcasts.com/git-talk > >There is a movie of the slides with voiceover and the slides as PDF. git scares me. I've heard from people (whom I trust and who tried out the "big 3" DVCS) that you can easily get things wrong by picking the wrong of several subtly different commands or options. Page 30 from that slideset demonstrates this nicely. How many commands are that?[1] From slide 370 on, it demonstrates the advantages and typical usage scenarios for a DVCS. Haven't listened to the voiceover yet, but this may be helpful. bye, Dirk [1] The answer is on slide 296: There are 152 commands ... -- http://www.geeklog.net/ http://geeklog.info/ From mark at the-howards.net Wed Jun 25 13:13:30 2008 From: mark at the-howards.net (Mark Howard) Date: Wed, 25 Jun 2008 13:13:30 -0400 Subject: [geeklog-devel] Hmm ... In-Reply-To: <20080624200452.503559630@smtp.haun-online.de> References: <20080624200452.503559630@smtp.haun-online.de> Message-ID: <03cd01c8d6e6$cb712070$62536150$@net> I was reading some of the righteously-indignant comments to this article - I don't see what the big deal is. I think this is sound security practice - eg. disable all potentially dangerous features, but go ahead and provide the ability to re-enable them through the configuration interface. For instance, I know that I have to go out of my way to configure 'su' to root to operate without a password, but I can still do it. Anyway - the article is written from the perspective of the folks that are trying to 'market' a $30 editor which utilizes this open interface, and they are annoyed that their users will be inconvenienced. (Yawn) I think that taking the problem to the level where you are creating an application-specific API (eg. what Flickr did) is frankly using the (probably real issue) to your own advantage, eg. I am sure there is a whole potential future market in 'Wordpress-enabled' applications which cost $20, etc., and I'm quite sure that Red Sweater would like this as well. Let's hope Matt doesn't buy into this - I mean he was able to raise $29.5M by sticking with open standards and interfaces so far, so why would he need to do anything differently? http://gigaom.com/2008/01/22/wordpresscom-creator-raises-29m/ It will be interesting to see whether they take the high road or low road, but shipping the thing with AtomPub disabled by default? No big deal - sound security practices - I know how to click a mouse on a check box, and if I don't, then the darn thing should be disabled ... ;^) -m -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Dirk Haun Sent: Tuesday, June 24, 2008 4:05 PM To: geeklog-devel Subject: [geeklog-devel] Hmm ... Long version: _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From dirk at haun-online.de Wed Jun 25 14:41:42 2008 From: dirk at haun-online.de (Dirk Haun) Date: Wed, 25 Jun 2008 20:41:42 +0200 Subject: [geeklog-devel] Hmm ... In-Reply-To: <03cd01c8d6e6$cb712070$62536150$@net> References: <20080624200452.503559630@smtp.haun-online.de> <03cd01c8d6e6$cb712070$62536150$@net> Message-ID: <20080625184142.507858550@smtp.haun-online.de> Mark Howard wrote: >I think this is sound security practice - >eg. disable all potentially dangerous features, but go ahead and provide the >ability to re-enable them through the configuration interface. That's one way of looking at it. The other is that disabling something after it was enabled by default previously sends a message to those that want to use it - namely, that it's probably not a good idea to enable it. As can be seen from the indecisive subject, I have no final opinion on this yet ... The exact quote from one of the WordPress people is: >We have choosen to disable Atom Publishing Protocol and the variety of >XML-RPC protocols by default as they expose a potential to be a security risk. That's very vague. You might as well just disable the entire website[1] as it exposes a potential risk of SQL injections and XSS. I thought that the "A Real Solution" section from the Red Sweater blog - possible financial interest on their part aside - had some good points. But maybe I only agree with them because it's what we're doing in 1.5.0 ;-) bye, Dirk [1] whatever software it's running on - this wasn't meant as a stab at WordPress -- http://www.haun-online.de/ http://spam.tinyweb.net/ From dirk at haun-online.de Wed Jun 25 14:44:50 2008 From: dirk at haun-online.de (Dirk Haun) Date: Wed, 25 Jun 2008 20:44:50 +0200 Subject: [geeklog-devel] MS SQL question Message-ID: <20080625184450.697391089@smtp.haun-online.de> In the install script, we have this function: /** * Check if a table exists * * @param string $table Table name * @return boolean True if table exists, false if it does not * */ function INST_checkTableExists ($table) { global $_TABLES, $_DB_dbms; $exists = false; if ($_DB_dbms == 'mysql') { $result = DB_query ("SHOW TABLES LIKE '{$_TABLES[$table]}'"); if (DB_numRows ($result) > 0) { $exists = true; } } return $exists; } As can be seen, it's only covering MySQL. How would you check for the existance of a table in MS SQL? bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ From mjervis at gmail.com Wed Jun 25 14:48:45 2008 From: mjervis at gmail.com (Michael Jervis) Date: Wed, 25 Jun 2008 19:48:45 +0100 Subject: [geeklog-devel] MS SQL question In-Reply-To: <20080625184450.697391089@smtp.haun-online.de> References: <20080625184450.697391089@smtp.haun-online.de> Message-ID: <7b42e7470806251148p34368c1cl808a9ad7001430cd@mail.gmail.com> SELECT 1 FROM sysobjects WHERE name= '{$_TABLES[$table]}' Probably want to check XTYPE as well, but I can't recall right now the correct value for table. On Wed, Jun 25, 2008 at 19:44, Dirk Haun wrote: > In the install script, we have this function: > > /** > * Check if a table exists > * > * @param string $table Table name > * @return boolean True if table exists, false if it does not > * > */ > function INST_checkTableExists ($table) > { > global $_TABLES, $_DB_dbms; > > $exists = false; > > if ($_DB_dbms == 'mysql') { > $result = DB_query ("SHOW TABLES LIKE '{$_TABLES[$table]}'"); > if (DB_numRows ($result) > 0) { > $exists = true; > } > } > > return $exists; > } > > As can be seen, it's only covering MySQL. How would you check for the > existance of a table in MS SQL? > > bye, Dirk > > > -- > http://www.geeklog.net/ > http://geeklog.info/ > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > -- Michael Jervis mjervis at gmail.com 504B03041400000008008F846431E3543A820800000006000000060000007765 62676F642B4F4D4ACF4F0100504B010214001400000008008F846431E3543A82 0800000006000000060000000000000000002000000000000000776562676F64 504B05060000000001000100340000002C0000000000 From dirk at haun-online.de Wed Jun 25 15:41:44 2008 From: dirk at haun-online.de (Dirk Haun) Date: Wed, 25 Jun 2008 21:41:44 +0200 Subject: [geeklog-devel] Going Mercurial Message-ID: <20080625194144.1992182726@smtp.haun-online.de> So, as mentioned before, we're going to try out a DVCS during this year's Summer of Code. We're going with Mercurial, mainly because nobody came forward in favour of any of the other systems in time ;-) This is an experiment, not a final decision. I've started a wiki page: The Best Practices section needs to be filled in. The links to the Mercurial wiki should provide some starters. Currently, this is aimed at our GSoC students working on 1.x. The idea is that you can check out from a central repository and then have a local copy that you can check in against. So you get the benefits of a version control system (being able to roll back changes, seeing what you changed, etc.). This is also an easy way to show off what you've done to your mentor and interested members of the community. Just run "hg serve" and point them to your IP address. Later on, when you get the account information from your mentor, you can check things back into the main repository ("push", in Mercurial's terminology). Btw, a repository that has been checked out anonymously can be used to check things back in under a specific account, so that shouldn't be a problem. That's the basic idea. From here on, everything's open for discussion. bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ From mark at the-howards.net Wed Jun 25 17:00:02 2008 From: mark at the-howards.net (Mark Howard) Date: Wed, 25 Jun 2008 17:00:02 -0400 Subject: [geeklog-devel] Hmm ... In-Reply-To: <20080625184142.507858550@smtp.haun-online.de> References: <20080624200452.503559630@smtp.haun-online.de> <03cd01c8d6e6$cb712070$62536150$@net> <20080625184142.507858550@smtp.haun-online.de> Message-ID: <041501c8d706$776c6ff0$66454fd0$@net> Playing devil's advocate - not picking on you - but - isn't that what we ended up doing with the use of HTML style directives in story content? :^) I think we owe it to the general population to leave advanced features disabled that we know only about 5% of them will use, as long as those advanced features present some sort of security issue. Clearly the protocol is not as robust as it needs to be otherwise they wouldn't be worried about it. This would seem to be an effective way to generate nicely-formatted SPAM, or worse - a way to inject what might look like authentic content into a site for phishing or other nefarious purposes. How secure is the authentication scheme? Is it as secure as what GL core code provides for in the core code itself? If so, perhaps a non-issue, but disabling generally-unused features by default is a common security practice - it doesn't have to be about a statement that it is extraordinarily dangerous. As you have said - I like WP a lot as well, use it myself, have a lot of friends that use it, etc etc. I was not picking on them, but I tend to be cynical about some of these things - I have to read them every day and evaluate them, and I feel like I might be turning into Robert Langdon, seeing patterns in everything ... :^) -m -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Dirk Haun Sent: Wednesday, June 25, 2008 2:42 PM To: geeklog-devel Subject: Re: [geeklog-devel] Hmm ... ... The other is that disabling something after it was enabled by default previously sends a message to those that want to use it - namely, that it's probably not a good idea to enable it. From wenerd87 at gmail.com Wed Jun 25 18:38:53 2008 From: wenerd87 at gmail.com (Jared Wenerd) Date: Wed, 25 Jun 2008 18:38:53 -0400 Subject: [geeklog-devel] summer of code comments In-Reply-To: References: Message-ID: Hello: I've been working the comment improvements for 1.x. Everything seems to be going well so far. Currently I've been working on the comment moderation queue but I'd like some feedback on past work. I've included a package which contains the changes I've made so far for the feature to edit comments. It should work with a default install then run the following SQL queries: INSERT INTO gl_features VALUES (27, 'comment.moderate', 'Ability to moderate comments', 1); INSERT INTO gl_groups VALUES (19, 'Comment Admin', 'Can moderate comments', 0); INSERT INTO gl_access VALUES (27, 19); INSERT INTO gl_group_assignments VALUES (19, NULL, 1); INSERT INTO gl_conf_values VALUES ('comment_edit', 'i:1;', 'select', 'Core', 'i:1;', 4, -1, 1680, 21); INSERT INTO gl_conf_values VALUES ('comment_edittime', 'i:3600;', 'text', 'Core', 'i:1800;', 4, -1, 1680, 21); (I plan on adding those to the install as well as changing the language files at a later time) The download is here: http://php.scripts.psu.edu/jgw5017/gsoc/gl-soc-edit.tar.gz I would appreciate any criticisms or suggestions. -Jared From mjervis at gmail.com Thu Jun 26 07:58:00 2008 From: mjervis at gmail.com (Michael Jervis) Date: Thu, 26 Jun 2008 12:58:00 +0100 Subject: [geeklog-devel] MS SQL question In-Reply-To: <7b42e7470806251148p34368c1cl808a9ad7001430cd@mail.gmail.com> References: <20080625184450.697391089@smtp.haun-online.de> <7b42e7470806251148p34368c1cl808a9ad7001430cd@mail.gmail.com> Message-ID: <7b42e7470806260458n16c8ee25icea80508ac1913a7@mail.gmail.com> SELECT 1 FROM sysobjects WHERE name='{$_TABLES[$table]}' AND XTYPE='U' is the full answer (tested) to the question. On Wed, Jun 25, 2008 at 19:48, Michael Jervis wrote: > SELECT 1 FROM sysobjects WHERE name= '{$_TABLES[$table]}' > > Probably want to check XTYPE as well, but I can't recall right now the > correct value for table. > > On Wed, Jun 25, 2008 at 19:44, Dirk Haun wrote: >> In the install script, we have this function: >> >> /** >> * Check if a table exists >> * >> * @param string $table Table name >> * @return boolean True if table exists, false if it does not >> * >> */ >> function INST_checkTableExists ($table) >> { >> global $_TABLES, $_DB_dbms; >> >> $exists = false; >> >> if ($_DB_dbms == 'mysql') { >> $result = DB_query ("SHOW TABLES LIKE '{$_TABLES[$table]}'"); >> if (DB_numRows ($result) > 0) { >> $exists = true; >> } >> } >> >> return $exists; >> } >> >> As can be seen, it's only covering MySQL. How would you check for the >> existance of a table in MS SQL? >> >> bye, Dirk >> >> >> -- >> http://www.geeklog.net/ >> http://geeklog.info/ >> >> _______________________________________________ >> geeklog-devel mailing list >> geeklog-devel at lists.geeklog.net >> http://eight.pairlist.net/mailman/listinfo/geeklog-devel >> > > > > -- > Michael Jervis > mjervis at gmail.com > 504B03041400000008008F846431E3543A820800000006000000060000007765 > 62676F642B4F4D4ACF4F0100504B010214001400000008008F846431E3543A82 > 0800000006000000060000000000000000002000000000000000776562676F64 > 504B05060000000001000100340000002C0000000000 > -- Michael Jervis mjervis at gmail.com 504B03041400000008008F846431E3543A820800000006000000060000007765 62676F642B4F4D4ACF4F0100504B010214001400000008008F846431E3543A82 0800000006000000060000000000000000002000000000000000776562676F64 504B05060000000001000100340000002C0000000000 From mjervis at gmail.com Thu Jun 26 14:26:41 2008 From: mjervis at gmail.com (Michael Jervis) Date: Thu, 26 Jun 2008 19:26:41 +0100 Subject: [geeklog-devel] The road ahead - post 1.5.0 In-Reply-To: <20080624193229.692187427@smtp.haun-online.de> References: <20080622182508.45447649@smtp.haun-online.de> <7b42e7470806230443o6876fdf4t1c9c1ba97c97c5c@mail.gmail.com> <20080623195557.511773626@smtp.haun-online.de> <7b42e7470806232351r36503e17x5a91bcce54ff9b46@mail.gmail.com> <20080624193229.692187427@smtp.haun-online.de> Message-ID: <7b42e7470806261126kda5af21reafd10051be5201e@mail.gmail.com> > For starters, we should start using the bugtracker more. Mantis has a > few features that we may want to use, e.g. subprojects, custom fields, > and filters. OK so do we want to start figuring out which bugs are critical for 1.5.[1|0-1] using Mantis and assigning them a status that indicates such and assigning them out? Should we then start using Mantis to create a sub-project for 1.5.[2|1] with feature requests (or whatever mantis has) to indicate what we should be building for it? Moving bugs we don't plan to fix in 1.5.[1|0-1] into fix for that if they are too big or whatever? > One problem with this: So far, our stance was that we would be > supporting the last two versions (current and previous release), and > that was usually easy to understand from the version numbers. Do we reserve version numbers for that then? 1.5.0 has fixes 1.5.1, 1.5.2 etc and the next release is 1.6? Since geeklog2 is now aptitude, can we decide when gl1 gets to be GL2? Or does it? if we release 1.5.0-1 as a bug fix only release, and we have a security issue, do we have to do 1.5.0sr1 and 1.5.0-1sr1? > Of course, if we go forward in smaller steps, our users may be less > reluctant to upgrading ... There's always that... > Depends. Some are very fast, others are only updated every other release. >>Do they necessarily prevent a release? > Depends, again. If there's a new feature with a user interface, we > should at least give the translators a chance. >>Can we provide language file updates >>via Geeklog.net post-release? > Sure - look at our download section. It tends to get cluttered up, > though, and some people may miss them. So we could identify "must have" translations where we have a reliable fast translator (such as German ;-)) and make sure the translator knows the road-map in advance and can have plenty of warning as we get ready and thus having the translations will be manageable. Anyone else want to chime in? Sounds workable to me... From dirk at haun-online.de Thu Jun 26 15:21:44 2008 From: dirk at haun-online.de (Dirk Haun) Date: Thu, 26 Jun 2008 21:21:44 +0200 Subject: [geeklog-devel] The road ahead - post 1.5.0 In-Reply-To: <7b42e7470806261126kda5af21reafd10051be5201e@mail.gmail.com> References: <20080622182508.45447649@smtp.haun-online.de> <7b42e7470806230443o6876fdf4t1c9c1ba97c97c5c@mail.gmail.com> <20080623195557.511773626@smtp.haun-online.de> <7b42e7470806232351r36503e17x5a91bcce54ff9b46@mail.gmail.com> <20080624193229.692187427@smtp.haun-online.de> <7b42e7470806261126kda5af21reafd10051be5201e@mail.gmail.com> Message-ID: <20080626192144.626433726@smtp.haun-online.de> Michael Jervis wrote: >OK so do we want to start figuring out which bugs are critical for >1.5.[1|0-1] using Mantis and assigning them a status that indicates >such and assigning them out? Yes. Too bad that Mantis doesn't support voting on bugs yet. Feel free to leave comments on the existing issues so we get an idea what's considered important (or not). Also, I'd say issues that aren't in the bugtracker simply don't exist, at least for the long and mid-term strategy. Of course, if an issue is easier to fix than to write a bug report for, then it should be fixed right away instead. >Should we then start using Mantis to create a sub-project for >1.5.[2|1] with feature requests (or whatever mantis has) to indicate >what we should be building for it? Moving bugs we don't plan to fix in >1.5.[1|0-1] into fix for that if they are too big or whatever? Yes. For postponed bugs/features, we could either create new custom fields or set the "fixed" drop-down to some future version number and/or the bug's status to "suspended". In other words, we'll find a way to mark the postponed issues somehow. Subprojects may come in handy for bigger changes that require several separate steps / changes. >Do we reserve version numbers for that then? 1.5.0 has fixes 1.5.1, >1.5.2 etc and the next release is 1.6? Nothing wrong with that, but I don't see how that would spare us from having to release a security update for all 3 1.5.x versions? >Since geeklog2 is now aptitude, >can we decide when gl1 gets to be GL2? Or does it? I think we should skip the version number 2 to avoid confusion. Nothing wrong with 1.10, 1.11, and so on. And then jump right to 3 when we get some really great feature ;-) >if we release 1.5.0-1 as a bug fix only release, and we have a >security issue, do we have to do 1.5.0sr1 and 1.5.0-1sr1? 1.5.0-1 would replace 1.5.0 as the baseline release supported, so that would only be 1.5.0-1sr1. Been there, done that: 1.3.8, 1.3.8-1, 1.3.8-1sr1 ... 1.3.8-1sr4. >So we could identify "must have" translations where we have a reliable >fast translator (such as German ;-)) and make sure the translator >knows the road-map in advance and can have plenty of warning as we get >ready and thus having the translations will be manageable. I guess the readers of geeklog-translations were better informed about the release plans for 1.5.0 than the readers of this mailing list ;-) In other words, I've already tried that. Oh, and btw, the German translation was the work of Markus Wollschl?ger this time around. >Anyone else want to chime in? Sounds workable to me... Yep. bye, Dirk -- http://www.haun-online.de/ http://geeklog.info/ From mjervis at gmail.com Thu Jun 26 15:56:33 2008 From: mjervis at gmail.com (Michael Jervis) Date: Thu, 26 Jun 2008 20:56:33 +0100 Subject: [geeklog-devel] The road ahead - post 1.5.0 In-Reply-To: <20080626192144.626433726@smtp.haun-online.de> References: <20080622182508.45447649@smtp.haun-online.de> <7b42e7470806230443o6876fdf4t1c9c1ba97c97c5c@mail.gmail.com> <20080623195557.511773626@smtp.haun-online.de> <7b42e7470806232351r36503e17x5a91bcce54ff9b46@mail.gmail.com> <20080624193229.692187427@smtp.haun-online.de> <7b42e7470806261126kda5af21reafd10051be5201e@mail.gmail.com> <20080626192144.626433726@smtp.haun-online.de> Message-ID: <7b42e7470806261256v4aa4f025r55cfa7254f3a2f63@mail.gmail.com> > Also, I'd say issues that aren't in the bugtracker simply don't exist, > at least for the long and mid-term strategy. Of course, if an issue is > easier to fix than to write a bug report for, then it should be fixed > right away instead. Yes, if we're going to use that to manage things, then we use that to manage things. not that plus the mail list archive and forum posts. if it needs doing, it goes in Mantis. > Yes. Too bad that Mantis doesn't support voting on bugs yet. Feel free > to leave comments on the existing issues so we get an idea what's > considered important (or not). > Yes. For postponed bugs/features, we could either create new custom > fields or set the "fixed" drop-down to some future version number and/or > the bug's status to "suspended". In other words, we'll find a way to > mark the postponed issues somehow. I'm afraid I'm not as familiar with Mantis as you, do you want to set some rules to say this is how we'll mark as must fix in the bug fix release and this is what goes in the next release release and we'll all follow them? > Nothing wrong with that, but I don't see how that would spare us from > having to release a security update for all 3 1.5.x versions? >>if we release 1.5.0-1 as a bug fix only release, and we have a >>security issue, do we have to do 1.5.0sr1 and 1.5.0-1sr1? > > 1.5.0-1 would replace 1.5.0 as the baseline release supported, so that > would only be 1.5.0-1sr1. Been there, done that: 1.3.8, 1.3.8-1, > 1.3.8-1sr1 ... 1.3.8-1sr4. Well you say that you support the last two versions, but they are now 1.4.1 and 1.5 and then become 1.5 and 1.6. Then the fixes for 1.5 go out as 1.5.1 etc instead of 1.5.0-1 and then 1.5.0-2. Sorry, I'll drop this now. It's just 1.5.0-1, 1.5.0-1sr1 and 1.5.0-2 seem "wrong" to me. I'd rather see them called 1.5.1, 1.5.2 (this was a security release) and 1.5.3 and have the message that the third digit is bug fix only, safe to upgrade releases. As safe as the old "horrible" version numbers. It's just me so I'll drop it. > I think we should skip the version number 2 to avoid confusion. Nothing > wrong with 1.10, 1.11, and so on. And then jump right to 3 when we get > some really great feature ;-) Ok sounds cool. > I guess the readers of geeklog-translations were better informed about > the release plans for 1.5.0 than the readers of this mailing list ;-) In > other words, I've already tried that. Ok. >>Anyone else want to chime in? Sounds workable to me... > > Yep. Glad it's not just me ;-) Maybe if we try it, they'll follow if it works, if it goes wrong, they can only say "I didn't tell you so!" ;-) Mike From mjervis at gmail.com Thu Jun 26 16:16:58 2008 From: mjervis at gmail.com (Michael Jervis) Date: Thu, 26 Jun 2008 21:16:58 +0100 Subject: [geeklog-devel] Rejecting Bugs Message-ID: <7b42e7470806261316s229eb431m7e66a01cf00f1c34@mail.gmail.com> I can't seem to reject bugs. This one: http://project.geeklog.net/tracking/view.php?id=670 Works fine, I can accept it, acknowledge it, confirm it, resolve it or mark it as feedback. I can't change the reproduce-ability or in anyway suggest (other than via a comment) it's not something that needs any work... -- Michael Jervis mjervis at gmail.com 504B03041400000008008F846431E3543A820800000006000000060000007765 62676F642B4F4D4ACF4F0100504B010214001400000008008F846431E3543A82 0800000006000000060000000000000000002000000000000000776562676F64 504B05060000000001000100340000002C0000000000 From dirk at haun-online.de Thu Jun 26 16:14:42 2008 From: dirk at haun-online.de (Dirk Haun) Date: Thu, 26 Jun 2008 22:14:42 +0200 Subject: [geeklog-devel] The road ahead - post 1.5.0 In-Reply-To: <7b42e7470806261256v4aa4f025r55cfa7254f3a2f63@mail.gmail.com> References: <20080622182508.45447649@smtp.haun-online.de> <7b42e7470806230443o6876fdf4t1c9c1ba97c97c5c@mail.gmail.com> <20080623195557.511773626@smtp.haun-online.de> <7b42e7470806232351r36503e17x5a91bcce54ff9b46@mail.gmail.com> <20080624193229.692187427@smtp.haun-online.de> <7b42e7470806261126kda5af21reafd10051be5201e@mail.gmail.com> <20080626192144.626433726@smtp.haun-online.de> <7b42e7470806261256v4aa4f025r55cfa7254f3a2f63@mail.gmail.com> Message-ID: <20080626201442.1683305471@smtp.haun-online.de> Michael Jervis wrote: >I'm afraid I'm not as familiar with Mantis as you, do you want to set >some rules to say this is how we'll mark as must fix in the bug fix >release and this is what goes in the next release release and we'll >all follow them? I don't know everything about Mantis yet either. But I'll think of something. Need to poke around in some corners first. >I'd rather see them called 1.5.1, 1.5.2 (this was >a security release) and 1.5.3 and have the message that the third >digit is bug fix only, safe to upgrade releases. Ah, now I get what you mean. >As safe as the old >"horrible" version numbers. It's just me so I'll drop it. Well, I guess I could live with that scheme. As long as we don't fall into the same trap as WordPress where you sometimes can't get a security fix without a bunch of new features. bye, Dirk -- http://www.haun-online.de/ http://geeklog.info/ From dirk at haun-online.de Thu Jun 26 16:24:57 2008 From: dirk at haun-online.de (Dirk Haun) Date: Thu, 26 Jun 2008 22:24:57 +0200 Subject: [geeklog-devel] Rejecting Bugs In-Reply-To: <7b42e7470806261316s229eb431m7e66a01cf00f1c34@mail.gmail.com> References: <7b42e7470806261316s229eb431m7e66a01cf00f1c34@mail.gmail.com> Message-ID: <20080626202457.156453913@smtp.haun-online.de> Michael Jervis wrote: >Works fine, I can accept it, acknowledge it, confirm it, resolve it or >mark it as feedback. There is no "rejected" state. Close it, then select a Resolution from the dropdown on the page you end up, e.g. "no change required" or "won't fix" or whatever else seems appropriate. bye, Dirk -- http://www.haun-online.de/ http://spam.tinyweb.net/ From mjervis at gmail.com Thu Jun 26 16:38:31 2008 From: mjervis at gmail.com (Michael Jervis) Date: Thu, 26 Jun 2008 21:38:31 +0100 Subject: [geeklog-devel] Rejecting Bugs In-Reply-To: <20080626202457.156453913@smtp.haun-online.de> References: <7b42e7470806261316s229eb431m7e66a01cf00f1c34@mail.gmail.com> <20080626202457.156453913@smtp.haun-online.de> Message-ID: <7b42e7470806261338g6c9cb833wde7974c16a70c9ec@mail.gmail.com> AH if I do update I get the missing options... Doh. From dirk at haun-online.de Fri Jun 27 15:04:42 2008 From: dirk at haun-online.de (Dirk Haun) Date: Fri, 27 Jun 2008 21:04:42 +0200 Subject: [geeklog-devel] The road ahead - post 1.5.0 In-Reply-To: <20080626201442.1683305471@smtp.haun-online.de> References: <20080622182508.45447649@smtp.haun-online.de> <7b42e7470806230443o6876fdf4t1c9c1ba97c97c5c@mail.gmail.com> <20080623195557.511773626@smtp.haun-online.de> <7b42e7470806232351r36503e17x5a91bcce54ff9b46@mail.gmail.com> <20080624193229.692187427@smtp.haun-online.de> <7b42e7470806261126kda5af21reafd10051be5201e@mail.gmail.com> <20080626192144.626433726@smtp.haun-online.de> <7b42e7470806261256v4aa4f025r55cfa7254f3a2f63@mail.gmail.com> <20080626201442.1683305471@smtp.haun-online.de> Message-ID: <20080627190442.707182017@smtp.haun-online.de> Dirk Haun wrote: >Michael Jervis wrote: > >>I'm afraid I'm not as familiar with Mantis as you, do you want to set >>some rules to say this is how we'll mark as must fix in the bug fix >>release and this is what goes in the next release release and we'll >>all follow them? > >I don't know everything about Mantis yet either. But I'll think of >something. Need to poke around in some corners first. Okay, I've created a custom field, tentatively named "Target". Those who can update a bug report (all developers, I would think) will see when hitting the "Update" button, that it's really a dropdown: - not specified (default) - Next Release - Future Release You can use that field as a filter on the "View Issues" page. Would that be sufficient? Do we need more/other options? bye, Dirk -- http://www.haun-online.de/ http://spam.tinyweb.net/ From trinity93 at gmail.com Fri Jun 27 17:32:22 2008 From: trinity93 at gmail.com (Trinity) Date: Fri, 27 Jun 2008 16:32:22 -0500 Subject: [geeklog-devel] The road ahead - post 1.5.0 In-Reply-To: <7b42e7470806261126kda5af21reafd10051be5201e@mail.gmail.com> References: <20080622182508.45447649@smtp.haun-online.de> <7b42e7470806230443o6876fdf4t1c9c1ba97c97c5c@mail.gmail.com> <20080623195557.511773626@smtp.haun-online.de> <7b42e7470806232351r36503e17x5a91bcce54ff9b46@mail.gmail.com> <20080624193229.692187427@smtp.haun-online.de> <7b42e7470806261126kda5af21reafd10051be5201e@mail.gmail.com> Message-ID: for a way of translating the lang files as a group project i recommend pootle http://translate.sourceforge.net/wiki/pootle/index it supports converting the resulting .po files to php value arrays in a php file. you can also convert a our lang files into the .po file that this software uses. it is writen in python and runs as a web based app that can be accessed from anywhere you can plce it. On Thu, Jun 26, 2008 at 1:26 PM, Michael Jervis wrote: > > For starters, we should start using the bugtracker more. Mantis has a > > few features that we may want to use, e.g. subprojects, custom fields, > > and filters. > > OK so do we want to start figuring out which bugs are critical for > 1.5.[1|0-1] using Mantis and assigning them a status that indicates > such and assigning them out? > > Should we then start using Mantis to create a sub-project for > 1.5.[2|1] with feature requests (or whatever mantis has) to indicate > what we should be building for it? Moving bugs we don't plan to fix in > 1.5.[1|0-1] into fix for that if they are too big or whatever? > > > > One problem with this: So far, our stance was that we would be > > supporting the last two versions (current and previous release), and > > that was usually easy to understand from the version numbers. > > Do we reserve version numbers for that then? 1.5.0 has fixes 1.5.1, > 1.5.2 etc and the next release is 1.6? Since geeklog2 is now aptitude, > can we decide when gl1 gets to be GL2? Or does it? > > if we release 1.5.0-1 as a bug fix only release, and we have a > security issue, do we have to do 1.5.0sr1 and 1.5.0-1sr1? > > > > Of course, if we go forward in smaller steps, our users may be less > > reluctant to upgrading ... > > There's always that... > > > Depends. Some are very fast, others are only updated every other release. > >>Do they necessarily prevent a release? > > Depends, again. If there's a new feature with a user interface, we > > should at least give the translators a chance. > >>Can we provide language file updates > >>via Geeklog.net post-release? > > Sure - look at our download section. It tends to get cluttered up, > > though, and some people may miss them. > > So we could identify "must have" translations where we have a reliable > fast translator (such as German ;-)) and make sure the translator > knows the road-map in advance and can have plenty of warning as we get > ready and thus having the translations will be manageable. > > Anyone else want to chime in? Sounds workable to me... > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From devel at portalparts.com Fri Jun 27 18:32:41 2008 From: devel at portalparts.com (Blaine Lang) Date: Fri, 27 Jun 2008 18:32:41 -0400 Subject: [geeklog-devel] The road ahead - post 1.5.0 In-Reply-To: References: <20080622182508.45447649@smtp.haun-online.de> <7b42e7470806230443o6876fdf4t1c9c1ba97c97c5c@mail.gmail.com> <20080623195557.511773626@smtp.haun-online.de> <7b42e7470806232351r36503e17x5a91bcce54ff9b46@mail.gmail.com> <20080624193229.692187427@smtp.haun-online.de> <7b42e7470806261126kda5af21reafd10051be5201e@mail.gmail.com> Message-ID: The XLIFF format for language files looks interesting as the one file contains all the translations. Whether we would parse the XML in this file or create separate language files from this one file is still a good question but I like the idea and it would make a nice SOC project. I would prefer to see an integrated GL Admin tool to manage the language file and remove any pootle and python dependency. - update the master XLIFF file translations - create the separate language files (assuming that was needed) This caught my interest as I have been working on an online tool for a project so translators could bring up any language file and edit the the translations without having to touch the real file. Blaine Trinity wrote: > for a way of translating the lang files as a group project i recommend > pootle > http://translate.sourceforge.net/wiki/pootle/index > > it supports converting the resulting .po files to php value arrays in > a php file. you can also convert a our lang files into the .po file > that this software uses. it is writen in python and runs as a web > based app that can be accessed from anywhere you can plce it. > > > On Thu, Jun 26, 2008 at 1:26 PM, Michael Jervis > wrote: > > > For starters, we should start using the bugtracker more. Mantis > has a > > few features that we may want to use, e.g. subprojects, custom > fields, > > and filters. > > OK so do we want to start figuring out which bugs are critical for > 1.5.[1|0-1] using Mantis and assigning them a status that indicates > such and assigning them out? > > Should we then start using Mantis to create a sub-project for > 1.5.[2|1] with feature requests (or whatever mantis has) to indicate > what we should be building for it? Moving bugs we don't plan to fix in > 1.5.[1|0-1] into fix for that if they are too big or whatever? > > > > One problem with this: So far, our stance was that we would be > > supporting the last two versions (current and previous release), and > > that was usually easy to understand from the version numbers. > > Do we reserve version numbers for that then? 1.5.0 has fixes 1.5.1, > 1.5.2 etc and the next release is 1.6? Since geeklog2 is now aptitude, > can we decide when gl1 gets to be GL2? Or does it? > > if we release 1.5.0-1 as a bug fix only release, and we have a > security issue, do we have to do 1.5.0sr1 and 1.5.0-1sr1? > > > > Of course, if we go forward in smaller steps, our users may be less > > reluctant to upgrading ... > > There's always that... > > > Depends. Some are very fast, others are only updated every other > release. > >>Do they necessarily prevent a release? > > Depends, again. If there's a new feature with a user interface, we > > should at least give the translators a chance. > >>Can we provide language file updates > >>via Geeklog.net post-release? > > Sure - look at our download section. It tends to get cluttered up, > > though, and some people may miss them. > > So we could identify "must have" translations where we have a reliable > fast translator (such as German ;-)) and make sure the translator > knows the road-map in advance and can have plenty of warning as we get > ready and thus having the translations will be manageable. > > Anyone else want to chime in? Sounds workable to me... > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > > ------------------------------------------------------------------------ > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > From dirk at haun-online.de Sat Jun 28 03:18:05 2008 From: dirk at haun-online.de (Dirk Haun) Date: Sat, 28 Jun 2008 09:18:05 +0200 Subject: [geeklog-devel] The road ahead - post 1.5.0 In-Reply-To: References: <20080622182508.45447649@smtp.haun-online.de> <7b42e7470806230443o6876fdf4t1c9c1ba97c97c5c@mail.gmail.com> <20080623195557.511773626@smtp.haun-online.de> <7b42e7470806232351r36503e17x5a91bcce54ff9b46@mail.gmail.com> <20080624193229.692187427@smtp.haun-online.de> <7b42e7470806261126kda5af21reafd10051be5201e@mail.gmail.com> Message-ID: <20080628071805.1471208385@smtp.haun-online.de> Trinity wrote: >it supports converting the resulting .po files to php value arrays in a php >file. The beauty of the current system (if you can even call it that) is its simplicity. All you need is a text editor and a copy of english.php and you can translate away. Keep in mind that the majority of our translators are users, not developers. If we require them to install some fancy software, then that will make it more complicated for them. Of course the current approach also has its problems as you're editing a PHP file and have to be aware of the usual traps and pitfalls, e.g. quotes. So I'm not opposed to changes here, I just wanted to point out that we shouldn't go over the top ... bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ From mjervis at gmail.com Sat Jun 28 04:14:25 2008 From: mjervis at gmail.com (Michael Jervis) Date: Sat, 28 Jun 2008 09:14:25 +0100 Subject: [geeklog-devel] The road ahead - post 1.5.0 In-Reply-To: <20080627190442.707182017@smtp.haun-online.de> References: <20080622182508.45447649@smtp.haun-online.de> <7b42e7470806230443o6876fdf4t1c9c1ba97c97c5c@mail.gmail.com> <20080623195557.511773626@smtp.haun-online.de> <7b42e7470806232351r36503e17x5a91bcce54ff9b46@mail.gmail.com> <20080624193229.692187427@smtp.haun-online.de> <7b42e7470806261126kda5af21reafd10051be5201e@mail.gmail.com> <20080626192144.626433726@smtp.haun-online.de> <7b42e7470806261256v4aa4f025r55cfa7254f3a2f63@mail.gmail.com> <20080626201442.1683305471@smtp.haun-online.de> <20080627190442.707182017@smtp.haun-online.de> Message-ID: <7b42e7470806280114s558a1290ja27b62a7a789b57a@mail.gmail.com> > Would that be sufficient? Do we need more/other options? I believe that will cover it. Suck it and see. Cheers, Mike From chipper at llamas.net Sat Jun 28 19:59:27 2008 From: chipper at llamas.net (Chris 'Chipper' Chiapusio) Date: Sat, 28 Jun 2008 19:59:27 -0400 Subject: [geeklog-devel] Hmm ... In-Reply-To: <041501c8d706$776c6ff0$66454fd0$@net> References: <20080624200452.503559630@smtp.haun-online.de> <03cd01c8d6e6$cb712070$62536150$@net> <20080625184142.507858550@smtp.haun-online.de> <041501c8d706$776c6ff0$66454fd0$@net> Message-ID: <20080628235927.GA15741@chipsworld.llamas.net> I'll just remind everyone that two huge examples of 'Secure out of the box' have evolved over the past 10 years... Linux.. and Windows.. It's not a bad thing. Chip On Wed, Jun 25, 2008 at 05:00:02PM -0400, Mark Howard wrote: >Playing devil's advocate - not picking on you - but - isn't that what we >ended up doing with the use of HTML style directives in story content? > >:^) > >I think we owe it to the general population to leave advanced features >disabled that we know only about 5% of them will use, as long as those >advanced features present some sort of security issue. > >Clearly the protocol is not as robust as it needs to be otherwise they >wouldn't be worried about it. This would seem to be an effective way to >generate nicely-formatted SPAM, or worse - a way to inject what might look >like authentic content into a site for phishing or other nefarious purposes. > >How secure is the authentication scheme? Is it as secure as what GL core >code provides for in the core code itself? If so, perhaps a non-issue, but >disabling generally-unused features by default is a common security practice >- it doesn't have to be about a statement that it is extraordinarily >dangerous. > >As you have said - I like WP a lot as well, use it myself, have a lot of >friends that use it, etc etc. I was not picking on them, but I tend to be >cynical about some of these things - I have to read them every day and >evaluate them, and I feel like I might be turning into Robert Langdon, >seeing patterns in everything ... :^) > >-m > -- ------ **** Warning **** This e-mail message, without warrant or warning, and despite US law as set forth in the Foreign Intelligence Surveillance Act of 1978, may be subject to monitoring by the United States National Security Agency and/or the Department of Defense. Information contained in this message may be used against any senders or recipients, now or in the future, in a public trial or secret tribunal. Please encrypt anything important. PGP Key: http://wwwkeys.pgp.net:11371/pks/lookup?op=get&search=0x6CFA486D From mjervis at gmail.com Sun Jun 29 03:52:11 2008 From: mjervis at gmail.com (Michael Jervis) Date: Sun, 29 Jun 2008 08:52:11 +0100 Subject: [geeklog-devel] summer of code comments In-Reply-To: References: Message-ID: <7b42e7470806290052p3e149f09l5337b6d3a818176f@mail.gmail.com> > I've included a package which contains the changes I've made so far OK I have it installed... > I would appreciate any criticisms or suggestions. Seems to be running very nicely! lib-comment.php, line 707 an xdebug call has been left in. Users see the [delete] link, which they can't use, they can only edit their comments. The delete link appears to still be restricted to admins with permissions to do so. But edit works nicely! I've got to test the time out and that admins can continually edit items past the time out. And I can't find the options in the config screens. Am I blind/hungover or is that still to do? I've got to diff the code and do a review of how it works next... Cheers, Mike From dirk at haun-online.de Sun Jun 29 15:10:40 2008 From: dirk at haun-online.de (Dirk Haun) Date: Sun, 29 Jun 2008 21:10:40 +0200 Subject: [geeklog-devel] [geeklog-cvs] Geeklog-1.x/system lib-security.php, 1.71, 1.72 In-Reply-To: <20080629190253.B561D10FE14@qs1489.pair.com> References: <20080629190253.B561D10FE14@qs1489.pair.com> Message-ID: <20080629191040.384765783@smtp.haun-online.de> Michael Jervis wrote: >! if($_DB_dbms == 'mssql') { >! $sql = "DELETE FROM {$_TABLES['tokens']} WHERE (DATEADD(ss, >ttl, created) < NOW())" > . " AND (ttl > 0)"; >+ } else { >+ $sql = "DELETE FROM {$_TABLES['tokens']} WHERE >(DATE_ADD(created, INTERVAL ttl SECOND) < NOW())" >+ . " AND (ttl > 0)"; >+ } $sql can also be an array: $sql['mysql'] = ... $sql['mssql'] = ... DB_query($sql); bye, Dirk -- http://www.haun-online.de/ http://spam.tinyweb.net/ From dirk at haun-online.de Sun Jun 29 15:21:23 2008 From: dirk at haun-online.de (Dirk Haun) Date: Sun, 29 Jun 2008 21:21:23 +0200 Subject: [geeklog-devel] Next version? Message-ID: <20080629192123.1033801702@smtp.haun-online.de> So, will the next version be strictly bugfixes only or are we going to sneak in a few minor features (or borderline bug/feature issues) as well? In any case, we should plan for a release soonish - mid/end July. Let's see: There's already one fix in CVS that needed a language file change (link category fixes) and I can see the need for a few more. Don't see any theme changes yet, although we may need some for ltr/rtl issues. The 'rootdebug' option should be removed from the config (and go back into siteconfig.php), so that would also be a database change. By our previous numbering scheme, that would call for a version 1.5.1 anyway. So, I guess I've answered my own question ;-) Let's just try and not get overboard with new features ... bye, Dirk -- http://www.haun-online.de/accu/ From mjervis at gmail.com Mon Jun 30 03:49:23 2008 From: mjervis at gmail.com (Michael Jervis) Date: Mon, 30 Jun 2008 08:49:23 +0100 Subject: [geeklog-devel] [geeklog-cvs] Geeklog-1.x/system lib-security.php, 1.71, 1.72 In-Reply-To: <20080629191040.384765783@smtp.haun-online.de> References: <20080629190253.B561D10FE14@qs1489.pair.com> <20080629191040.384765783@smtp.haun-online.de> Message-ID: <7b42e7470806300049j55a52caaga46c3a37395bf115@mail.gmail.com> > $sql can also be an array: > > $sql['mysql'] = ... > $sql['mssql'] = ... > DB_query($sql); Ah, now I'm not sure if that's better or not. Because with an IF you only have to process the string build once. Was wondering about having, as we do with languages, a $SQL array with the query fragments in it. But that might make the code harder to read. From devel at portalparts.com Mon Jun 30 08:38:10 2008 From: devel at portalparts.com (Blaine Lang) Date: Mon, 30 Jun 2008 08:38:10 -0400 Subject: [geeklog-devel] Next version? In-Reply-To: <20080629192123.1033801702@smtp.haun-online.de> References: <20080629192123.1033801702@smtp.haun-online.de> Message-ID: Agree Dirk -- quick bug fix release. Nothing too critical. Blaine Dirk Haun wrote: > So, will the next version be strictly bugfixes only or are we going to > sneak in a few minor features (or borderline bug/feature issues) as well? > > In any case, we should plan for a release soonish - mid/end July. > > Let's see: There's already one fix in CVS that needed a language file > change (link category fixes) and I can see the need for a few more. > Don't see any theme changes yet, although we may need some for ltr/rtl > issues. The 'rootdebug' option should be removed from the config (and go > back into siteconfig.php), so that would also be a database change. > > By our previous numbering scheme, that would call for a version 1.5.1 anyway. > > So, I guess I've answered my own question ;-) Let's just try and not get > overboard with new features ... > > bye, Dirk > > > From mjervis at gmail.com Mon Jun 30 13:43:43 2008 From: mjervis at gmail.com (Michael Jervis) Date: Mon, 30 Jun 2008 18:43:43 +0100 Subject: [geeklog-devel] Next version? In-Reply-To: <20080629192123.1033801702@smtp.haun-online.de> References: <20080629192123.1033801702@smtp.haun-online.de> Message-ID: <7b42e7470806301043p93cb238q96d92caed5a78baa@mail.gmail.com> > By our previous numbering scheme, that would call for a version 1.5.1 anyway. Would that imply we need to support 1.5.0 still then? I'm planning on fixing these issues tomorrow evening (or tonight if I can fix a couple of other things elsewhere first): Links in rtl: http://project.geeklog.net/tracking/view.php?id=671 Core plugins use global when they shouldn't: http://project.geeklog.net/tracking/view.php?id=663 I was hoping to look at: Root Debug: http://project.geeklog.net/tracking/view.php?id=673 and hardcoded strings: http://project.geeklog.net/tracking/view.php?id=656 but should they wait so it can be 1.5.0-1? I was thinking with 673 that we could do it keeping the value in the db with an override in site config so that there is no db change and it's only set in site config in the event of a catastrophe meaning the config UI is not available. I dont' think that's overkill, I think it's better house keeping. We ought to (in the spirit of the new plan) set a hard release date and plan for which issues are the criticals and who's doing what. Cheers, Mike From mjervis at gmail.com Mon Jun 30 14:03:49 2008 From: mjervis at gmail.com (Michael Jervis) Date: Mon, 30 Jun 2008 19:03:49 +0100 Subject: [geeklog-devel] Proposal: Roadmap Message-ID: <7b42e7470806301103g6d91558eoa1f8407076fe1b8a@mail.gmail.com> I've just quickly scratched up what I think is a semi-practical roadmap. Dates may need tweaking. What do people think? http://wiki.geeklog.net/wiki/index.php/Proposed_Roadmap -- Michael Jervis mjervis at gmail.com 504B03041400000008008F846431E3543A820800000006000000060000007765 62676F642B4F4D4ACF4F0100504B010214001400000008008F846431E3543A82 0800000006000000060000000000000000002000000000000000776562676F64 504B05060000000001000100340000002C0000000000 From dirk at haun-online.de Mon Jun 30 17:44:52 2008 From: dirk at haun-online.de (Dirk Haun) Date: Mon, 30 Jun 2008 23:44:52 +0200 Subject: [geeklog-devel] Next version? In-Reply-To: <7b42e7470806301043p93cb238q96d92caed5a78baa@mail.gmail.com> References: <20080629192123.1033801702@smtp.haun-online.de> <7b42e7470806301043p93cb238q96d92caed5a78baa@mail.gmail.com> Message-ID: <20080630214452.1391629986@smtp.haun-online.de> Michael Jervis wrote: >I was thinking with 673 that we could do it keeping the value in the >db with an override in site config so that there is no db change and >it's only set in site config in the event of a catastrophe meaning the >config UI is not available. I dont' think that's overkill, I think >it's better house keeping. If you can make this work, I'm all for it. bye, Dirk P.S. Just back from the local Webmonday and behind on emails ... -- http://www.geeklog.net/ http://geeklog.info/ From dburrows at debian.org Mon Jun 30 23:26:45 2008 From: dburrows at debian.org (Daniel Burrows) Date: Mon, 30 Jun 2008 20:26:45 -0700 Subject: [geeklog-devel] Regarding the name change of Geeklog. Message-ID: <20080701032645.GD6192@alpaca> Hello list, I am the author and maintainer of the aptitude frontend to the apt package management system. apt is a common backend used to install software on Debian GNU/Linux systems and systems derived from Debian (such as Ubuntu and Xandros). aptitude is a frontend to apt that provides terminal and command-line interfaces to apt, with a GTK+ graphical interface in development. The Web page of aptitude is http://algebraicthunk.net/~dburrows/projects/aptitude While as a free software author I have no way of quantifying how many users I have, aptitude is a part of the default Debian installation and appears to be the preferred package manager of many users of Debian and related systems. As you might have guessed by now, I'm writing to you because I just learned that you've decided to rename your software to "aptitude"; see, for instance, this mailing list post: http://eight.pairlist.net/pipermail/geeklog-devel/2008-June/003639.html I'm writing to make you aware of the fact that this name is already in use (for eight years now) by a piece of software that is moderately popular, and is probably even used by some of the same people who use Geeklog. This name change will lead to confusion and namespace difficulties for our users; please don't inflict that on them. I'm sure that there are plenty of perfectly fine names for your software that don't step on the names of established free software programs. Thanks, Daniel