AngleSharp / AngleSharp/AngleSharp.Js

Request for Support / Sponsorship

Ouverte
#90 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

help-wanted information
Langage dominant
C#
Étoiles
117
Forks
27
Merge moyen
17 min
PR mergées (30 j)
1

Description

Over the years this project had great contributors and sponsors. Moving forward the last year has shown that dedicated support (e.g., as provided by AWS and JetBrains) is crucial to allocate time for maintenance and move it forward. I'd like to continue in this mode; not only sometimes cutting out some of my spare time, but actually being able to have dedicated time slots.

So with this sticky note I call to support this project. It would be really wonderful and there are still some plans for a potential v2 that would benefit a lot from additional support (as well as its ecosystem, esp. CSS / JS / ...).

Background

In the past we already had some great sponsors who brought this project forward.

By far the largest contribution came from AWS:

Closely behind (and still active) is the sponsorship from JetBrains:

And other companies:

| | |

We also had individuals (much appreciated!) that have been very gracious:

🙏 thanks to everyone!

Also to be clear; AngleSharp and all associated libraries will always be free and MIT licensed.

There is no consequence from no sponsors coming in - except that my time available for the project will definitely be less as compared to having some sponsorship.

One final remark: While GitHub sponsorships are potentially the best way of supporting the project there are also other ways, e.g., getting in touch regarding consulting on AngleSharp best practices if you use it or directly getting in touch regarding development of specific features.

(Original post / issue available at https://github.com/AngleSharp/AngleSharp/issues/1163)

Guide de contribution

Ouvrir le guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Piste de recherche

Aucun fichier source, test ou point d’entrée de l’implémentation n’est identifié ; l’issue est une demande de sponsoring plutôt qu’une modification de code. Il n’existe pas de cible d’implémentation d’une taille adaptée à une première contribution ni de Definition of Done fondée sur le code.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Domaine
content
Type d'issue
Documentation
Difficulté
5/5
Temps estimé
Plus d'une semaine
Activité
À l'abandon
Clarté
À clarifier
Accessibilité débutants
1/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.