Hi Oleg, Thanks a lot. I read all the document, all seems fine. Just, I want to be sure, I understood that traveling or attending meetings physically is not required. If these are true, then please count me in :)
On Wednesday, February 26, 2020 at 7:45:38 PM UTC+1, Oleg Nenashev wrote: > > Hi, > > Thanks for your interest! It would be great to work with you on this > project > > We have all the requirements documented here: > https://jenkins.io/projects/gsoc/mentors/ > It is a long read, https://jenkins.io/blog/2019/12/20/call-for-mentors/ is > probably a quicker intro. > TL;DR: There is no need to make any commitment until April, but in summer > GSoC mentorship may require around 5 hours per week, give or take. > > Best regards, > Oleg > > On Wednesday, February 26, 2020 at 5:18:11 PM UTC+1, Aytunc Beken wrote: >> >> Hi Oleg, >> >> Came to my mind after I saw the Gsoc Approval. If you want/need, I will >> be happy to support/help you for mentoring this plugin. >> I do not know what are the requirements for this, just wanted to say this. >> >> Thanks. >> >> On Tuesday, February 25, 2020 at 9:28:44 AM UTC+1, Aytunc Beken wrote: >>> >>> Hi Oleg, >>> >>> First I want to focus on this new Pipeline As Yaml Plugin. After that, I >>> can work in this plugin (SPPR) also. >>> >>> So thanks a lot for the support, I will start working on this plugin >>> immediately. >>> >>> >>> On Monday, February 24, 2020 at 2:03:32 PM UTC+1, Oleg Nenashev wrote: >>>> >>>> Hi Aytunc, >>>> >>>> - Of course, I do not want to throw all the effort in the SPPR, I may >>>>> use some of the codes from there, if it is okay ? >>>>> >>>> As long as you follow the MIT License requirements, sure. >>>> You may also want to consider taking over this plugin or contributing >>>> to its codebase, but it is up to you. >>>> Obviously, it would be great to have this new plugin as oprn-source. >>>> >>>> - @Oleg, I saw that this plugin is also selected for GSC 2020, I want >>>>> to be sure that, writing this plugin will not affect GSC 2020 or any >>>>> other >>>>> Jenkins/Community Projects >>>>> >>>> >>>> GSoC 2020 lists potential project ideas, it is not a problem if some >>>> ideas overlap with pending work. Students would need to consider the >>>> ongoing developments in their project proposals, and ideally to sync-up >>>> with stakeholders in the dev list. >>>> It would be great to put a notice with a link to this thread so that >>>> potential applicants know there is ongoing parallel effort. >>>> >>>> BR, Oleg >>>> >>>> >>>> >>>> On Sat, Feb 22, 2020 at 2:25 PM Aytunc Beken <aytunc...@gmail.com> >>>> wrote: >>>> >>>>> Hi Vu Tuan, >>>>> >>>>> Thank you for the detailed information about the plugin. So in this >>>>> situation, my suggestions are below. >>>>> >>>>> - As the SPPR plugin is not developed any more and name of the plugin >>>>> do match with its purpose, starting a new plugin for PAY ( Pipeline As >>>>> Yaml) will be more accurate. >>>>> - Of course, I do not want to throw all the effort in the SPPR, I may >>>>> use some of the codes from there, if it is okay ? >>>>> - @Oleg, I saw that this plugin is also selected for GSC 2020, I want >>>>> to be sure that, writing this plugin will not affect GSC 2020 or any >>>>> other >>>>> Jenkins/Community Projects. >>>>> >>>>> Thanks. >>>>> >>>>> >>>>> On Saturday, February 22, 2020 at 2:13:34 PM UTC+1, Vu Tuan Pham wrote: >>>>>> >>>>>> Hi Aytunc, >>>>>> >>>>>> Thank you for reaching out to me. To give you some context, I took >>>>>> over this project from a GSoC project (Google Summer of Code) from a >>>>>> student. He was unable to finish the project on time, so I decided to >>>>>> take >>>>>> it over after GSoC to see if I can continue working on it to bring it to >>>>>> official release (1.0). Unfortunately, due to time permit and some of my >>>>>> personal reasons, I haven't had time to maintain it over the past 2 >>>>>> years. >>>>>> >>>>>> However, I can still help you my question at my best: >>>>>> - At first, the intend was to integrate with multiple version control >>>>>> systems as it mentioned in the description of the repo >>>>>> https://github.com/jenkinsci/simple-pull-request-job-plugin. But >>>>>> overtime, I think the target shifted toward Pipeline as YAML, which the >>>>>> name of the plugin is not reflecting what it is doing. >>>>>> - As I mentioned, iiuc, this project is no longer under development >>>>>> by anybody, so if you have any idea about a new project, you can always >>>>>> proceed ahead. If you think SPPR project is useful in some ways, you can >>>>>> also consider merging 2 projects, there is no restriction for you to do >>>>>> that. >>>>>> >>>>>> To understand more about this project, you can watch these >>>>>> presentation videos during GSoC 2018 (can skip to SPPR plugin >>>>>> presentation): >>>>>> https://www.youtube.com/watch?v=qWHM8S0fzUw&feature=youtu.be >>>>>> https://www.youtube.com/watch?v=tuTODhJOTBU&feature=youtu.be >>>>>> https://www.youtube.com/watch?v=GGEtN4nbtng&feature=youtu.be >>>>>> >>>>>> cc ...@Martin d'Anjou, who is the mentor of this project during GSoC >>>>>> 2018. I think Martin can give you some insights on the project. >>>>>> Let us know if you have any further questions. >>>>>> >>>>>> Thanks, >>>>>> Vu Tuan >>>>>> >>>>>> On Wednesday, February 19, 2020 at 4:54:07 AM UTC+8, Aytunc Beken >>>>>> wrote: >>>>>>> >>>>>>> Hi Oleg, >>>>>>> >>>>>>> Nice to meet you Vu Tuan. >>>>>>> >>>>>>> I have some doubts, may be you can help me understand things. >>>>>>> >>>>>>> - Why the name of the plugin is different ? Also It says it is about >>>>>>> pull requests from various version controls. If this plugin will >>>>>>> continue >>>>>>> focusing on both, It will be good to separate them. >>>>>>> - I was planing to use ModelASTPipelineDef >>>>>>> (org.jenkinsci.plugins.pipeline.modeldefinition.ast) for converting >>>>>>> Yaml to >>>>>>> Jenkins and vice versa. As this is internal model of Declarative >>>>>>> pipeline, >>>>>>> It will be easy to maintain. >>>>>>> >>>>>>> I will be glad if I can get your ideas/comment about these. >>>>>>> >>>>>>> Thanks. Regards >>>>>>> >>>>>> -- >>>>> You received this message because you are subscribed to a topic in the >>>>> Google Groups "Jenkins Developers" group. >>>>> To unsubscribe from this topic, visit >>>>> https://groups.google.com/d/topic/jenkinsci-dev/6ieyOlLQX0I/unsubscribe >>>>> . >>>>> To unsubscribe from this group and all its topics, send an email to >>>>> jenkin...@googlegroups.com. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/jenkinsci-dev/81073e48-032c-4f83-bbee-799fe1a7926f%40googlegroups.com >>>>> >>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/81073e48-032c-4f83-bbee-799fe1a7926f%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>> -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/f59aaec1-9309-4040-aa21-b150457aeb0b%40googlegroups.com.
