Integrate LibreSign with Nextcloud Task Processing

オープン
#9,056 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
php

調査の方向性

Start by locating LibreSign’s existing backend service boundaries, Nextcloud integration points, and test conventions; the issue does not name specific files or entry points. Read the Nextcloud public Task Processing APIs and the AI foundation’s capability and actor/context contracts before defining the reusable boundary. Done means the listed capability, lifecycle, ownership, security, and deterministic test requirements are met without provider-specific configuration.

索引モデルが issue の本文から書いたものです。

説明

backend php

Goal

Implement the reusable LibreSign backend integration with the public Nextcloud Task Processing APIs using the capability contract defined by the AI foundation.

Scope

Create the backend service boundary responsible for:

  • discovering available task types for the relevant user/context;
  • mapping Nextcloud task types to LibreSign semantic AI capabilities;
  • scheduling/running supported tasks;
  • retrieving results;
  • handling failures/cancellation;
  • exposing only the capability information needed by LibreSign consumers;
  • keeping provider-specific details out of product code unless exposed for neutral informational purposes.

Use the supported Nextcloud public APIs. Do not detect AI support by checking whether a particular provider or Assistant app is installed.

Capability surface

Frontend/application consumers should work with semantic LibreSign capabilities rather than raw provider names.

The representation should be able to distinguish individual features; avoid one global aiEnabled flag that hides whether summary, chat, generation or another operation is actually available.

Do not expose capabilities that do not yet have a LibreSign consumer.

Task ownership and actor context

Use the actor/context rules established by the foundation contract.

Task ownership, result retrieval and authorization must prevent one actor from seeing or operating another actor's tasks.

Public/external signer handling must follow the agreed policy/actor contract rather than a frontend shortcut.

Security

  • Minimize data sent to Task Processing.
  • Do not include provider credentials in LibreSign.
  • Validate task output at the consuming LibreSign boundary.
  • Fail closed when capability/authorization state cannot be resolved safely.
  • Do not convert technical capability into permission.
  • Preserve cancellation/error semantics without exposing internal provider details unnecessarily.

Tests

Use the deterministic Task Processing test provider to cover:

  • capability available and unavailable;
  • feature-specific capability mapping;
  • successful synchronous/asynchronous flow as applicable;
  • controlled failure;
  • cancellation;
  • actor/task ownership;
  • invalid output path;
  • policy denial remains authoritative even when technical capability exists.

Documentation

Developer-facing architecture documentation should explain the reusable Task Processing boundary only where it is needed for maintainers. End-user/provider setup belongs to product documentation tasks, not implementation notes.

Done when

  • LibreSign uses public Nextcloud Task Processing APIs through a reusable backend boundary.
  • Semantic LibreSign capabilities are exposed without provider coupling.
  • Task lifecycle/error handling follows the agreed contract.
  • Actor/task ownership is enforced.
  • Deterministic integration tests cover capability and failure paths.
  • No provider/model configuration stack is introduced in LibreSign.
主要言語
PHP
スター
844
フォーク
176
平均マージ
14時間 3分
マージ済み PR(30日)
344

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

LibreSign/libresign のほかの issue

LibreSign/libresign の issue をすべて見る

似ている issue

PHP の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。