Thanks On Thu, 21 May 2020, 23:04 Kyle Weaver, <[email protected]> wrote:
> Hi Chandan, sorry about that. Does this link work? > > > https://join.slack.com/t/seasonofdocs/shared_invite/enQtNTc0NDgyOTQ5Nzc4LTliZjVlZjRmNmU5ZmFiNmViNmNiMTM5NTdlNTJiYzIzZTk3MDlhMjM3NzE2MzIxNzIxNmZiMmMzNzRmZTI4NmU > > On Thu, May 21, 2020 at 1:32 PM Chandan Prakash < > [email protected]> wrote: > >> Thanks, >> >> The link to join slack channel is expired .I am new to slack ,so , it >> will be helpful for me if I get the slack URL . >> >> >> On Thu, 21 May 2020, 22:13 Kyle Weaver, <[email protected]> wrote: >> >>> Hi Chandan, >>> >>> >>> Thank you for the introduction and your interest to work on Apache Beam >>> documentation with Season of Docs. To participate in the program you >>> need to follow the guides here [1] [2]. If you are new to the program, we >>> suggest: >>> >>> 1. >>> >>> Start by studying our proposed project ideas and expected >>> deliverables for each of them [3]. >>> 2. >>> >>> Explore more in depth the existing related Beam documentation for >>> each project idea. We provided links to the background material, known >>> issues and current documentation for both project ideas [4] [5]. Choose >>> one >>> project you like the most. >>> 3. >>> >>> Start drafting a proposal with the gaps you have found and ideas for >>> improvement, and how you would present the new/updated/full >>> documentation. >>> Here are more tips on how to make your proposal stronger [6]. Please, >>> follow the guides and make sure you cover all points. >>> 4. >>> >>> Submit the project proposal to the Google program administrators >>> during the technical writer application phase. It opens on June 9, 2020. >>> If >>> you want any feedback for your initial draft, consider using Google >>> Docs and share on [email protected], so the community members can >>> leave their comments and suggestions (please check the access to the doc >>> before sending to the mailing list). >>> >>> If you have any ideas that you want to brainstorm about, don’t hesitate >>> to start a discussion in the community list or reach out on Slack channel >>> to discuss issues related to GSoD documentation [7]. Once you create an >>> account join #beam-gsod channel. >>> >>> Project administrators will assess proposals based on these guidelines >>> [8] >>> >>> Hope it helps. Let us know if you have more questions. >>> >>> Thanks, >>> >>> Beam GSoD team >>> >>> [1] https://developers.google.com/season-of-docs/docs/tech-writer-guide >>> >>> [2] https://developers.google.com/season-of-docs/terms/tech-writer-terms >>> >>> [3] https://cwiki.apache.org/confluence/display/BEAM/Google+Season+of+ >>> Docs >>> >>> [4] https://cwiki.apache.org/confluence/display/BEAM/Google+Season+of+ >>> Docs >>> #GoogleSeasonofDocs-1.DeploymentofaFlinkandSparkClusterswithPortableBeam >>> >>> [5] https://cwiki.apache.org/confluence/display/BEAM/Google+Season+of+ >>> Docs >>> #GoogleSeasonofDocs-2.Updateoftherunnercomparisonpage/capabilitymatrix >>> >>> [6] https://developers.google.com/season-of-docs/docs >>> /tech-writer-application-hints >>> >>> [7] https://join.slack.com/share/zt-eaml657m-KMamnNZfRF2BB7eQpmvveg >>> >>> [8] https://developers.google.com/season-of-docs/docs >>> /project-selection#assess-proposal >>> >>> >>> On Thu, May 21, 2020 at 12:18 AM Chandan Prakash < >>> [email protected]> wrote: >>> >>>> Hello community, >>>> I am Chandan Prakash , sophomore year student in CS from India. I >>>> really want to contribute to the documentation . I have gone through the >>>> project ideas . I am new to Apache beam as I have never used it before. >>>> Right now, I am exploring Apache beam , runner , SDKs ,etc. But I am >>>> quite familiar with open source . >>>> I also want to join slack channel for GSoD idea discussion . But , I >>>> don't know the workspace URL. >>>> Suggestions for where should I start are highly appreciated. >>>> >>>> >>>> Thanks >>>> >>>
