Audio Asylum Thread Printer

Get a view of an entire thread on one page

FAQ / News / Events

Asylum Feedback/Support

OK, some more issues....

68.34.58.110

[ Follow Ups ] [ Post Followup ] [ Thread: Display All Email Next ] [ Asylum Feedback/Support ]

In Reply to: Engineers WANTED for open source app! posted by anevsky on August 28, 2003 at 14:47:23:

Adam,
I think if you want to stick to an RUP approach lets stay with the first set of work products, what is the Vision, who are the stake holders, and what is this thing supposed to accomplish. I think I have a hunch but not exactly certain.
If you wanted to put something together, I would really like to see something where people can contribute to a centralized repository, where one would store all information related to a specific issue including and not limited to liner notes, actual images of the cover, reviews, etc. This way the client would only need to store information relevant to the actual copy one owns (condition, date purchased, etc) and reference the information stored in the repository.
I could imagine somebody like muzikmike could both contribute and benefit.
If you want to open a project on sourceforge I could contribute a few hours of my time. I have access to good GUI people and also a competent J2EE architect. I would prefer Java for portability. The larger issue is the actual hosting of the database which can get pretty enormous.
Dee
;-D

Follow Ups:

Re: OK, some more issues.... - anevsky 21:48:29 08/28/03 (0)
Like any application, I too would suggest a formal architecture phase, though possibly not so intense as if someone were paying for the software. The great thing about a bunch of developers who are vinylphiles doing this is that WE are the stakeholders. We might not make the best HCI choices, but we aren't designing middle-ware, and out "business" rules and objects are very clear.
So, in essence, I agree with you. I think the minimum amount of work would be a requirements document and use cases. A 4+1 approach, or a full RUP strikes me as overkill.
I'm a little more of an XP guy than a RUP guy as well. I like lots of small releases compared to giant milestones. Using a minimal set of requirements, we could craft an application which makes the application very useful and yet maintain extensibility for growth. I've been on projects where this was the goal - and some suffered from becoming too extensible (thus making many small deliveries impossible) while others delivered often but too much code was scrapped for each release because it wasn't flexible and extensible enough.
How, then, should we get this moving?
First, I need to know who would be involved, at what level, and how much. So, if you want to be involved - let me know.
After that, we'll move on to source forge or a mailing list to draft up some key documents.
I want this to happen, I really do.
Thanks everyone for the replies,
Adam
Re: OK, some more issues.... - Rod M 18:56:06 08/28/03 (2)
> > The larger issue is the actual hosting of the database which can get pretty enormous.
Yes, indeed! I was thinking also about the idea of storing cover scans and the like. Our db server is a couple years old and the primary server is about 3. I've been thinking that we might upgrade the db server and roll things down. I'm not sure how big this could get, but a raid array of four or five 36 or 73GB drives ought to do for a while.
- This could be a service only available to contributors :-) - Penguin 05:04:56 08/29/03 (1)
  would make contributing more desirable. Or a plain a plain subscription say $5/mo would help out with hosting.
  dee
  ;-D
  - Druther have the Yoyo ;-) (nt) - Ivan303 05:59:06 08/29/03 (0)
    nt

This post is made possible by the generous support of people like you and our sponsors:

You can not post to an archived thread.