labels

are usefull for people who can apply them where they can and one could say some issues may miss labels ( sorry i won't read them all to check if assertion is valid).

Using a stable release base for PR testing

i insist this is not for merging. it would quite easy to provide a build script testing various PR eg ./build-test 123 456 789 and that would maybe provide valid builds for months with pre populated ports/*/modules folder with various samples or tailored testsuites which have nothing to do in mainline tree.

You have learned all git tools ?

Good for you, i did not and i won't i feel too old for that. i use busybox, patch ( and wget/curl when platform is friendly enough to provide name resolution) and a folder full of diff i picked up here and here.

it not about avertising PR and even speak english in comments, code is all what would be expected.

forums / slacks etc ....

those are not about code, forums can go read-only/vanish anytime ( eg Playground.arduino.cc).

Everyone can submit PRs here

but not much people want to do it as merging possibility is short-lived and MIT only.

People could PR pointing to others people work, a way to promote shy people, or take away the burden of code sharing for people too busy to PR back,

no merging until original writer fix license or decide his work is ok and/or offers merging on his own.

That would be more about sharing than merging.

one big pile of outdated half-tested code samples

what's wrong with that ? did you look at cpython stdlib and PyPI closely ? using github search on that pile will be probably more helpfull than swimming in ads crowded blogs clones.

who's going to take care of that ?

Maybe here would the place for people to step up.
no need to master git, just github web interface, some social skills, extreme tolerance for beginners code, and a bit of relaxed english/C/python. More hobby spirit than "grown up committers".

#4993 js port could be used for showcasing ideas/modules/bugs.

Uh oh!

triaging : separate ideas-features-request from BUGS #4444

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions