From websitemaster at cogeco.net Fri Jan 1 21:15:52 2016 From: websitemaster at cogeco.net (Tom) Date: Fri, 1 Jan 2016 21:15:52 -0500 Subject: [geeklog-devel] Geeklog repository on GitHub In-Reply-To: References: <026301d143de$d17a29e0$746e7da0$@cogeco.net> <67F61D96-4E93-4F4A-B208-45913C99E52B@haun-online.de> <000801d1440e$713625e0$53a271a0$@cogeco.net> Message-ID: <006001d14503$81754620$845fd260$@cogeco.net> Kenji - did you want to give the "Mantis-issues to GitHub-issues" a shot after I have imported the Geeklog repository? Everyone else - I have imported some the repositories and have figured out the contributions thing. It looks like the contributions don't get linked properly in GitHub until you verify the email address the original commit was made under when importing a repository. The only way I could get mine to show up was adding my websitemaster email address even though I linked all the authors with the Github accounts on import of the repositories. Developers if you used an older email address for some of your Geeklog commits you might want to add it to your GitHub account. You can add the email address as a secondary one to your account (under settings). You do need to verify the address by clinking on link they send you. There are a fair number of old Geeklog Repositories http://project.geeklog.net/cgi-bin/hgwebdir.cgi/ Dirk is the Bad Behavior 2 one the latest version? I was thinking of adding that one to the Geeklog-Plugins organization. Also there is 2 Plugin Repository Repositories?. The one named ?GSoC 2009: Tim Patrick / Plugin Repository? looks to be the entire Geeklog CMS plus the repository. It has some later commits than the one named ?Plugin Repository? but it appears to be just a plugin. What do I want here? Also I guess this will also mess up the nightly tarball creation as well as the automated process which when we added a tag to the repository it would create the compressed file and then submit it to the file management plugin. We are going to be switching to the Downloads plugin so this already had to be changed. So new List of things to look at further. We need to figure out who plans on doing what (and if they need to be done): - Keep ?Geeklog-Core? Github organization name? - Nightly Tarball needs to grab files from Github (for both Geeklog and Pear) - Tag commit with version number which creates compressed file for download - Geeklog Bugtracker switch to Github Issues? Manual or some sort of export? Need to clean up bug and feature list anyways - Install github plugin for Jenkins - Update Website and Wiki with new links and info about Github and issues tracker Anything else I missed? Tom From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Kenji ITO Sent: Thursday, December 31, 2015 4:23 PM To: Geeklog Development Subject: Re: [geeklog-devel] Geeklog repository on GitHub I've found what looks like "Mantis-issues to GitHub-issues" converter at https://github.com/mistic100/mantis2github . I don't know if it is usable, but it's worth trying. As for PEAR, why don't we raise the required PHP version to 5.3.2 so that we can use Composer ( https://getcomposer.org/ )? 2016-01-01 6:01 GMT+09:00 Tom >: RE Pear - It's probably a good time to catch up. Do you think that is something you could work on in the next few months? (at least find out if anything major has broken) Dirk what are your thoughts on Git and the bug tracker? It will be a bit of work to get everything transferred over but once done maintenance would be a lot less. Tom -----Original Message----- From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net ] On Behalf Of Dirk Haun Sent: Thursday, December 31, 2015 11:01 AM To: Geeklog Development > Subject: Re: [geeklog-devel] Geeklog repository on GitHub Tom > wrote: > Geeklog also has more than one repository so all of them will need to be converted. - the PEAR repository, http://project.geeklog.net/cgi-bin/hgwebdir.cgi/pear/ Speaking of which: I haven't updated this in a while for fear of breaking things. On the PEAR side, quite a few packages have stopped supporting older PHP versions and made changes for PHP 7. But I guess now would be a good time to catch up? > - Geeklog Test Frame Work (needed?) Well, it's horribly out of date, very fragile, currently has a failing test(!) and all that, but it's the only kind of unit tests we have for Geeklog. > Jenkins? Dirk you know way more about this than I do. Can Jenkins use git? There's a git plugin (just like hg support is a plugin). I've never used it but I guess I could get it to work. Dirk -- https://www.themobilepresenter.com/ _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net https://pairlist8.pair.net/mailman/listinfo/geeklog-devel _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net https://pairlist8.pair.net/mailman/listinfo/geeklog-devel -- mystral-kk http://mystral-kk.net/ mystralkk at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From mystralkk at gmail.com Sat Jan 2 01:54:11 2016 From: mystralkk at gmail.com (Kenji ITO) Date: Sat, 2 Jan 2016 15:54:11 +0900 Subject: [geeklog-devel] Geeklog repository on GitHub In-Reply-To: <006001d14503$81754620$845fd260$@cogeco.net> References: <026301d143de$d17a29e0$746e7da0$@cogeco.net> <67F61D96-4E93-4F4A-B208-45913C99E52B@haun-online.de> <000801d1440e$713625e0$53a271a0$@cogeco.net> <006001d14503$81754620$845fd260$@cogeco.net> Message-ID: 2016-01-02 11:15 GMT+09:00 Tom : > Kenji - did you want to give the "Mantis-issues to GitHub-issues" a shot > after I have imported the Geeklog repository? > I would like to, but I have to be able to get access to Mantis data. Can somebody export Mantis data (SQL data) and send them to me? -------------- next part -------------- An HTML attachment was scrubbed... URL: From dirk at haun-online.de Sat Jan 2 02:43:55 2016 From: dirk at haun-online.de (Dirk Haun) Date: Sat, 2 Jan 2016 08:43:55 +0100 Subject: [geeklog-devel] Geeklog repository on GitHub In-Reply-To: <006001d14503$81754620$845fd260$@cogeco.net> References: <026301d143de$d17a29e0$746e7da0$@cogeco.net> <67F61D96-4E93-4F4A-B208-45913C99E52B@haun-online.de> <000801d1440e$713625e0$53a271a0$@cogeco.net> <006001d14503$81754620$845fd260$@cogeco.net> Message-ID: <1D5712FD-CFC4-4CC5-83EE-729922A271A3@haun-online.de> Tom wrote: > Dirk is the Bad Behavior 2 one the latest version? I was thinking of adding that one to the Geeklog-Plugins organisation. No, it's not the latest version, it's 2.0.49. Someone else did a port of the current 2.2.x branch: https://www.geeklog.net/filemgmt/index.php/1147 (That's 2.2.16 - the current release with fixes for PHP 7 is 2.2.17) > Also there is 2 Plugin Repository Repositories?. The one named ?GSoC 2009: Tim Patrick / Plugin Repository? looks to be the entire Geeklog CMS plus the repository. It has some later commits than the one named ?Plugin Repository? but it appears to be just a plugin. What do I want here? Uh ... I'm not sure. Have to get back to you on that one. Dirk -- https://www.themobilepresenter.com/ From websitemaster at cogeco.net Sat Jan 2 09:56:05 2016 From: websitemaster at cogeco.net (Tom) Date: Sat, 2 Jan 2016 09:56:05 -0500 Subject: [geeklog-devel] Geeklog repository on GitHub In-Reply-To: References: <026301d143de$d17a29e0$746e7da0$@cogeco.net> <67F61D96-4E93-4F4A-B208-45913C99E52B@haun-online.de> <000801d1440e$713625e0$53a271a0$@cogeco.net> <006001d14503$81754620$845fd260$@cogeco.net> Message-ID: <008801d1456d$b569b2d0$203d1870$@cogeco.net> It is not on the Geeklog Pair Server. Dirk where is the Bug Tracker located? From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Kenji ITO Sent: Saturday, January 2, 2016 1:54 AM To: Geeklog Development Subject: Re: [geeklog-devel] Geeklog repository on GitHub 2016-01-02 11:15 GMT+09:00 Tom >: Kenji - did you want to give the "Mantis-issues to GitHub-issues" a shot after I have imported the Geeklog repository? I would like to, but I have to be able to get access to Mantis data. Can somebody export Mantis data (SQL data) and send them to me? -------------- next part -------------- An HTML attachment was scrubbed... URL: From dirk at haun-online.de Sat Jan 2 10:21:33 2016 From: dirk at haun-online.de (Dirk Haun) Date: Sat, 2 Jan 2016 16:21:33 +0100 Subject: [geeklog-devel] Geeklog repository on GitHub In-Reply-To: <008801d1456d$b569b2d0$203d1870$@cogeco.net> References: <026301d143de$d17a29e0$746e7da0$@cogeco.net> <67F61D96-4E93-4F4A-B208-45913C99E52B@haun-online.de> <000801d1440e$713625e0$53a271a0$@cogeco.net> <006001d14503$81754620$845fd260$@cogeco.net> <008801d1456d$b569b2d0$203d1870$@cogeco.net> Message-ID: <66B03A72-341C-4473-AB3F-6158C41688BE@haun-online.de> Tom wrote: > It is not on the Geeklog Pair Server. Dirk where is the Bug Tracker located? http://project.geeklog.net/tracking/ hg.geeklog.net, project.geeklog.net and qs1489.pair.com are all the same machine, just different uses. Kenji ITO wrote: > I would like to, but I have to be able to get access to Mantis data. Can somebody export Mantis data (SQL data) and send them to me? We have automatic daily backups, but our Mantis is running on Postgres. Is that a problem? Dirk -- https://www.themobilepresenter.com/ From mystralkk at gmail.com Sat Jan 2 17:46:36 2016 From: mystralkk at gmail.com (Kenji ITO) Date: Sun, 3 Jan 2016 07:46:36 +0900 Subject: [geeklog-devel] Geeklog repository on GitHub In-Reply-To: <66B03A72-341C-4473-AB3F-6158C41688BE@haun-online.de> References: <026301d143de$d17a29e0$746e7da0$@cogeco.net> <67F61D96-4E93-4F4A-B208-45913C99E52B@haun-online.de> <000801d1440e$713625e0$53a271a0$@cogeco.net> <006001d14503$81754620$845fd260$@cogeco.net> <008801d1456d$b569b2d0$203d1870$@cogeco.net> <66B03A72-341C-4473-AB3F-6158C41688BE@haun-online.de> Message-ID: Dirk Haun wrote: > We have automatic daily backups, but our Mantis is running on Postgres. Is that a problem? The scripts I found at https://github.com/mistic100/mantis2github are for MySQLi, but I think I can manage. 2016-01-03 0:21 GMT+09:00 Dirk Haun : > Tom wrote: > > > It is not on the Geeklog Pair Server. Dirk where is the Bug Tracker > located? > > http://project.geeklog.net/tracking/ > > hg.geeklog.net, project.geeklog.net and qs1489.pair.com are all the same > machine, just different uses. > > > Kenji ITO wrote: > > > I would like to, but I have to be able to get access to Mantis data. > Can somebody export Mantis data (SQL data) and send them to me? > > We have automatic daily backups, but our Mantis is running on Postgres. Is > that a problem? > > Dirk > > > -- > https://www.themobilepresenter.com/ > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > https://pairlist8.pair.net/mailman/listinfo/geeklog-devel > -- mystral-kk http://mystral-kk.net/ mystralkk at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From websitemaster at cogeco.net Sun Jan 3 10:30:34 2016 From: websitemaster at cogeco.net (Tom) Date: Sun, 3 Jan 2016 10:30:34 -0500 Subject: [geeklog-devel] To Do list for GitHub Conversion - Use Geeklog-Core Org name? Message-ID: <00d701d1463b$b0938e10$11baaa30$@cogeco.net> First off is Geeklog-Core okay for the organization name on GitHub? Just what to tidy up on who is doing what on setting up our GitHub repositories. Please reply with what you can do along with your potential time line. Somethings are higher priority than others. To Do: - Nightly Tarball needs to grab files from Github (for both Geeklog and Pear) Low Priority - Never have looked at the script to see how it is currently done. Is this even needed now with everything Github offers? Should we just included a link to the zip on GitHub https://github.com/Geeklog-Core/geeklog/archive/master.zip - Tag commit with version number which creates compressed file for download Low Priority ? Needed for next Geeklog Release. Once again I believe GitHub does offer some of this functionality. Does anyone know more about this? - File Submission to Download Plugin on Geeklog Release Low Priority ? Maybe needed for next Geeklog Release. - Geeklog Bugtracker switch to Github Issues? Manual or some sort of export? Need to clean up bug and feature list anyways High Priority ? Kenji is looking into this. Hopefully import goes well else I can help out on coping over more recent Feature requests and bugs. This also still needs to be tidied up once imported - Install github plugin for Jenkins Medium Priority ? Dirk you got this one right? - Update Website and Wiki with new links and info about Github and issues tracker High Priority ? Once the announcement happens I can update the website and do some of the changes on the Wiki. If I have help on the wiki that would be great. I know Github has a wiki as well built in but I think we should keep with ours. I will also update Geeklog.net to use the Download Plugin at this time. - Developers update their Bio for their user account. Medium Priority ? Once this is done I will enable the ?Developers of Geeklog? page on Geeklog.net Well that is my list. Is there anything else I missed? Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: From dirk at haun-online.de Sun Jan 3 12:51:35 2016 From: dirk at haun-online.de (Dirk Haun) Date: Sun, 3 Jan 2016 18:51:35 +0100 Subject: [geeklog-devel] To Do list for GitHub Conversion - Use Geeklog-Core Org name? In-Reply-To: <00d701d1463b$b0938e10$11baaa30$@cogeco.net> References: <00d701d1463b$b0938e10$11baaa30$@cogeco.net> Message-ID: <2C87077C-AF48-4AB2-B989-06FB29EFDB68@haun-online.de> Tom wrote: > To Do: > - Nightly Tarball needs to grab files from Github (for both Geeklog and Pear) > > Low Priority - Never have looked at the script to see how it is currently done. Is this even needed now with everything Github offers? Should we just included a link to the zip on GitHub There's a bit more to creating a nightly (and release) tarball. There are some files and directories to be removed that we don't want to ship, e.g. the professional_css theme, old .sql upgrade files and those buildpackage.php files You also have to add the PEAR packages, drop the ".dist" from db-config.php.dist, siteconfig.php.dist and lib-custom.php.dist and make sure the permissions for various directories are set correctly. We also create and include a list of files that changed since the last release. > - Install github plugin for Jenkins > > Medium Priority ? Dirk you got this one right? I've installed the plugin but haven't tried pulling from github yet. Dirk -- https://www.themobilepresenter.com/ From cordiste at free.fr Sun Jan 3 17:15:21 2016 From: cordiste at free.fr (cordiste) Date: Sun, 3 Jan 2016 23:15:21 +0100 Subject: [geeklog-devel] Geeklog repository on GitHub In-Reply-To: References: <026301d143de$d17a29e0$746e7da0$@cogeco.net> <67F61D96-4E93-4F4A-B208-45913C99E52B@haun-online.de> <000801d1440e$713625e0$53a271a0$@cogeco.net> <006001d14503$81754620$845fd260$@cogeco.net> <008801d1456d$b569b2d0$203d1870$@cogeco.net> <66B03A72-341C-4473-AB3F-6158C41688BE@haun-online.de> Message-ID: Tom, I would like to add my plugins to https://github.com/Geeklog-Plugins How can we do this ? Ben 2016-01-02 23:46 GMT+01:00 Kenji ITO : > Dirk Haun wrote: > >> We have automatic daily backups, but our Mantis is running on Postgres. Is >> that a problem? > > The scripts I found at https://github.com/mistic100/mantis2github are for > MySQLi, but I think I can manage. > > > 2016-01-03 0:21 GMT+09:00 Dirk Haun : >> >> Tom wrote: >> >> > It is not on the Geeklog Pair Server. Dirk where is the Bug Tracker >> > located? >> >> http://project.geeklog.net/tracking/ >> >> hg.geeklog.net, project.geeklog.net and qs1489.pair.com are all the same >> machine, just different uses. >> >> >> Kenji ITO wrote: >> >> > I would like to, but I have to be able to get access to Mantis data. >> > Can somebody export Mantis data (SQL data) and send them to me? >> >> We have automatic daily backups, but our Mantis is running on Postgres. Is >> that a problem? >> >> Dirk >> >> >> -- >> https://www.themobilepresenter.com/ >> >> _______________________________________________ >> geeklog-devel mailing list >> geeklog-devel at lists.geeklog.net >> https://pairlist8.pair.net/mailman/listinfo/geeklog-devel > > > > > -- > mystral-kk > http://mystral-kk.net/ > mystralkk at gmail.com > > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > https://pairlist8.pair.net/mailman/listinfo/geeklog-devel > From websitemaster at cogeco.net Sun Jan 3 17:36:15 2016 From: websitemaster at cogeco.net (Tom) Date: Sun, 3 Jan 2016 17:36:15 -0500 Subject: [geeklog-devel] Geeklog repository on GitHub In-Reply-To: References: <026301d143de$d17a29e0$746e7da0$@cogeco.net> <67F61D96-4E93-4F4A-B208-45913C99E52B@haun-online.de> <000801d1440e$713625e0$53a271a0$@cogeco.net> <006001d14503$81754620$845fd260$@cogeco.net> <008801d1456d$b569b2d0$203d1870$@cogeco.net> <66B03A72-341C-4473-AB3F-6158C41688BE@haun-online.de> Message-ID: <00f401d14677$282dae70$78890b50$@cogeco.net> I couldn't find you on GitHub. Send me your GitHub name or email and I will send an invite. You may have to bear with me as I figure out how all the permissions work with GitHub. Tom -----Original Message----- From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of cordiste Sent: Sunday, January 3, 2016 5:15 PM To: Geeklog Development Subject: Re: [geeklog-devel] Geeklog repository on GitHub Tom, I would like to add my plugins to https://github.com/Geeklog-Plugins How can we do this ? Ben 2016-01-02 23:46 GMT+01:00 Kenji ITO : > Dirk Haun wrote: > >> We have automatic daily backups, but our Mantis is running on >> Postgres. Is that a problem? > > The scripts I found at https://github.com/mistic100/mantis2github are > for MySQLi, but I think I can manage. > > > 2016-01-03 0:21 GMT+09:00 Dirk Haun : >> >> Tom wrote: >> >> > It is not on the Geeklog Pair Server. Dirk where is the Bug Tracker >> > located? >> >> http://project.geeklog.net/tracking/ >> >> hg.geeklog.net, project.geeklog.net and qs1489.pair.com are all the >> same machine, just different uses. >> >> >> Kenji ITO wrote: >> >> > I would like to, but I have to be able to get access to Mantis data. >> > Can somebody export Mantis data (SQL data) and send them to me? >> >> We have automatic daily backups, but our Mantis is running on >> Postgres. Is that a problem? >> >> Dirk >> >> >> -- >> https://www.themobilepresenter.com/ >> >> _______________________________________________ >> geeklog-devel mailing list >> geeklog-devel at lists.geeklog.net >> https://pairlist8.pair.net/mailman/listinfo/geeklog-devel > > > > > -- > mystral-kk > http://mystral-kk.net/ > mystralkk at gmail.com > > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > https://pairlist8.pair.net/mailman/listinfo/geeklog-devel > _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net https://pairlist8.pair.net/mailman/listinfo/geeklog-devel From cordiste at free.fr Sun Jan 3 17:45:15 2016 From: cordiste at free.fr (cordiste) Date: Sun, 3 Jan 2016 23:45:15 +0100 Subject: [geeklog-devel] To Do list for GitHub Conversion - Use Geeklog-Core Org name? In-Reply-To: <2C87077C-AF48-4AB2-B989-06FB29EFDB68@haun-online.de> References: <00d701d1463b$b0938e10$11baaa30$@cogeco.net> <2C87077C-AF48-4AB2-B989-06FB29EFDB68@haun-online.de> Message-ID: +1 for Geeklog-Core name +1 to include a link to https://github.com/Geeklog-Core/geeklog/archive/master.zip To make this archive usable we just need to: - Remove the professional_css theme, old .sql upgrade files and those buildpackage.php files from the repository - Add the pear packages to the repository - modify the index.php and COM_checkInstalled to rename db-config.php.dist, siteconfig.php.dist and lib-custom.php.dist - Add a link to https://github.com/Geeklog-Core/geeklog/commits/master in the Geeklog History/Changes: public_html/docs/history Ben 2016-01-03 18:51 GMT+01:00 Dirk Haun : > Tom wrote: > >> To Do: >> - Nightly Tarball needs to grab files from Github (for both Geeklog and Pear) >> >> Low Priority - Never have looked at the script to see how it is currently done. Is this even needed now with everything Github offers? Should we just included a link to the zip on GitHub > > There's a bit more to creating a nightly (and release) tarball. There are some files and directories to be removed that we don't want to ship, e.g. the professional_css theme, old .sql upgrade files and those buildpackage.php files > > You also have to add the PEAR packages, drop the ".dist" from db-config.php.dist, siteconfig.php.dist and lib-custom.php.dist and make sure the permissions for various directories are set correctly. > > We also create and include a list of files that changed since the last release. > > >> - Install github plugin for Jenkins >> >> Medium Priority ? Dirk you got this one right? > > I've installed the plugin but haven't tried pulling from github yet. > > Dirk > > > -- > https://www.themobilepresenter.com/ > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > https://pairlist8.pair.net/mailman/listinfo/geeklog-devel From cordiste at free.fr Mon Jan 4 06:05:18 2016 From: cordiste at free.fr (cordiste) Date: Mon, 4 Jan 2016 12:05:18 +0100 Subject: [geeklog-devel] Geeklog repository on GitHub In-Reply-To: <00f401d14677$282dae70$78890b50$@cogeco.net> References: <026301d143de$d17a29e0$746e7da0$@cogeco.net> <67F61D96-4E93-4F4A-B208-45913C99E52B@haun-online.de> <000801d1440e$713625e0$53a271a0$@cogeco.net> <006001d14503$81754620$845fd260$@cogeco.net> <008801d1456d$b569b2d0$203d1870$@cogeco.net> <66B03A72-341C-4473-AB3F-6158C41688BE@haun-online.de> <00f401d14677$282dae70$78890b50$@cogeco.net> Message-ID: If anyone want to follow me on github :) My profile is on https://github.com/hostellerie You can read about permission levels for an organization on https://help.github.com/articles/permission-levels-for-an-organization/ Ben 2016-01-03 23:36 GMT+01:00 Tom : > I couldn't find you on GitHub. Send me your GitHub name or email and I will > send an invite. > > You may have to bear with me as I figure out how all the permissions work > with GitHub. > > Tom > > -----Original Message----- > From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] On > Behalf Of cordiste > Sent: Sunday, January 3, 2016 5:15 PM > To: Geeklog Development > Subject: Re: [geeklog-devel] Geeklog repository on GitHub > > Tom, > > I would like to add my plugins to https://github.com/Geeklog-Plugins > How can we do this ? > > Ben > > 2016-01-02 23:46 GMT+01:00 Kenji ITO : >> Dirk Haun wrote: >> >>> We have automatic daily backups, but our Mantis is running on >>> Postgres. Is that a problem? >> >> The scripts I found at https://github.com/mistic100/mantis2github are >> for MySQLi, but I think I can manage. >> >> >> 2016-01-03 0:21 GMT+09:00 Dirk Haun : >>> >>> Tom wrote: >>> >>> > It is not on the Geeklog Pair Server. Dirk where is the Bug Tracker >>> > located? >>> >>> http://project.geeklog.net/tracking/ >>> >>> hg.geeklog.net, project.geeklog.net and qs1489.pair.com are all the >>> same machine, just different uses. >>> >>> >>> Kenji ITO wrote: >>> >>> > I would like to, but I have to be able to get access to Mantis data. >>> > Can somebody export Mantis data (SQL data) and send them to me? >>> >>> We have automatic daily backups, but our Mantis is running on >>> Postgres. Is that a problem? >>> >>> Dirk >>> >>> >>> -- >>> https://www.themobilepresenter.com/ >>> >>> _______________________________________________ >>> geeklog-devel mailing list >>> geeklog-devel at lists.geeklog.net >>> https://pairlist8.pair.net/mailman/listinfo/geeklog-devel >> >> >> >> >> -- >> mystral-kk >> http://mystral-kk.net/ >> mystralkk at gmail.com >> >> >> _______________________________________________ >> geeklog-devel mailing list >> geeklog-devel at lists.geeklog.net >> https://pairlist8.pair.net/mailman/listinfo/geeklog-devel >> > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > https://pairlist8.pair.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > https://pairlist8.pair.net/mailman/listinfo/geeklog-devel > From komma at ivywe.co.jp Tue Jan 5 05:53:29 2016 From: komma at ivywe.co.jp (=?UTF-8?B?5LuK6aeS5ZOy5a2Q?=) Date: Tue, 5 Jan 2016 19:53:29 +0900 Subject: [geeklog-devel] Geeklog repository on GitHub In-Reply-To: References: <026301d143de$d17a29e0$746e7da0$@cogeco.net> <67F61D96-4E93-4F4A-B208-45913C99E52B@haun-online.de> <000801d1440e$713625e0$53a271a0$@cogeco.net> <006001d14503$81754620$845fd260$@cogeco.net> <008801d1456d$b569b2d0$203d1870$@cogeco.net> <66B03A72-341C-4473-AB3F-6158C41688BE@haun-online.de> <00f401d14677$282dae70$78890b50$@cogeco.net> Message-ID: Ben, Thank you so much. > If anyone want to follow me on github :) > My profile is on https://github.com/hostellerie I did. I added you as theme "default" Collaborators. https://github.com/ivywe/Default/settings/collaboration If anyone want to join us, please Fork and Pull Request to us. Thanks. -- Ivy From cordiste at free.fr Fri Jan 8 06:00:03 2016 From: cordiste at free.fr (cordiste) Date: Fri, 8 Jan 2016 12:00:03 +0100 Subject: [geeklog-devel] mysql connection issue Message-ID: Hi all, I just updated a server to mysql 5.6 and every sites with Geeklog display "Unfortunately, an error has occurred rendering this page. Please try again later. " Debug tell me the error is mysql_connect(): Headers and client library minor version mismatch. Headers:50542 Library:50627 The question is why wordpress or joomla sites are still working on the same server and not Geeklog? Ben From websitemaster at cogeco.net Fri Jan 8 06:52:57 2016 From: websitemaster at cogeco.net (Tom) Date: Fri, 8 Jan 2016 06:52:57 -0500 Subject: [geeklog-devel] mysql connection issue In-Reply-To: References: Message-ID: <128201d14a0b$1e040290$5a0c07b0$@cogeco.net> Your Geeklog install must be using a different php extension to try and connect to mysql than the other cms's. Make sure you update that extension to version 5.6. Tom -----Original Message----- From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of cordiste Sent: Friday, January 8, 2016 6:00 AM To: Geeklog Subject: [geeklog-devel] mysql connection issue Hi all, I just updated a server to mysql 5.6 and every sites with Geeklog display "Unfortunately, an error has occurred rendering this page. Please try again later. " Debug tell me the error is mysql_connect(): Headers and client library minor version mismatch. Headers:50542 Library:50627 The question is why wordpress or joomla sites are still working on the same server and not Geeklog? Ben _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net https://pairlist8.pair.net/mailman/listinfo/geeklog-devel From cordiste at free.fr Fri Jan 8 08:13:38 2016 From: cordiste at free.fr (cordiste) Date: Fri, 8 Jan 2016 14:13:38 +0100 Subject: [geeklog-devel] mysql connection issue In-Reply-To: <128201d14a0b$1e040290$5a0c07b0$@cogeco.net> References: <128201d14a0b$1e040290$5a0c07b0$@cogeco.net> Message-ID: Very strange because all users on this VPS are using the same php version. Ben 2016-01-08 12:52 GMT+01:00 Tom : > Your Geeklog install must be using a different php extension to try and > connect to mysql than the other cms's. Make sure you update that extension > to version 5.6. > > Tom > > -----Original Message----- > From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] On > Behalf Of cordiste > Sent: Friday, January 8, 2016 6:00 AM > To: Geeklog > Subject: [geeklog-devel] mysql connection issue > > Hi all, > > I just updated a server to mysql 5.6 and every sites with Geeklog display > "Unfortunately, an error has occurred rendering this page. > Please try again later. " > > Debug tell me the error is mysql_connect(): Headers and client library minor > version mismatch. Headers:50542 Library:50627 > > The question is why wordpress or joomla sites are still working on the same > server and not Geeklog? > > Ben > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > https://pairlist8.pair.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > https://pairlist8.pair.net/mailman/listinfo/geeklog-devel > From websitemaster at cogeco.net Fri Jan 8 09:58:01 2016 From: websitemaster at cogeco.net (Tom) Date: Fri, 8 Jan 2016 09:58:01 -0500 Subject: [geeklog-devel] mysql connection issue In-Reply-To: References: <128201d14a0b$1e040290$5a0c07b0$@cogeco.net> Message-ID: <12a501d14a24$f89f69d0$e9de3d70$@cogeco.net> Are you sure? Maybe you are using the mysqli php extension (which Geeklog will default to) and the others are using the regular mysql php extension. You could modify lib-database.php around line 133 and remove the mysqli check and just include: require_once $_CONF['path_system'] . 'databases/'. $_DB_dbms . '.class.php'; Here is someone else who is having a similar problem (different versions though) and the solution. It looks like you will need to upgrade PHP or at least the extension you are using. See below: http://stackoverflow.com/questions/10759334/headers-and-client-library-minor -version-mismatch Your PHP was compiled with MySQL 5.1 but now it is linking a mysql library of 5.5.X family. You have to upgrade PHP to a version compiled with MySQL 5.5 or revert back mysql client libraries to 5.1.x. Tom -----Original Message----- From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of cordiste Sent: Friday, January 8, 2016 8:14 AM To: Geeklog Development Subject: Re: [geeklog-devel] mysql connection issue Very strange because all users on this VPS are using the same php version. Ben 2016-01-08 12:52 GMT+01:00 Tom : > Your Geeklog install must be using a different php extension to try > and connect to mysql than the other cms's. Make sure you update that > extension to version 5.6. > > Tom > > -----Original Message----- > From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] > On Behalf Of cordiste > Sent: Friday, January 8, 2016 6:00 AM > To: Geeklog > Subject: [geeklog-devel] mysql connection issue > > Hi all, > > I just updated a server to mysql 5.6 and every sites with Geeklog > display "Unfortunately, an error has occurred rendering this page. > Please try again later. " > > Debug tell me the error is mysql_connect(): Headers and client library > minor version mismatch. Headers:50542 Library:50627 > > The question is why wordpress or joomla sites are still working on the > same server and not Geeklog? > > Ben > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > https://pairlist8.pair.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > https://pairlist8.pair.net/mailman/listinfo/geeklog-devel > _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net https://pairlist8.pair.net/mailman/listinfo/geeklog-devel From cordiste at free.fr Fri Jan 8 13:52:02 2016 From: cordiste at free.fr (cordiste) Date: Fri, 8 Jan 2016 19:52:02 +0100 Subject: [geeklog-devel] mysql connection issue In-Reply-To: <12a501d14a24$f89f69d0$e9de3d70$@cogeco.net> References: <128201d14a0b$1e040290$5a0c07b0$@cogeco.net> <12a501d14a24$f89f69d0$e9de3d70$@cogeco.net> Message-ID: Yes I'm sure :) Thanks for the link. On this VPS, some of the Geeklog sites are 1.8.2 (no mysqli) and some are 2.1.1. The strange thing is that other CMS are working with PHP not compiled with MySQL 5.6 8) and Geeklog is not :( The hosting provider is also checking this issue... 2016-01-08 15:58 GMT+01:00 Tom : > Are you sure? Maybe you are using the mysqli php extension (which Geeklog > will default to) and the others are using the regular mysql php extension. > > You could modify lib-database.php around line 133 and remove the mysqli > check and just include: > > require_once $_CONF['path_system'] . 'databases/'. $_DB_dbms . '.class.php'; > > > Here is someone else who is having a similar problem (different versions > though) and the solution. It looks like you will need to upgrade PHP or at > least the extension you are using. See below: > > http://stackoverflow.com/questions/10759334/headers-and-client-library-minor > -version-mismatch > > Your PHP was compiled with MySQL 5.1 but now it is linking a mysql library > of 5.5.X family. You have to upgrade PHP to a version compiled with MySQL > 5.5 or revert back mysql client libraries to 5.1.x. > > Tom > > > -----Original Message----- > From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] On > Behalf Of cordiste > Sent: Friday, January 8, 2016 8:14 AM > To: Geeklog Development > Subject: Re: [geeklog-devel] mysql connection issue > > Very strange because all users on this VPS are using the same php version. > > Ben > > 2016-01-08 12:52 GMT+01:00 Tom : >> Your Geeklog install must be using a different php extension to try >> and connect to mysql than the other cms's. Make sure you update that >> extension to version 5.6. >> >> Tom >> >> -----Original Message----- >> From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] >> On Behalf Of cordiste >> Sent: Friday, January 8, 2016 6:00 AM >> To: Geeklog >> Subject: [geeklog-devel] mysql connection issue >> >> Hi all, >> >> I just updated a server to mysql 5.6 and every sites with Geeklog >> display "Unfortunately, an error has occurred rendering this page. >> Please try again later. " >> >> Debug tell me the error is mysql_connect(): Headers and client library >> minor version mismatch. Headers:50542 Library:50627 >> >> The question is why wordpress or joomla sites are still working on the >> same server and not Geeklog? >> >> Ben >> _______________________________________________ >> geeklog-devel mailing list >> geeklog-devel at lists.geeklog.net >> https://pairlist8.pair.net/mailman/listinfo/geeklog-devel >> >> _______________________________________________ >> geeklog-devel mailing list >> geeklog-devel at lists.geeklog.net >> https://pairlist8.pair.net/mailman/listinfo/geeklog-devel >> > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > https://pairlist8.pair.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > https://pairlist8.pair.net/mailman/listinfo/geeklog-devel > From websitemaster at cogeco.net Fri Jan 8 14:29:13 2016 From: websitemaster at cogeco.net (Tom) Date: Fri, 8 Jan 2016 14:29:13 -0500 Subject: [geeklog-devel] mysql connection issue In-Reply-To: References: <128201d14a0b$1e040290$5a0c07b0$@cogeco.net> <12a501d14a24$f89f69d0$e9de3d70$@cogeco.net> Message-ID: <12b701d14a4a$db6c53c0$9244fb40$@cogeco.net> Weird. Let us know what the outcome is. -----Original Message----- From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of cordiste Sent: Friday, January 8, 2016 1:52 PM To: Geeklog Development Subject: Re: [geeklog-devel] mysql connection issue Yes I'm sure :) Thanks for the link. On this VPS, some of the Geeklog sites are 1.8.2 (no mysqli) and some are 2.1.1. The strange thing is that other CMS are working with PHP not compiled with MySQL 5.6 8) and Geeklog is not :( The hosting provider is also checking this issue... 2016-01-08 15:58 GMT+01:00 Tom : > Are you sure? Maybe you are using the mysqli php extension (which > Geeklog will default to) and the others are using the regular mysql php extension. > > You could modify lib-database.php around line 133 and remove the > mysqli check and just include: > > require_once $_CONF['path_system'] . 'databases/'. $_DB_dbms . > '.class.php'; > > > Here is someone else who is having a similar problem (different > versions > though) and the solution. It looks like you will need to upgrade PHP > or at least the extension you are using. See below: > > http://stackoverflow.com/questions/10759334/headers-and-client-library > -minor > -version-mismatch > > Your PHP was compiled with MySQL 5.1 but now it is linking a mysql > library of 5.5.X family. You have to upgrade PHP to a version compiled > with MySQL > 5.5 or revert back mysql client libraries to 5.1.x. > > Tom > > > -----Original Message----- > From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] > On Behalf Of cordiste > Sent: Friday, January 8, 2016 8:14 AM > To: Geeklog Development > Subject: Re: [geeklog-devel] mysql connection issue > > Very strange because all users on this VPS are using the same php version. > > Ben > > 2016-01-08 12:52 GMT+01:00 Tom : >> Your Geeklog install must be using a different php extension to try >> and connect to mysql than the other cms's. Make sure you update that >> extension to version 5.6. >> >> Tom >> >> -----Original Message----- >> From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] >> On Behalf Of cordiste >> Sent: Friday, January 8, 2016 6:00 AM >> To: Geeklog >> Subject: [geeklog-devel] mysql connection issue >> >> Hi all, >> >> I just updated a server to mysql 5.6 and every sites with Geeklog >> display "Unfortunately, an error has occurred rendering this page. >> Please try again later. " >> >> Debug tell me the error is mysql_connect(): Headers and client >> library minor version mismatch. Headers:50542 Library:50627 >> >> The question is why wordpress or joomla sites are still working on >> the same server and not Geeklog? >> >> Ben >> _______________________________________________ >> geeklog-devel mailing list >> geeklog-devel at lists.geeklog.net >> https://pairlist8.pair.net/mailman/listinfo/geeklog-devel >> >> _______________________________________________ >> geeklog-devel mailing list >> geeklog-devel at lists.geeklog.net >> https://pairlist8.pair.net/mailman/listinfo/geeklog-devel >> > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > https://pairlist8.pair.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > https://pairlist8.pair.net/mailman/listinfo/geeklog-devel > _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net https://pairlist8.pair.net/mailman/listinfo/geeklog-devel From websitemaster at cogeco.net Fri Jan 8 14:41:07 2016 From: websitemaster at cogeco.net (Tom) Date: Fri, 8 Jan 2016 14:41:07 -0500 Subject: [geeklog-devel] Geeklog has Switch to GitHub Message-ID: <12b801d14a4c$850f08e0$8f2d1aa0$@cogeco.net> Well it is official. Geeklog has switched to GitHub The Geeklog Core Organization with the repositories can be found here: https://github.com/Geeklog-Core We also are now using the GitHub Issues Tracker for all Geeklog Bug Reports and Feature Requests. Please submit all new issues and comment on any existing issues here: https://github.com/Geeklog-Core/geeklog The old Mercurial repository and Mantis Bug Tracker that we use will still exist for the time being as we organize things but please do not add any new information to them. We will also be updating Geeklog.net and the Geeklog Wiki over the next week with this new information. For more information on the switch please read: https://www.geeklog.net/article.php/geeklog-has-switched-to-github Tom From danstoner at gmail.com Fri Jan 8 16:33:25 2016 From: danstoner at gmail.com (Dan Stoner) Date: Fri, 8 Jan 2016 16:33:25 -0500 Subject: [geeklog-devel] Geeklog has Switch to GitHub In-Reply-To: <12b801d14a4c$850f08e0$8f2d1aa0$@cogeco.net> References: <12b801d14a4c$850f08e0$8f2d1aa0$@cogeco.net> Message-ID: I think this is great and will likely increase chances of contributions. - Dan Stoner On Fri, Jan 8, 2016 at 2:41 PM, Tom wrote: > Well it is official. Geeklog has switched to GitHub > > The Geeklog Core Organization with the repositories can be found here: > https://github.com/Geeklog-Core > > We also are now using the GitHub Issues Tracker for all Geeklog Bug Reports > and Feature Requests. Please submit all new issues and comment on any > existing issues here: https://github.com/Geeklog-Core/geeklog > > The old Mercurial repository and Mantis Bug Tracker that we use will still > exist for the time being as we organize things but please do not add any new > information to them. > > We will also be updating Geeklog.net and the Geeklog Wiki over the next week > with this new information. > > For more information on the switch please read: > https://www.geeklog.net/article.php/geeklog-has-switched-to-github > > Tom > > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > https://pairlist8.pair.net/mailman/listinfo/geeklog-devel From websitemaster at cogeco.net Mon Jan 11 06:44:55 2016 From: websitemaster at cogeco.net (Tom) Date: Mon, 11 Jan 2016 06:44:55 -0500 Subject: [geeklog-devel] CVS Mailing list Message-ID: <002901d14c65$7de9b090$79bd11b0$@cogeco.net> Do we want to keep the CVS Mailing list? People can now follow repositories which lets them know of changes etc so I am not sure if it is needed though I did like having the ability to search quickly any changes through Outlook the odd time I needed to (though I assume this is easy to do on GitHub as well). To get the mailing list to work again I assume I will have to create it a GitHub account using the geeklog-cvs at lists.geeklog.net email address. Thoughts? Tom -----Original Message----- From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Dan Stoner Sent: Friday, January 8, 2016 4:33 PM To: Geeklog Development Subject: Re: [geeklog-devel] Geeklog has Switch to GitHub I think this is great and will likely increase chances of contributions. - Dan Stoner On Fri, Jan 8, 2016 at 2:41 PM, Tom wrote: > Well it is official. Geeklog has switched to GitHub > > The Geeklog Core Organization with the repositories can be found here: > https://github.com/Geeklog-Core > > We also are now using the GitHub Issues Tracker for all Geeklog Bug > Reports and Feature Requests. Please submit all new issues and comment > on any existing issues here: https://github.com/Geeklog-Core/geeklog > > The old Mercurial repository and Mantis Bug Tracker that we use will > still exist for the time being as we organize things but please do not > add any new information to them. > > We will also be updating Geeklog.net and the Geeklog Wiki over the > next week with this new information. > > For more information on the switch please read: > https://www.geeklog.net/article.php/geeklog-has-switched-to-github > > Tom > > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > https://pairlist8.pair.net/mailman/listinfo/geeklog-devel _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net https://pairlist8.pair.net/mailman/listinfo/geeklog-devel From cordiste at free.fr Thu Jan 14 07:11:17 2016 From: cordiste at free.fr (cordiste) Date: Thu, 14 Jan 2016 13:11:17 +0100 Subject: [geeklog-devel] mysql connection issue In-Reply-To: <12b701d14a4a$db6c53c0$9244fb40$@cogeco.net> References: <128201d14a0b$1e040290$5a0c07b0$@cogeco.net> <12a501d14a24$f89f69d0$e9de3d70$@cogeco.net> <12b701d14a4a$db6c53c0$9244fb40$@cogeco.net> Message-ID: I needed to delete and then recreate all DB users to make it work. 2016-01-08 20:29 GMT+01:00 Tom : > Weird. Let us know what the outcome is. > > -----Original Message----- > From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] On > Behalf Of cordiste > Sent: Friday, January 8, 2016 1:52 PM > To: Geeklog Development > Subject: Re: [geeklog-devel] mysql connection issue > > Yes I'm sure :) > > Thanks for the link. > > On this VPS, some of the Geeklog sites are 1.8.2 (no mysqli) and some are > 2.1.1. The strange thing is that other CMS are working with PHP not compiled > with MySQL 5.6 8) and Geeklog is not :( > > The hosting provider is also checking this issue... > > 2016-01-08 15:58 GMT+01:00 Tom : >> Are you sure? Maybe you are using the mysqli php extension (which >> Geeklog will default to) and the others are using the regular mysql php > extension. >> >> You could modify lib-database.php around line 133 and remove the >> mysqli check and just include: >> >> require_once $_CONF['path_system'] . 'databases/'. $_DB_dbms . >> '.class.php'; >> >> >> Here is someone else who is having a similar problem (different >> versions >> though) and the solution. It looks like you will need to upgrade PHP >> or at least the extension you are using. See below: >> >> http://stackoverflow.com/questions/10759334/headers-and-client-library >> -minor >> -version-mismatch >> >> Your PHP was compiled with MySQL 5.1 but now it is linking a mysql >> library of 5.5.X family. You have to upgrade PHP to a version compiled >> with MySQL >> 5.5 or revert back mysql client libraries to 5.1.x. >> >> Tom >> >> >> -----Original Message----- >> From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] >> On Behalf Of cordiste >> Sent: Friday, January 8, 2016 8:14 AM >> To: Geeklog Development >> Subject: Re: [geeklog-devel] mysql connection issue >> >> Very strange because all users on this VPS are using the same php version. >> >> Ben >> >> 2016-01-08 12:52 GMT+01:00 Tom : >>> Your Geeklog install must be using a different php extension to try >>> and connect to mysql than the other cms's. Make sure you update that >>> extension to version 5.6. >>> >>> Tom >>> >>> -----Original Message----- >>> From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] >>> On Behalf Of cordiste >>> Sent: Friday, January 8, 2016 6:00 AM >>> To: Geeklog >>> Subject: [geeklog-devel] mysql connection issue >>> >>> Hi all, >>> >>> I just updated a server to mysql 5.6 and every sites with Geeklog >>> display "Unfortunately, an error has occurred rendering this page. >>> Please try again later. " >>> >>> Debug tell me the error is mysql_connect(): Headers and client >>> library minor version mismatch. Headers:50542 Library:50627 >>> >>> The question is why wordpress or joomla sites are still working on >>> the same server and not Geeklog? >>> >>> Ben >>> _______________________________________________ >>> geeklog-devel mailing list >>> geeklog-devel at lists.geeklog.net >>> https://pairlist8.pair.net/mailman/listinfo/geeklog-devel >>> >>> _______________________________________________ >>> geeklog-devel mailing list >>> geeklog-devel at lists.geeklog.net >>> https://pairlist8.pair.net/mailman/listinfo/geeklog-devel >>> >> _______________________________________________ >> geeklog-devel mailing list >> geeklog-devel at lists.geeklog.net >> https://pairlist8.pair.net/mailman/listinfo/geeklog-devel >> >> _______________________________________________ >> geeklog-devel mailing list >> geeklog-devel at lists.geeklog.net >> https://pairlist8.pair.net/mailman/listinfo/geeklog-devel >> > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > https://pairlist8.pair.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > https://pairlist8.pair.net/mailman/listinfo/geeklog-devel > From cordiste at free.fr Thu Jan 14 07:16:02 2016 From: cordiste at free.fr (cordiste) Date: Thu, 14 Jan 2016 13:16:02 +0100 Subject: [geeklog-devel] Geeklog has Switch to GitHub In-Reply-To: References: <12b801d14a4c$850f08e0$8f2d1aa0$@cogeco.net> Message-ID: Hi all, Nice switch. https://github.com/orgs/Geeklog-Core/people No public members https://github.com/orgs/Geeklog-Plugins/people I'm alone Do you really want to be anonymous members? :) Ben 2016-01-08 22:33 GMT+01:00 Dan Stoner : > I think this is great and will likely increase chances of contributions. > > - Dan Stoner > > > > On Fri, Jan 8, 2016 at 2:41 PM, Tom wrote: >> Well it is official. Geeklog has switched to GitHub >> >> The Geeklog Core Organization with the repositories can be found here: >> https://github.com/Geeklog-Core >> >> We also are now using the GitHub Issues Tracker for all Geeklog Bug Reports >> and Feature Requests. Please submit all new issues and comment on any >> existing issues here: https://github.com/Geeklog-Core/geeklog >> >> The old Mercurial repository and Mantis Bug Tracker that we use will still >> exist for the time being as we organize things but please do not add any new >> information to them. >> >> We will also be updating Geeklog.net and the Geeklog Wiki over the next week >> with this new information. >> >> For more information on the switch please read: >> https://www.geeklog.net/article.php/geeklog-has-switched-to-github >> >> Tom >> >> >> _______________________________________________ >> geeklog-devel mailing list >> geeklog-devel at lists.geeklog.net >> https://pairlist8.pair.net/mailman/listinfo/geeklog-devel > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > https://pairlist8.pair.net/mailman/listinfo/geeklog-devel > From dirk at haun-online.de Thu Jan 14 08:25:25 2016 From: dirk at haun-online.de (Dirk Haun) Date: Thu, 14 Jan 2016 14:25:25 +0100 Subject: [geeklog-devel] Geeklog has Switch to GitHub In-Reply-To: References: <12b801d14a4c$850f08e0$8f2d1aa0$@cogeco.net> Message-ID: <328E5520-44E4-4537-A76E-F947DC66BB4F@haun-online.de> cordiste wrote: > https://github.com/orgs/Geeklog-Core/people > No public members Hmm, that must be some odd default. Switched my membership to public now. Thanks for pointing this out. Dirk -- https://www.themobilepresenter.com/ From websitemaster at cogeco.net Thu Jan 14 09:12:10 2016 From: websitemaster at cogeco.net (Tom) Date: Thu, 14 Jan 2016 09:12:10 -0500 Subject: [geeklog-devel] Geeklog has Switch to GitHub In-Reply-To: <328E5520-44E4-4537-A76E-F947DC66BB4F@haun-online.de> References: <12b801d14a4c$850f08e0$8f2d1aa0$@cogeco.net> <328E5520-44E4-4537-A76E-F947DC66BB4F@haun-online.de> Message-ID: <000a01d14ed5$8f4eed10$adecc730$@cogeco.net> Had not noticed either. I switched both to public. Tom -----Original Message----- From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Dirk Haun Sent: Thursday, January 14, 2016 8:25 AM To: Geeklog Development Subject: Re: [geeklog-devel] Geeklog has Switch to GitHub cordiste wrote: > https://github.com/orgs/Geeklog-Core/people > No public members Hmm, that must be some odd default. Switched my membership to public now. Thanks for pointing this out. Dirk -- https://www.themobilepresenter.com/ _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net https://pairlist8.pair.net/mailman/listinfo/geeklog-devel From websitemaster at cogeco.net Thu Jan 14 09:13:24 2016 From: websitemaster at cogeco.net (Tom) Date: Thu, 14 Jan 2016 09:13:24 -0500 Subject: [geeklog-devel] mysql connection issue In-Reply-To: References: <128201d14a0b$1e040290$5a0c07b0$@cogeco.net> <12a501d14a24$f89f69d0$e9de3d70$@cogeco.net> <12b701d14a4a$db6c53c0$9244fb40$@cogeco.net> Message-ID: <000b01d14ed5$bb104020$3130c060$@cogeco.net> Weird. I wonder why it gave the error it did. Tom -----Original Message----- From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of cordiste Sent: Thursday, January 14, 2016 7:11 AM To: Geeklog Development Subject: Re: [geeklog-devel] mysql connection issue I needed to delete and then recreate all DB users to make it work. 2016-01-08 20:29 GMT+01:00 Tom : > Weird. Let us know what the outcome is. > > -----Original Message----- > From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] > On Behalf Of cordiste > Sent: Friday, January 8, 2016 1:52 PM > To: Geeklog Development > Subject: Re: [geeklog-devel] mysql connection issue > > Yes I'm sure :) > > Thanks for the link. > > On this VPS, some of the Geeklog sites are 1.8.2 (no mysqli) and some > are 2.1.1. The strange thing is that other CMS are working with PHP > not compiled with MySQL 5.6 8) and Geeklog is not :( > > The hosting provider is also checking this issue... > > 2016-01-08 15:58 GMT+01:00 Tom : >> Are you sure? Maybe you are using the mysqli php extension (which >> Geeklog will default to) and the others are using the regular mysql >> php > extension. >> >> You could modify lib-database.php around line 133 and remove the >> mysqli check and just include: >> >> require_once $_CONF['path_system'] . 'databases/'. $_DB_dbms . >> '.class.php'; >> >> >> Here is someone else who is having a similar problem (different >> versions >> though) and the solution. It looks like you will need to upgrade PHP >> or at least the extension you are using. See below: >> >> http://stackoverflow.com/questions/10759334/headers-and-client-librar >> y >> -minor >> -version-mismatch >> >> Your PHP was compiled with MySQL 5.1 but now it is linking a mysql >> library of 5.5.X family. You have to upgrade PHP to a version >> compiled with MySQL >> 5.5 or revert back mysql client libraries to 5.1.x. >> >> Tom >> >> >> -----Original Message----- >> From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] >> On Behalf Of cordiste >> Sent: Friday, January 8, 2016 8:14 AM >> To: Geeklog Development >> Subject: Re: [geeklog-devel] mysql connection issue >> >> Very strange because all users on this VPS are using the same php version. >> >> Ben >> >> 2016-01-08 12:52 GMT+01:00 Tom : >>> Your Geeklog install must be using a different php extension to try >>> and connect to mysql than the other cms's. Make sure you update that >>> extension to version 5.6. >>> >>> Tom >>> >>> -----Original Message----- >>> From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] >>> On Behalf Of cordiste >>> Sent: Friday, January 8, 2016 6:00 AM >>> To: Geeklog >>> Subject: [geeklog-devel] mysql connection issue >>> >>> Hi all, >>> >>> I just updated a server to mysql 5.6 and every sites with Geeklog >>> display "Unfortunately, an error has occurred rendering this page. >>> Please try again later. " >>> >>> Debug tell me the error is mysql_connect(): Headers and client >>> library minor version mismatch. Headers:50542 Library:50627 >>> >>> The question is why wordpress or joomla sites are still working on >>> the same server and not Geeklog? >>> >>> Ben >>> _______________________________________________ >>> geeklog-devel mailing list >>> geeklog-devel at lists.geeklog.net >>> https://pairlist8.pair.net/mailman/listinfo/geeklog-devel >>> >>> _______________________________________________ >>> geeklog-devel mailing list >>> geeklog-devel at lists.geeklog.net >>> https://pairlist8.pair.net/mailman/listinfo/geeklog-devel >>> >> _______________________________________________ >> geeklog-devel mailing list >> geeklog-devel at lists.geeklog.net >> https://pairlist8.pair.net/mailman/listinfo/geeklog-devel >> >> _______________________________________________ >> geeklog-devel mailing list >> geeklog-devel at lists.geeklog.net >> https://pairlist8.pair.net/mailman/listinfo/geeklog-devel >> > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > https://pairlist8.pair.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > https://pairlist8.pair.net/mailman/listinfo/geeklog-devel > _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net https://pairlist8.pair.net/mailman/listinfo/geeklog-devel From websitemaster at cogeco.net Thu Jan 14 09:33:13 2016 From: websitemaster at cogeco.net (Tom) Date: Thu, 14 Jan 2016 09:33:13 -0500 Subject: [geeklog-devel] Google Code Geeklog Plugin Repositories Message-ID: <001501d14ed8$7ff79710$7fe6c530$@cogeco.net> By the way I had Google update the Google Code Geeklog Plugin Repositories with a link pointing to the GitHub Geeklog Plugins Organization. Tom From websitemaster at cogeco.net Sun Jan 17 10:27:26 2016 From: websitemaster at cogeco.net (Tom) Date: Sun, 17 Jan 2016 10:27:26 -0500 Subject: [geeklog-devel] GitHub and CVS Mailing List Message-ID: <015701d1513b$92750d40$b75f27c0$@cogeco.net> I notice that someone had got GitHub to post commits to the Geeklog CVS mailing list, at least the last batch on Tuesday. Today's commits didn't get added. Do we know why? What was the fix? Tom From dirk at haun-online.de Sun Jan 17 10:36:57 2016 From: dirk at haun-online.de (Dirk Haun) Date: Sun, 17 Jan 2016 16:36:57 +0100 Subject: [geeklog-devel] GitHub and CVS Mailing List In-Reply-To: <015701d1513b$92750d40$b75f27c0$@cogeco.net> References: <015701d1513b$92750d40$b75f27c0$@cogeco.net> Message-ID: <91D08EAE-E8BE-401E-96AB-D677DA5CF996@haun-online.de> Tom wrote: > I notice that someone had got GitHub to post commits to the Geeklog CVS > mailing list, at least the last batch on Tuesday. I don't know who sent them there, but I noticed a couple of GitHub notifications in the moderation queue for geeklog-cvs and whitelisted the address they were coming from (noreply at github.com) > Today's commits didn't get added. Do we know why? What was the fix? The configuration of the mailing list hasn't changed and there's nothing in the moderation queue. Doesn't look like the problem is on this end. Dirk -- https://www.themobilepresenter.com/ From websitemaster at cogeco.net Mon Jan 18 06:57:10 2016 From: websitemaster at cogeco.net (Tom) Date: Mon, 18 Jan 2016 06:57:10 -0500 Subject: [geeklog-devel] GitHub and CVS Mailing List In-Reply-To: <91D08EAE-E8BE-401E-96AB-D677DA5CF996@haun-online.de> References: <015701d1513b$92750d40$b75f27c0$@cogeco.net> <91D08EAE-E8BE-401E-96AB-D677DA5CF996@haun-online.de> Message-ID: <01a601d151e7$5cd60480$16820d80$@cogeco.net> I found where the email is being sent from: https://github.com/Geeklog-Core/geeklog/settings/hooks (note only owners can see this) It is one of many services. This one called email has the following options: Install Notes 1. address whitespace separated email addresses (at most two) 2. secret fills out the Approved header to automatically approve the message in a read-only or moderated mailing list. 3. send_from_author uses the commit author email address in the From address of the email. I ran a test which resent the last commit to the mailing list so I am not sure what the problem is with it missing some commits. On a related note you can also setup webhooks on the page as well. Here is a quote about this from the page: Webhooks allow external services to be notified when certain events happen within your repository. When the specified events happen, we'll send a POST request to each of the URLs you provide. Learn more in our Webhooks Guide. We will also send events from this repository to your organization webhooks. This might be the way to setup a file submit to the downloads plugin since there is a release event we can enable. Tom -----Original Message----- From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Dirk Haun Sent: Sunday, January 17, 2016 10:37 AM To: Geeklog Development Subject: Re: [geeklog-devel] GitHub and CVS Mailing List Tom wrote: > I notice that someone had got GitHub to post commits to the Geeklog > CVS mailing list, at least the last batch on Tuesday. I don't know who sent them there, but I noticed a couple of GitHub notifications in the moderation queue for geeklog-cvs and whitelisted the address they were coming from (noreply at github.com) > Today's commits didn't get added. Do we know why? What was the fix? The configuration of the mailing list hasn't changed and there's nothing in the moderation queue. Doesn't look like the problem is on this end. Dirk -- https://www.themobilepresenter.com/ _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net https://pairlist8.pair.net/mailman/listinfo/geeklog-devel From websitemaster at cogeco.net Mon Jan 18 15:46:49 2016 From: websitemaster at cogeco.net (Tom) Date: Mon, 18 Jan 2016 15:46:49 -0500 Subject: [geeklog-devel] Geeklog.net Downloads Plugin Message-ID: <01e501d15231$5a630910$0f291b30$@cogeco.net> Yeaa... after about 3 plus hours of work I finally got the Downloads plugin to import the Filemgmt Plugin data on Geeklog.net There was a number of errors along the way with most of them being issues the result of old bugs in the filemgmt plugin causing problems when information wasn't saved properly. Here are the stats: Number of Downloads Plugin category data: 11 Number of Downloads Plugin file information data: 702 Number of Downloads Plugin vote data: 251 Number of Downloads Plugin history data: 165172 Number of Downloads Plugin submission data: 0 Conversion process was completed successfully! I currently have disabled the downloads plugin as I still need to update the download block as I have run out of time (Dirk is that a custom function?) Also Dirk I am wondering if we need to do some redirects via htaccess (which I know little about). Could you tackle this? Thanks Tom Root https://www.geeklog.net/filemgmt/index.php to https://www.geeklog.net/downloads/index.php Categories https://www.geeklog.net/filemgmt/viewcat.php?cid=8 to https://www.geeklog.net/downloads/index.php?cid=8 File Description https://www.geeklog.net/filemgmt/index.php?id=1157 to https://www.geeklog.net/downloads/index.php/1157 Download link https://www.geeklog.net/filemgmt/visit.php?lid=1157 to https://www.geeklog.net/downloads/visit.php/1157 From websitemaster at cogeco.net Mon Jan 18 16:32:31 2016 From: websitemaster at cogeco.net (Tom) Date: Mon, 18 Jan 2016 16:32:31 -0500 Subject: [geeklog-devel] GitHub Notifications Message-ID: <01e601d15237$bcd3efa0$367bcee0$@cogeco.net> FYI I have setup all repositories under the Geeklog Organization to email geeklog-cvs at lists.geeklog.net on commits. Tom From cordiste at free.fr Mon Jan 18 17:08:22 2016 From: cordiste at free.fr (cordiste) Date: Mon, 18 Jan 2016 23:08:22 +0100 Subject: [geeklog-devel] Geeklog.net Downloads Plugin In-Reply-To: <01e501d15231$5a630910$0f291b30$@cogeco.net> References: <01e501d15231$5a630910$0f291b30$@cogeco.net> Message-ID: Weel done :) For the redirection you can use something like Redirect permanent /filemgmt https://www.geeklog.net/downloads Ben 2016-01-18 21:46 GMT+01:00 Tom : > Yeaa... after about 3 plus hours of work I finally got the Downloads plugin > to import the Filemgmt Plugin data on Geeklog.net > > There was a number of errors along the way with most of them being issues > the result of old bugs in the filemgmt plugin causing problems when > information wasn't saved properly. Here are the stats: > > Number of Downloads Plugin category data: 11 > > Number of Downloads Plugin file information data: 702 > > Number of Downloads Plugin vote data: 251 > > Number of Downloads Plugin history data: 165172 > > Number of Downloads Plugin submission data: 0 > > Conversion process was completed successfully! > > I currently have disabled the downloads plugin as I still need to update the > download block as I have run out of time (Dirk is that a custom function?) > > Also Dirk I am wondering if we need to do some redirects via htaccess (which > I know little about). Could you tackle this? > > Thanks > > Tom > > > Root > https://www.geeklog.net/filemgmt/index.php > to > https://www.geeklog.net/downloads/index.php > > Categories > https://www.geeklog.net/filemgmt/viewcat.php?cid=8 > to > https://www.geeklog.net/downloads/index.php?cid=8 > > File Description > https://www.geeklog.net/filemgmt/index.php?id=1157 > to > https://www.geeklog.net/downloads/index.php/1157 > > Download link > https://www.geeklog.net/filemgmt/visit.php?lid=1157 > to > https://www.geeklog.net/downloads/visit.php/1157 > > > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > https://pairlist8.pair.net/mailman/listinfo/geeklog-devel > From websitemaster at cogeco.net Tue Jan 19 10:41:08 2016 From: websitemaster at cogeco.net (Tom) Date: Tue, 19 Jan 2016 10:41:08 -0500 Subject: [geeklog-devel] [SUSPECTED SPAM] Geeklog Roadmap Message-ID: <022001d152cf$d0bb78b0$72326a10$@cogeco.net> The old Geeklog Roadmap from Mantis is still linked on the Geeklog.net homepage: http://project.geeklog.net/tracking/roadmap_page.php It would be nice if GitHub had something similar with issues that was automated and used milestones and labels to build the roadmap but as far as I can tell they do not. Should we create a wiki page for our roadmap which we will have to manually keep updated or does someone have a better solution? Tom From websitemaster at cogeco.net Tue Jan 19 10:36:54 2016 From: websitemaster at cogeco.net (Tom) Date: Tue, 19 Jan 2016 10:36:54 -0500 Subject: [geeklog-devel] Geeklog.net Downloads Plugin In-Reply-To: References: <01e501d15231$5a630910$0f291b30$@cogeco.net> Message-ID: <021f01d152cf$39a9eb00$acfdc100$@cogeco.net> Okay, I have enabled the downloads plugin and changed the links. Let me know if I missed any. I notice that the old file autotag from the filemanagement plugin isn't used by the downloads plugin so I also installed the autotags plugin and created a file autotag which uses the downloads links. I notice that the old file management links produce an error when access (even when disabled). I have added the below htaccess rules after a quick search online (I am an IIS user so I don't know too much about htaccess) # From old Filemanagement Plugin to Downloads Plugin RewriteRule ^filemgmt/viewcat.php$ /downloads/index.php$1 [R=301,NC,L] RewriteRule ^filemgmt/(.*)$ /downloads/$1 [R=301,NC,L] This seems to take care of the file management links. If any htaccess experts know of a better way let me know. Thanks Tom -----Original Message----- From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of cordiste Sent: Monday, January 18, 2016 5:08 PM To: Geeklog Development Subject: Re: [geeklog-devel] Geeklog.net Downloads Plugin Weel done :) For the redirection you can use something like Redirect permanent /filemgmt https://www.geeklog.net/downloads Ben 2016-01-18 21:46 GMT+01:00 Tom : > Yeaa... after about 3 plus hours of work I finally got the Downloads > plugin to import the Filemgmt Plugin data on Geeklog.net > > There was a number of errors along the way with most of them being > issues the result of old bugs in the filemgmt plugin causing problems > when information wasn't saved properly. Here are the stats: > > Number of Downloads Plugin category data: 11 > > Number of Downloads Plugin file information data: 702 > > Number of Downloads Plugin vote data: 251 > > Number of Downloads Plugin history data: 165172 > > Number of Downloads Plugin submission data: 0 > > Conversion process was completed successfully! > > I currently have disabled the downloads plugin as I still need to > update the download block as I have run out of time (Dirk is that a > custom function?) > > Also Dirk I am wondering if we need to do some redirects via htaccess > (which I know little about). Could you tackle this? > > Thanks > > Tom > > > Root > https://www.geeklog.net/filemgmt/index.php > to > https://www.geeklog.net/downloads/index.php > > Categories > https://www.geeklog.net/filemgmt/viewcat.php?cid=8 > to > https://www.geeklog.net/downloads/index.php?cid=8 > > File Description > https://www.geeklog.net/filemgmt/index.php?id=1157 > to > https://www.geeklog.net/downloads/index.php/1157 > > Download link > https://www.geeklog.net/filemgmt/visit.php?lid=1157 > to > https://www.geeklog.net/downloads/visit.php/1157 > > > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > https://pairlist8.pair.net/mailman/listinfo/geeklog-devel > _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net https://pairlist8.pair.net/mailman/listinfo/geeklog-devel From cordiste at free.fr Wed Jan 20 06:16:35 2016 From: cordiste at free.fr (cordiste) Date: Wed, 20 Jan 2016 12:16:35 +0100 Subject: [geeklog-devel] Contributing to a Github repository Message-ID: Now that we are on Github, we must decide what is the best way for people to contribute to code. It seems to be a good practice to add a CONTRIBUTING label in the README.md file, so I propose the following steps based on the Github documentation: 1. Fork the repository and clone it locally. 2. Create a branch: your branch name should be descriptive, so that others can see what is being worked on. 3.Add commits to your branch: add, edit, or delete one or more files and make tests 4.Open a Pull Request: by using GitHub's @mention system in your Pull Request message, you can ask for feedback from specific people or teams 5.Before merging we discuss and review your code. The person or team reviewing your changes may have questions or comments. Thank you to modify and / or supplement this. Ben From websitemaster at cogeco.net Wed Jan 20 07:07:01 2016 From: websitemaster at cogeco.net (Tom) Date: Wed, 20 Jan 2016 07:07:01 -0500 Subject: [geeklog-devel] Contributing to a Github repository In-Reply-To: References: Message-ID: <024a01d1537b$12086d40$361947c0$@cogeco.net> That is a good idea especially since we can't do patches anymore. (at least like how we did before). I was also wanted to add a good practices page or something on our wiki/readme explaining the best way to contribute, add issues, and committing code. Here are a few help pages I have looked at so far. General Help https://help.github.com/ Glossary https://help.github.com/articles/github-glossary/ Contributing (Pull Requests) https://guides.github.com/activities/contributing-to-open-source/ https://guides.github.com/activities/forking/ Commits https://help.github.com/categories/commits/ Guides https://guides.github.com/ https://help.github.com/categories/commits/ Issue Guide https://guides.github.com/features/issues/ Markdown Guide https://guides.github.com/features/mastering-markdown/ https://help.github.com/categories/writing-on-github/ -----Original Message----- From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of cordiste Sent: Wednesday, January 20, 2016 6:17 AM To: Geeklog Subject: [geeklog-devel] Contributing to a Github repository Now that we are on Github, we must decide what is the best way for people to contribute to code. It seems to be a good practice to add a CONTRIBUTING label in the README.md file, so I propose the following steps based on the Github documentation: 1. Fork the repository and clone it locally. 2. Create a branch: your branch name should be descriptive, so that others can see what is being worked on. 3.Add commits to your branch: add, edit, or delete one or more files and make tests 4.Open a Pull Request: by using GitHub's @mention system in your Pull Request message, you can ask for feedback from specific people or teams 5.Before merging we discuss and review your code. The person or team reviewing your changes may have questions or comments. Thank you to modify and / or supplement this. Ben _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net https://pairlist8.pair.net/mailman/listinfo/geeklog-devel From cordiste at free.fr Wed Jan 20 07:53:31 2016 From: cordiste at free.fr (cordiste) Date: Wed, 20 Jan 2016 13:53:31 +0100 Subject: [geeklog-devel] Contributing to a Github repository In-Reply-To: <024a01d1537b$12086d40$361947c0$@cogeco.net> References: <024a01d1537b$12086d40$361947c0$@cogeco.net> Message-ID: Tom, As a Geeklog community member do I need to open an issue for a bug or enhancement in the Github repository or can I just commit my changes? And if I can commit directly, do I make it in the master branch or I need to create a new branch? For exemple: - Gus plugin I maked a pull request https://github.com/Geeklog-Plugins/gus/pull/2 - Forum plugin I added some issues https://github.com/Geeklog-Plugins/forum/issues/created_by/hostellerie We really need to clarify how everybody contribute :) Ben 2016-01-20 13:07 GMT+01:00 Tom : > That is a good idea especially since we can't do patches anymore. (at least > like how we did before). > > I was also wanted to add a good practices page or something on our > wiki/readme explaining the best way to contribute, add issues, and > committing code. Here are a few help pages I have looked at so far. > > General Help > https://help.github.com/ > > Glossary > https://help.github.com/articles/github-glossary/ > > > Contributing (Pull Requests) > https://guides.github.com/activities/contributing-to-open-source/ > https://guides.github.com/activities/forking/ > > Commits > https://help.github.com/categories/commits/ > > Guides > https://guides.github.com/ > > https://help.github.com/categories/commits/ > > Issue Guide > https://guides.github.com/features/issues/ > > Markdown Guide > https://guides.github.com/features/mastering-markdown/ > https://help.github.com/categories/writing-on-github/ > > > > -----Original Message----- > From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] On > Behalf Of cordiste > Sent: Wednesday, January 20, 2016 6:17 AM > To: Geeklog > Subject: [geeklog-devel] Contributing to a Github repository > > Now that we are on Github, we must decide what is the best way for people to > contribute to code. > > It seems to be a good practice to add a CONTRIBUTING label in the README.md > file, so I propose the following steps based on the Github > documentation: > > 1. Fork the repository and clone it locally. > 2. Create a branch: your branch name should be descriptive, so that others > can see what is being worked on. > 3.Add commits to your branch: add, edit, or delete one or more files and > make tests 4.Open a Pull Request: by using GitHub's @mention system in your > Pull Request message, you can ask for feedback from specific people or teams > 5.Before merging we discuss and review your code. The person or team > reviewing your changes may have questions or comments. > > Thank you to modify and / or supplement this. > > Ben > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > https://pairlist8.pair.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > https://pairlist8.pair.net/mailman/listinfo/geeklog-devel > From komma at ivywe.co.jp Wed Jan 20 08:57:33 2016 From: komma at ivywe.co.jp (=?UTF-8?B?5LuK6aeS5ZOy5a2Q?=) Date: Wed, 20 Jan 2016 22:57:33 +0900 Subject: [geeklog-devel] Contributing to a Github repository In-Reply-To: References: <024a01d1537b$12086d40$361947c0$@cogeco.net> Message-ID: Hi all, How about using slack. We can use GitHub app. https://get.slack.help/hc/en-us/articles/201824286-Setting-up-the-GitHub-app Please create an account in slack. and Create a Team https://geeklog.slack.com (not yet) https://geeklogjapan.slack.com (started.) -- Ivy From websitemaster at cogeco.net Wed Jan 20 10:23:07 2016 From: websitemaster at cogeco.net (Tom) Date: Wed, 20 Jan 2016 10:23:07 -0500 Subject: [geeklog-devel] Contributing to a Github repository In-Reply-To: References: <024a01d1537b$12086d40$361947c0$@cogeco.net> Message-ID: <025901d15396$77503500$65f09f00$@cogeco.net> Yes we do. Everyone I am pretty new to GitHub and I don't know all the right answers, so if I say anything that doesn't makes sense (or you know of a better way) let me know. For the Geeklog Plugins Community we have 4 organization owners (myself, mystralkk, dengen, and ben). That is enough for now. We all have access to all the repositories. Any other people who wish to contribute to any current repository should contact one of the owners of the particular repository explain what they want to do and they can discuss how to do it (ie a fork, create a team, or write access to repository, etc...). You never know what the owner of the repository has planned for the plugin so it is always best to discuss changes big or small with them and what your role maybe. Anyone who wants to add a new repository to Geeklog Plugins should contact one of the organizations owners and we can setup the new repository and give you full access to it. For us owners Ben since we have access to all repositories I still think if anyone of us (owners) want to make changes to someone else's plugin you should contact them first (especially if it is a big change) and discuss how to best accomplish the goal. I think any pull request (or fork) should have an issue attached to it to show if it is a bug fix or new feature. Us owners of repositories should also get better at adding what we are working on currently for a plugin. Either through some sort of Roadmap (using the GitHub wiki feature maybe) and added the feature we are working on in the repository issue tracker. This way people will have a better idea of what may be happening with the plugin. This also means added the required milestone version numbers and any labels. Regarding your pull request for the Gus plugin Ben, I missed seeing that and I approved the change. Thanks for finding the forum issues Ben. I haven't set up the new version numbers (in the code) for any of the plugins I am "in charge of" but you are more than welcome to commit any fixes you work on directly to master if you wish. Just make sure it has been tested well and it has an issue attached to it with a good description and appropriate labels. I had looked before where we can post this type of information about how to best contribute to the Geeklog Plugins Organization on GitHub (where people can find it) but the description for an organization can only contain a couple hundred characters. Maybe I need to create a page on Geeklog.net (or the Geeklog Wiki) about it and include the link in the description. Thoughts? Tom -----Original Message----- From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of cordiste Sent: Wednesday, January 20, 2016 7:54 AM To: Geeklog Development Subject: Re: [geeklog-devel] Contributing to a Github repository Tom, As a Geeklog community member do I need to open an issue for a bug or enhancement in the Github repository or can I just commit my changes? And if I can commit directly, do I make it in the master branch or I need to create a new branch? For exemple: - Gus plugin I maked a pull request https://github.com/Geeklog-Plugins/gus/pull/2 - Forum plugin I added some issues https://github.com/Geeklog-Plugins/forum/issues/created_by/hostellerie We really need to clarify how everybody contribute :) Ben 2016-01-20 13:07 GMT+01:00 Tom : > That is a good idea especially since we can't do patches anymore. (at > least like how we did before). > > I was also wanted to add a good practices page or something on our > wiki/readme explaining the best way to contribute, add issues, and > committing code. Here are a few help pages I have looked at so far. > > General Help > https://help.github.com/ > > Glossary > https://help.github.com/articles/github-glossary/ > > > Contributing (Pull Requests) > https://guides.github.com/activities/contributing-to-open-source/ > https://guides.github.com/activities/forking/ > > Commits > https://help.github.com/categories/commits/ > > Guides > https://guides.github.com/ > > https://help.github.com/categories/commits/ > > Issue Guide > https://guides.github.com/features/issues/ > > Markdown Guide > https://guides.github.com/features/mastering-markdown/ > https://help.github.com/categories/writing-on-github/ > > > > -----Original Message----- > From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] > On Behalf Of cordiste > Sent: Wednesday, January 20, 2016 6:17 AM > To: Geeklog > Subject: [geeklog-devel] Contributing to a Github repository > > Now that we are on Github, we must decide what is the best way for > people to contribute to code. > > It seems to be a good practice to add a CONTRIBUTING label in the > README.md file, so I propose the following steps based on the Github > documentation: > > 1. Fork the repository and clone it locally. > 2. Create a branch: your branch name should be descriptive, so that > others can see what is being worked on. > 3.Add commits to your branch: add, edit, or delete one or more files > and make tests 4.Open a Pull Request: by using GitHub's @mention > system in your Pull Request message, you can ask for feedback from > specific people or teams 5.Before merging we discuss and review your > code. The person or team reviewing your changes may have questions or comments. > > Thank you to modify and / or supplement this. > > Ben > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > https://pairlist8.pair.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > https://pairlist8.pair.net/mailman/listinfo/geeklog-devel > _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net https://pairlist8.pair.net/mailman/listinfo/geeklog-devel From cordiste at free.fr Wed Jan 20 12:18:34 2016 From: cordiste at free.fr (cordiste) Date: Wed, 20 Jan 2016 18:18:34 +0100 Subject: [geeklog-devel] Contributing to a Github repository In-Reply-To: <025901d15396$77503500$65f09f00$@cogeco.net> References: <024a01d1537b$12086d40$361947c0$@cogeco.net> <025901d15396$77503500$65f09f00$@cogeco.net> Message-ID: @Tom For Owners Open an issue for every bug or feature request and close it with via commit message make sense https://help.github.com/articles/closing-issues-via-commit-messages/ For others: For any bug or feature request: 1. Create a New issue https://help.github.com/articles/creating-an-issue/ If you can solve the bug 2. Edit the file and propose file change https://help.github.com/articles/editing-files-in-another-user-s-repository/ For contribution and new features to a plugin: 1. Fork it 2.Create your feature branch (git checkout -b my-new-feature) 3. Commit your changes (git commit -am 'Add some feature') 4. Push to the branch (git push origin my-new-feature) 5. Create new pull request @ Ivy Can you try the slack tool and tell us if we really need it? To much tools can be difficult, and using the geeklog-devel mailing list is cool :) Ben 2016-01-20 16:23 GMT+01:00 Tom : > Yes we do. > > Everyone I am pretty new to GitHub and I don't know all the right answers, > so if I say anything that doesn't makes sense (or you know of a better way) > let me know. > > For the Geeklog Plugins Community we have 4 organization owners (myself, > mystralkk, dengen, and ben). That is enough for now. We all have access to > all the repositories. Any other people who wish to contribute to any current > repository should contact one of the owners of the particular repository > explain what they want to do and they can discuss how to do it (ie a fork, > create a team, or write access to repository, etc...). You never know what > the owner of the repository has planned for the plugin so it is always best > to discuss changes big or small with them and what your role maybe. > > Anyone who wants to add a new repository to Geeklog Plugins should contact > one of the organizations owners and we can setup the new repository and give > you full access to it. > > For us owners Ben since we have access to all repositories I still think if > anyone of us (owners) want to make changes to someone else's plugin you > should contact them first (especially if it is a big change) and discuss how > to best accomplish the goal. > > I think any pull request (or fork) should have an issue attached to it to > show if it is a bug fix or new feature. Us owners of repositories should > also get better at adding what we are working on currently for a plugin. > Either through some sort of Roadmap (using the GitHub wiki feature maybe) > and added the feature we are working on in the repository issue tracker. > This way people will have a better idea of what may be happening with the > plugin. This also means added the required milestone version numbers and any > labels. > > Regarding your pull request for the Gus plugin Ben, I missed seeing that and > I approved the change. > > Thanks for finding the forum issues Ben. I haven't set up the new version > numbers (in the code) for any of the plugins I am "in charge of" but you are > more than welcome to commit any fixes you work on directly to master if you > wish. Just make sure it has been tested well and it has an issue attached to > it with a good description and appropriate labels. > > I had looked before where we can post this type of information about how to > best contribute to the Geeklog Plugins Organization on GitHub (where people > can find it) but the description for an organization can only contain a > couple hundred characters. Maybe I need to create a page on Geeklog.net (or > the Geeklog Wiki) about it and include the link in the description. > > Thoughts? > > Tom > > > -----Original Message----- > From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] On > Behalf Of cordiste > Sent: Wednesday, January 20, 2016 7:54 AM > To: Geeklog Development > Subject: Re: [geeklog-devel] Contributing to a Github repository > > Tom, > > As a Geeklog community member do I need to open an issue for a bug or > enhancement in the Github repository or can I just commit my changes? > And if I can commit directly, do I make it in the master branch or I need to > create a new branch? > > For exemple: > > - Gus plugin I maked a pull request > https://github.com/Geeklog-Plugins/gus/pull/2 > > - Forum plugin I added some issues > https://github.com/Geeklog-Plugins/forum/issues/created_by/hostellerie > > We really need to clarify how everybody contribute :) > > Ben > > 2016-01-20 13:07 GMT+01:00 Tom : >> That is a good idea especially since we can't do patches anymore. (at >> least like how we did before). >> >> I was also wanted to add a good practices page or something on our >> wiki/readme explaining the best way to contribute, add issues, and >> committing code. Here are a few help pages I have looked at so far. >> >> General Help >> https://help.github.com/ >> >> Glossary >> https://help.github.com/articles/github-glossary/ >> >> >> Contributing (Pull Requests) >> https://guides.github.com/activities/contributing-to-open-source/ >> https://guides.github.com/activities/forking/ >> >> Commits >> https://help.github.com/categories/commits/ >> >> Guides >> https://guides.github.com/ >> >> https://help.github.com/categories/commits/ >> >> Issue Guide >> https://guides.github.com/features/issues/ >> >> Markdown Guide >> https://guides.github.com/features/mastering-markdown/ >> https://help.github.com/categories/writing-on-github/ >> >> >> >> -----Original Message----- >> From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] >> On Behalf Of cordiste >> Sent: Wednesday, January 20, 2016 6:17 AM >> To: Geeklog >> Subject: [geeklog-devel] Contributing to a Github repository >> >> Now that we are on Github, we must decide what is the best way for >> people to contribute to code. >> >> It seems to be a good practice to add a CONTRIBUTING label in the >> README.md file, so I propose the following steps based on the Github >> documentation: >> >> 1. Fork the repository and clone it locally. >> 2. Create a branch: your branch name should be descriptive, so that >> others can see what is being worked on. >> 3.Add commits to your branch: add, edit, or delete one or more files >> and make tests 4.Open a Pull Request: by using GitHub's @mention >> system in your Pull Request message, you can ask for feedback from >> specific people or teams 5.Before merging we discuss and review your >> code. The person or team reviewing your changes may have questions or > comments. >> >> Thank you to modify and / or supplement this. >> >> Ben >> _______________________________________________ >> geeklog-devel mailing list >> geeklog-devel at lists.geeklog.net >> https://pairlist8.pair.net/mailman/listinfo/geeklog-devel >> >> _______________________________________________ >> geeklog-devel mailing list >> geeklog-devel at lists.geeklog.net >> https://pairlist8.pair.net/mailman/listinfo/geeklog-devel >> > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > https://pairlist8.pair.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > https://pairlist8.pair.net/mailman/listinfo/geeklog-devel > From websitemaster at cogeco.net Fri Jan 22 10:18:53 2016 From: websitemaster at cogeco.net (Tom) Date: Fri, 22 Jan 2016 10:18:53 -0500 Subject: [geeklog-devel] Drop Support for COM_siteHeader and COM_siteFooter Message-ID: <002d01d15528$448d78b0$cda86a10$@cogeco.net> I think it is time to remove the depreciated functions COM_siteHeader COM_siteFooter and make the COM_createHTMLDocument the required function for creating a Geeklog Page. I have added a feature request for it here https://github.com/Geeklog-Core/geeklog/issues/657 and set it for the v2.2.0 milestone. Depending on time lines we can move it back if needed. Obviously if we do this then it will make any plugins that use the above functions unable to work with Geeklog 2.2.0 or higher. Some of the plugins which will need updating (which I have been involved in) include: GUS Ban Autotags Nettools Searchrank The change isn't difficult to do it is just a little time consuming as you have to run a search through all the plugin code and replace the two calls with the one and then test things just to make sure it all works. I see this happening in a year or so but I wanted to give plugin developers notice now. I would also post about this on Geeklog.net if everyone agrees with the decision. If that is not enough time then maybe we can say Geeklog v2.2.0 will be the last version to support COM_siteHeader and COM_siteFooter but I rather make Geeklog 2.1.X the last version to support the functions. Thoughts? Tom From cordiste at free.fr Fri Jan 22 12:25:07 2016 From: cordiste at free.fr (cordiste) Date: Fri, 22 Jan 2016 18:25:07 +0100 Subject: [geeklog-devel] Drop Support for COM_siteHeader and COM_siteFooter In-Reply-To: <002d01d15528$448d78b0$cda86a10$@cogeco.net> References: <002d01d15528$448d78b0$cda86a10$@cogeco.net> Message-ID: Plugins developers can prepare the switch with something like if (function_exists('COM_createHTMLDocument')) { COM_output( COM_createHTMLDocument($display) ); } else { COM_output( COM_siteHeader('plugin_name') . $display . COM_siteFooter() ); } 2016-01-22 16:18 GMT+01:00 Tom : > I think it is time to remove the depreciated functions > > COM_siteHeader > COM_siteFooter > > and make the COM_createHTMLDocument the required function for creating a > Geeklog Page. > > I have added a feature request for it here > > https://github.com/Geeklog-Core/geeklog/issues/657 > > and set it for the v2.2.0 milestone. Depending on time lines we can move it > back if needed. > > Obviously if we do this then it will make any plugins that use the above > functions unable to work with Geeklog 2.2.0 or higher. > > Some of the plugins which will need updating (which I have been involved in) > include: > > GUS > Ban > Autotags > Nettools > Searchrank > > The change isn't difficult to do it is just a little time consuming as you > have to run a search through all the plugin code and replace the two calls > with the one and then test things just to make sure it all works. > > I see this happening in a year or so but I wanted to give plugin developers > notice now. I would also post about this on Geeklog.net if everyone agrees > with the decision. > > If that is not enough time then maybe we can say Geeklog v2.2.0 will be the > last version to support COM_siteHeader and COM_siteFooter but I rather make > Geeklog 2.1.X the last version to support the functions. > > Thoughts? > > Tom > > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > https://pairlist8.pair.net/mailman/listinfo/geeklog-devel > From mystralkk at gmail.com Fri Jan 22 17:28:42 2016 From: mystralkk at gmail.com (Kenji ITO) Date: Sat, 23 Jan 2016 07:28:42 +0900 Subject: [geeklog-devel] Drop Support for COM_siteHeader and COM_siteFooter In-Reply-To: <002d01d15528$448d78b0$cda86a10$@cogeco.net> References: <002d01d15528$448d78b0$cda86a10$@cogeco.net> Message-ID: 2016-01-23 0:18 GMT+09:00 Tom : > I think it is time to remove the depreciated functions > > COM_siteHeader > COM_siteFooter > > and make the COM_createHTMLDocument the required function for creating a > Geeklog Page. > > I have added a feature request for it here > > https://github.com/Geeklog-Core/geeklog/issues/657 > > and set it for the v2.2.0 milestone. Depending on time lines we can move it > back if needed. > > Obviously if we do this then it will make any plugins that use the above > functions unable to work with Geeklog 2.2.0 or higher. > > Some of the plugins which will need updating (which I have been involved > in) > include: > > GUS > Ban > Autotags > Nettools > Searchrank > > The change isn't difficult to do it is just a little time consuming as you > have to run a search through all the plugin code and replace the two calls > with the one and then test things just to make sure it all works. > > I see this happening in a year or so but I wanted to give plugin developers > notice now. I would also post about this on Geeklog.net if everyone agrees > with the decision. > > If that is not enough time then maybe we can say Geeklog v2.2.0 will be the > last version to support COM_siteHeader and COM_siteFooter but I rather make > Geeklog 2.1.X the last version to support the functions. > > Thoughts? > > Tom > I agree. In addition to COM_siteHeader and COM_siteFooter functions, I would suggest dropping support for MSSQL, since few people seem to need it. With Geeklog-2.2.x, why don't we bump up the PHP version required to 5.3.2? In so doing, we can use namespace and Composer ( https://getcomposer.org/ ). -------------- next part -------------- An HTML attachment was scrubbed... URL: From websitemaster at cogeco.net Fri Jan 22 20:04:41 2016 From: websitemaster at cogeco.net (Tom) Date: Fri, 22 Jan 2016 20:04:41 -0500 Subject: [geeklog-devel] Drop Support for COM_siteHeader and COM_siteFooter In-Reply-To: References: <002d01d15528$448d78b0$cda86a10$@cogeco.net> Message-ID: <005001d1557a$0a9b0e40$1fd12ac0$@cogeco.net> I am fine with dropping MSSQL as well. I am also fine with upping the php version number so we can define namespaces. I haven?t used composer before so if anyone has any input on it let us know. Tom From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Kenji ITO Sent: Friday, January 22, 2016 5:29 PM To: Geeklog Development Subject: Re: [geeklog-devel] Drop Support for COM_siteHeader and COM_siteFooter 2016-01-23 0:18 GMT+09:00 Tom >: I think it is time to remove the depreciated functions COM_siteHeader COM_siteFooter and make the COM_createHTMLDocument the required function for creating a Geeklog Page. I have added a feature request for it here https://github.com/Geeklog-Core/geeklog/issues/657 and set it for the v2.2.0 milestone. Depending on time lines we can move it back if needed. Obviously if we do this then it will make any plugins that use the above functions unable to work with Geeklog 2.2.0 or higher. Some of the plugins which will need updating (which I have been involved in) include: GUS Ban Autotags Nettools Searchrank The change isn't difficult to do it is just a little time consuming as you have to run a search through all the plugin code and replace the two calls with the one and then test things just to make sure it all works. I see this happening in a year or so but I wanted to give plugin developers notice now. I would also post about this on Geeklog.net if everyone agrees with the decision. If that is not enough time then maybe we can say Geeklog v2.2.0 will be the last version to support COM_siteHeader and COM_siteFooter but I rather make Geeklog 2.1.X the last version to support the functions. Thoughts? Tom I agree. In addition to COM_siteHeader and COM_siteFooter functions, I would suggest dropping support for MSSQL, since few people seem to need it. With Geeklog-2.2.x, why don't we bump up the PHP version required to 5.3.2? In so doing, we can use namespace and Composer ( https://getcomposer.org/ ). -------------- next part -------------- An HTML attachment was scrubbed... URL: From mystralkk at gmail.com Fri Jan 22 23:41:19 2016 From: mystralkk at gmail.com (Kenji ITO) Date: Sat, 23 Jan 2016 13:41:19 +0900 Subject: [geeklog-devel] URL Routing feature Message-ID: I implemented a simple URL routing feature (issue #211) and added "feature/url-routing" branch to the Geeklog-Core repository. Have a look at it and enjoy! -- mystral-kk http://mystral-kk.net/ mystralkk at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From websitemaster at cogeco.net Sat Jan 23 11:34:48 2016 From: websitemaster at cogeco.net (Tom) Date: Sat, 23 Jan 2016 11:34:48 -0500 Subject: [geeklog-devel] URL Routing feature In-Reply-To: References: Message-ID: <00a701d155fb$fa1557b0$ee400710$@cogeco.net> Will do. Thanks for also adding the upgrade code for 2.1.2 Tom From: geeklog-devel [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Kenji ITO Sent: Friday, January 22, 2016 11:41 PM To: Geeklog Development Subject: [geeklog-devel] URL Routing feature I implemented a simple URL routing feature (issue #211) and added "feature/url-routing" branch to the Geeklog-Core repository. Have a look at it and enjoy! -- mystral-kk http://mystral-kk.net/ mystralkk at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: