Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to officially create the PSC #39

Open
cvvergara opened this issue Nov 19, 2020 · 4 comments
Open

How to officially create the PSC #39

cvvergara opened this issue Nov 19, 2020 · 4 comments

Comments

@cvvergara
Copy link
Member

cvvergara commented Nov 19, 2020

  • Mail to all previous PSC to ask if they are continuing
  • Example: Top X commiters as PSC
  • One the first PSC meeting is motion approve others no commiters like Daniel, Regina,
@cvvergara
Copy link
Member Author

has to be done before the application

@dkastl
Copy link
Member

dkastl commented Nov 20, 2020

Well, it's not only because I'm "affected", but I think every Open Source project should try to achieve diversity in the way "contribution" is measured. Commits to a repository are of course very straight-forward metrics, but they can be bad for diversity in roles.

So what's important for a PSC member? Maybe things like this:

  • be active and responsive
  • be reliable and transparent
  • represent a group in the pgRouting project (users/developers)
  • have a vision and goals
  • enjoy pgRouting community

Being one of the top commiter qualifies for a lot of these points, but doesn't necessarily include other points.

@dkastl
Copy link
Member

dkastl commented Nov 20, 2020

For example, start with what Github provides us: https://github.com/pgRouting/pgrouting/graphs/contributors
From the first 10 contributors I'm not even sure if all of them are still interested. And I miss many others.

@woodbri
Copy link

woodbri commented Nov 20, 2020

It is good to have some non-commiter power users on the PSC as advocates for the user base. This has worked well in the mapserver PSC. A developers solution is not always the best user solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants