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 - Arantor
6631
Features: Miscellaneous / Re: Media area (Aeva Media integration)
« on August 23rd, 2011, 05:22 PM »
We're getting pretty off topic at this point, but to sum up.Quote No, it isn't. But it doesn't work like that in practice. Why would I join a project team for a project that I wouldn't have any say over the administration and direction of? I would note that at least one other person won't contribute to SMF, because they don't feel like they can contribute to a project without having some say over its direction.Quote In which case then, let's suppose SimpleDesk were taken on by the NPO.
Can anyone, seriously, see my being made part of the project by a vote? Survey says no, which would imply that the team would be quite happy to solicit any contributions made without giving any authority to dictate its future. This says to me that I wouldn't want to contribute...
but it is not actually a requirement.
Project members are added by team vote, or as part of a new Project's existing team by an NPO vote(not sure of this at the moment), and the new project members are then added as NPO members by a BoD decision after they have actually joined a project.
Can anyone, seriously, see my being made part of the project by a vote? Survey says no, which would imply that the team would be quite happy to solicit any contributions made without giving any authority to dictate its future. This says to me that I wouldn't want to contribute...
6632
Features: Miscellaneous / Re: Media area (Aeva Media integration)
« on August 23rd, 2011, 02:53 PM »
To successfully mash two totally different memes, from generations apart...
As any fule kno, the cake is lie.
OK, here's the deal with SimpleDesk from my personal POV. SimpleDesk 2.0 should be released later on today. 23rd August is an important day for me personally and has been the last couple of years or so, so it seems very apt that it should be released today, after all there's been no bugs to speak of for weeks, that needed fixing in the RC, so I just needed to up at do it, really.
There is some stuff that will be committed to trunk after that, namely a limited search feature (limited because it's slow on the basis that I have neither the time nor energy to really polish it, hence it going into their trunk so that whoever comes later can implement it more fully). It is an index style based on the custom index, but without the issue related to PHP 5.3.7 that will break SMF's custom indexes, plus it has the ability to do prefix matching (or it will when I've finished it)
In light of all the stuff that happened, both publicly and not so publicly where I've been rather pissed off with what's happened, I made it very clear that once SD 2.0 final was released, I'd be cutting my ties, less stuff holding me back as it were, less stuff to - as I said at the time - feel tainted by.
Because it's BSD licensed, I'm able to fork my own work and reuse it in a manner more consistent with a mentality I'm happy with; the only reason I came back to work on it earlier this year is because of an arrangement being made with certain people with whom I owed a favour or two to. I do not like the fact that I ended up spending an awful lot of time on something which, ultimately, I've come to regret doing because of all the stuff that dragged it down, not least the overshadowing feeling that it's going to be absorbed into the SM NPO at some point. Though, fortunately, that isn't going to happen today - which means that I have no risk of being dragged in, however inadvertently, into the NPO.[1]
I should note that SD has a BSD licence for all the freedoms it grants, including the freedom to do just that, so I won't hold it against SMF for doing it per se, only for the fact that they would be benefitting, yet again, from my hard work and leaving me little to show for it.
The future, from my POV, involves me developing WedgeDesk for Wedge, making everything leaner and likely rewriting more than porting. This isn't really a bad thing because it means I can take the opportunity to correct some of the mistakes I made in development.
As any fule kno, the cake is lie.
OK, here's the deal with SimpleDesk from my personal POV. SimpleDesk 2.0 should be released later on today. 23rd August is an important day for me personally and has been the last couple of years or so, so it seems very apt that it should be released today, after all there's been no bugs to speak of for weeks, that needed fixing in the RC, so I just needed to up at do it, really.
There is some stuff that will be committed to trunk after that, namely a limited search feature (limited because it's slow on the basis that I have neither the time nor energy to really polish it, hence it going into their trunk so that whoever comes later can implement it more fully). It is an index style based on the custom index, but without the issue related to PHP 5.3.7 that will break SMF's custom indexes, plus it has the ability to do prefix matching (or it will when I've finished it)
In light of all the stuff that happened, both publicly and not so publicly where I've been rather pissed off with what's happened, I made it very clear that once SD 2.0 final was released, I'd be cutting my ties, less stuff holding me back as it were, less stuff to - as I said at the time - feel tainted by.
Because it's BSD licensed, I'm able to fork my own work and reuse it in a manner more consistent with a mentality I'm happy with; the only reason I came back to work on it earlier this year is because of an arrangement being made with certain people with whom I owed a favour or two to. I do not like the fact that I ended up spending an awful lot of time on something which, ultimately, I've come to regret doing because of all the stuff that dragged it down, not least the overshadowing feeling that it's going to be absorbed into the SM NPO at some point. Though, fortunately, that isn't going to happen today - which means that I have no risk of being dragged in, however inadvertently, into the NPO.[1]
I should note that SD has a BSD licence for all the freedoms it grants, including the freedom to do just that, so I won't hold it against SMF for doing it per se, only for the fact that they would be benefitting, yet again, from my hard work and leaving me little to show for it.
The future, from my POV, involves me developing WedgeDesk for Wedge, making everything leaner and likely rewriting more than porting. This isn't really a bad thing because it means I can take the opportunity to correct some of the mistakes I made in development.
| 1. | Since, correct me if I'm wrong, active team members of a project are automatically made NPO members. I am currently an active SD team member, and if it became part of the NPO, that would make me an NPO team member by definition. |
6633
Off-topic / Re: Aeva Add Sites
« on August 23rd, 2011, 12:32 PM »I just wanted to help inside you for the love of the SMF.
6634
Features: Miscellaneous / Re: Media area (Aeva Media integration)
« on August 23rd, 2011, 11:16 AM »
The statement was clarifying that we aren't planning on putting SimpleDesk in the core. I have already stated I will be porting SimpleDesk to Wedge in the future, and a lot of the work that goes into what I'm doing with the permissions page and also the plugins system is based on supporting SimpleDesk's needs (which are not actually that far different from most other things once you start looking past names of things and into the heart of what is actually needed)
6635
Off-topic / Re: PHP 5.3.7
« on August 23rd, 2011, 09:57 AM »5.3.X (final)
But if they can't even be bothered to upgrade to a security patch of PHP in 6 months after it came out, I'd be asking questions...
6636
Off-topic / Re: PHP 5.3.7
« on August 23rd, 2011, 09:32 AM »
If they're on 5.2, they should be on 5.2.17 - it's been out over 6 months, and hosts don't really have much reason not to upgrade.
6637
Development blog / Re: A nice kick in the CSS
« on August 23rd, 2011, 12:10 AM »Credit for what? Does anyone know of anything he did for the SMF community that wasn't linked in one way or another to the selling of a commercial version of his work...?
I can hardly give the benefit of the doubt to someone who's widely recognized by the SMF community for his tendency to monetize everything he does for them.
So far, most of his changes to the SMF codebase (according to his commit logs) was to rename all entries of SMF into his fork name. I don't know about you, but when I'm seeing something like "SMF wishes to thank everyone who spent countless hours on the project", I'm not going to change SMF into my fork name after I only worked on it for a couple of hours... It shows a lack of respect for SMF itself. I wait a year before I did the same...
Until proven otherwise, to me he's just going to release an SMF with his mods (and the mods that were given to him ) built in, and on top of that he'll be selling a "pro" version of his forum with the "pro" (commercial) versions of the same mods... It's all about getting extra exposure for his $250 'suite'.
Let's just say only time will tell which conception of a SMF fork will make it into the hearts of the SMF community. But I think I already know...
Oh, well, I guess that's it now, I wrote a blurb about the damn fork...
I'm honestly curious to see if he forks SimpleDesk to make ezDesk for his fork. I already told him a year ago that he could, long before I was thoroughly and totally disgusted with his behaviour[1], when he wished we would make it for 1.1.x and I told him up front that he was welcome to port it himself. Funnily enough he never did to my knowledge.
| 1. | Back then I was more 'mildly annoyed' by it. |
6638
I doubt this will affect most of you but anyway.
http://www.theregister.co.uk/2011/08/22/php_security_warning/
Long story short: do not use PHP 5.3.7, it has a fairly nasty vulnerability in the internal crypt library that, well, doesn't crypt things properly.
It does have an impact on both SMF and Wedge, as it happens. Specifically that older forums make use of the crypt function in order to hash passwords, as well as custom indexes, will be compromised by this bug.
I doubt the older forums thing is a huge deal for the vast majority of users, but potentially the custom indexes one is. If your host uses 5.3.7, get them to upgrade to a dev version or kick them to upgrade to 5.3.8 when it is released in the next few days.
http://www.theregister.co.uk/2011/08/22/php_security_warning/
Long story short: do not use PHP 5.3.7, it has a fairly nasty vulnerability in the internal crypt library that, well, doesn't crypt things properly.
It does have an impact on both SMF and Wedge, as it happens. Specifically that older forums make use of the crypt function in order to hash passwords, as well as custom indexes, will be compromised by this bug.
I doubt the older forums thing is a huge deal for the vast majority of users, but potentially the custom indexes one is. If your host uses 5.3.7, get them to upgrade to a dev version or kick them to upgrade to 5.3.8 when it is released in the next few days.
6639
Features / Re: These two bytes may not matter to you...
« on August 22nd, 2011, 11:44 PM »- I think the most logical solution would be to keep the situation where the admin can choose a default theme+skin, but outside of this one, if users choose another theme, they'll get the root skin for it (except, of course, if they directly choose another skin within the theme.)
* admin can choose a default theme+skin
* user can choose a theme+skin for themselves (if it's turned on, otherwise they have what the admin says to have) - and this is remembered.
It doesn't really matter so much how it works internally, as long as the user can pick a theme (and a skin within it, if appropriate) and it remembers it. If a user changes to another theme but doesn't pick a specific skin, the default is fine.
Really, we're not talking about anything different to the case of SMF themes + their variants.
6640
Development blog / Re: A nice kick in the CSS
« on August 22nd, 2011, 11:24 PM »Don't feel bad, I don't think it is humanly possible to not be
6642
The Pub / Re: Copyrights
« on August 22nd, 2011, 09:10 PM »
Provided that we actually link to it, that is...
6643
Off-topic / Re: Aeva Add Sites
« on August 22nd, 2011, 02:44 PM »
I'd also note that even if requests were being taken, the site isn't really popular enough, and that auto embedding may also be in contravention of the ToS of own3d.tv anyway...
6644
Features / Re: New revs - Public comments
« on August 22nd, 2011, 01:35 PM »And work from that... We'd just need to ensure they're in harmony with the corresponding default from each individual function.
Interestingly this behaviour is also present in the profile area where you hit an item with subitems, without the default tab being highlighted...
Posted: August 22nd, 2011, 01:25 PM
OK, fixed it, it was broken in r886 with related changes to the menu code removing unnecessary stuff around figuring out the first/last items.
Posted: August 22nd, 2011, 01:33 PM
Committed in r961.
6645
Features / Re: New revs
« on August 22nd, 2011, 01:35 PM »
Revision: 961
Author: arantor
Date: 12:35:04, 22 August 2011
Message:
! If there's no menu item explicitly selected but we're in a place where we probably should have one because we subsections and we should highlight the first subsection, select it. (Subs-Menu.php)
----
Modified : /trunk/Sources/Subs-Menu.php
Author: arantor
Date: 12:35:04, 22 August 2011
Message:
! If there's no menu item explicitly selected but we're in a place where we probably should have one because we subsections and we should highlight the first subsection, select it. (Subs-Menu.php)
----
Modified : /trunk/Sources/Subs-Menu.php