-
Notifications
You must be signed in to change notification settings - Fork 409
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Republish Hacktobest blog post #3429
Conversation
Marketing blog posts should be reviewed by @ptrfarkas and @AlekSi. |
Codecov Report
@@ Coverage Diff @@
## main #3429 +/- ##
==========================================
+ Coverage 75.37% 75.41% +0.04%
==========================================
Files 422 422
Lines 26263 26263
==========================================
+ Hits 19795 19807 +12
+ Misses 5324 5316 -8
+ Partials 1144 1140 -4 see 3 files with indirect coverage changes
Flags with carried forward coverage won't be shown. Click here to find out more. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd check the info about t-shirts :)
Also, I think now there are more rules about issues now - https://hacktoberfest.com/participation/#pr-mr-details. E.g. the repo should have a particular topic/label. It's on our side to check that we have all these necessary things.
The rest looks good to me!
website/blog/2023-09-26-how-to-contribute-to-open-source-2022.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me now!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's also bump the date to tomorrow
Do you see a typo, a mistake, or something that doesn't look clear? | ||
|
||
We have several good first issues that you can start with. | ||
For example, you could implement the [`$first` accumulator](https://github.com/FerretDB/FerretDB/issues/2128), [improve embedded package documentation](https://github.com/FerretDB/FerretDB/issues/2326), or [fix linter issues](https://github.com/FerretDB/FerretDB/issues/2733). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The last one is already taken
|
||
We have several good first issues that you can start with. | ||
For example, you could implement the [`$first` accumulator](https://github.com/FerretDB/FerretDB/issues/2128), [improve embedded package documentation](https://github.com/FerretDB/FerretDB/issues/2326), or [fix linter issues](https://github.com/FerretDB/FerretDB/issues/2733). | ||
You could also try your hands at [updating glossary list with more details](https://github.com/FerretDB/FerretDB/issues/3427), [update aggregation section to cover `$unset` and `$project` commands](https://github.com/FerretDB/FerretDB/issues/3428), and more. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Both are taken
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That changes the image of the old blog post as well. I'm not sure this is ok
@@ -25,24 +25,25 @@ This is how the members of the open source community encourage new tech enthusia | |||
|
|||
[Hacktoberfest](https://hacktoberfest.com/) is an annual online event celebrating the open source movement. | |||
This year, registration starts on September 26. | |||
To participate, you need to send at least four open-sourced pull requests on GitHub or Gitlab between October 1st and October 31st, and those pull requests need to be accepted by the repository owners. | |||
To participate, you need to send at least four open-sourced pull requests on GitHub or Gitlab between October 1st and October 31st, for projects that indicate they are looking for Hacktoberfest contributions (`hacktoberfest` labels), and those pull requests need to be accepted by the repository owners. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@@ -71,7 +72,7 @@ It's essential to find some "low-hanging fruit" that will give you inspiration f | |||
On GitHub, it might make sense to look for "good-first-issue" labels. | |||
Usually, issues that are marked with such a label don't require special knowledge about the project. | |||
|
|||
There is one more tradition here, in October, some open source projects mark their issues with the "[hacktoberfest](https://github.com/search?q=label%3Ahacktoberfest&type=issues)" label, and such issues are often suitable for first-time contributors. | |||
There is one more tradition here, in October, some open source projects mark their issues with the [`hacktoberfest`](https://github.com/search?q=label%3Ahacktoberfest&type=issues) label, and such issues are often suitable for first-time contributors. | |||
|
|||
At FerretDB, we are preparing for Hacktoberfest too! | |||
So, if you are looking for something to contribute to, take a look at the good first issues in our [FerretDB](https://github.com/FerretDB/FerretDB/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) and [github-actions](https://github.com/FerretDB/github-actions/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) repositories. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No github-actions
this year
author: Elena Grahovac | ||
description: Contributing to open source might seem daunting, but you can start your tech journey during Hacktoberfest 2022. | ||
description: Contributing to open source might seem daunting, but you can start your tech journey during Hacktoberfest 2023. | ||
image: /img/blog/hacktoberfest.jpg |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's the old logo
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's probably better we update the image, and make it similar to other recent blog posts.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure why we insist on using the single file for two different images, but I'm sure it is not a good idea. File names are free. We can have hacktoberfest.jpg
and something like hacktoberfest-2023.jpg
in the same directory
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On the same note – both the URL and file name mention 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The URL is okay since we are republishing; we don't want to change the URL. Otherwise, the current link won't be reachable
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't understand why we are making it so needlessly complicated. Can we just create a new post instead of "republishing" with wrong logo and different years in the URL and text?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That would mean creating a new blog post entirely from scratch without plagiarizing the previous one, even when 80% of the content will remain the same. This way, we are just updating the old blog posts with new information rather than rewriting the entire thing all over again. It's a normal process with old posts that just require a bit of new info.
Description
Readiness checklist
task all
, and it passed.@FerretDB/core
), Milestone (Next
), Labels, Project and project's Sprint fields.