You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -308,7 +309,7 @@ that you would like to see on the list, we encourage you to
308
309
[initiate a new discussion] to evaluate it with others.
309
310
310
311
[overview of these sponsoring goals]: ../index.md#goals
311
-
[initiate a new discussion]: https://github.com/squidfunk/mkdocs-material/discussions/new/chooses
312
+
[initiate a new discussion]: https://github.com/squidfunk/mkdocs-material/discussions
312
313
313
314
[__What happens if I reach my sponsoring limit for my current tier?__](#insiders-limit){ #insiders-limit }
314
315
@@ -361,7 +362,7 @@ for sponsorship.
361
362
It depends. If you are using the Insiders edition as an individual, you can work
362
363
directly with the private repository, as you do not need to share the Insiders
363
364
features with others. If you are working with a team, it is best to create a
364
-
private fork using the individual account you listed as a collaborator of
365
+
private [fork] using the individual account you listed as a collaborator of
365
366
Material for MkDocs to grant access to all members of your organization to
366
367
your fork.
367
368
@@ -425,7 +426,7 @@ organization is also considered commercial use, as with all commercial software.
425
426
426
427
[__What constitutes non-commercial use of the Insiders edition?__](#non-commercial-use){ #non-commercial-use }
427
428
428
-
Non-commercial use of our Material for MkDocs refers to private use. This
429
+
[Non-commercial] use of our Material for MkDocs refers to private use. This
429
430
includes individuals using the Insiders edition for private or purely
430
431
non-commercial Open Source projects. We offer two different tiers for
431
432
non-commercial use, depending on the number of sites you want to build.
@@ -436,7 +437,7 @@ Our fair use policy includes the following guidelines:
436
437
437
438
- Please refrain from __distributing the source code__ of Insiders. While you
438
439
may use the software for public, private, or commercial projects and may
439
-
privately fork or mirror it, we ask that you keep the source code private. This
440
+
privately [fork] or [mirror] it, we ask that you keep the source code private. This
440
441
is important to our sponsorware strategy, which helps us fund ongoing
441
442
development and support of the software. If this guidelines is violated,
442
443
everybody loses, as it will reduce the time of us maintainers we can set aside
@@ -452,7 +453,7 @@ No. Whether you're an individual or a company, you may use Material for
452
453
MkDocs Insiders precisely under the same terms as Material for MkDocs, which are
453
454
given by the [MIT license].
454
455
455
-
[MIT license]: ../../license.md
456
+
[MIT license]: ../../license.md
456
457
457
458
[__Can outside collaborators build and run the documentation locally without access to Insiders?__](#insiders-outside-collaborators){ #insiders-outside-collaborators }
458
459
@@ -560,23 +561,21 @@ transactions for us. Consequently, we have decided to introduce a setup fee for
560
561
any additional administrative tasks other than those handled by GitHub Sponsors
561
562
that require our attention and involve the completion of forms or adherence to
562
563
company processes when purchasing Material for MkDocs Insiders. If your purchase
563
-
departmenz requires additional time and effort from our team, please be aware
564
+
department requires additional time and effort from our team, please be aware
564
565
that the setup fee will apply. For detailed information and specific inquiries,
565
566
please reach out to us at sponsors@squidfunk.com.
566
567
567
568
[__Can I sponsor privately?__](#sponsorship-private){ #sponsorship-private }
568
569
569
-
Yes, you can. GitHub gives you the option to set your sponsorship to [private]
570
-
when you set up your sponsorship. Additionally, we have a recommended workflow
571
-
for you: We suggest you create a new GitHub bot account. This bot account should
572
-
not be tied to a particular individual and should be privately listed as an
573
-
owner of your GitHub organization. This account can then be used to sponsor
574
-
Material for MkDocs privately. As a bot account, it will automatically be listed
575
-
as a collaborator of the private Insiders repository. You can clone, fork, or
576
-
mirror using this account. All information will be kept confidential; only the
577
-
bot account and us maintainers will have insights into his sponsorship.
Yes, you can. GitHub offers the option to [set your sponsorship to private] when
571
+
you initiate your sponsorship. This means that your account will not appear in
572
+
sponsor-listings so there is no public affiliation with Material for MkDocs.
573
+
Only we know that you sponsored, but we will never disclose this information
574
+
without your written consent.
575
+
576
+
[set your sponsorship to private]: https://docs.github.com/en/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship#managing-the-privacy-setting-for-your-sponsorship
0 commit comments