Zandronum

Wartorn / Blzut3:
-Fix validation : done
-Set up SFTP for www-data account : done
-Get that main site design down ASAP [TIHan]
-Get the wiki operational. : NEVERMIND I'M AN IDIOT
-SSL?

Dark-Assassin:
-Separate thread for this.

Developers:
-Get the fork going : Done, awaiting source commit

Everyone:
-Come up with a name. : done
--Register domain for said name : you're on it
-Figure out how to migrate community
--Core server hosts (IRC, forum, game)
--External server hosts (NJ, IDDQD, Armada, Grandvoid, Oblacek, Node-3, IFOC, more?)
--Everyone else


Add more as necessary.

Wartorn wrote: -SSL?

SSL would be great, even if the just use a self signed certificate.

I just noticed that the "forum contains unread posts" icons don't update for me after reading all new posts.

It should now. There was a setting I enabled to make sure it updates when all posts in there are read.
The option is still kind of beta, so not completely sure if it will work all the time or not. It's not a plugin by the way.

Still doesn't work for me. Even if I click the icon to mark all as read it doesn't work. It looks read right after clicking, but if I reload the page, the forum is marked as having new posts again.

Hmm, I'll look around to see if this is fixable.

Edit:
Ok, I think I have found a patch, but PostgueSQL errors strike again. Dammit, i'm sick of these errors only happening with PostgueSQL and not MySQL.
I have personally checked the syntax and it's right. I even run the queries manually in a test area of my MySQL database and it doesn't give an error.
I have also checked plugins and patches on my own forums and I still get 0 errors.

Postgre isn't MySQL. I think it's better to develop not under the assumption everything works as is between the two.

-=Dark-Assassin=- wrote:I even run the queries manually in a test area of my MySQL database and it doesn't give an error.
I have also checked plugins and patches on my own forums and I still get 0 errors.

Why don't you install a PostgreSQL database in your test area?

Outside of schema defintions the main difference in syntax between MySQL and PostgreSQL is PostgreSQL uses standards compliant quote behavior. So where MySQL uses accent marks you have to use double quotes IIRC.

Honestly if a plugin isn't working with PostgreSQL that probably means they aren't using the DBAL correctly and likely have security vulnerabilities. :P

Nevermind I'm an idiot, the wiki is on Konar's server :X

Current status on things:

Name:
Already been decided as "Zandronum" by Torr. Domain's registered as you can probably tell.
Main Site:
We need an update on this from TIHan and Joel (His designer friend who's doing us a neato looking design), but we kinda established an icon (The favicon) that isn't out of line with what was already proposed to Joel so that's good.
Forum:
A bit buggy, but works. Is continuously being worked on and may not be rock-solid stable when we release.
Port:
The code is ready and public. We need to release 98e as a "1.0" of sorts and figure out something else for stability.
Master Server:
Reform talks have to be taken a bit more seriously but at this time the concern is getting it propagated domain-wise, which is as ready as it ever will be.
-Hosts: We have to talk with all of our cluster hosts and make sure that it's smooth. This has yet to be done but can be started on soon now that the name has been secured.
-Events: At some point we'll have to get the staff members of these respective events (FNF, SNS) onto this board so they can continue to plan accordingly.
IRC:
The domains are ready. We can move whenever.
Wiki:
The wiki is off-server and still active, but I think it might need some cleaning up. Tiger will clean it up when he's free.

Etc:
-There's a problem that we have to discuss the stock content included with Skulltag (skulltag_data.pk3) and how we're going to deal with this, but for the most part I think what was discussed is to release it as a separate pack that's along the lines of "Backwards Compatibility" pack to maintain compatibility with the wads designed for it and will not be maintained any further. The problem deals with the fact that we don't want to auto-load the content any more to create a better standard for ZDoom compatibility (Remember how Carnevil broke the gravity on the sphere pickups?) and a fair amount of the content is "dirty" (i.e. ripped from sources without permission). It's unknown if this includes the content within /skins and /announcers (Although the latter less likely)
--Similarly, we're considering including SpaceDM9 as an official modification included with Zandronum which best represents the technological capacity of the port and expanding off it, much like the stock content did. That's all in talks with Essel and the respective parties.
-There's also the issue with cross-community advertisement, to get the word out about the fork and make sure everyone migrates properly. I have no idea how we're going to do this yet.
--Additionally, there's the issue of how we're going to try and get our -current- users onto the new fork- Since that's kind of a big deal. Currently, Carnevil is our cockblock in that regard in that he controls Skulltag.com and we have no way around that.
-I swear I'm forgetting something here. I'll expand on this when I remember.

So, we have the name, the domain and a forum. When do we link the public to http://zandronum.com/forum? The Skulltag forum is down for about a week now and IMHO we should direct the public to the new forum as soon as possible.

I'd say it's safe to do it as soon as the binary package is ready and the master is propagated domain-wise. We should also get in touch with Bond to revise IDE as necessary to get people over.

Binary as in public stable release? Since 98e/1.0 is not fully ready, this is not going to happen soon. We can try to make a new beta build where all the stuff is renamed and skulltag_data is not auto loaded anymore though.

Yeah, I think that'd be the safest bet. We can release 1.0 as an experimental RC that doesn't autoload skulltag_data and release a version of 98d for stability. I think personally starting off with the RC as the recommended build first would help amplify testing, since this is all "new" in a sense.

It's worth reiterating, though, if SpaceDM9 is to be adapted into an official mapset, that it's not actually compatible with 98d because correct behavior in it depends on some bugfixes that have been made since then.

So, look out for that.

esselfortium wrote: It's worth reiterating, though, if SpaceDM9 is to be adapted into an official mapset, that it's not actually compatible with 98d because correct behavior in it depends on some bugfixes that have been made since then.

So, look out for that.

Said RC would contain all changes up to now, so I'd believe the said changes would be in.

We should really get this up though, if that's all we need to make Zandronum public.. is there anything we need to go through before we make the RC?

Wartorn wrote: Yeah, I think that'd be the safest bet. We can release 1.0 as an experimental RC that doesn't autoload skulltag_data and release a version of 98d for stability.

I don't think that we should release a rebranded 98d. That takes quite some effort and we don't gain much from it.

Dusk wrote: We should really get this up though, if that's all we need to make Zandronum public.. is there anything we need to go through before we make the RC?

I don't see why we can't make Zandronum public without an RC. IMHO the current code is not tested well enough to label it as RC, but as I said earlier releasing a first beta build soon is no problem. I'll just have to take care of the autoloading of skulltag_data.pk3 (make it listed as loaded wad on the server. if it is loaded, etc.).

is it ok to leave 'staff discussion' and 'development' forums visible to guests/normal users?

Edward-san wrote: is it ok to leave 'staff discussion' and 'development' forums visible to guests/normal users?

This is for the eyes of the public. We have our private place though.

Torr Samaho wrote: I don't see why we can't make Zandronum public without an RC. IMHO the current code is not tested well enough to label it as RC, but as I said earlier releasing a first beta build soon is no problem. I'll just have to take care of the autoloading of skulltag_data.pk3 (make it listed as loaded wad on the server. if it is loaded, etc.).

Well, you're free to try and release what you need to. We just want a binary to offer somewhere when we launch.

Edward-san wrote: is it ok to leave 'staff discussion' and 'development' forums visible to guests/normal users?

Please give me a reason to close up Development. As for Staff, it's fine if our regular users see how we operate. I want them to.