Zardoz wrote:Apologies for further depressing you, Aloys, but I think it is telling that Cyan's latest outreach to the community was to allow a small set of fanz access to the MOULagain server to drum up IC chatter prior to the MOULagain launch. You can tell who many of them are by perusing the KI list in this MOUL forum post - look for the four digit KI numbers. And so Cyan is apparently not shy about reaching out to the community, just not this one - which seems absurd because that part of the community that is good at IC chatter seems the least important to open-source's chances of long run success.
Aloys wrote:Now MOUL starts again, but that's not what was expected or even needed, and that's aggravating and demotivating to me.
I do understand that MOUL is supposed to be a first step toward the eventual release of the codebase, but we're not getting actual news regarding that. We've offered our help several times, and haven't really heard any concerte reply (positive or negative) other than 'hear hear'. Maybe I'm just running out of energy. We're taking baby steps, at best, when we don't really see any real obstacles to progression. Cyan keep mentionning that they need to plug out 3rd party code and replace it or document the missing parts, if that's the only obstacle that's something we can take care of, we have told them, they won't answer.
Paradox wrote:I see some great irony here... Cyan wants to put fan Ages on their MOUL server before releasing any source.
None of our Ages are compatible with MOUL.
None of our plugins are compatible with MOUL until Cyan releases theirs, or Blender 2.6 is released and PyPRP gets a major rewrite.
It's a perfect Catch-22 situation.
GPNMilano wrote:I do understand that MOUL is supposed to be a first step toward the eventual release of the codebase, but we're not getting actual news regarding that. We've offered our help several times, and haven't really heard any concerte reply (positive or negative) other than 'hear hear'. Maybe I'm just running out of energy. We're taking baby steps, at best, when we don't really see any real obstacles to progression. Cyan keep mentionning that they need to plug out 3rd party code and replace it or document the missing parts, if that's the only obstacle that's something we can take care of, we have told them, they won't answer.
Answer me this. How on earth do you plan on pulling out 3d party code from a plugin, when you yourself are not liscensed to see that 3d party code? I really would like to know the answer to this as this is the exact reason why the GoW and anyone else whose not employeed by Cyan, can't pull out said code. You can't pull out something you're not allowed to see in the first place. Hence why Cyan must do this.
GPNMilano wrote:Aloys wrote:Now MOUL starts again, but that's not what was expected or even needed, and that's aggravating and demotivating to me.
First I don't see how this wasn't expected. Rand in just about every communication he's had with the media, and with the community told us that they wanted to start their own server first to bring the community together. And that after that they would open-source, but sort of be the keeper of it. I'm paraphrasing but really that's pretty much what he's been saying right along. What people selectively hear should not be blamed on the speaker but those listening to the words.
GPNMilano wrote:I do understand that MOUL is supposed to be a first step toward the eventual release of the codebase, but we're not getting actual news regarding that. We've offered our help several times, and haven't really heard any concerte reply (positive or negative) other than 'hear hear'. Maybe I'm just running out of energy. We're taking baby steps, at best, when we don't really see any real obstacles to progression. Cyan keep mentionning that they need to plug out 3rd party code and replace it or document the missing parts, if that's the only obstacle that's something we can take care of, we have told them, they won't answer.
Answer me this. How on earth do you plan on pulling out 3d party code from a plugin, when you yourself are not liscensed to see that 3d party code? I really would like to know the answer to this as this is the exact reason why the GoW and anyone else whose not employeed by Cyan, can't pull out said code. You can't pull out something you're not allowed to see in the first place. Hence why Cyan must do this.
ddb174 wrote:They haven't been saying this all along, this was more recent. Indeed, at the time, several people pointed out that this might be backpeddling: opening a server to keep people happy, and keep people from complaining about open-source. After all, most mystonline.com users could care less about open-source so long as they have a shard to play on.
Chogon wrote:+ MORE servers will be restarted. These will be run by Cyan and run on machines that are either owned or leased by Cyan. The software and game assets will be as it was when Myst Online was shutdown on the GameTap servers. However, all the accounts and avatars from the GameTap servers will not be available and will have to be re-created.
It's actually pretty straightforward: Cyan simply hires them as (very-low-paidcontractors. It's been done before.
Users browsing this forum: No registered users and 20 guests