openfirst-devel Mailing List for openFIRST (Page 2)
Brought to you by:
xtimg
Menu
▾
▴
openfirst-devel — Discussion list for openFIRST development.
You can subscribe to this list here.
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(7) |
Aug
(4) |
Sep
(5) |
Oct
(8) |
Nov
(1) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2006 |
Jan
|
Feb
(1) |
Mar
|
Apr
(3) |
May
(7) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Tim G. <ti...@op...> - 2005-09-20 23:28:05
|
On 20-Sep-05, at 7:09 PM, David Di Biase wrote: > Hey Tim, Hey list, > What exactly does he mean by help/support and developing a ground > floor? I believe we need more insight into the request. I know no more than what's in the e-mail; it was addressed to me and I forwarded it to the list, there have been no prior communications to that message. That said, feel free to contact him regarding more information and to (with his permission) post it to the list. > Also as founding members of openFIRST I believe you and I should > discuss the potential future of the project (of course with input from > the others) but the decision is up to us in the end. > > Agreed? That's what the list is for, discussion about the potential future of the project. The way the message itself is written, specifically the "would OpenFIRST or anyone associated with it be willing to help a new organization" bit leads me to believe that it's an open offer to more than just our project (and some of the people on the openFIRST-devel list are indeed parts of other FIRST-related Organisations) so I'm not entirely sure that any official action has to be taken by the project itself and some people on the list may be interested as individuals rather than as representatives of openFIRST. That being said, I'd prefer the discussion and decision (if any) to be open and using the list rather than in camera between you (Dave) and I since it seems to me that it will largely be others following through with any actions required by said decision. Tim |
|
From: David Di B. <dav...@gm...> - 2005-09-20 23:10:04
|
Hey Tim, What exactly does he mean by help/support and developing a ground floor? I= =20 believe we need more insight into the request. Also as founding members of openFIRST I believe you and I should discuss th= e=20 potential future of the project (of course with input from the others) but= =20 the decision is up to us in the end. Agreed? David On 9/20/05, Tim Ginn <ti...@op...> wrote: >=20 > Begin forwarded message: >=20 > > From: Leon Machado IV <leo...@gm...> > > Date: September 20, 2005 9:22:55 AM EDT > > To: ti...@op... > > Subject: General Help > > Reply-To: Leon Machado IV <leo...@gm...> > > > > Greetings, > > > > I'd like to quickly introduce myself and then get to the point of this > > email. My name is Leon Machado. A couple of years ago myself along > > with a handful of other people started an organization known as the > > Inspiration Foundation, Inc. (better known as iF). After talking to > > people and faltering some, the organization basically went no where. > > I was up at WPI a couple of weeks ago and just happened to be talking > > to an old FIRST friend, and she had the idea of supporting FIRST > > teams, the same basic idea we had a couple of years ago. After some > > discussion, we decided it would be better to take it slower then the > > first time, and build a solid base with a lot of great connections > > before trying to tackle our dreams of supporting numerous FIRST teams. > > > > Our basic question is two fold. The first is OpenFIRST looking for > > help or support in anyway? The second is would OpenFIRST or anyone > > associated with it be willing to help a new organization develop a > > ground floor and hopefully grow with us? > > > > Feel free to pass this email around, and have any questions, comments, > > etc., be either gathered and sent in one email, or let everyone send > > individual emails to me at leo...@gm... . I hope to hear > > back from you soon. Many thanks for the time your and you're > > organization is giving to this. > > > > Yours in FIRST, > > Leon O. Machado IV > > President, The Inspiration Foundation, Inc. >=20 >=20 --=20 David Di Biase Spyral Productions Inc. http://www.spyral-productions.com |
|
From: Tim G. <ti...@op...> - 2005-09-20 21:22:19
|
Begin forwarded message: > From: Leon Machado IV <leo...@gm...> > Date: September 20, 2005 9:22:55 AM EDT > To: ti...@op... > Subject: General Help > Reply-To: Leon Machado IV <leo...@gm...> > > Greetings, > > I'd like to quickly introduce myself and then get to the point of this=20= > email.=A0 My name is Leon Machado.=A0 A couple of years ago myself = along=20 > with a handful of other people started an organization known as the=20 > Inspiration Foundation, Inc. (better known as iF).=A0 After talking to=20= > people and faltering some, the organization basically went no where.=A0=20= > I was up at WPI a couple of weeks ago and just happened to be talking=20= > to an old FIRST friend, and she had the idea of supporting FIRST=20 > teams, the same basic idea we had a couple of years ago.=A0 After some=20= > discussion, we decided it would be better to take it slower then the=20= > first time, and build a solid base with a lot of great connections=20 > before trying to tackle our dreams of supporting numerous FIRST teams. > > Our basic question is two fold.=A0 The first is OpenFIRST looking for=20= > help or support in anyway?=A0 The second is would OpenFIRST or anyone=20= > associated with it be willing to help a new organization develop a=20 > ground floor and hopefully grow with us? > > Feel free to pass this email around, and have any questions, comments,=20= > etc., be either gathered and sent in one email, or let everyone send=20= > individual emails to me at leo...@gm... .=A0 I hope to hear=20= > back from you soon.=A0 Many thanks for the time your and you're=20 > organization is giving to this. > > Yours in FIRST, > Leon O. Machado IV > President, The Inspiration Foundation, Inc. |
|
From: Jamie B. <ast...@gm...> - 2005-09-11 21:30:07
|
I need to know of anyone using a DBMS other than MySQL! I'm coding for enough of MySQL's extensions to the SQL "standard" that some compatibility checks should be done. --=20 Jamie ------------------------------------------------------------------- http://endeavour.zapto.org/astro73/ Thank you to JosephM for inviting me to Gmail! Have lots of invites. Gmail now has 2GB. |
|
From: Jamie B. <ast...@gm...> - 2005-08-28 04:54:54
|
Could we use Mozilla-style properties files for translations? Extremely simple syntax, directly translatable into a flat associative array, and requires no fancy editors or anything. The only trick is figuring out the encoding to use... I've included part of the properties file from the Firefox DOM Inspector. It can also be found at <chrome://inspector/locale/inspector.properties> (in Mozilla or FireFox). Note that this format is geared towards short snippets, not long blocks. --=20 Jamie newAttribute.title =3D New Attribute editAttribute.title =3D Edit Attribute enterAttrName.message =3D Enter the attribute name: enterAttrValue.message =3D Enter the attribute value: findNodesDocumentEnd.message =3D End of document reached. findNodesDocumentEnd.title =3D Find Nodes # The following items correspond to the node types defined by the # W3C DOM Core specification. 1 =3D Element 2 =3D Attribute 3 =3D Text 4 =3D CDATA Section 5 =3D Entity Reference ------------------------------------------------------------------- http://endeavour.zapto.org/astro73/ Thank you to JosephM for inviting me to Gmail! Have lots of invites. Gmail now has 2GB. |
|
From: Jamie B. <ast...@gm...> - 2005-08-24 18:12:27
|
I have created a branch in CVS called REL1_1_BRANCH for this interim release. It starts at the last release date (April 14, 2004 for everything except awards and emoticon, which are April 12, 2004). Any bugs that were fixed after that date must be commited to that branch. Any new bugs found in this branch should have the version 1.1 (1.1.0 will be the release). Any current bugs that have not been fixed in REL1_1_BRANCH have the keyword REL1_1. (I'm currently working on tagging bugs). The modules bashinstall, config, config_asp, logger_asp, modules, update, and www are excluded from all of the above. On 8/23/05, Tim Ginn <ti...@op...> wrote: > This is a post to the openFIRST discussion list, subscription management = information is included at the bottom of this message. > _______________________________________________ >=20 > On 23-Aug-05, at 4:37 PM, Jamie Bliss wrote: >=20 > > Because the next release is going to be massive, I'm wondering if we > > should have an interim release, for 2 reasons: > > - To ease the transition > > - To quench the parched masses ;) >=20 > I think that's a good idea. I'd like to see the simple Bugzilla bugs > which are still open for assorted modules fixed, too (I'm sure one of > the newer people could take this on as most of them are quick things to > fix properly). >=20 > > Some of the things I'm thinking should go in there is the file > > structure changes and the new DB object. >=20 > I like that idea; were you thinking of having the DB object there as a > required thing that's used by all the code, or being there for the > benefit of people with custom applications to give them an opportunity > to migrate? I think as an interim release intended to ease the > transition having it there but not required or necessarily used by > everything would be helpful (e.g. no massive rewrites to every module > just to have it work, etc.). >=20 > > We could also toss in the > > older dev module system (the one bassed on openfirst.info.php), since > > that is considerably simpler than the XML one we're working on > > currently. >=20 > I'm not a big fan of tossing in the older dev module system that's > based on openfirst.info.php-- the last released version (which was a > while ago) doesn't use it and I don't see the point in having people > migrate to it in the interim and then away from it when the next full > release comes out. If we don't formally release anything using > openfirst.info.php we'll never have to worry about officially > supporting it in the future and maintaining some semblance of > compatibility which I think would simplify our lives considerably in > the future (especially since there is no Support Coordinator at the > present time). >=20 > > Anybody up to this? >=20 > By all means; I could use the practice packaging another release (it's > been a while) and may even end up writing some new tools to help me out > (reference: BZ id #243). >=20 >=20 > Tim >=20 >=20 >=20 > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practic= es > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & Q= A > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf >=20 >=20 > _______________________________________________ > openFIRST-devel mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/openfirst-devel >=20 --=20 Jamie ------------------------------------------------------------------- http://endeavour.zapto.org/astro73/ Thank you to JosephM for inviting me to Gmail! Have lots of invites. Gmail now has 2GB. |
|
From: Tim G. <ti...@op...> - 2005-08-23 21:10:50
|
On 23-Aug-05, at 4:37 PM, Jamie Bliss wrote: > Because the next release is going to be massive, I'm wondering if we > should have an interim release, for 2 reasons: > - To ease the transition > - To quench the parched masses ;) I think that's a good idea. I'd like to see the simple Bugzilla bugs which are still open for assorted modules fixed, too (I'm sure one of the newer people could take this on as most of them are quick things to fix properly). > Some of the things I'm thinking should go in there is the file > structure changes and the new DB object. I like that idea; were you thinking of having the DB object there as a required thing that's used by all the code, or being there for the benefit of people with custom applications to give them an opportunity to migrate? I think as an interim release intended to ease the transition having it there but not required or necessarily used by everything would be helpful (e.g. no massive rewrites to every module just to have it work, etc.). > We could also toss in the > older dev module system (the one bassed on openfirst.info.php), since > that is considerably simpler than the XML one we're working on > currently. I'm not a big fan of tossing in the older dev module system that's based on openfirst.info.php-- the last released version (which was a while ago) doesn't use it and I don't see the point in having people migrate to it in the interim and then away from it when the next full release comes out. If we don't formally release anything using openfirst.info.php we'll never have to worry about officially supporting it in the future and maintaining some semblance of compatibility which I think would simplify our lives considerably in the future (especially since there is no Support Coordinator at the present time). > Anybody up to this? By all means; I could use the practice packaging another release (it's been a while) and may even end up writing some new tools to help me out (reference: BZ id #243). Tim |
|
From: Jamie B. <ast...@gm...> - 2005-08-23 20:37:16
|
Because the next release is going to be massive, I'm wondering if we should have an interim release, for 2 reasons: - To ease the transition - To quench the parched masses ;) Some of the things I'm thinking should go in there is the file structure changes and the new DB object. We could also toss in the older dev module system (the one bassed on openfirst.info.php), since that is considerably simpler than the XML one we're working on currently. Anybody up to this? --=20 Jamie ------------------------------------------------------------------- http://endeavour.zapto.org/astro73/ Thank you to JosephM for inviting me to Gmail! Have lots of invites. Gmail now has 2GB. |
|
From: Daniel Z. <web...@gm...> - 2005-07-22 22:20:37
|
Hello everyone, I recently joined the OpenFIRST project and I'd like to introduce myself as the new Validity Coordinator. I'm Daniel Zollman, the webmaster of Lower Merion High School's rookie FIRST team (Pennsylvania). I have experience in (X)HTML, CSS, PHP, and a little MySQL. If you'd like to contact me, feel free to email me ( web...@gm... ) or IM me ( worldbringer, AIM and Yahoo IM). Dan Zollman |
|
From: Tim G. <ti...@op...> - 2005-07-20 22:28:39
|
Hello, I've discussed with several of you a plan for how to restructure the openFIRST Project such that things don't get bogged down with one central point of authority while at the same time there's a definite go-to person for each area. The conclusion we reached is that the project should organised as follows. There are a number of teams, each team has a coordinator who works with everyone on the team to make sure the goals of the team are being followed, that people aren't duplicating effort, etc. If/when a quick decision affecting the whole project needs to be made it may fall to the coordinators to do it and coordinators should know the answer to questions about their area or at least who to ask to get them. The teams are (where someone's already opted to be the coordinator his name and e-mail is listed; we'd like to have each person being the coordinator for at most one area): Development - Jamie - ja...@op... Internationalization - Guilherme - gui...@op... Validity Testing Accessibility Administration - Tim - ti...@op... Evangelism Support Here's a brief description of what each team does: Development - the development of modules to be distributed (actual coding is done only by FIRST students; the coordinator is most likely, but not necessarily a FIRST student). Internationalization - translates project documents, distributed modules, etc. into languages other than English (translation for distributed modules must be done by students; translation for other areas is not necessarily done by a student; the coordinator may or may not be a FIRST student) Validity - ensures that markup, CSS, Javascript, etc. used throughout the project comply with the respective standards (for work on distributed modules this must be done by students; for other areas it is not necessarily student done; the coordinator may or may not be a FIRST student) Testing - pretty self explanatory; not just for the distributed modules (this is open to everyone; the coordinator may or may not be a FIRST student) Accessibility - responsible for ensuring that the site, modules, etc. work for those who are faced with disabilities such as blindness, poor vision, and those accessing openFIRST materials through a medium other than a conventional web browser (such as those using a PDA/cell phone browser, screen reader, braile output device, etc.) (for work on distributed modules actual code changes must be done by students but discovering issues is open to everyone; the coordinator may or may not be a FIRST student and would ideally have access to some devices other than the conventional web browser) Administration - responsible for handling all server side stuff, projects that aren't distributed (such as FIRST Blogs), etc. (this isn't student only, it is strongly encouraged that the coordinator be someone who has been with the openFIRST Project for a long duration and therefore is most likely not still a FIRST student though ideally will have been one in the past) Evangelism - tasked with getting users/volunteers/generally spreading the word about the project. (anyone and everyone can be part of this group; the coordinator may or may not be a FIRST student) Support - responsible primarily for supporting the shipped modules using Bugzilla, e-mail, forums, and potentially other means (anyone may be a member of this group; the coordinator may or may not be a FIRST student) So, if you'd like to opt to be a coordinator, first and foremost make sure you have the time and skills to do it effectively, and then pick your area and let me (or preferably this list) know what it is. |
|
From: Tim G. <ti...@op...> - 2005-07-16 02:06:09
|
Hello, It's about time that I posted something about the latest project I've been working on for a little over a week now. The site is called FIRST Blogs. The address is http://blog.openfirst.org/ . The short term goal is merely to aggregate blogs from people currently or previously affiliated with FIRST. The blogs are all from people involved in FIRST (be that as a current/former student, mentor, sponsor, or whatever else) and are included regardless of where they're hosted (Live Journal, personal sites, My Space, Xanga, and others) in one place. Currently the site produces an RSS feed of all of the blogs combined in addition to the HTML version shown on the main page. Recently there has also been the addition of a form to recommend a blog to be shown on the site (in addition to the method of just e-mailing me with the details). Possible future directions for the site include the direct provision of blogging space for users and the creation of a more topic-oriented list. These possibilities will be re-evaluated later, but at this point the goal is mainly to get as many people blogging to the site, and reading the site as possible. Acknowledgements: Thanks to Dave for creating the FIRST Blogs Logo and helping me work through the site design Thanks to Bharat for creating the openFIRST Powered Logo Cheers, Tim P.S. If you've got a blog and aren't already there, feel free to give me the info and I'll add you to the site. |
|
From: Tim G. <ti...@op...> - 2005-07-13 22:27:10
|
Hey, I've started a convention of marking with the prefix "[JJ]" bugs that should be able to be easily fixed by people with little/no prior knowledge of how the openFIRST system works. This will give people who want to help out, but don't have an in-depth understanding of how the overall code works a chance to help with things and get a bit of an idea of how things operate. So, when filing new bugs, or reviewing old ones, if you notice that there's only an entry-level of experience required to fix the bug, or that a fix is relatively quick to research and complete (about an hour or so max), mark it as a Junior Job bug with the tag "[JJ]". I'm actively seeking out people who will take on junior jobs, too (and have had a few people express interest so far). Cheers, Tim |
|
From: Timothy G. <tim...@sy...> - 2005-07-12 02:44:22
|
Hey, Just to let you know, I've posted the announcement in the appropriate places and as I write this am running the update site shell script for the news to show up on the main page. Cheers, Tim |
|
From: Timothy G. <tim...@sy...> - 2005-07-07 21:52:24
|
Good news, It looks like the DNS changes for openfirst.org have propagated to most places; so, here is that announcement revised with the "better" domains, etc. I'd still like any comments/suggestions/what not before this thing gets sent out. I've also tweaked/added a few minor things to this version. Tim <h1>openFIRST Project Announces Pending Deadline for End of Support for Old Versions</h1> <i>The openFIRST project will be ending support for old versions of the openFIRST Portal System as of November 1st, 2005.</i> OPENFIRST, July 11th, 2005 -- In a move to reduce the burden on core developers caused by the requirement to maintain support for old versions of the openFIRST Portal System modules, the openFIRST Project has created a plan to phase out support for the oldest versions of the software. Every effort is being made to reduce the burden that the removal of support for old versions will have on those who use software from the project. This includes providing a large window of support between this announcement and the deadline, as well as the deadline having been chosen to be after we believe most FIRST teams will have resumed for the upcoming season. The modules scheduled to have their supported lives ended on November 1st, 2005 are: - Versions of the awards module prior to version 1.0.2 (released April 12th, 2004) - Versions of the base module prior to version 1.0.2 (released April 15th, 2004) - Versions of the emoticon module prior to version 1.0.2 (released April 12th, 2004) - Versions of the feedback module prior to version 1.0.2 (released April 15th, 2004) - Versions of the guestbook module prior to version 1.0.2 (released April 15th, 2004) - Versions of the logger module prior to version 1.0.2 (released April 15th, 2004) - Versions of the members module prior to version 1.0.2 (released April 15th, 2004) - Versions of the messenger module prior to version 1.0.1 (released April 15th, 2004) - Versions of the news module prior to version 1.0.1 (released April 15th, 2004) - Versions of the photogallery module prior to version 1.0.0 (released April 15th, 2004) - Versions of the search module prior to version 1.0.0 (released April 15th, 2004) It is suggested that users of older versions of any of these modules upgrade to the newest version listed on the "Latest File Releases" listing displayed at http://sourceforge.net/projects/openfirst . Support for those upgrading from old versions will be provided even after the November 1st end of support for the old version (since the support for the upgrade is part of the support for the newer version). Those who encounter troubles as a result of upgrading are encouraged to report these bugs to the openFIRST development team. Bug reporting may be done through the openFIRST Bugzilla server for issues with the main openFIRST distribution itself at http://bugzilla.openfirst.org/ or alternatively at the openFIRST Forum on Chief Delphi at http://www.chiefdelphi.com/forums/forumdisplay.php?f=108 Please do not e-mail those affiliated with the project directly to report bugs (doing so will just have your bug report added to the BZ server, and it frees up people's time to actually fix the bugs if you do that yourself). It is not recommended that users upgrade to the version of openFIRST in CVS as this version is currently in an unstable state and is undergoing significant deep rooted changes and restructuring which will render it incompatible with older versions of the software (an upgrade path will be provided at the time these new builds are released for external testing). At this time, please do not report bugs obvious found in CVS versions of the openFIRST software; non-obvious bugs, if discovered, should be reported through the openFIRST Bugzilla Server at http://bugzilla.openfirst.org/ . Comments/suggestions for future versions of the software, including listings of the software/web-services you would most like to see openFIRST integrate with are also welcome at the openFIRST Bugzilla Server. <h2>About the openFIRST Project</h2> openFIRST is an initiative to help FIRST Robotics web sites prosper by aiding their developers with design and construction of components for their team's web site. To do this, we have developed open-source components using PHP and ASP using the services of SourceForge.net. openFIRST was initially founded by David Di Biase and Tim Ginn in 2003 at the FIRST Canadian Regional, where both their teams competed. During the competition David and Tim discussed a potential project of this mass. The weeks following consisted of constant develop until the beginning of 2004 season, where they released their creation to the world. To this day the openFIRST development is striving to expand and create one of the largest most widely used open-source softwares for the FIRST competition's of North America. Their next goal is to expand the openFIRST source code and make it even more advanced and easy-to-use with the help of FIRST student programmers. More information about the openFIRST Project is available at http://www.openfirst.org/ <h2>Related Links</h2> openFIRST Project Homepage - http://www.openfirst.org/ openFIRST Bugzilla Server - http://bugzilla.openfirst.org/ openFIRST Forum on Chief Delphi Forums - http://www.chiefdelphi.com/forums/forumdisplay.php?f=108 openFIRST Source Forge Project Page - http://sourceforge.net/projects/openfirst/ Source Forge - http://www.sourceforge.net/ |
|
From: Tim G. <ti...@ti...> - 2005-07-06 03:13:49
|
Hey, This is my first draft of the announcement of the end of support for old openFIRST versions. I'd greatly appreciate any/all comments, etc. Since this is also the first post to the openfirst-devel list, to make it clear what the list is for, the list is intended to be a discussion list for the future direction of the openFIRST project and issues relating to development/FIRST. Also, I'm aware that the announcement doesn't mention Bugzilla, or use the openfirst.org address, this is deliberate because at the time of writing the domain name issue with openfirst.org has not been resolved yet (Dave's working on it) so this means that Bugzilla, the update server, www.openfirst.org, etc. are inaccessible. If this changes before the 11th (which is my tentative date for releasing the announcement, unless anyone has objections) then I'll switch those addresses to the ones that we'd prefer being used. Thanks, Tim <h1>openFIRST Project Announces Pending Deadline for End of Support for Old Versions</h1> <i>The openFIRST project will be ending support for old versions of the openFIRST Portal System as of November 1st, 2005.</i> OPENFIRST, July 11th, 2005 -- In a move to reduce the burden on core developers caused by the requirement to maintain support for old versions of the openFIRST Portal System modules, the openFIRST Project has created a plan to phase out support for the oldest versions of the software. Every effort is being made to reduce the burden that the removal of support for old versions will have on those who use software from the project. This includes providing a large window of support between this announcement and the deadline, as well as the deadline having been chosen to be after we believe most FIRST teams will have resumed for the upcoming season. The modules scheduled to have their supported lives ended on November 1st, 2005 are: - Versions of the awards module prior to version 1.0.2 (released April 12th, 2004) - Versions of the base module prior to version 1.0.2 (released April 15th, 2004) - Versions of the emoticon module prior to version 1.0.2 (released April 12th, 2004) - Versions of the feedback module prior to version 1.0.2 (released April 15th, 2004) - Versions of the guestbook module prior to version 1.0.2 (released April 15th, 2004) - Versions of the logger module prior to version 1.0.2 (released April 15th, 2004) - Versions of the members module prior to version 1.0.2 (released April 15th, 2004) - Versions of the messenger module prior to version 1.0.1 (released April 15th, 2004) - Versions of the news module prior to version 1.0.1 (released April 15th, 2004) - Versions of the photogallery module prior to version 1.0.0 (released April 15th, 2004) - Versions of the search module prior to version 1.0.0 (released April 15th, 2004) It is suggested that users of older versions of any of these modules upgrade to the newest version listed on the "Latest File Releases" listing displayed at http://sourceforge.net/projects/openfirst . Support for those upgrading from old versions will be provided even after the November 1st end of support for the old version (since the support for the upgrade is part of the support for the newer version). Those who encounter troubles as a result of upgrading are encouraged to report these bugs to the openFIRST development team. Bug reporting may be done through the openFIRST Forum on Chief Delphi at http://www.chiefdelphi.com/forums/forumdisplay.php?f=108 It is not recommended that users upgrade to the version of openFIRST in CVS as this version is currently in an unstable state and is undergoing significant deep rooted changes and restructuring which will render it incompatible with older versions of the software (an upgrade path will be provided at the time these new builds are released for external testing). At this time, please do not report bugs obvious found in CVS versions of the openFIRST software; non-obvious bugs, if discovered, should be reported through the openFIRST Forum on Chief Delphi at http://www.chiefdelphi.com/forums/forumdisplay.php?f=108 . Comments/suggestions for future versions of the software, including listings of the software/web-services you would most like to see openFIRST integrate with are welcome at the forum. <h2>About the openFIRST Project</h2> openFIRST is an initiative to help FIRST Robotics web sites prosper by aiding their developers with design and construction of components for their team's web site. To do this, we have developed open-source components using PHP and ASP using the services of SourceForge.net. openFIRST was initially founded by David Di Biase and Tim Ginn in 2003 at the FIRST Canadian Regional, where both their teams competed. During the competition David and Tim discussed a potential project of this mass. The weeks following consisted of constant develop until the beginning of 2004 season, where they released their creation to the world. To this day the openFIRST development is striving to expand and create one of the largest most widely used open-source softwares for the FIRST competition's of North America. Their next goal is to expand the openFIRST source code and make it even more advanced and easy-to-use with the help of FIRST student programmers. More information about the openFIRST Project is available at http://openfirst.sourceforge.net/ |
