2023 May 18 Jenkins GSoC Office Hours

Apologies for getting this out late.

Attendees: JMM, Kris, Bruno, Rajiv, Dheeraj, Jagruti, Vandit, Ashutosh, Harsh

Agenda & Notes:

  • For all projects
    • What has been achieved in the past week?
    • What has been scheduled for the coming week?
    • Is there anything that is bothering you that we can help with?
  • Building jenkins.io with alternative tools
    • Had a first meeting on May 14
    • Created contributor bio
    • Completed project page
    • Created first blog post
    • Created public repo for project
    • Kris will send email to engage with community on project planning
    • Exams postponed in late May (will end on 27th)
    • JMM: Work and studies go first (general comment), exams, private life, work take priority
    • No worries for now
    • Rajiv thinks the project is going well, agrees with the suggested approach
  • Adding probes to plugin health score
    • Continuing with project
    • Had some issues with testing
    • Created bio and project page
    • Had two meetings with mentors
    • Plans for next week is to continuing with adding probe, and to make sure blog will be completed
    • JMM reminded to involve community
    • No worries for now, but time management may be an issue in the future
    • JMM suggests Jagruti to talk to mentors and even org admins when there is an issue
    • Dheeraj is happy with current progress, seen the work on the bio and project page, and expects to see the blog post next week
    • Jagruti is more/only free during weekend, but Adrien is unavailable on weekends
  • Docker based quickstart
    • Has uploaded bio
    • Scheduled first call for tomorrow due to time conflicts (mentors on PTO and unavailable before then)
    • Will discuss timeline and deliverables then
    • Has Slack channel on CDF space also a Gitter channel on Matrix
    • No worries currently
  • GitLab Plugin Modernization
    • Exams are over for Harsh
    • Things will be much faster
    • Done bio and project page
    • Will need to do blog post
    • Will discuss project plans tomorrow in 3rd meeting
    • Already has two meetings
    • No worries for now
  • Important to have the community engaged
    • Blog post is important but may not be sufficient
      • Should introduce contributors
      • Should introduce projects (idea, plans, timeline, deliverables, etc.)
      • Should be between 400 and 800 words ideally (or long enough to convey everything)
      • Will be in AsciiDoc, which is an extension of markdown
    • Should have lead mentor or contributor send an email / message on Discourse to get feedback from key stakeholders