Menu
▾
▴
radioactive-developers — The RadioActive Project Developer Mailing List
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(30) |
Sep
(12) |
Oct
(11) |
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2006 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(6) |
Dec
(7) |
| 2007 |
Jan
(1) |
Feb
(1) |
Mar
(2) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(3) |
Aug
(3) |
Sep
(9) |
Oct
(8) |
Nov
(20) |
Dec
(35) |
| 2009 |
Jan
(10) |
Feb
(14) |
Mar
(14) |
Apr
(20) |
May
(32) |
Jun
(17) |
Jul
(29) |
Aug
(6) |
Sep
|
Oct
|
Nov
|
Dec
(7) |
| 2010 |
Jan
(9) |
Feb
(6) |
Mar
(3) |
Apr
(2) |
May
(1) |
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Somen M. <som...@ra...> - 2004-09-08 03:20:56
|
Hi guys, The middleware requirements are finally up on our site. Check them out here: http://developers.radioactivehq.org/docs.html We hope the design will be posted up tomorrow! If you guys get the chance, read over the docs and give us some feedback =) Also our Development Environment doc is constantly being updated, so check that out as well. Thanks, Somen |
|
From: Somen M. <som...@ra...> - 2004-09-04 23:13:28
|
Hi guys, I have placed 2 documents online, the prototype EPC-IS requirements and the prototype EPC-IS design document. Please look them over. I know they are simple, but probably all we need for the prototype. You can find them here: http://developers.radioactivehq.org/docs.html Look over the sections, and we will soon be making a list of tasks/modules people can program. In the meantime, take a look at the development environment document there to setup all your cvs and other stuff. Thanks! Somen |
|
From: Somen M. <som...@ra...> - 2004-08-31 03:00:57
|
Hi Guys, Its time for some development! I think its time for us to develop quick and dirty prototypes of our software. Initially, we want to develop prototypes of the EPC-IS and the middleware. I have just added a quick requirements document at our development site (http://developers.radioactivehq.org/docs.html) for the EPC-IS. Initially, this software will be a exactly what its supposed to be, a rapid prototype which will allow everyone to learn a bit more about what the software will do. Shaun and I plan to have short design and requirements docs by the end of this week. We'd like to know who wants to participate directly in the creation/coding of the prototypes. I think it's a very important first step in the success of our project. So for all the developers and people who want to develop, please email me and we'll start to organize tasks based on our upcoming design. All the coding will be done in Java for any of you that forgot =). Thanks, Somen |
|
From: Somen M. <som...@ra...> - 2004-08-31 03:00:57
|
Hi Guys, Its time for some development! I think its time for us to develop quick and dirty prototypes of our software. Initially, we want to develop prototypes of the EPC-IS and the middleware. I have just added a quick requirements document at our development site (http://developers.radioactivehq.org/docs.html) for the EPC-IS. Initially, this software will be a exactly what its supposed to be, a rapid prototype which will allow everyone to learn a bit more about what the software will do. Shaun and I plan to have short design and requirements docs by the end of this week. We'd like to know who wants to participate directly in the creation/coding of the prototypes. I think it's a very important first step in the success of our project. So for all the developers and people who want to develop, please email me and we'll start to organize tasks based on our upcoming design. All the coding will be done in Java for any of you that forgot =). Thanks, Somen |
|
From: Somen M. <som...@ra...> - 2004-08-30 01:53:05
|
Hi John, I don't think XP is at all useful for what we are doing. I think our current process is similar to RUP but a slimmed down version. One thing about RUP that I like is that they have business requirements. Loosely, our process is: Architecture and Requirements Design/prototype Development (testing) Release Support/fixes/upgrades All the while, developing modules simultaneously that will be integrated.. testing is done soon after and while a module is being written. What do you think? I might have over simplified things, but I think it is what our project needs. Somen -----Original Message----- From: rad...@li... [mailto:rad...@li...] On Behalf Of John Davidson Sent: Sunday, August 29, 2004 4:29 AM To: rad...@li... Cc: rad...@li... Subject: [Radioactive-design] Process, anyone? Hi all, Are we using any development process? XP? RUP? From my experience XP doesn't work well with a distributed team like ours and much our requirements is based on fixed standards, and RUP is too heavy for our purpose. I'm thinking we should combine the positive attributes of an agile process like XP w/ RUP, this way we retain the ability to adapt quickly to requirements changes, yet have control over the architecture and overall status of the project. What do y'all think? For those unfamiliar with either process mentioned, here're some links -- XP http://www.extremeprogramming.org http://www.martinfowler.com/articles/newMethodology.html RUP http://www.ibm.com/software/awdtools/rup/ jd _________________________________________________________________ Don't just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/ ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click _______________________________________________ Radioactive-design mailing list Rad...@li... https://lists.sourceforge.net/lists/listinfo/radioactive-design |
|
From: John D. <jd0...@ho...> - 2004-08-29 08:28:44
|
Hi all, Are we using any development process? XP? RUP? From my experience XP doesn't work well with a distributed team like ours and much our requirements is based on fixed standards, and RUP is too heavy for our purpose. I'm thinking we should combine the positive attributes of an agile process like XP w/ RUP, this way we retain the ability to adapt quickly to requirements changes, yet have control over the architecture and overall status of the project. What do y'all think? For those unfamiliar with either process mentioned, here're some links -- XP http://www.extremeprogramming.org http://www.martinfowler.com/articles/newMethodology.html RUP http://www.ibm.com/software/awdtools/rup/ jd _________________________________________________________________ Dont just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/ |
|
From: Somen M. <som...@ra...> - 2004-08-29 02:03:22
|
Hi Guys, We put up a new web site just for the RA team. It's located here: http://developers.radioactivehq.org/ Basically, this website will be the team's internal hub and will provide information and resources. We will post how-to documents, tasks, timelines, roles, etc. Check it out and email me if you have any suggestions. Thanks, Somen |
|
From: Shaun R. <sha...@ra...> - 2004-08-28 14:51:09
|
Hi John, I agree that we don't want to get too code centric just yet. My thoughts in starting that thread in the developers list was to just get some barinstorming going from as many people as possible. Then, the design team can take these starter ideas from the thread and expand on them for the requirements document. Most of the requirements and design conversation will be going through the design list only. Thanks, Shaun |
|
From: John D. <jd0...@ho...> - 2004-08-27 20:48:59
|
Guys, Shouldn't the requirement and design threads be on the "design" list, and not the "developers" list just yet? If we get too code-centric, we run the risk of not thinking ideas through before pounding out code. jd _________________________________________________________________ FREE pop-up blocking with the new MSN Toolbar get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ |
|
From: Shaun R. <sha...@ra...> - 2004-08-25 03:44:35
|
1. Provide data warehousing for EPC ids and associated extra metta data (time stamps etc.) |
|
From: Shaun R. <sha...@ra...> - 2004-08-25 03:41:36
|
Hi all, I think that our best plan will be to use a template for our EPC-IS requirements document. Somen suggested this one: http://www2.ics.hawaii.edu/~johnson/413/lectures/5.2.html and it looks pretty good to me. We are not going to follow it exactly how it is written, but close. Any of the object oriented items, I want to push more into design and architecture. The requirements should just describe what we want to do, not how we are going to do it. I put the shell into Open Office as a template. I would like to fill in any of it that I can and then throw it into cvs. I was hoping that we could all try and think of a few functional requirement for the EPC-IS server, based on your personal experience with RFID, and research done on the EPC-IS and related technology. Take a look at section 3 of the template online. I think an easy way to do this is to just get a mailing list thread going, with replies. Then we can expand on them when everyone likes the list. I will send out an email to the whole development team and then we can streamline the list, and work towards providing better descriptions. Cheers, Shaun |
|
From: Shaun R. <sha...@ra...> - 2004-08-23 02:44:37
|
Hey, So, now that we have some technical decision made, we have to get started on documentation. We are going to have a requirements document. This will be a little different than usual requirements documents, in that many of the requirements are in EPC and Auto-Id documentation already. These are not the most up to date documentation, but they are great for a start. I will be making a template in Open Office for these requirements. I know everyone is eager to get going, and so am I. Once the template is done I can divided it into sections to get filled out and I think we will be through it quickly. I got bumped from some of the source forge mailing lists over the weekend. I am not sure why, but noticed Source Forge to be a bit buggy. If you did not receive any emails all weekend, I would suggest applying to the lists again. Also, I noticed some "ToDos" in the mail archives. I would like to get some people responsible for certain items. There will be something set up off the home page soon where you can go and browse the task list, and volunteer. Thanks, Shaun |
|
From: <rp...@te...> - 2004-08-22 21:53:26
|
confirm 323167 --------------------------------------------- This message was sent using Endymion MailMan. http://www.endymion.com/products/mailman/ |
|
From: Pawel L. <lo...@lo...> - 2004-08-22 17:02:41
|
Guys, Since you've probably read my post in Design group, I will not be repeating introductions. I'm glad dev started with QA and I'm sorta sorry to see them being divided. But then "what do I know about testing" ;-)? We, dev people, should be responsible for unit testing. I would say to do the unit tests before the actual code (XP style) but this is not good idea for *now*, at the beginning. Let's do something without stiff requirements, for fun, to quickly deliver working version 0.1. We will start introducing unit testing then. No matter what, let's build and test our stuff before check-in against latest code base. We will create official policy to that effect when we have a week of broken builds. All other official testing belongs to QA. We should help them automate testing though. Now to dev stuff that has not been discussed yet: - Seeing Java selected as the tool, how do we do builds? JDK + Ant? - What are the 3rd party packages selected for dev, incl. versions? Axis? What else? - Do we have short instructions on how to setup a dev environment? - Do we have short instructions on how checkout code? - Do we have short instructions on how to perform a build? - Do we have short instructions on how to perform some basic integration tests? - Do we have a checkin policy? Does code submitted need to be verified by some people before checking in? - We will start worrying about branching when we get to some stable release. Agreed? - What tool do we use for dev execution tracking? Tasks from SF.net OK for everyone? - Seen some code posted to the list. Please add it to CVS in tests branch, so it can be easily built and accessed by all. (I will repeat the IRC request here) Please make sure that if a decision is about to be made, a post to list is made so all can see it and react. Thanks, Pawel |
|
From: Shaun R. <sha...@ra...> - 2004-08-20 02:10:35
|
Both! I have been doing some talking with different members of the team and it looks like we are going to tackle both the EPC-IS and the middleware (savant) at the same time. We feel that the design team is strong enough and there are enough developers to accomplish this. It will be a large task for sure, but there are many benefits to this including: - code reuse (my favourite). - easier to have the two standardized, easier to support. - will be better to release the two at the same time, will give us a better reputation. - overall a more rapid development process. If anyone has any questions or major concerns, please let Somen or I know, or even better hop into the channel #radioactive on irc.freenode.net so we can talk about it. Cheers, Shaun |
|
From: Michael M. <mi...@ne...> - 2004-08-19 05:02:05
|
This is a simply piece of Java that shows how to query ONS, what the format of an EPC is and how to parse the output from ONS.... -MM |
|
From: Michael M. <mi...@ne...> - 2004-08-19 04:59:35
|
On Wed, 2004-08-18 at 21:11, Ramana Murthy wrote: > <snip> This is a test too... -MM |
|
From: Ramana M. <ra...@ap...> - 2004-08-19 01:12:10
|
|
From: Somen M. <som...@ra...> - 2004-08-19 00:48:02
|
Hello, Harvinder has pointed me to a good article that people might find interesting. It's about application frameworks. http://www.acmqueue.com/modules.php?name=Content&pa=showpage&pid=176 Thanks, Somen |
|
From: Shaun R. <sha...@ra...> - 2004-08-15 21:46:09
|
Hello, I have started one more mailing list. This will pertain to specific issues around quality assurance. This list is open for everyone, not just people who are interested in doing quality work. I created a separate list for quality so we can keep things organized, and distribute information and discussions in a modular way. If you are interested in subscribing to this list, please go here: https://sourceforge.net/mail/?group_id=115899 Thanks, Shaun |
|
From: Somen M. <som...@ra...> - 2004-08-13 22:33:36
|
Hello Everyone, We have put together a great design team. The design team consists of 7 members. Here is a list of the 7 people. Somen Mondal Shaun Ricci Venky Nakhate Sapan Shah Ismail Nalwala Julian Canagaratnam Randall Brown I think we have put together an amazing design team with a vast amount of experience and knowledge. I will try to update the bios online, the user list and the bios are already outdated. The design team will communicate via another mailing list (rad...@li...). For all the design team members and whoever is interested, please sign up here: https://sourceforge.net/mail/?group_id=115899 Initial design discussions will begin through the mailing list and hopefully we will have a meeting on Sunday in our IRC channel (#radioactive on the freenode irc network). Thanks, Somen |
|
From: Shaun R. <sha...@ra...> - 2004-08-13 03:56:44
|
Sorry if you get this twice, I used the wrong list the first time. Ok, So it looks like we have some people interested in quality. This is great news, I think it is a very important part of the project. So far Ismail, Randy and Greg have said they can help out. Also Woody mentioned he could contribute some security knowledge to the group. I am just gathering all of the info from the early brainstorming emails flying around. I will put these into a document over the weekend that will include a list of tasks we can have discussions about. If you have any ideas in the meantime, hop on the IRC channel to see if anyone is around or shoot out an email. Cheers, Shaun |
|
From: Somen M. <som...@ra...> - 2004-08-13 00:05:27
|
Hi Guys, In response to Woody's comments, I think Woody has summed up our goals perfectly. I have added a few things. If anyone wants to add something, please do :) "One consistent Suite of applications" "an EPC-IS, Savant, ONS, Discovery service" "Open, Free and kick-ass Quality" "Certified by EPC" "be able to compete and surpass any commercial product" "be as common to RFID as Apache is to the internet" "be the premier EPC network software solution as well as the only open source solution." I think once we brainstorm a couple more and listen to everyone's suggestions, I will add a "Goal" section on the website. Thanks, Somen -----Original Message----- From: rad...@li... [mailto:rad...@li...] On Behalf Of Dieter Houthooft Sent: Thursday, August 12, 2004 10:37 AM To: Rad...@li... Subject: [Radioactive-developers] Re: QA Before we get to design and coding, shouldn`t the goals of what we want to achieve be defined somewhere. I don`t mean "Create an EPC Information System". Some ideas: "One consistent Suite of applications" "an EPC-IS, Savant, ONS" "Open, Free and kick-ass Quality" "Certified by EPC" Anyway about the QA: I volunteer to do some security assurance. It should be a part of QA as I am a strong believer in the fact that security results in quality. woody. |
|
From: Somen M. <som...@ra...> - 2004-08-13 00:05:27
|
Hi Guys, In response to Woody's comments, I think Woody has summed up our goals perfectly. I have added a few things. If anyone wants to add something, please do :) "One consistent Suite of applications" "an EPC-IS, Savant, ONS, Discovery service" "Open, Free and kick-ass Quality" "Certified by EPC" "be able to compete and surpass any commercial product" "be as common to RFID as Apache is to the internet" "be the premier EPC network software solution as well as the only open source solution." I think once we brainstorm a couple more and listen to everyone's suggestions, I will add a "Goal" section on the website. Thanks, Somen -----Original Message----- From: rad...@li... [mailto:rad...@li...] On Behalf Of Dieter Houthooft Sent: Thursday, August 12, 2004 10:37 AM To: Rad...@li... Subject: [Radioactive-developers] Re: QA Before we get to design and coding, shouldn`t the goals of what we want to achieve be defined somewhere. I don`t mean "Create an EPC Information System". Some ideas: "One consistent Suite of applications" "an EPC-IS, Savant, ONS" "Open, Free and kick-ass Quality" "Certified by EPC" Anyway about the QA: I volunteer to do some security assurance. It should be a part of QA as I am a strong believer in the fact that security results in quality. woody. |
|
From: Ismail N. <ena...@ya...> - 2004-08-12 14:41:29
|
Reposting to the Sourceforge dev list ------------ Theres various things that will have to be determined once any real development artificat comes alive. However to address your email: You are right usually coding standards are just norms that developers chose to pick and have nothing specific to the project. Coding standards usually address policies that developers will follow e.g. naming conventions, documentation conventions, error handling conventions and format and indentation conventions. Usually they are language specific for historical reasons. I can provide some coding standards and guidelines for java and oo development tommorow :) Your description of the various test scenarios is very accurate however we may have to adapt a little in our situation. Clearly in our present situation roles may not be as clear as testers and developers and having a system test team. I have a feeling a lot of us will be doing a various kinds of testing. The most important thing about the tests is not who does them rather when they get done. Unit tests are best done during development. They are a suite of tests that have to be kept updated and run frequently using some sort of framework or tool. Regression tests will also be some sort of automated tests like you mentioned that get done whenever a build is completed to ensure that functionality is not lost. System test will have to be done on a particular build to test the whole whether a defect or functionality works as part of the compelete integrated system thanks -Ismail --- Randall Brown <ran...@gm...> wrote: > All, > Yes we definitely need someone to write a coding standard or at least > we will have to agree to use one that is already written(I am sure > there some that are freely available). Am I wrong in thinking that a > coding standard really would not have any specific info about the > radioactive project in it? To me it just defines the format of the > code. > > Just to open up a discussion I will let you know how the company I > work for handles testing. > > Unit Testing - Unit testing is preformed by the developers involved > in > writing the new feature or fixing the bug. The developers are > responsible for defining the set of test they are to run. > > System Testing - Tests the functionality of the new feature or bug > fix > within the context of the whole system. This testing is handled by a > dedicated team of testers. The system test people are responsible for > defining the complete set of tests for a each feature of the > software. > > Regression Testing - Tests to make sure that nothing has been broken > during the new development. One way to do this testing is to automate > it. The company I work for has a set of pearl scripts and test > programs that are run on every new version of our software. These > scripts produce a pass or fail for a set of tests. The benefits of > using testing scripts is once the script is written it take very > little human time to preform the regression testing. Of course that > every time a new feature is added to the software new test cases will > have to be added to the script. The system test group is responsible > for the maintenance of the scripts. Of course we will probably have > to > have some regression testing that is not preformed by scripts, but I > think we should try to minimize the amount of human time spent > regression testing while still maintaining a high standard of care. > > Thanks, > Randy > > On Wed, 11 Aug 2004 21:55:15 -0400, Shaun Ricci > <sha...@ra...> wrote: > > > > Hi Everyone, > > > > I was wondering if anyone was interested in doing quality work. I > think > > this is a huge job, and probably could > > use more than one person. Things that you will do are manage unit > > testing, regression testing, releases, write coding standards etc. > > Probably a lot of communicating to the other developers as well. > You will > > get a very good knowledge of the entire piece of software. If you > are > > interested, let me know. > > > > Cheers, > > Shaun > > > ===== Ismail Nalwala email:ena...@ya... |
226 messages has been excluded from this view by a project administrator.
