Thanks for the feedback, Chris and Martin. What I'm going to do is keep CGRAN down until we have some sort of plan/resolution and use it as a form of motivation. Every time I've managed to resurrect CGRAN from the dead, I just leave it go and forget about it for some time again. I think that the down time might help us come to a conclusion sooner.
Several people have e-mailed me about access to the repository. I was able to get the repo back up, and it should be anonymously readable here: https://www.cgran.org/svn/projects To address Chris' thoughts, I've always felt CGRAN was useful in two aspects: 1) To find useful and up-to-date projects (albeit rare), and 2) To find more historical projects that highlight the capabilities of GNU Radio and SDRs and to resurrect and/or build from them. I know the latter has been a killer, but I've found multiple times that people came to CGRAN to dig up old code and build something new from it. But if anything, these two types of projects need to be clearly marked and separated. Academically, I know that students are very willing to take brutally dead code and use pieces of it for projects. Maintenance over time is simply just difficult. Once projects are complete, many people move on but GNU Radio keeps on chugging. I know that I lost time to maintain my projects. Pybombs could at least guide the user to get correct versions, let them know there is a mismatch, etc. It can also provide the link from a project to where the actual code and repository are. I think that pybomb entries can point to github locations, right? On Mon, Sep 29, 2014 at 2:07 PM, Martin Braun <martin.br...@ettus.com> wrote: > This is something that comes up at our dev calls (and other dev meetings) > regularly, and we really need to address it sooner rather than later. > > George, if the support burden is getting to much, we can surely fix a > short-term solution by migrating stuff to some temporary location (let's > take this specific discussion offline, though). > > In the future, we'd like to have something that ties in nicely with > Pybombs, and also uses the gits. How exactly, that's something we need to > decide, and any community input on this is appreciated. > > Cheers, > M > > > On 29.09.2014 11:01, George Nychis wrote: > >> The machine that runs CGRAN down in some basement somewhere at Carnegie >> Mellon has hit some issues again. Given that I'm no longer at the >> university, these issues are becoming harder for me to address. At this >> point, it's probably best for CGRAN to "move on" as we've all been in >> discussion about over time. >> >> What I can do if everyone still finds CGRAN useful is: >> >> 1. Provide a more reliable host and machine for it >> 2. Update it to be more useful to the community (e.g., more towards >> git) >> >> It still gets a lot of hits (~16,000 a month) and every time it goes >> down people hunt me down and ask when it's coming back up. So it seems >> as though the community still uses it. >> >> I can update it with Pybombs or Gitlib or whatever people feel is >> appropriate. It can be more of a portal page even, without a repository >> if most people just use Github now anyway. Do people still like it is a >> standalone service, or is it better to just "roll it in" to the GNU >> Radio webpage somewhere now? I want to do whatever the community finds >> is most useful. >> >> Thanks! >> George >> >> >> _______________________________________________ >> Discuss-gnuradio mailing list >> Discuss-gnuradio@gnu.org >> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio >> >> > > _______________________________________________ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio >
_______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
