Nothing amazing, just an update from 3.5.0 to 3.7.0, addressing a few Rails security bugs. Come bother us on #sourcemage on irc.freenode.net if you notice things not behaving well. Poke BeepDog specifically.
MySQL and this webapp weren't getting along terribly well. Perhaps it's because we were using the old mysql gem rather than the mysql2 gem.
Everything is now using mysql2 and we're running against a newer MySQL so hopefully things will be better now. Watching things happen, and they seem to mostly be in the ruby process space, not in the mysqld process space, so I suppose that's a good thing. I'd rather have ruby doing the work, than mysql clogging itself up.
MySQL didn't like it that we had a leap second a little while ago.
I remember hearing about a glitch in the linux kernel that caused things to bomb, but this is the first I'd heard about the same problem happening to mysql.
Solution found here: http://stackoverflow.com/a/11293475/423218
date -s "`date`"
Which I guess just forces the date to a point and gets it less freaked out. It's certainly made mysql a bit snappier, thankfully.
Updated Chiliproject (1 comment)
Updating Chiliproject is easy! We're running the latest version now, and I haven't seen any problems.
Let BeepDog know on irc://irc.freenode.net/#sourcemage if there are any problems (Did I do an IRC url correctly?)
So a bit of ruby scripting fu later, and a rake task that I can re-run, and we've eliminated all the spam from the chiliproject site.
It completely destroys locked accounts and anything the locked account posted, files, comments issues, comments.
Then registered accounts that haven't been activated and are older than two weeks also get nuked.
Hooray for no spam.
Spammers are smarter than they used to be (1 comment)
A friendly internet denizen contacted me about epic buttons of spam on one of our news pages.
Sadly, the registration requiring email activation is no longer sufficient, as the spam bots have email accounts. Not surprising.
So the only solution for chiliproject, sadly (as well as most other things, including the wiki we're using) is to set up manual account activation.
Perhaps one day, I can work out a much better, much more integrated authentication framework using LDAP as the backend and tie in all the items into one account, and activate them more smarter.
Until then, sorry :(
Big Fat Warning on Bugzilla (2 comments)
We need to get moved over from bugzilla to using the chiliproject based issue trackers to take advantage of the release planning. And in support of that, since I cannot simply make bugzilla read-only, I have added a Big Fat Warning(tm) to be displayed in bugzilla to remind people not to use it.
This is probably also a good time to review our process and make some improvements where necessary.
Thanks for your patience as we're all busy people, and we work to get this ironed out.
August seems like a good time for the next developer meeting. It will have been about 4 months since our last meeting, and we can check up on the status of things we decided to do that meeting, and plan on doing more new things.
I've created a wiki page here, that anyone in the Developer Group can edit and modify. Feel free to add items to the agenda that you feel need to be discussed by the entire project team.
Chiliproject 2.0.0 (2 comments)
Our wonderful website/bugtracker/wiki contrapulator has gone through an upgrade!
As Chiliproject progresses and develops new features, I shall endeavor to keep it up to date, and that will require some down time. This most recent release was a major point change, and such took a long time to update.
The Chiliproject team is well on their way to bringing their project up to date with the latest Rails and Ruby technologies. This should result in a better, faster experience on the site for all of us.
Some wiki pages migrated! (1 comment)
One of our industrious developers has spent the time to migrate some of our core wiki pages into the Chiliproject wiki for Source Mage General! Thanks to Ryuji for migrating those pages for us!
The converted pages are as follows:
http://wiki.sourcemage.org/SourceMage_Wiki -> http://sourcemage.org/projects/source-mage/wiki/Wiki
http://wiki.sourcemage.org/SourceMage/Developers -> http://sourcemage.org/projects/source-mage/wiki/Developers
http://wiki.sourcemage.org/SourceMage/Glossary -> http://sourcemage.org/projects/source-mage/wiki/GlossaryOfTerms
http://wiki.sourcemage.org/SourceMage/Developer_Organization -> http://sourcemage.org/projects/source-mage/wiki/DeveloperOrganization
http://wiki.sourcemage.org/SourceMage/Hall_of_Fame -> http://sourcemage.org/projects/source-mage/wiki/HallOfFame
http://wiki.sourcemage.org/SourceMage/SocialContract -> http://sourcemage.org/projects/source-mage/wiki/SocialContract
http://wiki.sourcemage.org/SourceMage/History -> http://sourcemage.org/projects/source-mage/wiki/OurHistory
http://wiki.sourcemage.org/SourceMage/Contact_Us -> http://sourcemage.org/projects/source-mage/wiki/ContactUs
http://wiki.sourcemage.org/SourceMage/Voting_Policy -> http://sourcemage.org/projects/source-mage/wiki/VotingPolicy
http://wiki.sourcemage.org/SourceMage/Keysigning -> http://sourcemage.org/projects/source-mage/wiki/KeySigning
http://wiki.sourcemage.org/New_to_Source_Mage_GNU/Linux -> http://sourcemage.org/projects/source-mage/wiki/NewToSourceMage
http://wiki.sourcemage.org/Download_Source_Mage -> http://sourcemage.org/projects/source-mage/wiki/Download
http://wiki.sourcemage.org/NewInstall -> http://sourcemage.org/projects/source-mage/wiki/InstallGuide
http://wiki.sourcemage.org/SourceMage -> http://sourcemage.org/projects/source-mage/wiki/AboutSourceMage
Thanks for all the hard work!
Also available in: Atom