Uploaded image for project: 'Jenkins Website'
  1. Jenkins Website
  2. WEBSITE-595

Review student GSoC page for specific content

    Details

    • Similar Issues:

      Description

      The GSoC student page should contain:

      • Links to 
      • A reference to a coding style guideline for writing jenkins plugins
      • A reference to a "model" Pipeline plugin
      • Improve instructions for student interaction on mailing list
        • Maybe one thread per student application instead of one thread per project proposal with multiple students on the same thread
      • How to write documentation for the student project
        • how to document the project itself
        • how to write blog posts on the jenkins website
      • Formal expectations
        • application period expectations
          • we expect a proposal that includes a description and a proposed schedule
          • good communication with potential mentors
        • community bonding period expectations
          • we expect a detailed design document, updated schedule
          • regular communication with mentor
          • pair coding
        • coding periods expectations
          • code contributions frequency
          • PR expectations
          • status updates frequency
          • blog post frequency
          • slides and presentation (once per coding period, maybe add one after community bonding)
      • Add list of important recordings
        • on plugin dev and release
        • past years' evaluations
        • how to do extension points

      Feedback to all orgs from Google:

      • Setting up a general set of code submission rules (formatting, proper commenting, documentation ..etc) and show some "good examples" to students
      • Stress the importance of IRC (or your community's chat channel) students commented they didn't realize how helpful it was until late in the program and they wished they'd been active in the channels from the beginning.
      • Clear instructions on setting up the work environment

       

        Attachments

          Activity

          deepchip Martin d'Anjou created issue -
          deepchip Martin d'Anjou made changes -
          Field Original Value New Value
          Epic Link JENKINS-54059 [ 194676 ]
          deepchip Martin d'Anjou made changes -
          Description The GSoC student page should contain:
           * Links to 
           ** [https://wiki.jenkins.io/display/JENKINS/Plugin+tutorial]
           ** [https://jenkins.io/doc/developer/tutorial/]
           ** [https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins]
           * A reference to a coding style guideline for writing jenkins plugins
           * A reference to a "model" Pipeline plugin

           
          The GSoC student page should contain:
           * Links to 
           ** [https://wiki.jenkins.io/display/JENKINS/Plugin+tutorial]
           ** [https://jenkins.io/doc/developer/tutorial/]
           ** [https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins]
           * A reference to a coding style guideline for writing jenkins plugins
           * A reference to a "model" Pipeline plugin
           * Improve instructions for student interaction on mailing list
           ** Maybe one thread per student application instead of one thread per project proposal with multiple students on the same thread

           
          deepchip Martin d'Anjou made changes -
          Description The GSoC student page should contain:
           * Links to 
           ** [https://wiki.jenkins.io/display/JENKINS/Plugin+tutorial]
           ** [https://jenkins.io/doc/developer/tutorial/]
           ** [https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins]
           * A reference to a coding style guideline for writing jenkins plugins
           * A reference to a "model" Pipeline plugin
           * Improve instructions for student interaction on mailing list
           ** Maybe one thread per student application instead of one thread per project proposal with multiple students on the same thread

           
          The GSoC student page should contain:
           * Links to 
           ** [https://wiki.jenkins.io/display/JENKINS/Plugin+tutorial]
           ** [https://jenkins.io/doc/developer/tutorial/]
           ** [https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins]
           * A reference to a coding style guideline for writing jenkins plugins
           * A reference to a "model" Pipeline plugin
           * Improve instructions for student interaction on mailing list
           ** Maybe one thread per student application instead of one thread per project proposal with multiple students on the same thread

          Feedback to all orgs from Google:
           * Setting up a general set of code submission rules (formatting, proper commenting, documentation ..etc) and show some "good examples" to students
           * Stress the importance of IRC (or your community's chat channel) students commented they didn't realize how helpful it was until late in the program and they wished they'd been active in the channels from the beginning.
           * Clear instructions on setting up the work environment


           
          deepchip Martin d'Anjou made changes -
          Description The GSoC student page should contain:
           * Links to 
           ** [https://wiki.jenkins.io/display/JENKINS/Plugin+tutorial]
           ** [https://jenkins.io/doc/developer/tutorial/]
           ** [https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins]
           * A reference to a coding style guideline for writing jenkins plugins
           * A reference to a "model" Pipeline plugin
           * Improve instructions for student interaction on mailing list
           ** Maybe one thread per student application instead of one thread per project proposal with multiple students on the same thread

          Feedback to all orgs from Google:
           * Setting up a general set of code submission rules (formatting, proper commenting, documentation ..etc) and show some "good examples" to students
           * Stress the importance of IRC (or your community's chat channel) students commented they didn't realize how helpful it was until late in the program and they wished they'd been active in the channels from the beginning.
           * Clear instructions on setting up the work environment


           
          The GSoC student page should contain:
           * Links to 
           ** [https://wiki.jenkins.io/display/JENKINS/Plugin+tutorial]
           ** [https://jenkins.io/doc/developer/tutorial/]
           ** [https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins]
           ** [https://wiki.jenkins.io/display/JENKINS/Beginners+Guide+to+Contributing]
           ** [https://jenkins.io/project/governance/]
           * A reference to a coding style guideline for writing jenkins plugins
           * A reference to a "model" Pipeline plugin
           * Improve instructions for student interaction on mailing list
           ** Maybe one thread per student application instead of one thread per project proposal with multiple students on the same thread
           * How to write documentation for the student project
           ** how to document the project itself
           ** how to write blog posts on the jenkins website
           * Formal expectations
           ** application period expectations
           *** we expect a proposal that includes a description and a proposed schedule
           *** good communication with potential mentors
           ** community bonding period expectations
           *** we expect a detailed design document, updated schedule
           *** regular communication with mentor
           *** pair coding
           ** coding periods expectations
           *** code contributions frequency
           *** PR expectations
           *** status updates frequency
           *** blog post frequency
           *** slides and presentation (once per coding period, maybe add one after community bonding)

          Feedback to all orgs from Google:
           * Setting up a general set of code submission rules (formatting, proper commenting, documentation ..etc) and show some "good examples" to students
           * Stress the importance of IRC (or your community's chat channel) students commented they didn't realize how helpful it was until late in the program and they wished they'd been active in the channels from the beginning.
           * Clear instructions on setting up the work environment

           
          deepchip Martin d'Anjou made changes -
          Description The GSoC student page should contain:
           * Links to 
           ** [https://wiki.jenkins.io/display/JENKINS/Plugin+tutorial]
           ** [https://jenkins.io/doc/developer/tutorial/]
           ** [https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins]
           ** [https://wiki.jenkins.io/display/JENKINS/Beginners+Guide+to+Contributing]
           ** [https://jenkins.io/project/governance/]
           * A reference to a coding style guideline for writing jenkins plugins
           * A reference to a "model" Pipeline plugin
           * Improve instructions for student interaction on mailing list
           ** Maybe one thread per student application instead of one thread per project proposal with multiple students on the same thread
           * How to write documentation for the student project
           ** how to document the project itself
           ** how to write blog posts on the jenkins website
           * Formal expectations
           ** application period expectations
           *** we expect a proposal that includes a description and a proposed schedule
           *** good communication with potential mentors
           ** community bonding period expectations
           *** we expect a detailed design document, updated schedule
           *** regular communication with mentor
           *** pair coding
           ** coding periods expectations
           *** code contributions frequency
           *** PR expectations
           *** status updates frequency
           *** blog post frequency
           *** slides and presentation (once per coding period, maybe add one after community bonding)

          Feedback to all orgs from Google:
           * Setting up a general set of code submission rules (formatting, proper commenting, documentation ..etc) and show some "good examples" to students
           * Stress the importance of IRC (or your community's chat channel) students commented they didn't realize how helpful it was until late in the program and they wished they'd been active in the channels from the beginning.
           * Clear instructions on setting up the work environment

           
          The GSoC student page should contain:
           * Links to 
           ** [https://wiki.jenkins.io/display/JENKINS/Plugin+tutorial]
           ** [https://jenkins.io/doc/developer/tutorial/]
           ** [https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins]
           ** [https://wiki.jenkins.io/display/JENKINS/Beginners+Guide+to+Contributing]
           ** [https://jenkins.io/project/governance/]
           * A reference to a coding style guideline for writing jenkins plugins
           * A reference to a "model" Pipeline plugin
           * Improve instructions for student interaction on mailing list
           ** Maybe one thread per student application instead of one thread per project proposal with multiple students on the same thread
           * How to write documentation for the student project
           ** how to document the project itself
           ** how to write blog posts on the jenkins website
           * Formal expectations
           ** application period expectations
           *** we expect a proposal that includes a description and a proposed schedule
           *** good communication with potential mentors
           ** community bonding period expectations
           *** we expect a detailed design document, updated schedule
           *** regular communication with mentor
           *** pair coding
           ** coding periods expectations
           *** code contributions frequency
           *** PR expectations
           *** status updates frequency
           *** blog post frequency
           *** slides and presentation (once per coding period, maybe add one after community bonding)
           * Add list of important recordings
           ** on plugin dev and release
           ** past years' evaluations

          Feedback to all orgs from Google:
           * Setting up a general set of code submission rules (formatting, proper commenting, documentation ..etc) and show some "good examples" to students
           * Stress the importance of IRC (or your community's chat channel) students commented they didn't realize how helpful it was until late in the program and they wished they'd been active in the channels from the beginning.
           * Clear instructions on setting up the work environment

           
          deepchip Martin d'Anjou made changes -
          Description The GSoC student page should contain:
           * Links to 
           ** [https://wiki.jenkins.io/display/JENKINS/Plugin+tutorial]
           ** [https://jenkins.io/doc/developer/tutorial/]
           ** [https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins]
           ** [https://wiki.jenkins.io/display/JENKINS/Beginners+Guide+to+Contributing]
           ** [https://jenkins.io/project/governance/]
           * A reference to a coding style guideline for writing jenkins plugins
           * A reference to a "model" Pipeline plugin
           * Improve instructions for student interaction on mailing list
           ** Maybe one thread per student application instead of one thread per project proposal with multiple students on the same thread
           * How to write documentation for the student project
           ** how to document the project itself
           ** how to write blog posts on the jenkins website
           * Formal expectations
           ** application period expectations
           *** we expect a proposal that includes a description and a proposed schedule
           *** good communication with potential mentors
           ** community bonding period expectations
           *** we expect a detailed design document, updated schedule
           *** regular communication with mentor
           *** pair coding
           ** coding periods expectations
           *** code contributions frequency
           *** PR expectations
           *** status updates frequency
           *** blog post frequency
           *** slides and presentation (once per coding period, maybe add one after community bonding)
           * Add list of important recordings
           ** on plugin dev and release
           ** past years' evaluations

          Feedback to all orgs from Google:
           * Setting up a general set of code submission rules (formatting, proper commenting, documentation ..etc) and show some "good examples" to students
           * Stress the importance of IRC (or your community's chat channel) students commented they didn't realize how helpful it was until late in the program and they wished they'd been active in the channels from the beginning.
           * Clear instructions on setting up the work environment

           
          The GSoC student page should contain:
           * Links to 
           ** [https://wiki.jenkins.io/display/JENKINS/Plugin+tutorial]
           ** [https://jenkins.io/doc/developer/tutorial/]
           ** [https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins]
           ** [https://wiki.jenkins.io/display/JENKINS/Beginners+Guide+to+Contributing]
           ** [https://jenkins.io/project/governance/]
           * A reference to a coding style guideline for writing jenkins plugins
           * A reference to a "model" Pipeline plugin
           * Improve instructions for student interaction on mailing list
           ** Maybe one thread per student application instead of one thread per project proposal with multiple students on the same thread
           * How to write documentation for the student project
           ** how to document the project itself
           ** how to write blog posts on the jenkins website
           * Formal expectations
           ** application period expectations
           *** we expect a proposal that includes a description and a proposed schedule
           *** good communication with potential mentors
           ** community bonding period expectations
           *** we expect a detailed design document, updated schedule
           *** regular communication with mentor
           *** pair coding
           ** coding periods expectations
           *** code contributions frequency
           *** PR expectations
           *** status updates frequency
           *** blog post frequency
           *** slides and presentation (once per coding period, maybe add one after community bonding)
           * Add list of important recordings
           ** on plugin dev and release
           ** past years' evaluations
           ** how to do extension points
           **

          Feedback to all orgs from Google:
           * Setting up a general set of code submission rules (formatting, proper commenting, documentation ..etc) and show some "good examples" to students
           * Stress the importance of IRC (or your community's chat channel) students commented they didn't realize how helpful it was until late in the program and they wished they'd been active in the channels from the beginning.
           * Clear instructions on setting up the work environment

           
          deepchip Martin d'Anjou made changes -
          Assignee Martin d'Anjou [ deepchip ]
          deepchip Martin d'Anjou made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          Hide
          deepchip Martin d'Anjou added a comment -

          See https://github.com/jenkins-infra/jenkins.io/pull/1905

          Not finished yet. The big items that are still needed are:

          • links to past year's presentations and slides to serve as example
          • Coding style guidelines
          • How to write blog posts on jenkinsio, how to write documentation for the gsoc project
          Show
          deepchip Martin d'Anjou added a comment - See https://github.com/jenkins-infra/jenkins.io/pull/1905 Not finished yet. The big items that are still needed are: links to past year's presentations and slides to serve as example Coding style guidelines How to write blog posts on jenkinsio, how to write documentation for the gsoc project
          Hide
          deepchip Martin d'Anjou added a comment -

          The latest pushes  on the aforementionned pull-request add the missing elements listed in the comment above.

          Show
          deepchip Martin d'Anjou added a comment - The latest pushes  on the aforementionned pull-request add the missing elements listed in the comment above.
          oleg_nenashev Oleg Nenashev made changes -
          Project Jenkins [ 10172 ] Jenkins Website [ 10401 ]
          Key JENKINS-54287 WEBSITE-595
          Workflow JNJira + In-Review [ 232337 ] WEBSITE: Software Development Workflow [ 233410 ]
          Component/s content [ 20860 ]
          Component/s other [ 15490 ]
          oleg_nenashev Oleg Nenashev made changes -
          Status In Progress [ 3 ] Done [ 10004 ]
          Resolution Fixed [ 1 ]

            People

            • Assignee:
              deepchip Martin d'Anjou
              Reporter:
              deepchip Martin d'Anjou
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: