Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Maintenance] Add acceptable milestones and proper label filters #9

Open
1 of 2 tasks
xames3 opened this issue Oct 27, 2024 · 2 comments
Open
1 of 2 tasks

[Maintenance] Add acceptable milestones and proper label filters #9

xames3 opened this issue Oct 27, 2024 · 2 comments
Assignees
Labels
awaiting changes pull requests that need updates or corrections based on feedback community contributions from the community or enhancements that support community engagement discussion needed pull requests that need community or team input before moving forward enhancement enhancements to existing functionality or the addition of new features or content good first issue pull requests related to issues that are ideal for newcomers to start with help wanted extra attention is needed and appreciate some help low priority pull requests that are less critical and can wait if necessary miscellaneous miscellaneous changes and some of the general inner workings open science contributions that enhance transparency, reproducibility, or accessibility in line with Open Science

Comments

@xames3
Copy link
Collaborator

xames3 commented Oct 27, 2024

  • this is a trivial issue with fewer key deliverables:

    • setup appropriate labels for issues and pull requests. we can follow a similar strategy for the repository labels mentioned on the CreativeCommons site here. although, we don't need to comply totally to their schema (<emoji>⎵<category>:⎵<name>) but can use it as a baseline for relevant flows.
    • although, this is not as significant as the other task, but we need to setup milestones for the project. as of now, no details about milestones are found pertaining to open-source and open-science, which does seem appropriate for our project. need to discuss this internally in the next meeting or maybe ask the @ciesin-geospatial core development team for this information.
@xames3 xames3 self-assigned this Oct 27, 2024
@xames3 xames3 converted this from a draft issue Oct 27, 2024
@xames3 xames3 added enhancement enhancements to existing functionality or the addition of new features or content good first issue pull requests related to issues that are ideal for newcomers to start with help wanted extra attention is needed and appreciate some help awaiting changes pull requests that need updates or corrections based on feedback community contributions from the community or enhancements that support community engagement discussion needed pull requests that need community or team input before moving forward low priority pull requests that are less critical and can wait if necessary open science contributions that enhance transparency, reproducibility, or accessibility in line with Open Science miscellaneous miscellaneous changes and some of the general inner workings labels Oct 27, 2024
@xames3 xames3 moved this to Backlog in TOPS SCHOOL NLU Tasks Nov 1, 2024
@xames3
Copy link
Collaborator Author

xames3 commented Nov 10, 2024

  • labels have already been added to the project. the @ciesin-geospatial team needs to decide on the deliverable milestones for the repository. can be moved to in progress.

@xames3 xames3 moved this from Todo to In Progress in Open-Source Projects Kanban Board Nov 10, 2024
@xames3 xames3 moved this from Backlog to Ready in TOPS SCHOOL NLU Tasks Nov 26, 2024
@jfmartinez4 jfmartinez4 moved this from Ready to In progress in TOPS SCHOOL NLU Tasks Dec 9, 2024
@jfmartinez4
Copy link
Collaborator

@xames3 I think we can start with the same labels with have in the NLU Task project.
Priority: 0, 1, 2
Module: Main page (and general), M1, M2, M3, M4, Community Led, Mini lessons.
I like the friendliness label. I would suggest initially keeping it to just a few.

As for milestones, I think we can discuss further as the new year approaches with a new cohort of students.
Main goals would be:

  • Finish translating qmd to sphinx (Druvil)
  • Contibution guidelines (Akshay)
  • Create community-led lesson (with spring students)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting changes pull requests that need updates or corrections based on feedback community contributions from the community or enhancements that support community engagement discussion needed pull requests that need community or team input before moving forward enhancement enhancements to existing functionality or the addition of new features or content good first issue pull requests related to issues that are ideal for newcomers to start with help wanted extra attention is needed and appreciate some help low priority pull requests that are less critical and can wait if necessary miscellaneous miscellaneous changes and some of the general inner workings open science contributions that enhance transparency, reproducibility, or accessibility in line with Open Science
Projects
Status: In progress
Development

No branches or pull requests

3 participants