Thanks for doing this - and I will say this is a great way for anyone
out there to contribute directly to the project. Issue trackers need
maintenance too. It's not that hard to spot basic problems with JIRAs
and request fixes, as a way to engage the reporter usefully.

I triage PRs but rarely look at JIRAs anymore, just because the volume
and noise level is larger. But it is important.

On Mon, Jul 27, 2020 at 10:12 PM Hyukjin Kwon <gurwls...@gmail.com> wrote:
>
> Hi all,
>
> I would like to ask for some help about JIRA maintenance contributions in 
> Apache Spark.
> I tend to see less and less people active in JIRA maintenance contributions.
>
> I have regularly checked all JIRAs and monitored them continuously for the 
> last 4 years.
> For the last week, I didn't have time to take a look, and I felt frustrated 
> that there are
> many JIRAs that look clearly needing action. Here are the examples only from 
> the last week:
>
> Exact duplication:
>     Resolve one and link another one as a duplicate.
> - https://issues.apache.org/jira/browse/SPARK-32370
> - https://issues.apache.org/jira/browse/SPARK-32369
>
> Different languages:
>     Ask English translations which dev people use to communicate.
>     If the reporter is inactive, we can resolve it till then.
> - https://issues.apache.org/jira/browse/SPARK-32355
>
> No JIRA description:
>      Ask to fill the JIRA description. Not so many people know what the issue 
> the
>     JIRA describes just from reading the title which will end up that nobody 
> can work
>     on the JIRA.
> - https://issues.apache.org/jira/browse/SPARK-32361
> - https://issues.apache.org/jira/browse/SPARK-32359
> - https://issues.apache.org/jira/browse/SPARK-32388
> - https://issues.apache.org/jira/browse/SPARK-32390
> - https://issues.apache.org/jira/browse/SPARK-32400
>
> Malformed image:
>     If the attached image looks malformed to you, ask to fix.
> - https://issues.apache.org/jira/browse/SPARK-32433
>
> Questions:
>     Questions should usually go to mailing list or stackoverflow per 
> http://spark.apache.org/community.html
> - https://issues.apache.org/jira/browse/SPARK-32460
>
>
> There is clear guidance about JIRA maintenance "Contributing to JIRA 
> Maintenance"
> in http://spark.apache.org/contributing.html (thanks @Sean Owen for writing 
> this).
> I hope to see more people and ask for some help in the JIRA maintenance.
>
> FWIW, at least I, as a PMC, monitor most of these JIRA maintenance 
> contributions from the
> community and take them into account when/where it should be.
>
>
> Thanks all in advance.

---------------------------------------------------------------------
To unsubscribe e-mail: dev-unsubscr...@spark.apache.org

Reply via email to