LibreSign / LibreSign/libresign
Batch Signature Management with Collectives Integration
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 818
- Forks
- 146
- Avg merge
- 11h 31m
- Merged PRs (30d)
- 326
Description
LibreSign currently requires adding participants individually. We need batch signature management using Nextcloud Collectives, where each Collective represents a signature batch (project, contract, initiative).
Why Collectives (not Groups)?
- Better semantic context (projects/initiatives vs system permissions)
- Built for collaboration with documentation support
- More flexible member management
- Avoids confusion between system groups and signature batches
Required Features
1. CRUD Management in LibreSign Menu
Interface to create/edit/delete Collectives and manage members directly from LibreSign.
2. Smart Collective Selection
When adding participants, allow selecting a Collective with smart filtering:
- Filter by contact method (email/WhatsApp/SMS/Telegram)
- Show only Collectives with valid contacts for selected method
- Display member count (e.g., "Project Alpha: 12 valid emails out of 15 members")
3. Frontend Member Expansion
When a Collective is selected, expand all members into the regular participants list. This keeps backend simple - no Collective resolution during signing, just individual signers.
UI Concept
Contact Method: [Email ▼]
Available Batches:
📁 Project Alpha (15 members, 12 with email)
📁 Q1 2026 NDAs (23 members, 20 with email)
[Select] → Expands into individual participants list
Benefits
- Users can review/modify expanded list before sending
- Reuses existing signer validation logic
- No additional database tables needed
- Simple backend (processes individual signers only)
Dependency
Requires Collectives app installed. Show friendly message if unavailable.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing LibreSign's existing participant management and how the LibreSign menu handles related actions, then investigate the available Nextcloud Collectives integration. Done means users can manage Collectives and members, filter batches by contact method, expand selected members into editable individual participants, and receive a friendly message when Collectives is unavailable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100