> On Mar 8, 2022, at 8:55 AM, Sean Busbey <sbus...@apple.com.INVALID> wrote:
>
>
> Hi folks!
>
> Right now we have contributor guidelines in a couple of places:
>
> * source tree as CONTRIBUTING.md and DEVNOTES, visible on GitHub
> * confluence on a HOW TO CONTRIBUTE and Developer Section pages, linked from
> the website
I would suggest the CONTRIBUTING.md be updated and the confluence stuff go away.
>
> We also have a few different ways of accepting contributions
>
> * JIRA patches - review on JIRA or review in review board
> * GitHub PRs
I am not aware that review board is still used.
>
> It looks like only the JIRA/reviewboard workflow is covered in our
> contribution guide, but the GitHub PR route has come to dominate.
Correct. I think review board was replaced by GitHub PRs.
>
> I’d like to update our contribution guides to give new folks a clear single
> path to on ramp.
I’m OK with that.
>
> What do folks think about taking a GitHub centric approach?
+1
>
> Given our current community activity levels, IMHO minimizing friction from
> the audience of folks who have a GitHub account gives us the easiest path to
> casual contributions.
+1
>
> To start I’d suggest:
>
> - remove review board use
As I said, I think that is just a documentation issue.
> - suggest all changes as PRs
Generally, I am OK with that. As there have been no commits and no other
participants I didn’t see the point of doing PRs for all the work I have done
so far for 1.10.0 as they would still be awaiting approval. In fact, I sent an
email to the Flume private list in November informing them I was moving to CTR
for this work due to the lack of activity in the project. I got approval for
that from a couple of the active PMC members. However, I am happy to create PRs
so you can review what I do before it gets committed from here.
> - consolidate our project guidelines in CONTRIBUTING.md and DEVNOTES
+1
Ralph
