AngleSharp / AngleSharp/AngleSharp.Js

Request for Support / Sponsorship

Abierto
#90 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

help-wanted information
Lenguaje dominante
C#
Estrellas
117
Forks
27
Merge medio
17 min
PR fusionados (30 d)
1

Descripción

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)

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Línea de trabajo

No se identifica ningún archivo fuente, prueba ni punto de entrada de la implementación; el issue es una solicitud de patrocinio, no un cambio de código. No existe un objetivo de implementación de un tamaño adecuado para alguien que contribuye por primera vez ni una Definition of Done basada en código.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Área
content
Tipo de issue
Documentación
Dificultad
5/5
Tiempo estimado
Más de una semana
Estado de actividad
Estancado
Claridad
Necesita aclaración
Aptitud para principiantes
1/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.