Skip to main content

Cookie settings

We use cookies to ensure the basic functionalities of the website and to enhance your online experience. You can configure and accept the use of the cookies, and modify your consent options, at any time.

Essential

Preferences

Analytics and statistics

Marketing

Help

Participatory processes are time-limited activities designed to involve the community in specific decisions, consultations, or initiatives.

They are commonly used for:

  • Collecting ideas and feedback

  • Discussing and improving proposals

  • Running consultations or decision-making processes

  • Voting on defined topics within a set timeframe

Each participatory process has a clear start and end date and may include different phases such as idea collection, discussion, and voting.

Participatory processes allow community members to actively contribute to decisions and shape the direction of Scriptony Foundation’s projects and initiatives.

Process phases

This phase announces the first public technical release of Outcome (v0.1.0). It presents the scope, included features, known limitations, and intended use of this early version. The goal is to set clear expectations, explain what v0.1.0 is and is not, and provide a stable reference point for the community before release.

Comments are enabled to allow clarification questions and general observations, but this phase does not collect feature requests or decisions.

This phase documents the active development period leading up to the v0.1.0 release. It provides links to source code repositories, development documentation, and technical notes published during implementation.

This phase is informational only. Discussion and comments are disabled to keep the content focused, stable, and easy to reference.

This phase invites early feedback after the scope of v0.1.0 has been published. Participants may share reactions, usability impressions, and high-level suggestions based on their understanding or early testing of the release.

Feedback collected here is advisory and non-binding. It may inform documentation improvements and future development priorities, but it does not alter the defined scope of v0.1.0.

This phase outlines the direction after the v0.1.0 release. It summarizes lessons learned, highlights confirmed next milestones, and presents the roadmap toward later versions (including v0.2.x and v1.0.0).

This phase closes the v0.1.0 process and provides continuity into future planning processes.

Outcome v0.1.0 – First Public Release

Outcome v0.1.0 — First Public Release (Planned: June)

Start date / End date

25 Jan 2026 / 17 Jun 2026

Current phase

This process belongs to

Outcome Project Development

About this process

First public technical release of Outcome, focusing on core project structure, file format, and basic writing workflow. This process presents the scope, limitations, and next steps of version v0.1.0 and gathers early community feedback.

This participatory process documents and communicates the first public release of Outcome (v0.1.0).

The goal of v0.1.0 is to establish the technical foundation of the Outcome platform: a native project file format, cross-platform desktop application, and the core writing model (projects, works, blocks, and elements). This version is intentionally limited in scope and functionality and is not intended for production or real-time writing use.

Through this process, the Scriptony Foundation shares:

  • What is included in v0.1.0

  • What is intentionally excluded

  • Known limitations

  • The development and documentation approach

  • The planned direction after v0.1.0

Community members are invited to review, understand, and provide feedback, helping to inform priorities for future versions (v0.2.x and v1.0.0), while maintaining realistic expectations about the maturity of this early release.

We are preparing the first public technical release of Outcome (v0.1.0).

This release focuses on laying the groundwork: a native binary project file, cross-platform desktop support, a basic writing model, and the first user interface design. It is an early milestone intended for exploration, testing, and feedback — not yet for long-term or production writing.

This process presents the scope and limitations of v0.1.0 and outlines the direction for future development. We invite the community to follow the progress, review the documentation, and share constructive feedback to help shape the next phases of Outcome.

Related processes

1
Media picture: Outcome Roadmap Feedback & Priorities

Outcome Roadmap Feedback & Priorities

1. 📢 Roadmap Presentation
What is decided
The scope and content of Outcome v0.1.0 are already defined and implemented by the project team. Feedback collected through this process may influence:
Who participates
Outcome users and early adopters, Writers and creatives interested in the project, Developers and contributors, Members of the Scriptony community, Anyone interested in open, transparent software development
How is it decided
This process does not include voting or binding decisions. Input is collected through comments and discussions. The Outcome project team reviews the feedback and incorporates it where appropriate, balancing technical feasibility, project goals, and long-term stability.
Scope
Desktop application development, File formats and data structures, Writing workflow foundations, Documentation and transparency, Early community feedback
Organization Area
Software Development, Creative Writing Tools, Open-source Infrastructure
Promoter group
Scriptony Foundation – Outcome Project Team

Related assemblies

1

Outcome Project Assembly
Reference: SCR-PART-2026-02-12

Confirm

Please log in

The password is too short.