openmw.org

Branching from the 0.34.0 planning thread, here's my proposition:

1. Get a good understanding of what features are left before we are feature complete on the OpenMW side.
2. Do a news post write-up on these features, and announce that once they are finished, we can enter a Beta phase. More on that below.
3. Share this news post around to try to rally development for the last handful of features we need.

In response to Zini:

Zini wrote:Low activity: We actually have quite a lot going on on the OpenCS side of things and we are still getting plenty of bug fixes. it is to be expected that things are slowing down on the OpenMW side of features. But of course the fact that scrawl is currently busy with other stuff contributes to this perception. I think he mentioned that he would be able to go full speed again at the beginning of December. I don't think we have a problem here that makes immediate action necessary.

Bug fixes are obviously needed before 1.0, but my view (which may be incorrect, please correct me if I am wrong) is that we only have a handful of features left to implement, and if we can clean those up, we can announce we are in Beta, and focus only on bug fixes and optimizations.

Zini wrote:FPS optimisation: Too broad for an issue. The batching task will improve performance (though probably not much for vanilla Morrowind content) and then there is OGRE 2.0.

I definitely understand this is a broad issue. But can we add it as a task on the tracker to be closed once these other issues are handled? We are all aware that it needs to be done, but it'd be nice to see it on the to-do list, and even nicer to be able to close it once we hit a certain threshold.

Zini wrote:Non-Morrowind features: Not in favour of that. For most of these we would need a fully functional OpenCS first anyway.

Which of these http://bugs.openmw.org/projects/openmw/ ... &group_by= are non-Morrowind features? That link filters only 0.34 and 1.0 version-tagged issues, so it should not include anything extra?

The point of a Beta is this: it lets people know that we are feature complete, and it's a point where we formally call for testing. We've already been doing that, but a lot of people walk away when they see that this or that feature is not implemented. We're basically feature complete at this point, but if we can formally announce that we are feature complete, people will be more inclined to test. It also sets a milestone goal for us for getting everything implemented. It's like the "1.0" of development, after which only bug fixes and optimization happen. I think it'd be a good goal for the project, and gives us good direction as we try to slog through the last bit of work to get things done.

I think this is a really good idea, and I'm strongly advocating it! I can definitely carry the banner for this effort, but Zini I need your blessing. I don't want to be trying to run off and do something with development planning that you're not on board with. Basically right now I am just asking permission to organize development this way, and to be able to write up a post to that effect, and to post it. And if I do a write-up on the remaining features, I want to make sure I've got a definitive list...

Bug fixes are obviously needed before 1.0, but my view (which may be incorrect, please correct me if I am wrong) is that we only have a handful of features left to implement, and if we can clean those up, we can announce we are in Beta, and focus only on bug fixes and optimizations.

That is correct. But I think at least one of these features won't be doable pre OGRE-2.0.

I definitely understand this is a broad issue. But can we add it as a task on the tracker to be closed once these other issues are handled?

Fine. Feel free to do that.

Which of these http://bugs.openmw.org/projects/openmw/ ... &group_by= are non-Morrowind features? That link filters only 0.34 and 1.0 version-tagged issues, so it should not include anything extra?

None. Well, except for one OpenCS task that has been sneaking into this list. My comment about non-Morrowind-features was directed at something else.

Zini wrote:My comment about non-Morrowind-features was directed at something else.

Roger, makes sense.

Do you mind if I run with this? I'll definitely post my write-up here for corrections/comments/approval before posting it in news. Also it'll probably take me a few days, as tomorrow is a big holiday here.

Raevol, maybe we should contact past OpenMW developers and just ask if they could help with the final push to beta status. There are folks like jhooks and werdanith. We want to be respectful. A message to former developers could be an update that the project is finally close to beta, a thank you for their past contributions, and an ask if they have any time to come back to the project even if only temporarily. I imagine some of the folks still lurk and check in on the project. These folks contributed at some point to the project, so they probably do want to see it completed. Here's a link to the contributors. https://www.openhub.net/p/openmw/contributors

Finally, here's a list of sites to think about for new recruitment.

Ogre3d: Most long time community members there are likely familiar with OpenMW, but people might be persuaded to chip in
Gamedev.net: There is a jobs page
Moddb/Indiedb: There are forums as well news post. If you do a news post you should use a gif image as moving images on the front page attract much more attention.
Freegamer@blogspot: It's a small community, but it's focused entirely on open source games. I wrote an article a few years ago. It would be nice to have an update.
All manner of Elder Scrolls fan sites: Just hope you get lucky and a fan with programming ability sees

Excellent, all good points. I'll definitely post on those/contact those people.

Two things to consider:

1) We have no beginner tasks, which is highly discouraging to people who have never touched OpenMW before to jump into.

2) OpeMW-CS needs more love right now, it needs parity with OpenMW so that when people starting using it, it puts more pressure on OpenMW to fix the remaining issues.

If you want to reach out to more people and bring more devs in, go for it, but don't fall into the trap that more people == faster development time. Please read:
https://en.wikipedia.org/wiki/The_Mythical_Man-Month

adding manpower to a late software project makes it later

+1

Since my name was mentioned, personally I'd love to get involved again, but I just don't have the time right now.
Hopefully, in a few months, after I have resolved some issues I can get my hands dirty again.
Great job to all the contributors btw, your work is inspiring.

raevol wrote:

Zini wrote:My comment about non-Morrowind-features was directed at something else.

Roger, makes sense.

Do you mind if I run with this? I'll definitely post my write-up here for corrections/comments/approval before posting it in news. Also it'll probably take me a few days, as tomorrow is a big holiday here.

Sure.

I kinda need some filling up for a new newspost. When the most exciting thing has been an irate modder crying about being a victim, I'm eager to add something of substance.