GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Code of Conduct, default Issue/PR templates by APickledWalrus · Pull Request #2 · SkriptLang/.github

Conversation

@APickledWalrus

@APickledWalrus APickledWalrus commented Jul 17, 2025 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Member

Given our growing community spaces and presence, I have taken the time to draft a Code of Conduct for our community. The goal is to briefly describe the community we want to build, covering what behavior we want to promote, what behavior we want to avoid, and what we will do to preserve it.
better link for viewing: https://github.com/SkriptLang/.github/blob/feature/default-templates/CODE_OF_CONDUCT.md

I have also drafted generic issue and pull request templates to be used when a repository does not have one (simplifies repository management). I have attempted to strike a balance between being generic while also providing enough information for it to actually be useful across various repositories.
There are two types of issues: bug reports and suggestions. Blank issues are disabled. The pull request template is slightly modified from Skript's new template. For help/support, a link to the SkriptLang Discord is included.

Any feedback is welcome (and encouraged!)

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
Efnilite reacted with thumbs up emoji
All reactions
  • 👍 1 reaction
APickledWalrus added 2 commits July 17, 2025 13:30
@APickledWalrus
First draft
f0095fb
@APickledWalrus
Wording tweaks
dfa34ba
@EquipableMC

EquipableMC commented Jul 17, 2025

Copy link
Copy Markdown

I don't know if this is out of scope or falls under this PR, but could we get something (like an FAQ or guide) that describes how PRs should be done for Skript (and other projects) to also help guide people that want to improve Skript and other projects? Just a thought/suggestion.
All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
@APickledWalrus

APickledWalrus commented Jul 17, 2025

Copy link
Copy Markdown
Member Author

I don't know if this is out of scope or falls under this PR, but could we get something (like an FAQ or guide) that describes how PRs should be done for Skript (and other projects) to also help guide people that want to improve Skript and other projects? Just a thought/suggestion.

The contributing guide should cover this. Skript's is a bit outdated though. A generic one could be useful, though for the Skript repository we might want one more tailored. Regardless, it is on my list to get that updated.
All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
erenkarakal
erenkarakal approved these changes Jul 17, 2025
View reviewed changes
Comment thread .github/ISSUE_TEMPLATE/bug-report.yml Resolved

Uh oh!

There was an error while loading. Please reload this page.
Comment thread .github/PULL_REQUEST_TEMPLATE.md Resolved

Uh oh!

There was an error while loading. Please reload this page.
Comment thread CODE_OF_CONDUCT.md Resolved

Uh oh!

There was an error while loading. Please reload this page.
Comment thread CODE_OF_CONDUCT.md Resolved

Uh oh!

There was an error while loading. Please reload this page.
@APickledWalrus @erenkarakal
Apply corrections from review
7291353 
Co-authored-by: Eren <[email protected]>
@EquipableMC

EquipableMC commented Jul 17, 2025

Copy link
Copy Markdown

I don't know if this is out of scope or falls under this PR, but could we get something (like an FAQ or guide) that describes how PRs should be done for Skript (and other projects) to also help guide people that want to improve Skript and other projects? Just a thought/suggestion.

The contributing guide should cover this. Skript's is a bit outdated though. A generic one could be useful, though for the Skript repository we might want one more tailored. Regardless, it is on my list to get that updated.

Alright, I just did not know what fell under what lol, but good to know, thank you!
APickledWalrus reacted with heart emoji
All reactions
  • ❤️ 1 reaction

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
Efnilite
Efnilite approved these changes Jul 17, 2025
View reviewed changes

@Efnilite Efnilite left a comment

Copy link
Copy Markdown
Member

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice work pickle 🙏

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
All reactions
Comment thread .github/PULL_REQUEST_TEMPLATE.md Resolved

Uh oh!

There was an error while loading. Please reload this page.
@APickledWalrus @Efnilite
Remove accidental extra space
cb7f32f 
Co-authored-by: Efnilite <[email protected]>
sovdeeth
sovdeeth requested changes Jul 30, 2025
View reviewed changes
Comment thread CODE_OF_CONDUCT.md

@sovdeeth sovdeeth Jul 30, 2025 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Member

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is a solid base. I would like to see more elaboration on scope (i.e. applies to github, discord, etc.).

See astropy's:

This code of conduct applies to all community situations online and offline, including mailing lists, forums, social media, conferences, meetings, associated social events, and one-to-one interactions.

or Contributor Covenant's:

This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public or other spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.

It's already covered, but I would also like some phrasing in Standards that specifically calls out being supportive and welcoming to new contributors.

Some language around proper accreditation/citation where appropriate and not plagiarizing code would also be welcome. I think Contributor Covenant v3 has a good set of standards we could pull from (and cite them at the end if we do).

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
All reactions
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@sovdeeth sovdeeth sovdeeth requested changes
+2 more reviewers
@Efnilite Efnilite Efnilite approved these changes
@erenkarakal erenkarakal erenkarakal approved these changes
Reviewers whose approvals may not affect merge requirements

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

5 participants

@APickledWalrus @EquipableMC @sovdeeth @Efnilite @erenkarakal
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.