AngleSharp / AngleSharp/AngleSharp.Js
Request for Support / Sponsorship
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- C#
- Sterne
- 117
- Forks
- 27
- Ø Merge
- 17 Min.
- Gemergte PRs (30 T.)
- 1
Beschreibung
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:
- daveaglick
- vmeganathan81
- jfoshee
- Mrxx99
- iamcarbon
- DorYos
- LukeTOBrien
- zunjae
- Alellujah
- Gavin-Williams
🙏 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)
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Es wird keine Quelldatei, kein Test und kein Einstiegspunkt für die Implementierung identifiziert; das Issue ist eine Sponsoring-Anfrage und keine Codeänderung. Es gibt kein Implementierungsziel in einer für Neueinsteiger geeigneten Größe und keine codebasierte Definition of Done.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Bereich
- content
- Issue-Typ
- Dokumentation
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 1/100