> Should I submit the proposal as a GitHub link or a PDF? Either is fine for submitting the proposal.
> I’d also love any tips you have on improving my proposal. Have you shared it as a google doc like mentioned earlier? Thanks, Danny On Sun, Mar 23, 2025 at 8:37 AM Aditya <adiworkprof...@gmail.com> wrote: > Subject: Question About Proposal Submission > > Hi Danny, > > Should I submit the proposal as a GitHub link or a PDF? > > I’d also love any tips you have on improving my proposal. > > Thanks, > Aditya > > On Sat, 22 Mar, 2025, 17:32 Aditya, <adiworkprof...@gmail.com> wrote: > >> >> Thanks Danny >> >> I will write and share this in a Google docs >> >> Thanks >> Aditya >> >> On Sat, 22 Mar, 2025, 01:42 Danny McCormick, <dannymccorm...@google.com> >> wrote: >> >>> Hey Aditya, I would recommend sharing this as a google doc or something >>> which allows people to leave comments on it if you'd like feedback. At a >>> high level, the proposal generally looks reasonable and well written to me, >>> though! >>> >>> Thanks, >>> Danny >>> >>> On Wed, Mar 19, 2025 at 5:10 PM Aditya <adiworkprof...@gmail.com> wrote: >>> >>>> *Subject:* Request for Feedback on My GSoC Proposal >>>> >>>> Hi Danny, >>>> >>>> I hope you're doing well. >>>> >>>> I’ve been working on my GSoC proposal and would really appreciate your >>>> feedback on it: >>>> GitHub Link: GSoC Proposal >>>> <https://github.com/aditya0yadav/gsoc-proposal/> >>>> >>>> I’ll also be providing an Initial Proof of Concept once the application >>>> period starts. Your insights would be invaluable in refining it. >>>> >>>> Looking forward to your thoughts! >>>> >>>> Thanks, >>>> Aditya >>>> >>>> On Mon, Mar 17, 2025 at 6:48 PM Danny McCormick < >>>> dannymccorm...@google.com> wrote: >>>> >>>>> Hey Aditya, there is not necessarily a single set of benchmarks which >>>>> we can use to evaluate an IO, and defining exactly what/how we should be >>>>> measuring completeness and performance is part of the work to be done >>>>> here. >>>>> I think this is a good thing for you to try to initially define in your >>>>> project proposal, though it would probably evolve over the life of a >>>>> project. https://beam.apache.org/documentation/io/io-standards/#python >>>>> is also probably a good starting place. >>>>> >>>>> In general, my recommendation for questions like this would be to try >>>>> to suggest an approach you think is reasonable in a proposal and then >>>>> share >>>>> the broader proposal with the dev list for feedback. >>>>> >>>>> Thanks, >>>>> Danny >>>>> >>>>> Thanks, >>>>> Danny >>>>> >>>>> On Sun, Mar 16, 2025 at 1:50 PM Aditya <adiworkprof...@gmail.com> >>>>> wrote: >>>>> >>>>>> *Subject:* Inquiry on Success Metrics for Pinecone and Tecton I/O >>>>>> Connectors (GSoC Proposal) >>>>>> >>>>>> Hi Danny, >>>>>> >>>>>> I hope you're doing well. >>>>>> >>>>>> As I prepare my GSoC proposal, I am seeking guidance on defining >>>>>> success metrics for the I/O connectors we plan to develop for Pinecone >>>>>> and >>>>>> Tecton. Specifically, I would like to understand the key benchmarks and >>>>>> standards we should aim for in terms of functionality, performance, >>>>>> reliability, documentation, code quality, and integration within Apache >>>>>> Beam pipelines. >>>>>> >>>>>> Your insights would be invaluable in shaping a strong proposal and >>>>>> ensuring alignment with project goals. >>>>>> >>>>>> Looking forward to your thoughts. >>>>>> >>>>>> Best regards, >>>>>> Aditya >>>>>> >>>>>>>
