As SQLA 2.0 seems to be available soon: I'd like to get to know the resume that has been taken from the results of Mark's (not too unambiguos) poll "What do you want done with the newsgroup data?". So, dear SQLA 2.0 developers, please let us know what kind of newsgroup import variant or archive site are you gonna present to us? (No, I won't ask why...) |
I know all of you are eager to learn about what we have been doing, so here is the current state of SQLA 2.0: We have spent the last many months porting OSQA to use SQL Anywhere as its back end database (the port actually only took an hour or so since SA's django driver "just worked" :-) and making enhancements to it to be able to better serve our needs. Some of the changes that we have made are:
We have been using a version of the revised OSQA software internally for quite a few months and believe it is ready to go live.... but we need to wait for Sybase IT to do some "magic" to make the site visible to the internet. Once SQLA 2.0 is accessible to the world we will load in the SQLA 1.0 data - i.e. this site's data - and then plan to have a period of time where the user community can try it out and give us feedback. Sometime during the beta period we will announce the date for the official switch-over to occur. On that date we will take a final dump of the SQLA 1.0 data and put it into the new SQLA 2.0 database. Note: Any data entered into the SQLA 2.0 site during the beta period will be lost. At some later time - within a few weeks to months of SQLA 2.0 going live - we plan to load the newsgroup data into SQLA 2.0 and all SQL Anywhere related newsgroups will be changed to be read-only.
Note that I have not given any dates to when any of this is going to happen because at this time we don't know the answer to that part of the process. This community (and the newsgroup community) will be notified when we know this information and everyone will be invited to participate in the new SQLA 2.0 Q&A forum. ... so stay tuned! So user "NNTP" is gonna have a whole WHACKLOAD of reputation points from day one, right? :) @Breck: No. User NNTP will not initially have any reputation because when we load the NNTP data "under the covers" there is no adjustment to the user reputation. Once the data is loaded and users choose to up-vote entries owned by NNTP then the user will gain rep points. @Mark: Great information, and fine that it is available now:) Just a few more questions (call me curious...): 1. Any plans to count upvotes on comments as rep points (cf. http://sqlanywhere-forum.sap.com/questions/1045)? 2. Any plans to associate particular NNTP users with SQLA users (cf. Breck's comment on http://sqlanywhere-forum.sap.com/questions/1185) - or a facility to take ownership of a imported NNTP question/comment? (Note: All regarded as "nice to have" features!) 1
@volker: 1) Nothing has been done so far to award rep points for upvoted comments. 2) This is difficult to do in a fair and equitable manner. Our current thought is to keep the data import process simple so we can get it done this century :-) I would in fact like to go live with the newsgroup data in SQLA 2.0 but, again, we are trying to make the switch to SQLA 2.0 as soon as we can and we want to make sure we get it right, so we are doing one step at a time. A subset of the newsgroup data may be put into SQLA 2.0 during the beta period so users can see what it is going to look like. @All: I should also note that in OSQA there is no limit on the length of a comment (actually, the size is admin-configurable but I see no reason to make the size limit fairly large). Also, comments can be formatted in the same way that questions and answers can be formatted - if you look under the covers at the OSQA DB schema you will see that questions, answers, and comments are all in the same table with each type of entry having a different "flag" to indicate what it is. @Mark: So you are motivating me for more that loooooong comments? - I'm not sure whether this is for the good of the community:) - Besides that, I agree that a fast launch is better than too much features. Your plans sound well-thought - thanks. @Mark: Will the current sqla.stackexchange.com users be ported to SQLA 2.0 or will everyone have to create a fresh login? @Reimer: According to http://sqlanywhere-forum.sap.com/questions/840, your login can be ported as long as you supply an email address:) 1
@Reimer: Volker has already answered your question, but I wanted to add that once SQLA 2.0 is accessible to the internet we will need to do some additional testing (and possibly some tweaks) so that the users get moved over smoothly. In the meantime, make sure that your SQLA user account has a valid email address so that it can be used to reset your SQLA 2.0 account's password. This may not needed but I think it is better to have a fallback solution than none at all :-) More comments hidden
|
To answer my particular question, I dare to quote from Mark's elaborate explanation:
That's the Migrate to SQLA (Bulk Load) approach, it seems. |