Skip to content

GSoC feedback on the pvlib contribution process #2078

Closed

Description

@AdamRJensen

This issue is for the 2024 cohort of GSoC students to document challenges related to contributing to pvlib.

The aim is to learn about the challenges that new contributors face, and hopefully be able to make changes to make the process easier.

2024 GSoC students: @echedey-ls, @IoannisSifnaios, @RDaxini
Mentors: @kandersolar, @AdamRJensen

Activity

  1. IoannisSifnaios commented on Jun 6, 2024

    @IoannisSifnaios
    Member

    I think I am missing some documentation guidelines. E.g., when a parameter in a function is unitless, how to you denote that? Right now, I found three different ways: [-], [unitless], or nothing.
    [Adam] - we should make a template function that showcases our preferences in how to write a function, e.g., function name, units, etc.

  2. added
    GSoCContributions related to Google Summer of Code.
    on Jun 6, 2024
  3. cwhanse commented on Jun 6, 2024

    @cwhanse
    Member

    I prefer [unitless] but I don't think we've made a consensus choice.

    @pvlib/pvlib-core your vote? [unitless], [-] or nothing?

  4. locked and limited conversation to collaborators on Jun 6, 2024
  5. converted this issue into a discussion #2081 on Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    GSoCContributions related to Google Summer of Code.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions