Re: Need some help and contributions in PySpark API documentation
Thanks, Hyukjin. I will go through the reference links you have provided and will reach out to understand what is the best place to start. Thanks for adding tips for new contributors like me. Regards, Rohit Mishra On Wed, Aug 5, 2020 at 12:12 PM Hyukjin Kwon wrote: > Hi all, > > I am trying to redesign the PySpark documentation at SPARK-31851 > <https://issues.apache.org/jira/browse/SPARK-31851>. > Basically from: > >- https://spark.apache.org/docs/latest/api/python/index.html >to: >- https://hyukjin-spark.readthedocs.io/en/latest/index.html (draft) > > The base works are done, and I am now adding new pages such as user guide, > getting started, etc. > > There are many contents to write. I am trying to do one by one but there > are > too many, and I can’t do it all alone. > > I would like to ask the Spark dev community some help to build useful > pages in > PySpark documentation. > I filed some sub-tasks at SPARK-31851 > <https://issues.apache.org/jira/browse/SPARK-31851> so please help some > of the subtasks. > > In addition, feel free to create more sub-tasks if you guys have some good > ideas > to include in official PySpark documentation. > > I wrote some tips at here > <https://issues.apache.org/jira/browse/SPARK-31851?focusedCommentId=17171275=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17171275> > so new contributors should also be able to work on some. > I hope we can manage to build the new and better PySpark documentation > together :-). > > Thanks! > >
[no subject]
Hello Everyone, Someone asked this question on JIRA and since it was a question I requested him to check stack overflow. Personally I don't have an answer to this question so in case anyone has an idea please feel free to update the issue. I have marked it resolved for the time being but thought to take your opinion. Whenever you are free, link is here - https://issues.apache.org/jira/browse/SPARK-32527 Thanks in advance for your time. Regards, Rohit Mishra
Re: Contributing to JIRA Maintenance
Thanks Sean for your elaborate and valuable explanation. I will look into it from tomorrow and will reach out if required. Have a good day. Regards, Rohit Mishra On Tue, 28 Jul 2020 at 11:20 PM, Sean Owen wrote: > To help with JIRA, I don't think you need to know a lot about the code > structure. I think we're talking about more basic triage, like, is it > a question that should go to the mailing list instead? is there enough > detail to understand it at all? is it tagged with a few appropriate > components, does its affected version make sense? Finding duplicate > issues is hard but quite valuable if you can identify related issues > and mark them. > > I can also tell you about using the JIRA Client to search for issues > that don't make much sense, like, open and targeting a released > version. > > Actually I think anyone can modify issues in JIRA, so you don't need > special permission. You could consult with me or Hyukjin or dev@ after > making a few changes to check if they're on the right track. > > iss...@spark.apache.org (IIRC) gets a copy of all the JIRA emails > about changes. I don't know if it's that useful to subscribe to. > > Documenting the code structure - might be kind of hard in any detail, > but if you put together a doc that is useful and doesn't require a lot > of maintenance, that gives a good overview, we could consider adding > that to the developer docs. > > > > On Tue, Jul 28, 2020 at 12:16 PM Rohit Mishra > wrote: > > > > Hello All, > > > > I have recently joined the Dev mailing list to help the community. Since > I am in my attempt to understand the code base before contributing, I think > looking into Jira maintenance will be a good way to help. I will start > looking into it. Do I need anyone’s approval? > > > > In case I need any help in the beginning can I mail here or there is a > separate mailing id related to Jira maintenance? > > > > Just a trivial question- Do we have any document to give an overview of > the code structure for newbie like me, I can create one if there isn’t any. > > > > Thanks, > > Rohit Mishra > > > > On Tue, 28 Jul 2020 at 6:46 PM, Sean Owen wrote: > >> > >> 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 > 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
Re: Contributing to JIRA Maintenance
Hello All, I have recently joined the Dev mailing list to help the community. Since I am in my attempt to understand the code base before contributing, I think looking into Jira maintenance will be a good way to help. I will start looking into it. Do I need anyone’s approval? In case I need any help in the beginning can I mail here or there is a separate mailing id related to Jira maintenance? Just a trivial question- Do we have any document to give an overview of the code structure for newbie like me, I can create one if there isn’t any. Thanks, Rohit Mishra On Tue, 28 Jul 2020 at 6:46 PM, Sean Owen wrote: > 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 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 > >
Re: Unsubscribe
I think you have sent this request to wrong email address. I don’t want to unsubscribe from Dev mail list. I don’t remember I have send any such request. Regards, Rohit Mishra On Tue, 23 Jun 2020 at 7:39 PM, Jeff Evans wrote: > That is not how you unsubscribe. See here: > https://gist.github.com/jeff303/ba1906bb7bcb2f2501528a8bb1521b8e > > On Tue, Jun 23, 2020 at 5:02 AM Kiran Kumar Dusi > wrote: > >> Unsubscribe >> >> On Tue, 23 Jun 2020 at 15:18 Akhil Anil wrote: >> > >> -- >>> Sent from Gmail Mobile >>> >>
