Wiki pre-release?

[JWPlatt]

I just want to check in and make sure no one is being held on up anything generally, but specifically with the temporary "Squee" wiki. This is what we'll use to do all wiki work until Announcement. Has everyone who needs access gotten in? If not, please let me know.

Remember, you should see the "Squee" OpenUru.org icon with the "X" over it where the wiki logo usually is. If you don't, you're in the wrong place.

Once you get past the mailbox, that is.

[JWPlatt]

Ok, I added a few things tonight on the Squee wiki:

http://squee.openuru.org/index.php?title=Main_Page
http://squee.openuru.org/index.php?titl ... com_Engine
http://squee.openuru.org/index.php?titl ... _And_Tools

You'll see I've started my announcement spiel and stated unilateral things only hinted at in my ToDo list. The Announcement part is what I intend to post or distribute elsewhere. I haven't really had much guidance on development plans, and some other things - other than reading and getting through life this many years. Some of you might have different personal preferences on how to say things; what to say, or not to say. I'm just doing what, in my experience, I think is right. Please, please feel free to jump in there, discuss, and make the text better. Although I wrote it, I don't feel I own any of the text - it's for all of us to pick apart, rewrite, whatever.

As always, make sure you are on the correct wiki: Squee.

[Mac_Fife]

In terms of overall "structure", I'm not sure about the third page in that set I feel that for consistency, we should always serve "source code" from repos and provide download links for binaries, and the associated wiki description pages should direct you accordingly. Just my feeling though.

[rarified]

I feel that for consistency, we should always serve "source code" from repos and provide download links for binaries, and the associated wiki description pages should direct you accordingly.

I think I agree with this. We can (with both Fisheye and Jenkins) have links that assemble a source bundle from the current tip revision of the repo, and enable downloading a single archive. But that should be considered secondary.

One item on the second page; the header probably should read "CyanWorlds.com Engine..." not "Cyan<space>Worlds.com Engine...".

_R

[JWPlatt]

Mark would like to have a pre-repo zip of the source bundle available for download. i.e., as originally released to OpenUru.org directly from Cyan. In fact, Cyan's original zip does not exactly resemble either my initial push or subsequent empty folder corrections because of Mercurial's omission of empty folders and my placeholder.txt files. Does this change your thoughts? We can certainly document the availabilty of current source bundle downloads in the manner you suggest. Could one of you add that text to the page?

[Mac_Fife]

Mark would like to have a pre-repo zip of the source bundle available for download. i.e., as originally released to OpenUru.org directly from Cyan.

Yeah, I can see the sense in that, to be sure that everyone gets a chance at the "original" material, and avoid any perception that we may have interfered with it. However, the organization of that Sources and Tools page was all over the place, so I've moved things about.

[Mac_Fife]

We've only had the Squee wiki for two weeks, but it's already feeling strange for me that we'll soon see it go. I guess I've been in and out of there quite a bit in past fortnight .

[JWPlatt]

Maybe I'll leave the install in a read-only state. People are going to see and try the username/password shown on page 2 of this thread. Wouldn't hurt to let folks see how things were managed. It and the live install will both point to the Squee wiki database.

Make sure to export your Mini work prior.

[a'moaca']

The external link syntax allowing you to specify what the link is called does not work on this wiki?

http://meta.wikimedia.org/wiki/Help:URL ... rnal_links

That is, if I say "[http://external-link/to/big/hairy/url information]" I get literally that ([http://external-link/to/big/hairy/url information]), and not information.

[Mac_Fife]

That works OK as far as I can tell on the browsers I use...
On http://squee.openuru.org/index.php?titl ... s_and_SDKs I have this in the first (unboxed) paragraph:

Code: Select all

The CyanWorlds.com Engine (CWE) is released under the [http://www.gnu.org/licenses/gpl.html GPLv3 Open Source license] but 

Which is rendering as:
The CyanWorlds.com Engine (CWE) is released under the GPLv3 Open Source license but
...with the little box/arrow external link symbol just after the word "license".