On Thu, May 15, 2008 at 12:39 PM, <[EMAIL PROTECTED]> wrote: > Personally, I think that all posting access to the list should be > removed. Yes, nobody should be able to post messages to the list. > Instead, posting would be via a blog website, and the blog messages > would then be echoed into various NANOG mailing lists based on > which blog category was being used. Subscribers could then construct > their own personal NANOG list by subscribing to the blog categories > that they are interested in. Threading would work very well since > on a blog, you have to identify the thread before you post. > > There are literally hundreds of blogging software packages out > there, many of them blog construction tool kits with dozens > of plugins available. Given the fact that the list runs on Mailman > which is written in Python, I suggest that folks have a look at > this list of Python blogging software: > http://wiki.python.org/moin/PythonBlogSoftware > My sense is that PyBlosxom and the Django-based stuff are the > more popular. It's too late to do this as a Summer Of Code project > but the same principal could be applied, i.e. find a university > student, put them together with a technical mentor, and give them > access to the server needed to test and trial the blog. > > If the SC isn't interested in testing this right now, then I suggest > that the new MLC give serious consideration to taking this on as > a project. > > --Michael Dillon
I'll say it.... You, M Dillon, are out of touch with what NANOG is. NANOG is not a mailinglist software development company/group, nor should it be developing it's own custom one-off of off-the-shelf products. -Jim P. _______________________________________________ Nanog-futures mailing list [email protected] http://mailman.nanog.org/mailman/listinfo/nanog-futures
