X Tutup
Skip to content

DOC: update new contributor guidance re timelines, AI, reaching out#31163

Merged
timhoffm merged 1 commit intomatplotlib:mainfrom
story645:contrib-guide
Feb 25, 2026
Merged

DOC: update new contributor guidance re timelines, AI, reaching out#31163
timhoffm merged 1 commit intomatplotlib:mainfrom
story645:contrib-guide

Conversation

@story645
Copy link
Copy Markdown
Member

@story645 story645 commented Feb 15, 2026

PR summary

Incorporates timeline/complexity discussion from #29686 (comment),
attempts to direct complete newbies to talk to us before they try to tackle an issue, and updates the AI policy to encourage using direct translations.

draft cause I haven't built the docs locally yet

PR checklist

@github-actions github-actions bot added the Documentation: devdocs files in doc/devel label Feb 15, 2026
@story645 story645 marked this pull request as draft February 15, 2026 21:09
@story645 story645 force-pushed the contrib-guide branch 2 times, most recently from 56c8e27 to ce07f90 Compare February 15, 2026 23:23
@story645 story645 force-pushed the contrib-guide branch 3 times, most recently from b995981 to 2ed8092 Compare February 15, 2026 23:35
@story645 story645 closed this Feb 15, 2026
@story645 story645 reopened this Feb 15, 2026
@story645
Copy link
Copy Markdown
Member Author

story645 commented Feb 15, 2026

I really need to stop reusing branch names, it creates all sorts of git horribleness (I never remember I'm reusing them)

@story645 story645 marked this pull request as ready for review February 17, 2026 18:07
@timhoffm
Copy link
Copy Markdown
Member

I really need to stop reusing branch names, it creates all sorts of git horribleness (I never remember I'm reusing them)

Try more specific ones, e.g. here doc-contrib-timeline. That significantly reduces the likelihood of collisions. It also helps you remember what the branch was about.

Comment on lines +301 to +302
complicated issue for your first contribution - please ask in the incubator
channel if you need help gauging the complexity of the work.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Suggested change
complicated issue for your first contribution - please ask in the incubator
channel if you need help gauging the complexity of the work.
complicated issue for your first contribution - please ask in the *new
contributor channel* if you need help gauging the complexity of the work.

That's what it's called above.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

it's called incubator on gitter/discourse, so Ill streamline to that

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Semi OT: Is incubator a good name? It’s rather an advanced word that people with little English knowledge may not know. Also I’m not clear how welcoming it sounds.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

I dunno, it's what we decided on back when @melissawm was contributor experience lead the first time. We can discuss again, but I think is out of scope here.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Re: name, I don't have strong opinions! We could try "New contributor space" or something if it makes it clearer.

As far as instructions go, I'm not sure it's clear to new contributors that the incubator is a chat on the discourse interface (I didn't know discourse had a chat feature until a month ago!)

This should probably be mentioned here: https://matplotlib.org/devdocs/devel/contribute.html#contributor-incubator but I think can be a follow-up.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Yeah, I think name change is maybe a separate discussion and we should probably discuss on the call if it's time to move the chat links to discourse (I think we've adopted it at this point)

@story645
Copy link
Copy Markdown
Member Author

story645 commented Feb 20, 2026

It also helps you remember what the branch was about.

I remembered what this branch is about, I just forgot I'd (and apparently other people) had used this name before :/ locally I renamed it to contrib-timeline as part of cleaning up my git mess.

@story645 story645 force-pushed the contrib-guide branch 2 times, most recently from 78aacbb to 05ca319 Compare February 23, 2026 19:41
@story645
Copy link
Copy Markdown
Member Author

updated w/ the second commit from #31124 which pulled in "please do direct translation" guidance cause I think it makes more sense here

@story645 story645 changed the title DOC: update new contributor guidance w/ tighter timelines DOC: update new contributor guidance re timelines, AI, reaching out Feb 23, 2026
ncm + use direct translations

 Co-authored-by: Ruth Comer <10599679+rcomer@users.noreply.github.com>
 Co-authored-by: Tim Hoffmann <2836374+timhoffm@users.noreply.github.com>
@timhoffm timhoffm merged commit 1017fe1 into matplotlib:main Feb 25, 2026
20 checks passed
@story645 story645 deleted the contrib-guide branch February 25, 2026 21:21
@QuLogic QuLogic added this to the v3.11.0 milestone Feb 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Documentation: devdocs files in doc/devel

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

X Tutup