Hi all,
I dip in and out of the forums looking for interesting projects. Often I'l want to review the 'final' revision of a design but this is often buried in hundreds of replies in tens of pages. Even when I find what I'm looking for I'm not sure why it's been modified the way it has, it's history and how well tested it is.
First off I wonder if anyone else feels the same? If so, and there's enough support, i suggest diyAudio has a separate section to the website with a list of all the projects that happen to be in the forums. Each project has its own page with documentation and revision history. What I'm thinking of is very similar to open cores.org which, if you don't know, list open source FPGA IP cores with some documentation.
Thanks
I dip in and out of the forums looking for interesting projects. Often I'l want to review the 'final' revision of a design but this is often buried in hundreds of replies in tens of pages. Even when I find what I'm looking for I'm not sure why it's been modified the way it has, it's history and how well tested it is.
First off I wonder if anyone else feels the same? If so, and there's enough support, i suggest diyAudio has a separate section to the website with a list of all the projects that happen to be in the forums. Each project has its own page with documentation and revision history. What I'm thinking of is very similar to open cores.org which, if you don't know, list open source FPGA IP cores with some documentation.
Thanks
This is a public discussion forum, not a collaborative design forum. People who wish to can already arrange proper change control on their design; many folk on here will have no experience of doing such things. The most you can expect is that a few designs may end up with the sort of documented history which you desire.
My experience (in industrial software development) is that it can be difficult to get even professional programmers to properly document changes. If a note is required they will write a note, but it will often omit key details.
My experience (in industrial software development) is that it can be difficult to get even professional programmers to properly document changes. If a note is required they will write a note, but it will often omit key details.
I absolutely agree with you Boscoe. I started diyAudio to make it easy for people to make DIY audio projects. For newbies especially, wading through thousands of pages of threads is not the ideal path to sparking the DIY fire and encouraging further learning. The wiki was envisaged to foster this kind of single location of information for projects, but due to the software being terrible and human nature (people get enthusiastic then lose interest) it's never had its day in the sun.
For what it's worth, I feel it's the 2nd most important thing for me to do with diyAudio - to make an absolutely fantastic projects area that solves all these problems. I have had my focus unfortunately dragged elsewhere over the last 5 years but I've been taking action over the last few months to give me the time to get back to focusing on diyAudio.
The most important thing here is of course the discussion community. And so I agree with DF96 about that 100%. The discussions are the heart of soul of what this community has become. I also agree with DF96 about the problems of "human nature" in getting people to properly document changes. This would extend to taking nice photos of builds, covering small details, basically anything that might be helpful to others but that the author themselves doesn't want to or isn't capable of doing.
I have a whole bunch of ideas of how to make inroads to solving these problems, and I'll be posting more about them soon. There's no point starting a projects section and having it fall apart because it ends up having old and outdated information defeating the purpose. There needs to be good two way information flow between discussions and the projects.
For what it's worth, I feel it's the 2nd most important thing for me to do with diyAudio - to make an absolutely fantastic projects area that solves all these problems. I have had my focus unfortunately dragged elsewhere over the last 5 years but I've been taking action over the last few months to give me the time to get back to focusing on diyAudio.
The most important thing here is of course the discussion community. And so I agree with DF96 about that 100%. The discussions are the heart of soul of what this community has become. I also agree with DF96 about the problems of "human nature" in getting people to properly document changes. This would extend to taking nice photos of builds, covering small details, basically anything that might be helpful to others but that the author themselves doesn't want to or isn't capable of doing.
I have a whole bunch of ideas of how to make inroads to solving these problems, and I'll be posting more about them soon. There's no point starting a projects section and having it fall apart because it ends up having old and outdated information defeating the purpose. There needs to be good two way information flow between discussions and the projects.
It's good to hear that - I think DF96 is a bit too pessimistic.
i would like to say i would help but I don't have a lot of time for these things. Imagine, though, how powerful something like that could be. A full list and reference of just about anything audio related.
i would like to say i would help but I don't have a lot of time for these things. Imagine, though, how powerful something like that could be. A full list and reference of just about anything audio related.
- Status
- Not open for further replies.