Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - Nao
1891
The Pub / Re: Wedge repo -- installation feedback
« on January 21st, 2014, 06:20 PM »In addition I get this error when I open the root dir:Code: [Select] Warning: copy(/home/public/beta/wedge-master/gz/app/Class-System.php): failed to open stream: Permission denied in /home/public/beta/wedge-master/index.php on line 247
/gz/ and its sub-folders need to be writable (CHMOD 0755).
If /gz/ is writable, I *could* consider creating all of the sub-folders on the fly, either at install time or execution time. That would make less folders to fix, I don't know.
1892
The Pub / Re: Wedge repo -- installation feedback
« on January 21st, 2014, 06:19 PM »
Hmm... I guess it's because of the BIT(1) element.
Open install.sql, and replace all occurrences of bit(1) with tinyint(1) -- that should help.
I don't get why it doesn't work, though. The official MySQL website does say that it was introduced in v5.0.3, which is the minimum version Wedge will accept.
Perhaps an incompatibility in the install.php file, I don't know... Will look into it.
Great movie, BTW.
Open install.sql, and replace all occurrences of bit(1) with tinyint(1) -- that should help.
I don't get why it doesn't work, though. The official MySQL website does say that it was introduced in v5.0.3, which is the minimum version Wedge will accept.
Perhaps an incompatibility in the install.php file, I don't know... Will look into it.
Great movie, BTW.
1893
The Pub / Re: Wedge repo -- installation feedback
« on January 21st, 2014, 04:50 PM »
He just created a topic, but I made the announcement first (this post), and wrote a longer blog post to announce it 'properly'.
If we can't open ourselves to external scrutiny, then it should have remained a private project... ;)
If we can't open ourselves to external scrutiny, then it should have remained a private project... ;)
1894
Features / Re: New revs
« on January 21st, 2014, 04:32 PM »
[master 66876f5] The new language cache wasn't purged by uncache. (Subs-Cache.php)
1 file changed, 2 insertions(+), 1 deletion(-)
Should I keep posting new revs here, when you can now just access the rev log here..?
https://github.com/Wedge/wedge/commits/
1 file changed, 2 insertions(+), 1 deletion(-)
Should I keep posting new revs here, when you can now just access the rev log here..?
https://github.com/Wedge/wedge/commits/
1895
The Pub / Re: Repository name poll! Yayer!!
« on January 21st, 2014, 04:21 PM »
Thanks!
Feel free to Like the "That'll do" blog post, or comment on it, if you're downloading the alpha at some point! (Or just send your good mental waves around if you're a lurking guest, of course!)
Feel free to Like the "That'll do" blog post, or comment on it, if you're downloading the alpha at some point! (Or just send your good mental waves around if you're a lurking guest, of course!)
1896
Features / Re: New revs
« on January 21st, 2014, 04:18 PM »
+4-4
* ! Minor typo in license file. (license.txt, readme.md.txt)
* GitHub isn't smart enough to guess that 'readme.md.txt' is the same as 'README.md', except on my terms.
(Kinda amusing/fitting that Wedge became public on its 2400th commit. Well, technically commits no longer have numbers, but here they still do...)
* ! Minor typo in license file. (license.txt, readme.md.txt)
* GitHub isn't smart enough to guess that 'readme.md.txt' is the same as 'README.md', except on my terms.
(Kinda amusing/fitting that Wedge became public on its 2400th commit. Well, technically commits no longer have numbers, but here they still do...)
1897
The Pub / Wedge repo -- installation feedback
« on January 21st, 2014, 04:13 PM »
I was in the process of writing the blog post about it all. (Yesterday, I spent like an hour writing the README for the repo[1], so it felt comparatively faster.)
Anyway, yeah, the importer will be ready when it's ready, and since it still worked a few weeks ago, I'm guessing it doesn't require a lot of work, and I could even fix it now, but... Really, REALLY, all I want is to finish that pesky movie I was watching.
Anyway, yeah, the importer will be ready when it's ready, and since it still worked a few weeks ago, I'm guessing it doesn't require a lot of work, and I could even fix it now, but... Really, REALLY, all I want is to finish that pesky movie I was watching.
| 1. | Hopefully you don't find its humor too lacking in taste... That's what happens when you're over-stressed :P |
1898
Development blog / That'll do.
« on January 21st, 2014, 04:08 PM »
And here it is. I wanted to postpone it even more... But you don't deserve it. If anything goes wrong, I'll deserve it. In the meantime, please enjoy this; some of you have been waiting over three years for this moment.
https://github.com/Wedge/wedge
Read the README for instructions.
I will attempt to release a public alpha once I get some feedback confirming that everything's working all right.
https://github.com/Wedge/plugins
This is the official plugin repository. Most of these were written by Pete, John and Shitiz. The current license for them is the Wedge license; eventually, though, my goal is to make it clear which plugins are under more permissive licenses. Perhaps I'll even be able to make them all MIT, or something. If you write a plugin and don't want to share it under the MIT license, you can always push it elsewhere.
https://github.com/Wedge/languages
This one isn't a new repo, I introduced it recently on this blog, but what's new is that all of its files are now governed by the MIT license.
Lastly, if you're planning to make the switch to Wedge from an active SMF forum, please remember this:
https://github.com/Wedge/wedge
Read the README for instructions.
I will attempt to release a public alpha once I get some feedback confirming that everything's working all right.
https://github.com/Wedge/plugins
This is the official plugin repository. Most of these were written by Pete, John and Shitiz. The current license for them is the Wedge license; eventually, though, my goal is to make it clear which plugins are under more permissive licenses. Perhaps I'll even be able to make them all MIT, or something. If you write a plugin and don't want to share it under the MIT license, you can always push it elsewhere.
https://github.com/Wedge/languages
This one isn't a new repo, I introduced it recently on this blog, but what's new is that all of its files are now governed by the MIT license.
Lastly, if you're planning to make the switch to Wedge from an active SMF forum, please remember this:
- There is currently no 'proper' importer available. Pandos confirmed to me that the official importer is broken, so I'll look into it ASAP.
- Said official importer will be pushed to the Wedge/tools repo (or its own repo) when available. I'm planning to have it around by next weekend at the latest.
- If Thorsten looks into it before I do (I know he loves this kind of thing), then he may fix the importer before I do. See? A programmer's logic is no more complex than yours.
- It's still an alpha, even three years in. Meaning nothing is set in stone, and if a change I make breaks your forum, you can't complain to me. And if it makes it better, then you can't complain either. That was the whole point, after all.
1899
The Pub / Re: Repository name poll! Yayer!!
« on January 21st, 2014, 03:38 PM »
git.exe push --force --progress "origin" master:master
Counting objects: 31933, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (6687/6687), done.
Writing objects: 100% (31933/31933), 12.01 MiB | 48.00 KiB/s, done.
Total 31933 (delta 25350), reused 31762 (delta 25214)
To ...@github.com/Wedge/wedge/
+ 629e5ad...4c0e855 master -> master (forced update)
Success (402170 ms @ 21/01/14 15:37:40)
Counting objects: 31933, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (6687/6687), done.
Writing objects: 100% (31933/31933), 12.01 MiB | 48.00 KiB/s, done.
Total 31933 (delta 25350), reused 31762 (delta 25214)
To ...@github.com/Wedge/wedge/
+ 629e5ad...4c0e855 master -> master (forced update)
Success (402170 ms @ 21/01/14 15:37:40)
1900
The Pub / Re: Repository name poll! Yayer!!
« on January 21st, 2014, 03:36 PM »
Believe it or not, but... I'm currently uploading the repo.
So, in a few minutes (depending on my connection's speed, but it's a bit slow... and it's a big repo), you'll finally be able to download it. And maybe install it (if it works.) And maybe use it. And maybe enjoy it. ;)
So, in a few minutes (depending on my connection's speed, but it's a bit slow... and it's a big repo), you'll finally be able to download it. And maybe install it (if it works.) And maybe use it. And maybe enjoy it. ;)
1901
The Pub / Re: Repository name poll! Yayer!!
« on January 21st, 2014, 03:22 PM »
I don't know. Maybe they'll jump ship if I remove Aeva Media from sm.org entirely... :P
I'm not planning to do it, though, for these reasons:
- I'm proud of the fact that 3 years after I gave up on it, it's still the best gallery system available for SMF. (Or, as Arantor so elegantly puts it, "the least worst". Go ahead, Pete, make my day and code your own! I'm sure it'll be better than the 2 years of my life I invested on it!)
- It's free advertising for Wedge.
- Wedge only adds a few features (those from the non-free Aeva Media 2.x) to Aeva Media, and as such, switching from SMF to Wedge *just* for the gallery upgrades wouldn't make sense.
I will not, however, update Aeva Media for SMF 2.1 or later, or port it to any other fork. I will let it die its glorious death, while it keeps on living in Wedge. :)
I'm not planning to do it, though, for these reasons:
- I'm proud of the fact that 3 years after I gave up on it, it's still the best gallery system available for SMF. (Or, as Arantor so elegantly puts it, "the least worst". Go ahead, Pete, make my day and code your own! I'm sure it'll be better than the 2 years of my life I invested on it!)
- It's free advertising for Wedge.
- Wedge only adds a few features (those from the non-free Aeva Media 2.x) to Aeva Media, and as such, switching from SMF to Wedge *just* for the gallery upgrades wouldn't make sense.
I will not, however, update Aeva Media for SMF 2.1 or later, or port it to any other fork. I will let it die its glorious death, while it keeps on living in Wedge. :)
1902
Features / Re: Language revs
« on January 21st, 2014, 03:18 PM »
* Changed license for language files to the MIT license. I don't think it'll hurt Wedge much if these files find themselves in the wild; anything in Wedge that's NOT a language file is still under the Wedge license, so don't get it wrong! Also added the DCO to the repo, and changed copyright to add contributors. (DCO, LICENSE, README)
@ The main goal is to allow more freedom to translators, and allow them to 'forget' to sign-off their commits. I would still recommend signing them off, until we get some proper legal advice on this.
:edit: I thought clicking the 'Push' button would feel exhilarating, but in fact it felt more awkward than ever... Well, we'll see if I can live with permissive licenses in the future... :P
@ The main goal is to allow more freedom to translators, and allow them to 'forget' to sign-off their commits. I would still recommend signing them off, until we get some proper legal advice on this.
:edit: I thought clicking the 'Push' button would feel exhilarating, but in fact it felt more awkward than ever... Well, we'll see if I can live with permissive licenses in the future... :P
1903
The Pub / Re: Repository name poll! Yayer!!
« on January 21st, 2014, 02:56 PM »
Okay, so /Wedge is a (close) winner, and I don't want to spend my life on this, so I chose /Wedge. If it turns out I can't live with /Wedge as an account name, I'll just switch back to /wedge, and screw up everyone who's been playing with the Wedge repo, but... Well, there are worse things in life, and I've already made my life complicated enough.
So I did a quick database update to turn all wedge/wedge into Wedge/wedge, which MAY have, ahem, transformed some of your posts as well, in this topic, but I don't think anyone will mind if their messages are case-corrupted, because well, the choice is made... :^^;:
So I did a quick database update to turn all wedge/wedge into Wedge/wedge, which MAY have, ahem, transformed some of your posts as well, in this topic, but I don't think anyone will mind if their messages are case-corrupted, because well, the choice is made... :^^;:
1904
Features / Re: New revs
« on January 21st, 2014, 01:09 PM »
[master 79ff7de]
2 files changed, 11 insertions(+), 11 deletions(-)
* Turned a few of the database's TINYINT(1) fields into BIT(1), which is new in MySQL 5. Please note that existing tables don't need to be updated if you can't bother -- BIT is the same as TINYINT, it just takes less space. Also, I didn't change everything, because there are some tinyints that actually accept more than a boolean value, and I don't want to screw these up, so I have to do all of these manually. If anyone wants to convert more, be my guest. (install.sql)
! Fixed writable folder locations. Thanks Pandos! (install.php)
2 files changed, 11 insertions(+), 11 deletions(-)
* Turned a few of the database's TINYINT(1) fields into BIT(1), which is new in MySQL 5. Please note that existing tables don't need to be updated if you can't bother -- BIT is the same as TINYINT, it just takes less space. Also, I didn't change everything, because there are some tinyints that actually accept more than a boolean value, and I don't want to screw these up, so I have to do all of these manually. If anyone wants to convert more, be my guest. (install.sql)
! Fixed writable folder locations. Thanks Pandos! (install.php)
1905
The Pub / Re: Repository name poll! Yayer!!
« on January 21st, 2014, 12:10 PM »
Well, it also depends on whether I can keep the *motivation* to work on Wedge as long as there's no one using it, AND whether I can keep the *courage* to work on Wedge when it's ultra-successful and the forum is as busy as SMF's.