As I have mentioned before, this year Jackson project will be
participating in Hacktoberfest more heavily. I created a repo:

https://github.com/FasterXML/Hacktoberfest2020

to contain some of information that is most relevant to this event (as
opposed to work done for specific modules).
Basic information for Hacktoberfest 2020 can be found here:

    https://hacktoberfest.digitalocean.com/

but the idea is that during the month of October, one can submit PRs
against pretty much any Github repository (with some reasonable
limits), and getting 4 accepted qualifies you for a T-shirt (or one of
alternatives).

In addition, some companies sponsor additional activities: this year
my employer, Indeed.com, is participating:

https://engineering.indeedblog.com/indeed-hacktoberfest-2020/

and gives out additional prizes for just 2 eligible contributions.
Jackson projects (basically anything under FasterXML/ Org at Github)
are included as one of projects Indeed is involved with (author works
for the company, and/or company is heavily using).

So far so good.

I plan to use a bit more time over this October to try to support contributors.
But one big part of this event is to figure out things that new (to
project, at least) contributors could help with. This is something I
could really use help with!

With that in mind, I was hoping that existing module owners (f.ex
Scala and Kotlin module owners, Java 8 date/time) could maybe suggest
something to add on README at:

https://github.com/FasterXML/Hacktoberfest2020

as sort of an advertisement, help wanted.
I will also make sure there is "good-first-issue" label available for
repos (if missing somewhere, let me know if you can not add it), so
that issues may be labeled with it.

And more generally, anyone with time to contribute is more than
welcome to do things like:

1. Tag issues -- if you can add "good-first-issue" label, do so; if
not, add a note cc me so I can add!
2. Follow discussions on issues and help answer questions if you can;
add notes on thoughts for solving things.
3. For repos with "to-evaluate" label, help with triage would be
appreciated: cc me to help change labels (and if anyone knows if it is
possible to give "metadata admin" rights, let me know -- I'd love to
delegate some of power, without necessarily giving push rights)
4. Suggestions for Issue templates to use for projects would be great
(file an issue with template -- unless there's a way to do PR?)
5. Something else? Let me know!

-+ Tatu +-

-- 
You received this message because you are subscribed to the Google Groups 
"jackson-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jackson-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jackson-dev/CAL4a10iG3kuRD7JO0-aYphN-sLrC0zaaUktxp8okR1Wxb7ZSJg%40mail.gmail.com.

Reply via email to