Messages

  Entire forum

Auto Light Dark

English

If I could resurrect this project I'd do it.  But as we all saw, it needs a top notch programmer to immerse him or herself into it.  That's not me.

I think that with all of us working together we could reach a fairly decent level of programming. It may take longer, and it may not be the level that Arantor, Nas, or JBlaze has, but i'm sure that we can all still pull our own.

Some of the Beta Testers on there that i've seen (especially tfs) have an amazing work ethic. Sure, we may not have the skills yet, but it's our passion for this project that will drive us.

I'd be willing to help. I don't know much about code, but it's better than the standstill that's happening now. And I say that anyone that wants to help, code expert or not, should be able to help to. Basically like the direction that Youra has taken for their project, because I don't see any other way that development can get going.

As for a paid version, I say no. There is no reason to split off the project into different versions, there is not enough manpower to do it, and it's not like there is any kind of support-prevention needed.

I know what a move to an apartment is like secondhand from my brother, but I can tell that it can get kind of crazy. Best of luck with the new place, B.

And spoogs, there is still the idea of creating modules for SD. I can't really code all that well either, but at least it's better than nothing. Some development is better than no development. And I think we can all agree that we'd rather not see Nas overextend himself by trying to add SimpleDesk coding to this list of things that need to be done. So rather than have that, i'm sure that the Staff that is still left can try to whip up some minor things to help push things along. At least until things slow down for Nas.

I don't think it wise to give random people commit access =/

No, in my idea they do not have the ability to commit. They start building for a feature, and once they are done they send it to a dev to review. Then the dev cleans it up, and the dev himself commits it.

I can understand why development here would come to crawl then. Arantor has left the team, and has been gone from SMF for a while. JBlaze resigned as Customizer on SMF. And Nas is busy with development of SMF (which obviously comes first). I kind of feel bad for him, balancing so many projects at once.

As for some of the other teamies here....Trekkie101 is On Haitus. SleePy is...well, yeah, SleePy is still active on SMF. B hasn't bee active on SMF as far as I can see in the public boards. (He might be posting on the private boards, and his last active date is still pretty recent, but he still doesn't post a lot on the private boards). It seems that hades has left the team. Though the QA people still seem kind of active from what their profiles say, but I haven't checked the Tracker in a while so I can't tell if they have been active there.

Please note, that i'm just sharing my observation on what the status of the team is. This may not accurately reflect what is going on in private on here, or on the actual SMF community site.

I mean, there are people here who'd love to help support this project, but not many have the ability to code. At least, code well enough to contribute as a developer to the project. Some do, but i'm not sure if they'd be willing to take on the project.

I been thinking lately that it might be helpful to make module development for SD public for other people to work on it, but in actuality i'm not sure that would help much. What is needed is core development kick start of the project. Since there people in the community who would love to help with the project and since 1.1 is a feature-heavy release, maybe getting together "Community Developer Helpers" (or a better name than that) who are assigned a feature to work on as a group. And then send it to Nas or someone else to review, polish, and then commit. This way all Nas has to do is just polish up existing code for features instead of working on his own, which will allow him to spend more time doing other things.

Bah, i'm just tossing ideas out right now. At least it's something.

Right behind you Nas, and the SD team.

Seconded.

Anyway I can help? SimpleDesk is still one of the best projects out there for SMF, IMO, and if there is anyway I can contribute to help keep the ball rolling please let me know.

The plan I use (I have T-Mobile) we have a "data plan" that has a moderately high monthly fee you pay which gives you access to unlimited access to everything using your phone.  This mean unlimited texts, unlimited emails, and unlimited internet usage, and etc.

I'm pretty sure that AT&T and Verizon have the same kind of plans that come with their smartphones.

I'd agree that it is.

I'm sure that your BT/QA team is more than capable of being able to determine which of the features should not be included into the core by default and should be saved from plugin, and from there sort out the list as to what is possible development-wise to have as plugins.

Also, if the title of plugin is going to be perceived negatively then how about giving it a new name like "extension"? Or there is also the slightly corny route of having plugins as "drawers" for the SimpleDesk.

As for having a large third-party developmental group to help you, then I think you're right in assuming that it's not going to be that large. The way I see it is that since SD is a niche inside of SMF there is not as large an area for modders to write their own plugins as there is for SMF.

However there is still the point about how easy it's going to be for users to pick up SD development and start running with it, and how large the learning curve with it is. Depending on how significant you want user plugin development to be, it's something to take into account.

Just my 2 cents.

How would the features be decided then if they are core or a plugin? What I could see end up happening is that people would whine about having to download a feature as a plugin instead of it being core. I'm not saying that doing a plugin system isn't a more logical approach, personally I think it is, but i'm simply saying that other people will complain about the "more work" being made for them.

As for the community, i'm not sure that theres a lot of availability of plugin developers. So in terms of community support i'd say not to expect for much help. I for one, would love to contribute to the project but with my lack of skills I would just be more of a hinderance than a contributor. One problem I can foresee is that the Devs would have to "train" plugin developers instead of taking the time to build SD on their own, unless a new system was in place to go along with plugin development release. The majority of the plugin construction would have to be within the team, which is not so bad I suppose. I don't really see any hit in release time for this for the reasons that you've stated Arantor and for the basic fact that it's not like anything new is being developed. Instead of being built into the core, features are just being built as plugins.

Personally i'm all for this idea. It'll clear the core SD out of bulk, and I trust the Dev Team to build a plugin system that is simple and easy to use.

Wow, that UI for the permissions system looks so beautiful. You guys really take every little thing into account which is awesome for a such a large mod like this. I mean, in order to see what Template the Role is based off of you have clear images that tell you instead of just having text that take up space. SD Devs really love to use their space wisely.

This is a great site to see. Thats for posting it Arantor.

Heh, looking back on it I asked some pretty stupid questions...

But information and updates on the project are always good. So it's not so bad.

Thanks for this Arantor! Now excuse me while I go sneak into hades' hideout, and steal hiz kittehs.

Ah, wow.....that was really really great.

Nice find, JB.

Wow, SD development was more intense than I thought. So much going on the back-end that it can barely be conceived! You all make it look so easy.

Great read, Arantor. And very fascinating to say the least. I'm sorry about what happened to your father though. My heart goes out to you and your family.

As for SD itself, the dedication that all of the team members put in is just a reflection of how great the product they come out with is.

Best of luck for the road ahead!

[nocomment][/nocomment]

The OP already got his answer. Can we just lock this thread please?

How long are we waiting, just wondering?