Skip to main content

So How Do I get involved with SednaX?

The SednaX project has been filled so far with lots of talk and ideas but not a lot of direct output (this led Craig Berntsonto keep it off his 2005 highlights) but that's about to change.

I interviewed Craig, Rick and Doug on what the plan is and how the 400+ developers who have signed up can start getting involved with this open Visual FoxPro community project.

As noted in the interview, it's important to note that SednaX doesn't have to rely on Dotnet components (although there may be some benefits there) and that each project will have its own timeline. It's not a "packaged" solution - but more of a organization of several related projects.

We touch on the commercial vs. open aspect of the project as well - so commercial developers (such as Doug and Rick) can know what to expect from such a project.

What also struck me was Craig's comment about "tricks up their sleeves" from the Fox team themselves - as things like source control are still being worked out, one can only imagine (at least my thought would be) what a great coup this would be if MS allowed the entire project to be driven from the Visual Studio Team system approach. It might give MS more credibility and visibility and it would benefit the Fox community as extra add-ons would be built to help integrate the two environments as Scott and Craig have talked about before.

As Craig has noted, we live in exciting times...

The Fox Show podcast: News, reviews and training on Visual FoxPro

Comments

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site: http://foxincloud.com/blog/2017/12/27/VFP-community-lessons-from-foxincloud-site.html What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older. Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments. But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward. FoxPro VFP