add CONTRIBUTING.md #626
No reviewers
Labels
No labels
bazel
bluetooth
board settings
boot_stage2
bug
build
c++
can't reproduce
clang
clib-interface
cmsis
code cleanliness
code size
compiler version issues
cyw43_driver
debug
discussion
documentation
duplicate
dynamic_clock
elf2uf2
enhancement
errata
filesystem
flash layout
floating point
FreeRTOS
hardware_adc
hardware_claim
hardware_clocks
hardware_dma
hardware_exception
hardware_flash
hardware_gpio
hardware_i2c
hardware_irq
hardware_pio
hardware_pwm
hardware_rcp
hardware_rtc
hardware_spi
hardware_sync
hardware_uart
hardware_vreg
hardware_watchdog
hardware_xosc
help wanted
host
IAR
installation
invalid
linker scripts
lto
lwip
mbedtls
missing API
needs reporter detail
networking
newlib
newlib-multicore
non-c
non-cmake
non-gcc
openocd
orphan PR
OS integration
pico_async_context
pico_base
pico_binary_info
pico_flash
picolibc
pico_lwip
pico_malloc
pico_multicore
pico_printf
pico_runtime
pico_stdio
pico_stdio_usb
pico_sync
pico_time
pico_util
pioasm
port
question
review
review2
rtos interop
runtime init
static library
svd
test
tinyusb
vscode
wifi integration
wontfix
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-raspberrypi/pico-sdk!626
Loading…
Reference in a new issue
No description provided.
Delete branch "contributing.md"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
@ -0,0 +1,25 @@# Contributing to Raspberry Pi Pico C/C++ SDK"ideally a some code" -> "ideally some code"
@ -0,0 +1,25 @@# Contributing to Raspberry Pi Pico C/C++ SDKCould mention space between
)and{? 🤷@ -0,0 +1,25 @@# Contributing to Raspberry Pi Pico C/C++ SDKyeah, not feeling like listing everything right now - i think "match existing" covers it
@kilograham You might want to restructure it somewhat, see for instance the CONTRIBUTING.md file in the documentation repo. There we have an introduction, instructions on how we want you to contribute, the definition of the type of content we want, and then the content we don't want, and a reminder about what licensing it's going to be under.
@kilograham I've redrafted based on our email discussion. Hope that suits? It now (somewhat) mirrors the documentation repo version.
i removed "pico pico", but also remove the first paragraph since that sort of stuff is already in the README
@ -0,0 +1,25 @@# Contributing to Raspberry Pi Pico C/C++ SDKShould be "Raspberry Pi Pico C/C++ SDK"
"In order to contribute new or updated code, you must first create a GitHub account..."
Seems likely that the people with the technical ability to be submitting SDK PRs, will also be technical enough to already have a GitHub account? 🤷