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.
1981
The Pub / Re: New maintenance task
« on January 13th, 2013, 12:23 AM »
That's why I'm wary of implementing a check against file contents. File dates, not so much.
1982
Other software / Re: Discussing Wedge on simplemachines.org
« on January 12th, 2013, 09:45 PM »Now this is even trickier because when your prototypes aren't ready to be released as developers, and with the lack of current developers, then the problem is greater than it could have been. I've always wondered if Customizers had a close relationship with the core developers, or if they were treated as two seperate entities.
Once upon a time I believe they were more intermixed than they are now.
1983
Other software / Re: Discussing Wedge on simplemachines.org
« on January 12th, 2013, 09:31 PM »This response atleast gives me hope that other developers might feel (somewhat) the same. But you are completely fair in your reasoning, and I think that's why Wedge will continue to grow.
Right, and the issue is that there are competent people hanging around but they've already been through the issues of working with SMF and the organization, and that will probably require a drastic change to get them in the position.
On another note, there are people who already have an opportunity of doing this job, and those are the current Customizers.
Though, given some of the things I've seen lately, I would have plenty more to say on the relative skills of some of the Customisers. Theoretically, they're supposed to be proto-devs, knowing the guts of SMF pretty well, but writing things that aren't intended to be core features, as well as reviewing mods from the community, for technical or logistical or security issues. Trouble is, I'm not seeing anything of substance coming out of the Customisers that indicates they've got what it takes to be devs.
As for looking for developers... Well, I don't think it is very feasible. It's not like we have developers arriving to SMF every week...
One thing I would draw your attention to: http://www.simplemachines.org/community/index.php?action=stats#stats
Look at the figures for the yearly summaries. What does that tell you?
| 1. | I could be wrong but I'm pretty sure Bloc was dev team at one point, e.g. around 1.1 and what was then NDT. Bloc, if I'm wrong, please feel free to correct me :) |
1984
Other software / Re: Discussing Wedge on simplemachines.org
« on January 12th, 2013, 08:53 PM »Right, but do you think people (or atleast you) would come back with a new change in the politics?
I think the biggest problem is the people in charge vs. the people who can move SMF forward as a competitive product because let's face it: the developers are the ones with the time, energy, passion, and skills to push out great updates, while the people in charge need to do their jobs in making sure the project runs smoothly. Since the developers don't want to come back, and the people in charge probably don't want them back, now what?
I would note, I have heard from several current team members that they would be quite enthusiastic about seeing me back on the SMF team - there is sufficient change from how it was a few years ago about people coming and going that gives me hope, but that's not the biggest problem any more.
1985
Other software / Re: Discussing Wedge on simplemachines.org
« on January 12th, 2013, 07:54 PM »
I don't think that matters so much. I think there is an understanding on both sides as to what is needed, but the fundamental change most needed isn't going to happen: getting great people up top running the show. We even agree on what traits are necessary, but people who are known in the community as having the necessary things don't want the job. Which means recruiting outside the community, which is nigh on impossible.
1986
Other software / Re: Discussing Wedge on simplemachines.org
« on January 12th, 2013, 07:24 PM »
You have a twisted sense of humour, TE :P
1987
The Pub / Re: New maintenance task
« on January 12th, 2013, 05:16 PM »
That occurred to me too, though I can imagine problems if folk edit their files directly, especially theme ones.
1988
Other software / Re: Discussing Wedge on simplemachines.org
« on January 12th, 2013, 06:19 AM »
If you don't see disagreements as a Grudge, do you see them as a Thantos or an Orstio? :P
* Arantor waits for the joke to go flying overhead and land with a splat.
1989
The Pub / New maintenance task
« on January 12th, 2013, 05:56 AM »
Been thinking about this a bit, not entirely sure what it needs, but thought I'd suggest it.
It's been the case for a long time that plugins can't touch the core, and it's now the case that files don't end in ?> which means one of my original thoughts on this subject is no longer necessary.
But anyway. I was going to do a maintenance task, running say every other week, to scan the files. It would scan the files for things like rogue characters at the start or end of files (though with the lack of trailing ?> this is a bit more difficult), perhaps for common injection type things and report to the admin area.
I kind of see this as a new area above the 'New to Wedge' box that's there, maybe even replacing it, don't know yet, where the admin panel flags up some tasks that are needed. For example, it strikes me that it would be neat to include a monthly reminder to update your anti spam Q&A as a 'Things to do' page.
This isn't original; IPB does it, and it strikes me that having such a notification (similar to, but more prominent, the admin panel upgrade notification in SMF) would be beneficial in encouraging people to fix things.
I could go on to have it be popping up even on a fresh install as 'You haven't set questions yet...' like a sort of warning. I'm getting a bit ahead of myself *rerail!*
So, maintenance task doing a health check. It could also conceivably do checking of file dates now that the core files don't need to be touched, except for Subs-Aeva-Sites.php which gets rewritten on updating the active site list. (Need to fix that. It causes havoc on systems that lock permissions down, not to mention the fact that having a core file be writable is asking for trouble.)
Comments?
It's been the case for a long time that plugins can't touch the core, and it's now the case that files don't end in ?> which means one of my original thoughts on this subject is no longer necessary.
But anyway. I was going to do a maintenance task, running say every other week, to scan the files. It would scan the files for things like rogue characters at the start or end of files (though with the lack of trailing ?> this is a bit more difficult), perhaps for common injection type things and report to the admin area.
I kind of see this as a new area above the 'New to Wedge' box that's there, maybe even replacing it, don't know yet, where the admin panel flags up some tasks that are needed. For example, it strikes me that it would be neat to include a monthly reminder to update your anti spam Q&A as a 'Things to do' page.
This isn't original; IPB does it, and it strikes me that having such a notification (similar to, but more prominent, the admin panel upgrade notification in SMF) would be beneficial in encouraging people to fix things.
I could go on to have it be popping up even on a fresh install as 'You haven't set questions yet...' like a sort of warning. I'm getting a bit ahead of myself *rerail!*
So, maintenance task doing a health check. It could also conceivably do checking of file dates now that the core files don't need to be touched, except for Subs-Aeva-Sites.php which gets rewritten on updating the active site list. (Need to fix that. It causes havoc on systems that lock permissions down, not to mention the fact that having a core file be writable is asking for trouble.)
Comments?
1990
Other software / Re: Discussing Wedge on simplemachines.org
« on January 12th, 2013, 05:48 AM »Don't assume that bluntness = patronizing, because it does not and was not in my case.
All those words I said months ago are becoming a reality now... as sad as that statement is.
One man does not make a team, and it's not really down to specific statements from any individuals - and that's where it really grates, is because it's so subtle, but so present. It is a closing of ranks, of stonewalling, and similar behaviours - but you have to be on the other side of it to realise it's going on. I suspect half the time the people doing it don't even realise they're doing it.
There are events I won't go into about political machinations, even down to someone admitting to me that they had had a hand in rigging team leader elections by 'encouraging' people to vote in certain lines with the intent of pushing the project forward. I mention this because it is the sort of behaviour that got things to where they are - non-visible signs of people acting with an agenda that serves to close ranks.
There is a sad corollary to this tale. Earlier on today someone who saw this thread, who shall remain nameless (save for the fact they are outside the SMF team), suggested that I step up to the plate as SMF dev, because I have the skills, I have the ability and you KNOW I'm not going to stand for this kind of crap. I said no to the person suggesting it, mostly because I'm far happier with Wedge, but that's really the sort of change that's needed now.
I think the only way to make SMF work is for someone with the skills, the time, and the balls to tell the management to get stuffed when it counts, to step up as lead dev. Ema's too nice for that, Lab doesn't have the skills or experience for it. I don't particularly want the job either because I'd much rather not have to split my time between SMF and Wedge, but if SMF is going to be saved, it's going to take someone like me to do it, someone with the charisma to engage people and motivate, someone with the skills to put their money where their mouth is and someone who ultimately can deliver in spite of management.
The person who suggested this course of action also suggested that perhaps the only way to save SMF is for Wedge to become SMF 3.0 - it is after all a natural conclusion to come to and it's been rather understated.
I think it's fairly clear to say that that isn't going to happen, but not because I'd veto it (I'm not entirely sure how Nao feels on the subject). The Wedge brand is growing, and we're happy with what we have here, and I only dread to think how much work would be required in renaming it back, not to mention engineering everything from 2.1 into Wedge (since we haven't adopted SCEditor or anything, though I'm sorely tempted to), not to mention the freedom that being here gives me that being at SMF wouldn't, as previously discussed. This is assuming I could put my personal pride aside, and my ego, but that's my problem, not SMF's.
There's your answer, folks. SMF will wither and fail after 2.1 unless it can recruit some serious talent, but there's no talent up to scratch coming up through the community, and the only talent that has the skills has sufficiently been alienated by past history that they'd never take up the mantle. Once bitten, twice shy and all that.
It's on a knife edge, and it may yet be saved, but I think something akin to a divine intervention is what's needed. There are people who could help, but they need reaching out to, and they're going to need assurances that it won't be like before - and they won't be ready to believe you. But as I see it, that's the only real future prospects SMF has.
1991
Features / Re: New revs
« on January 12th, 2013, 03:33 AM »
(1 file, 1KB)
Revision: 1841
Author: arantor
Date: 12 January 2013 02:32:48
Message:
! There was a collision between what used to be $context['user']['avatar'] and $user_info['avatar']. Hopefully fixed now. Haven't found any other such collisions, but it's always possible. (Subs.php)
----
Modified : /trunk/Sources/Subs.php
Revision: 1841
Author: arantor
Date: 12 January 2013 02:32:48
Message:
! There was a collision between what used to be $context['user']['avatar'] and $user_info['avatar']. Hopefully fixed now. Haven't found any other such collisions, but it's always possible. (Subs.php)
----
Modified : /trunk/Sources/Subs.php
1992
Archived fixes / Re: Why does Wedge look different for me?
« on January 12th, 2013, 03:19 AM »
No... you open phpMyAdmin, click on the database, find wedge_settings, then go through the wedge_settings table until you find a row where the 'variable' column has an entry of 'default_index', then you click on the edit button for that row and change the value from Welcome to Home.
1993
Features / Re: Improving how smileys are managed
« on January 12th, 2013, 01:18 AM »
Well, Wedge templates are fundamentally more modular than SMF ones, and there is a powerful (and complex) template nesting system, the advantage of which is that you can interject templates in between other templates.
But I never made any bones about the fact Wedge is more plugin rather than theme orientated, that's just the direction we wanted to take it. Given that, I was never comfortable giving the theme *too* much power, but it has *sufficient* power from our perspective for the most part.
But I never made any bones about the fact Wedge is more plugin rather than theme orientated, that's just the direction we wanted to take it. Given that, I was never comfortable giving the theme *too* much power, but it has *sufficient* power from our perspective for the most part.
1994
Other software / Re: Discussing Wedge on simplemachines.org
« on January 12th, 2013, 01:04 AM »Yes... we all are a buch of egocentric bastards:
I left because you keep trying to run things like a corporation and fail to realize that SMF is an open source project now.
i left because, what did you call me? oh yeah, a poisonous people and you were suppose to replace me with some other person who can work under your command.. I'm still waiting as I'm eager to meet my replacement
And lastly, I left because no one actually saw me as a dev, even in this whole convo... I was never approached when the whole Norv thing imploded, never approached to do anything, heck, I wasn't even approached when Dialogo started... talking about feeling like a complete outkast... neither of both sides wanted me :P so thats why I decided to work on my own, to let people know what I'm capable of...
Dialogo/Elkarte is a very specific beast. I haven't joined because I don't want to crowd them, though I commented on a few things on Github. It has certain roads it is going to walk down, lead by Norv. They're roads I don't particularly care to share, but that's down to me. I do get the impression that you might feel happier staying out of it, though.
I tried to give SMF some directions (currently there is none...),
You're wrong, not even a feasible explanation on why I was suppose to be wrong at...
Oh, BTW, I started on support, moved to Cust, did a lot of documentation in Spanish, a good portion of the Spanish_latin language was done by me... so yeah, I'm not a codemonkey only nor am I the egocentric bastard you think all devs are...
Seems to me that the underlying issue with all this stems from peoples DIFFERENCES OF OPINION in all areas of development / management. Resulting in feelings of rejection, questions of self worth, challenges of ego, beliefs that one persons ideas are far better than another's and so on. And the fact that no resolve is possible purely because you simply cant please everyone!
There are things I've done, and things Nao's done that we've individually disliked the other going off and doing. But even though I might disagree with what he did or he disagrees with what I'm doing, there's always respect, and there's always an understanding that the disagreements are not personal.
Extrapolating this a bit, I see a lot of arguments where people don't seem to be able to handle disagreeing with an idea vs ignoring an idea. If I make an observation about the characteristics of something, that's fine. If it disagrees with where you want to take it, also fine - but when you're taking it where you're taking it, be sure to take what I've said into account. It may change your direction, it might not, but you can explain that you disagree with me without making me feel like it was a waste of my time introducing my observations. This is something lacking in a lot of arguments.
I disagree, for example, with how SMF is implementing hooks in SMF 2.1. I've explained my concerns with the proposals, and that's fine. They can still do it how they were going to do it, and that's also fine. But if they run into the problems I outlined, I'm not going to be very impressed if they start whining about it when they get there. It's the proverbial "I told you so" moment, and it's not even a smug triumphant one, but an understated and sanguine one.
Having to cater for everyone's whim is one thing that SMF is stuck with and it becomes infinitely harder as the team expands whereas in Wedges case less people result in fewer clashes of opinion. Things can be discussed and resolved in a timely fashion without encountering the red tape and personality clashes that are prevalent in a larger scale operation.
Here's the thing. When we introduce new ideas and concepts, we introduce them but we don't entirely open the floor. We open the floor for feedback, discussion and so on, but it's not likely that what ends up getting written will be too far from what was discussed. This is an example of what I'm on about - I'll open the floor, let people have their say and take it into account when polishing it - even if I don't agree with where they're trying to take it. SMF hasn't learned that ability yet.
I cannot understand the fear of "breaking" SMF so to speak..why could not the work being done in forks now, have been done inside SMF too? It would make a lot of sense if SMF embraced forking, or rather "directions" instead of trying to follow a "safe" path and alienate everything else(which is even done mostly by ex-SMF people lol).
Wedge is one direction, Elkarte is another, bloQS is another. These may be partially or completely mutually exclusive - so SMF does nothing and sits with what is safe. But the rest of us do something not safe, but what we learned from the journey, we're not encouraged to share, and in some cases have been actively discouraged from so doing. It's like they embraced the name of freedom but not the spirit somehow, which is a shame.
1995
Features / Re: New revs
« on January 12th, 2013, 12:29 AM »
(17 modified, 2 deleted, 17KB)
Revision: 1839
Author: arantor
Date: 11 January 2013 23:28:24
Message:
! Typo in index template. (index.template.php)
! Removal of the crazy wesql::extend stuff. It should never have lingered. So, what was wedbExtra is now part of the packages stuff (which might be renamed yet), which makes sense as the packages stuff loaded it anyway. What was wedbSearch was just folded into the search code or flattened out, e.g. the test for 'supports fulltext'., and lastly, wedbPackages is no longer a singleton in the way it was set up. It made no sense to be, in hindsight, it's just a collection of static methods now. It's not had proper testing though so it might be all kinds of borked. (lots of files)
----
Modified : /trunk/Sources/Class-DB.php
Deleted : /trunk/Sources/Class-DBExtra.php
Modified : /trunk/Sources/Class-DBPackages.php
Deleted : /trunk/Sources/Class-DBSearch.php
Modified : /trunk/Sources/ManageMaintenance.php
Modified : /trunk/Sources/ManagePlugins.php
Modified : /trunk/Sources/ManagePosts.php
Modified : /trunk/Sources/ManageSearch.php
Modified : /trunk/Sources/ManageSearchEngines.php
Modified : /trunk/Sources/ManageSmileys.php
Modified : /trunk/Sources/Packages.php
Modified : /trunk/Sources/ScheduledTasks.php
Modified : /trunk/Sources/Search2.php
Modified : /trunk/Sources/Subs-Admin.php
Modified : /trunk/Sources/Subs-Plugins.php
Modified : /trunk/Themes/default/index.template.php
Modified : /trunk/other/tools/repair_settings.php
Modified : /trunk/other/xml/detailed-version.php
Modified : /trunk/root/install.php
Revision: 1839
Author: arantor
Date: 11 January 2013 23:28:24
Message:
! Typo in index template. (index.template.php)
! Removal of the crazy wesql::extend stuff. It should never have lingered. So, what was wedbExtra is now part of the packages stuff (which might be renamed yet), which makes sense as the packages stuff loaded it anyway. What was wedbSearch was just folded into the search code or flattened out, e.g. the test for 'supports fulltext'., and lastly, wedbPackages is no longer a singleton in the way it was set up. It made no sense to be, in hindsight, it's just a collection of static methods now. It's not had proper testing though so it might be all kinds of borked. (lots of files)
----
Modified : /trunk/Sources/Class-DB.php
Deleted : /trunk/Sources/Class-DBExtra.php
Modified : /trunk/Sources/Class-DBPackages.php
Deleted : /trunk/Sources/Class-DBSearch.php
Modified : /trunk/Sources/ManageMaintenance.php
Modified : /trunk/Sources/ManagePlugins.php
Modified : /trunk/Sources/ManagePosts.php
Modified : /trunk/Sources/ManageSearch.php
Modified : /trunk/Sources/ManageSearchEngines.php
Modified : /trunk/Sources/ManageSmileys.php
Modified : /trunk/Sources/Packages.php
Modified : /trunk/Sources/ScheduledTasks.php
Modified : /trunk/Sources/Search2.php
Modified : /trunk/Sources/Subs-Admin.php
Modified : /trunk/Sources/Subs-Plugins.php
Modified : /trunk/Themes/default/index.template.php
Modified : /trunk/other/tools/repair_settings.php
Modified : /trunk/other/xml/detailed-version.php
Modified : /trunk/root/install.php