INETA Infrastructure
Our team consists of the following members:
- Chris Goldfarb
- Devin Rader
- Jason Beres
- John Bristowe
- Keith Franklin
- Shervin Shakibi
We are committed to serving the INETA community at-large anyway we can. However, it's important to note that we all serve in a volunteer capacity. That stated, sometimes it can be difficult to facilitate requests in a timely manner. Despite this, we work very hard to squash each and every bug we find.
On a personal note: I love volunteering for INETA and I am honored to be a member of the Infrastructure committee. I have never met so many passionate people in one organization who are determined to serve a community the best way they can.
INETA Website
A new version of the Website (http://www.ineta.org/) was deployed shortly after TechEd 2003.
Presently, my team is firefighting issues that come down the pipeline. We recently squashed a number of bugs related to view state. (This was resolved by persisting session state in SQL Server.) With luck, we hope to have the site completely stable by next week.
INETA vNext
The Infrastructure committee is currently planning ahead to vNext to incorporate a ton of change requests in the queue. We are focusing on a number of key features including:
- More administration features
- Better internationalization (i18n) support
- Increased extensibility
admin.ineta.org
We are hoping to push administration to a new level with this Website (http://admin.ineta.org/). Currently, the site only serves as a test-bed for a read-only scenario. Eventually, a security policy will be applied.
This site represents some of our push for better i18n support, as evidenced by addresses. Example:
http://admin.ineta.org/groups/?userGroupID=14
Lack of i18n support is a huge problem for us at the moment. A large number of group leaders have reported problems while registering their user groups. Additionally, some views of these addresses don't make much sense. For example, Canada has provinces, not states. ;-)
We want to be able to support as many different types of addresses as we can. i18n is a huge change request for us that we're pushing very hard.
blogs.ineta.org
Coming soon. (Hopefully.)
bugs.ineta.org
We have recently installed FogBUGZ to help coordinate bugs and feature requests. The Infrastructure committee uses FogBUGZ extensively to help improve the site. We also use SourceGear's Vault as our code repository.
Both are excellent pieces of software and are highly recommended.
INETA Events
We are working with Steven Smith (ASPAlliance.com) and friends (including Mitch Denny, Kent Sharkey, and Jeff Julian) on a new framework for event aggregation:
http://www.gotdotnet.com/Community/Workspaces/workspace.aspx?id=a3b4fcdd-efcc-4aae-b57b-da2d164e4ba0
Event sharing is a really exciting notion that the INETA Infrastructure committee would like to support. The hope is to turn the knob up on communication amongst various entities (i.e. ASPAlliance.com, MSDN, INETA user groups) via aggregation. Imagine a scenario where a user could view a calendar displaying all INETA-related events for the current month. Even better, imagine a pub/sub model where event-related announcements are delivered via .NET Alerts, iCalendar items, or RSS. Our hope is to facilitate this communication by providing a standard and an implementation. Exciting stuff indeed.
INETA Web Services
Anyone who knows me knows that I want to implement INETA-related Web services very, very badly. Personally, I see an incredible opportunity for collaboration among INETA members by exposing SOAP endpoints.
11:33:54 AM 
|
