LibreSign / LibreSign/libresign

List LibreSign in beginner-friendly open source directories

Open Beginner friendly
#8,284 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

community good first issue
Dominant language
PHP
Stars
818
Forks
146
Avg merge
11h 31m
Merged PRs (30d)
326

Description

LibreSign has several open good first issue tasks and has recently received useful contributions from new contributors.

We should make these issues easier to discover by listing LibreSign in active community directories that accept new projects through pull requests.

This work does not require maintainer access to LibreSign. Any community contributor can choose one of the directories below, follow its contribution guide and submit LibreSign.

Up For Grabs

Submit LibreSign to:

https://github.com/up-for-grabs/up-for-grabs.net

Follow the current instructions for listing a project:

https://github.com/up-for-grabs/up-for-grabs.net/blob/gh-pages/docs/list-a-project.md

The entry should:

  • use https://github.com/LibreSign/libresign as the project repository;
  • point to issues with the good first issue label;
  • use appropriate project tags such as php, javascript, vue, pdf and signature when accepted by the directory;
  • follow the current file format and contribution rules of Up For Grabs.

Awesome for Beginners

Submit LibreSign to:

https://github.com/MunGell/awesome-for-beginners

Follow the current contribution guide:

https://github.com/MunGell/awesome-for-beginners/blob/main/CONTRIBUTING.md

Add LibreSign to the appropriate technologies using:

  • repository: https://github.com/LibreSign/libresign
  • beginner label: good first issue

Follow the current data.json format and submit only the LibreSign addition in the pull request.

How to contribute

Different contributors can work on each directory independently.

Before starting, please comment here with the directory you want to work on. This helps avoid duplicate submissions.

After opening the external pull request, add a comment here with its link.

If the directory changes its requirements and LibreSign no longer qualifies, document the reason here instead of trying to bypass its rules.

Done when

  • A pull request adding LibreSign is opened in Up For Grabs.
  • The Up For Grabs PR follows its current project-listing requirements.
  • A pull request adding LibreSign is opened in Awesome for Beginners.
  • The Awesome for Beginners PR follows its current contribution requirements.
  • Both external pull request links are recorded in this issue.
  • Any review feedback required to make the submissions valid is addressed, when reasonable.

The external pull requests do not need to be merged before this issue can be completed. Their final acceptance is controlled by the maintainers of those projects.

Good first issue

This issue does not require changes to the LibreSign source code or maintainer permissions.

Choose one directory, read its contribution guide, add LibreSign following the existing format, open the pull request and share the link here.

This is a small way to help more new contributors discover LibreSign and its beginner-friendly issues.

Additional context
  • If you have questions, feel free to ask in this issue.
  • Give a ⭐️ to LibreSign if you find the project useful.
  • You can also join our community: https://t.me/LibreSign

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with Up For Grabs' list-a-project guide and the Awesome for Beginners CONTRIBUTING.md, then inspect their current project-entry formats, including data.json. Add LibreSign using the repository URL and good first issue label, open the applicable external pull requests, and record both links here; completion does not require either PR to be merged.

Written by the indexing model from the issue text.

Assessment

Tech stack
github
Domain
content
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
78/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.