diff --git a/src/components/ProjectThumbnail.astro b/src/components/ProjectThumbnail.astro new file mode 100644 index 00000000..f2bb63d7 --- /dev/null +++ b/src/components/ProjectThumbnail.astro @@ -0,0 +1,26 @@ +--- +export interface Props { + description: string, + env: string, + img: string, + repo: string +} + +const { description, env, img, repo } = Astro.props; +--- + +
+
+
+

+ + {env}/ +
+ {repo} + +

+ +
+ {description &&

{description}

} +
+
\ No newline at end of file diff --git a/src/content/articles/can-i-take-this-issue.mdx b/src/content/articles/can-i-take-this-issue.mdx index 232ea8da..adc4868f 100644 --- a/src/content/articles/can-i-take-this-issue.mdx +++ b/src/content/articles/can-i-take-this-issue.mdx @@ -9,6 +9,8 @@ lastUpdateDate: '2023-05-17' title: 'Can I Take This Issue?' --- +import ProjectThumbnail from '../../components/ProjectThumbnail.astro' +

Open-source software development is a collaborative effort that relies on volunteers to contribute to the project. Contributors have different skill levels and come from various backgrounds. As such, project maintainers have a crucial role in ensuring that the contributions received are of high quality and meet the project's goals. One way maintainers do this is by providing clear guidelines on how contributors can submit their work. Unfortunately, contributors don't always take the time to read these guidelines, and maintainers don't always assign issues, which can lead to confusion and frustration on both sides. In this article, we'll explore the issue of unassigned contributions and discuss what can be done to address it.

## So Can I Take It or Not? @@ -186,20 +188,7 @@ Everything can start from the creation of these issues with the issues templates At the time of writing, GitHub doesn't provide any options to add some Markdown content at the end of the issues when using issue templates. However, you can use GitHub Actions to do that. Here is an example of a GitHub Action that adds a message for newly created issues: -
-
-
-

- - Open-reSource/
- labs-append-markdown-to-issues - -

- -
-

[Labs] Automatically append Markdown to issues

-
-
+ An infinite way of managing labels is possible. Let's imagine, for example, a "to analyze" label that can be picked up only by a core team member. When this core team member analyzed the issue and provided expectations, clarity, and guidance, the label could be transformed into an "analyzed" label, and a new "ready for dev" label could be applied combined to "high priority" and "low complexity" labels, and a "version 12" label, "bug" or "feature", "core team" if it is reserved for the core team, or "pr welcome" when it is OK for external contributors to work on it. When doing that, contributors can start to help or not, filter the backlog by labels, and the core team can focus on the most important issues. If the workflow is automated, the issue can go to one or another project, be in a roadmap, etc. This is just an example, but you can imagine how powerful it can be. @@ -266,20 +255,7 @@ Writing this article was the occasion to try creating a semi-automation The source code of this experiment is available on GitHub via the card below. -
-
-
-

- - Open-reSource/
- labs-we-don-t-assign-issues - -

- -
-

[Labs] "we don't assign issues" label that writes a comment and is then auto-deleted

-
-
+ Unfortunately, if there are intermediate comments before maintainers have the time to use this label, it won’t work. And it stays semi-automatic. diff --git a/src/content/articles/contrib-rocks.mdx b/src/content/articles/contrib-rocks.mdx index c6ccd4c0..ac805e99 100644 --- a/src/content/articles/contrib-rocks.mdx +++ b/src/content/articles/contrib-rocks.mdx @@ -11,23 +11,13 @@ lastUpdateDate: '2024-04-27' title: 'contrib.rocks: Generate an Image of GitHub Repositories Top Contributors' --- +import ProjectThumbnail from '../../components/ProjectThumbnail.astro' +

[contrib.rocks](https://contrib.rocks/) is a an online tool that generates an image of the top contributors of a GitHub repository that can be embedded in any website or Markdown file; including its README file.

It is completely free and maintained by Suguru Inatomi, a.k.a. [lacolaco](https://github.com/lacolaco). The source code is available on GitHub: -
-
-
-

- - lacolaco/
- contributors-img - -

- -
-
-
+ This service allows to give a visual representation of the top contributors of any GitHub repository. diff --git a/src/content/articles/display-your-sponsors-in-your-github-readmes.mdx b/src/content/articles/display-your-sponsors-in-your-github-readmes.mdx index 268acf93..b942f9d8 100644 --- a/src/content/articles/display-your-sponsors-in-your-github-readmes.mdx +++ b/src/content/articles/display-your-sponsors-in-your-github-readmes.mdx @@ -10,24 +10,13 @@ lastUpdateDate: '2023-05-19' title: 'Display Your Sponsors in Your GitHub READMEs' --- +import ProjectThumbnail from '../../components/ProjectThumbnail.astro' +

A simple nice way to reward your sponsors could be to showcase them in the projects you create on GitHub. And what a better place to do that than in your READMEs? This article will show you how to do that easily!

There are several ways to display your sponsors in your GitHub READMEs, but this article will focus on a single one by using [SponsorKit](https://github.com/antfu/sponsorkit) created by [Anthony Fu](https://github.com/antfu). -
-
-
-

- - antfu/
- sponsorkit - -

- -
-

πŸ’– Toolkit for generating sponsors images πŸ˜„

-
-
+ **SponsorKit** is a toolkit for generating sponsors images that supports GitHub Sponsors, Open Collective, Patreon, and Afdian. @@ -47,20 +36,7 @@ You can find more information about how to create a GitHub token in the [GitHub In order to facilitate the process, we have created for you a template repository that you can use to create your own repository: https://github.com/Open-reSource/sponsorkit-starter. -
-
-
-

- - Open-reSource/
- sponsorkit-starter - -

- -
-

Starter template for SponsorKit

-
-
+ ### From the Starter Template diff --git a/src/content/articles/repobeats.mdx b/src/content/articles/repobeats.mdx index 6ca5a09d..30cd0471 100644 --- a/src/content/articles/repobeats.mdx +++ b/src/content/articles/repobeats.mdx @@ -11,6 +11,8 @@ lastUpdateDate: '2024-04-02' title: 'Repobeats: GitHub README analytics' --- +import ProjectThumbnail from '../../components/ProjectThumbnail.astro' +

[Repobeats](https://repobeats.axiom.co/) is a tool that provides analytics of a GitHub repository that can be embedded in any Markdown file; including its README file.

It is completely free and maintained by [axiom.com](https://axiom.co/), but does not seem to be an open-source project as it is not referenced in [github.com/axiomhq](https://github.com/axiomhq). @@ -56,20 +58,7 @@ Here is what it looks like for our [openresource.dev GitHub repository](https:// And here is the same kind of data, but on a more active repository like freeCodeCamp: -
-
-
-

- - freeCodeCamp/
- freeCodeCamp - -

- -
-

freeCodeCamp.org's open-source codebase and curriculum. Learn to code for free.

-
-
+ ![Alt](https://repobeats.axiom.co/api/embed/89be0a1a1c8f641c54f9234a7423e7755352c746.svg 'Repobeats analytics image for freeCodeCamp GitHub repository')