Ask.wireshark.org runs on OSQA, which is no longer maintained or supported. Over time features such as external authentication and spam filtering have degraded. It depends on an old, EOLed version of Django. It also fills an important role in supporting Wireshark by providing a quick and easy way for users and developers to get answers.
I would like to migrate to a different platform before OSQA degrades even further. I will post some options for a future home below. Please add votes, comments, and other options as needed.
UPDATE March 31: I just ran across this discussion on Ask Fedora. They're having issues maintaining ASKBOT, but Evgeny Fadeev (ASKBOT's main developer) seems to want to help. One person suggested moving to Stack Exchange, but other comments there roughly echo the SE comments below.
UPDATE October 29: Ask.wireshark.org was migrated to Askbot. The old OSQA content was moved to osqa-ask.wireshark.org. New account registration has been disabled on osqa-ask and other updates will probably be disabled at some point.
asked 29 Mar '17, 13:33
Gerald Combs ♦♦
edited 01 Nov '17, 08:44
showing 5 of 9 show 4 more comments
We should continue to self-host using ASKBOT, which is an active fork of OSQA.
This is probably our best bet if we want to try to keep the current site content.
answered 29 Mar '17, 13:34
Gerald Combs ♦♦
I think this is the best option probably, because it lets us keep the current content. Going for Stack Exchange could be a way to continue as well, but I usually prefer self hosting because it allows more control.
(29 Mar '17, 14:26) Jasper ♦♦
Note that "keep the current site content" is speculative at this point. Askbot doesn't have any sort of OSQA import tool, but there is a script available that might make a good starting poing.
(30 Mar '17, 09:31) Gerald Combs ♦♦
Will ASKBOT allow people to add pcaps? Do other Q&A software packages?
(30 Mar '17, 14:45) SYN-bit ♦♦
Good point by @SYN-bit. The second biggest issue for me is being able to upload JPG/PNG files, that are scaled correctly even in comments (which OSQA doesn't do well, but I guess that's mostly a CSS issue). Maybe we can get the guys from Cloudshark help us with integrating something like a PCAP upload/embbed method :-)
(30 Mar '17, 14:59) Jasper ♦♦
It looks like you can allow arbitrary file extensions via ASKBOT_ALLOWED_UPLOAD_FILE_TYPES. A dedicated capture repository would be pretty useful, however.
(30 Mar '17, 15:37) Gerald Combs ♦♦
Can we configure ASKBOT to, when somebody tries to upload an image, ask "Is this a screenshot of a capture? If you can, could you please upload the raw capture file, instead?" That alone would be a major win.
(31 Mar '17, 18:25) Guy Harris ♦♦
This upcoming Sunday, October 29 I'm going to try migrating to Askbot, including the following:
(27 Oct '17, 16:27) Gerald Combs ♦♦
showing 5 of 7 show 2 more comments
We should continue to self-host using some other Q&A software.
Please reply with your preferred software.
answered 29 Mar '17, 13:34
Gerald Combs ♦♦
edited 29 Mar '17, 14:17
Looking at the demo's on this list they all look the same, so it will be backend features which will make the difference. Probably the most relevant would be content retention.
(30 Mar '17, 04:28) Jaap ♦
Make a site yourselves. It cannot be too hard. That way migration of current content is irrelevant. Just use the current format with your own front end. So you're keeping all the data now in the same format + same database just add to it. Loads of geniuses on here helping out folks, surely a few of you know PHP, MySQL etc. :)
(05 Apr '17, 12:07) King0r
I wouldn't underestimate the effort to code such a site. It's more than just a "question, answer and comment" kind of thing. You need registration, password recovery, user management (e.g. banning SPAMmers), moderation, karma handling, up/down voting, tag handling, searching, and all of that has to be secure. So it's not just a Weekend with some PHP and a MySQL DB ;-)
(15 Apr '17, 04:56) Jasper ♦♦
Are we open to commercial solutions or are only free solutions being considered? I ask because http://www.osqa.net redirects to http://www.dzonesoftware.com/products/open-source-question-answer-software, and DZone Software offers AnswerHub, its enterprise version of OSQA. I don't know the cost, so it might be prohibitively expensive, but if it's reasonably-priced, then it might be the easiest way to migrate from OSQA. And who knows, they might offer a discount to us, perhaps even at
(05 Jul '17, 08:47) cmaynard ♦♦
In a former life (job) I worked at a fairly large forum company. One of the things I dealt with fairly regularly was migration from various - often proprietary or uncommon - forum software to more standard stuff (SMF, vBulletin, etc). Obviously the back-end to logins varied pretty strongly in many cases.
Commonly one thing that could be done would be to determine the hashing mechanism for the old forum, import the old login hashes/salts/etc into an additional table/column in the DB of the new forum, and amend the login function to accept the old hashed value. The first time a user logged in to the new forum, it would populate the new password fields and then NULL the old ones. After a certain time the old hashes were simply dumped for MIA users who never logged into the new system.
Alternately, you could just blank all the logins and require users to "reset" their passwords for the first login. It's less convenient for users but involves less work/modifications to back-end scripts and may be considered somewhat more secure depending on how old logins were stored.
I'd be happy to lend a hand with this for you guys, as well.
answered 27 Oct '17, 10:23
We should upgrade to Mailman 3 and use HyperKitty. We're currently managing the Wireshark mailing lists using Mailman 2 and archiving them using MHonArc. HyperKitty is a modern archiver that allows voting, but it appears to be missing other features that make Q&A sites useful, such as the ability to accept a particular answer.
answered 26 Apr '17, 14:02
Gerald Combs ♦♦
I do like the mailing list more so than a Q&A. IMHO, people don't really get it and use the Q&A as a forum anyway. So, a forum style site would not be so bad.
(26 Apr '17, 15:55) Jaap ♦
Although I like the Q&A style, migrating to HyperKitty would be okay for me.
Is a data migration from OSQA to Mailman3/HyperKitty feasible?
(27 Apr '17, 04:11) Uli
I think going back to a mail list format for general Q&A would be a retrograde step. Fine for the user and dev mailing lists.
While I do spend a lot of time reformatting and reorganising things on Ask, this does allow us to keep the questions, answers and comments vaguely coherent. A mail list doesn't provide such facilities so degenerates into a mess of mixed questions and answers.
(27 Apr '17, 05:51) grahamb ♦
@grahamb: What about a Forum then? Slightly different from a Q&A, not being rigid in answers and comments (where most of the confusion comes from IMHO).
(27 Apr '17, 07:54) Jaap ♦
The problem with a forum is always that the good answer is on page 7 of 15, and not clearly visible as "best answer", so it takes much longer to find what someone is looking for.
I have no idea how often people end up on ask.wireshark.org and are just happy to see the best match right away - we shouldn't assume that everyone visiting the site is actively posting. My guess is the "googled -> found the answer" visitor numbers are much much higher than interactive users. For those, a forum is much less useful.
(27 Apr '17, 08:52) Jasper ♦♦
Again, I think forums are a retrograde step, whenever I search for things in them they just seem to be a cesspit of out of date stuff and meandering uselessness.
I guess like the Ask site they do need some admin TLC.
I'm just sold on the Q&A style, it's a pity SO\SE aren't very nice places sometimes.
(27 Apr '17, 08:55) grahamb ♦
@jasper and @grahamb I totally agree. I love the Q&A style with all possibilities. And for that kind what like people are asking questions and get one or more answers wether a mailing list nor a forum are the right tools for that. Maybe something like a ticketing system would be able to do such a job...?
(27 Apr '17, 09:17) Christian_R
showing 5 of 7 show 2 more comments
We should Migrate to Stack Exchange.
answered 29 Mar '17, 13:35
Gerald Combs ♦♦
I'm personally not in favor of migrating to Stack Exchange. I somewhat recently began checking for Wireshark-related questions being posted there and here are some of my observations:
It seems to me that most Wireshark-related questions are being asked on Stack Overflow. But in general Stack Overflow is supposed to be about programming-related questions and most Wireshark-related questions tend to be about Wireshark usage, not Wireshark programming. This sometimes results in moderators downvoting, closing and/or deleting questions, with some moderators suggesting to repost the question on Super User, Server Fault, or elsewhere.
While one could argue that the moderators are justified in their actions, the end result is that users don't end up getting any help for their questions, nor do they tend to repost their question elsewhere. Like it or not, Stack Overflow is where many users are going for help - when they're not coming here that is - at least as far as I can tell.
Some moderators also tend to be way too picky, in my opinion, about how questions are asked or answered. Here, I think we try to help everyone as much as possible, even if a question isn't entirely clear. (We'll ask questions in comments to help elicit more information). But there, moderators just downvote or close questions, which I think isn't particularly nice to the users.
Sometimes specific answers are hard to give due to the lack of detail in the question. Rather than leave a question completely unanswered, I will sometimes try to provide some answer that will hopefully help someone at least get started. But this can sometimes backfire with picky moderators, as it did for me with this question.
In any case, I'm in favor of continuing to self-host, but whether that should be with ASKBOT or some other software, I don't know.
(30 Mar '17, 10:13) cmaynard ♦♦
Good point that if we don't self-host, we're likely to lose whatever moderation capabilities we currently have.
(30 Mar '17, 10:17) grahamb ♦
Thanks for your insight in how StackEchange moderation works. I always enjoyed the open and welcoming character of the Wireshark community and feel proud to be part of it. It does not sound like the same atmosphere can be maintained on there (maybe not even on any non-self-hosted platform). So I wold vote for the most conveniently managed self-hosted platform with all the features that we would like (it would be very very nice if posting pcaps will be possible on the new platform!)
(30 Mar '17, 14:44) SYN-bit ♦♦
I second @cmaynard, I think we have a good moderation team at this site, with patient and fair behavior - the other large sites are sometimes quite harsh when moderating questions. At our own site we can help even if people are straying somewhat from the main topic without someone deciding it's off-topic and shutting it down.
(30 Mar '17, 15:05) Jasper ♦♦
Stackoverflow moderators strike again, placing this question "on hold".
Besides the moderator problem, moving to StackExchange means Wireshark questions will be split among StackOverflow, SuperUser, ServerFault, etc. It's quite a pain to have to check several different sites instead of dealing with all Wireshark-related questions in a single forum such as this.
(31 Mar '17, 07:37) cmaynard ♦♦
To be clear, I was wondering if we should propose our own site on Area 51 which would presumably have our own set of moderators.
I definitely agree with Chris' assessment of overzealous moderation on the main SE sites.
(31 Mar '17, 11:21) Gerald Combs ♦♦
I think we really should take care that we don't destroy the really great feeling of this community. And I think that this is one of a few sites where people get really worth full answers. I can't say that about stackexchange, at least what I have seen there.
(31 Mar '17, 11:23) Christian_R
Going through Area 51 seems completely ridiculous. If you want to migrate with an Q&A like this one, you should go on a fast track. I mean contacting StackExchange and asking them in what way you could move this Q&A as it is, keeping all the 10k+ questions and answers as well as all the users (if they want) and your own moderators. I'm not sure how this looks on the legal and personal privacy side, but technically speaking starting all over seems so silly! You as a community gathered round a piece of software of this import should have no less to say on StackExchange than Canonical, who stand behind Ubuntu and its AskUbuntu SE site.
(26 May '17, 17:12) tomasz
Emphasis on "your own moderators", otherwise, if I ever have to deal with an SE moderator whining about a more correct but less detailed answer, I'll end up once again deleting my SE account (the last time that happened, I burned all my SE accounts to the ground and didn't look back - life's too short to deal with that nonsense).
(26 May '17, 20:33) Guy Harris ♦♦
@cmaynard I think that a lot of your experience with moderation at current Stack Exchange (SE) sites is not really relevant to an option of creating a new SE site. I am using SE sites for several years already and I find them extremely useful. In the comments above I see some misunderstanding and I would like to try to correct the assumptions here:
(19 Jul '17, 09:42) pabouk
showing 5 of 10 show 5 more comments
Good news: I managed to get Askbot up and running at https://shiny-new-ask.wireshark.org/questions/ . Bad news: I've been trying to export OSQA's data in a form that can be imported by Askbot but haven't had any luck so far.
Migration update: I've managed to generate XML and JSON dumps of the OSQA data using OSQA's built-in tools. Importing the XML dump fails immediately. Importing the JSON succeeds for users and tags but fails for questions, answers, votes, etc.
Given the difficulties with the migration so far I'm tempted to it to user accounts with a reputation above a certain threshold (e.g. 50 or 100). This would avoid punishing users who have dedicated their time to answering questions and let us drop the several thousand bot-generated accounts we currently have. Unfortunately this would mean dropping the current database of questions and answers.
... and there's already spam at https://shiny-new-ask.wireshark.org/questions/! I was going to delete the spam questions, but attempting to login using Wireshark Q&A credentials doesn't appear to be working.
Unfortunately this would mean dropping the current database of questions and answers. Presumably when you wrote "dropping", you meant "not migrated"? In other words, in the worst case, the current OSQA database would remain as a reference that we could either point to or copy information from, rather than completely disappearing?
Is it possible that with some processing the OSQA export would import into AskBot, or are the schemas just too different?
@Chris I didn't configure any of the antispam options after yesterday's test import. The import script I'm using assumes we're using LDAP authentication and doesn't migrate passwords. I had to go through the password recovery process for my account.
I suppose we could try to preserve the current environment by setting up a separate read-only instance, e.g. at crusty-old-ask.wireshark.org, but I'd rather let someone else have the title of "Earth's last OSQA administrator".
@Graham The data migration path is long and winding: OSQA DB → OSQA Django ORM → XML or JSON export → Askbot Django ORM → Askbot DB. The XML and JSON exports were both failing until I removed some bot-created tags. The OSQA JSON export consumes a large amount of RAM and takes a long time. The Askbot XML import consumes a larger amount of RAM, takes a longer amount of time, and then fails. The Askbot JSON import manages to migrate users but then fails because the OSQA JSON export is missing "forum.node" models. Given that Askbot is a fork of OSQA, migrating data has been surprisingly difficult.
Would it make sense to acquire provisional consulting service by askbot.com to get the data migrated?
Maybe askbot could be disabled for now to stop the spam? Manually deleting them all is getting boring.
What about discourse. It's from the founders of Stackoverflow, works similar, and is open source you can host yourself.
no matter what I write I always get the message that it is Spam