Pysal: NumFOCUS affiliation

[slumnitz]

In order to become affiliated with NumFOCUS, we need to send an email to NumFOCUS explaining how your project would answer the following questions:

• Is the project focused on science or general development?
• How large and diverse is the project in terms of its contributor base?
• Does the project accept community contributions?
  
  
  
  • yes
  
  
• What is the governance structure of the project, and is it documented?
  
  
  
  • Discussion in meeting
  
  
  • potentially fixed place necessary for written governance structure, e.g. on Pysal.org
  
  
• Does the project use an OSI approved license?
• What communication channels does the project have with the public/its users?
  
  
  
  • Gitter channel
  
  
  • Google group
  
  
  • Github
  
  
  • pysal.org project website
  
  
  • google hangouts monthly dev meetings
  
  
• Does the project have a public code of conduct?
  
  
  
  • In progress
  
  

[jGaboardi]

PySAL Dev Meeting: January 4th, 2019

[sjsrey]

In order to become affiliated with NumFOCUS, we need to send an email to NumFOCUS explaining how your project would answer the following questions:

• Is the project focused on science or general development?
  The project is focused on geospatial data science.
• How large and diverse is the project in terms of its contributor base?
  The PySAL project has 22 core developers. Age distribution runs from 60+ to masters and undergraduate students. Gender distribution: 18 male, 4 female
• Does the project accept community contributions?
  
  
  
  • yes
  
  
• What is the governance structure of the project, and is it documented?
  
  
  
  • Discussion in meeting
  
  
  • potentially fixed place necessary for written governance structure, e.g. on Pysal.org
  
  
• Does the project use an OSI approved license?
  
  
  
  • Yes: BSD 3-Clause License
  
  
• What communication channels does the project have with the public/its users?
  
  
  
  • Gitter channel
  
  
  • Google group
  
  
  • Github
  
  
  • pysal.org project website
  
  
  • google hangouts monthly dev meetings
  
  
• Does the project have a public code of conduct?
  
  
  
  • In progress
  
  

[jGaboardi]

@slumnitz @sjsrey Did we need/want to schedule a time tomorrow to discuss this (as mentioned in the Friday meeting)?

[sjsrey]

@slumnitz @sjsrey Did we need/want to schedule a time tomorrow to discuss this (as mentioned in the Friday meeting)?

Sure: I am available PST 10-12, 3-6.

[jGaboardi]

I am available during those time as well.

How about you, @slumnitz ?

[slumnitz]

Sorry, I can do tomorrow only after 7pm. How about Monday any time from 7 am onwards?

[sjsrey]

I think we don't necessarily have to meet yet. We could draft the letter and identify the next steps on posting the COC. How does that sound to both of you?

[slumnitz]

Sounds good to me. I am happy to give the government structure document a go on Monday. I would potentially draft it similarly to the COC so everyone can have a look?

[slumnitz]

Who is the maintainer of the Pysal-dev google group?

[sjsrey]

Who is the maintainer of the Pysal-dev google group?

[email protected]

[sjsrey]

I can add other owners. Are you and @jGaboardi ok with being added?

[jGaboardi]

@sjsrey yes, I’m ok with being added.

_{Sent with GitHawk}

[slumnitz]

@sjsrey me too!

[sjsrey]

You both now are owners.

[jGaboardi]

[WIP] * Please edit as necessary *

~Repurposing the pysal-dev googlegroup~

• ~rename (Information --> General Information)~

  • ~pysal-CoC~
  • ~other ideas?~

• ~archive off?~

  • ~Content Control --> Archive Options~

• ~enable multiple channels~

  • ~public forum visible to all~
  • ~private forum visible only to owners~

• ~email option~

  • ~should this simply be the private forum above?~

• ~permissions~

  • ~Basic~
  • ~Posting~
  • ~Moderation~
  • ~Access~

[slumnitz]

Hello @jGaboardi and @sjsrey,

I took some time looking through governance structures of other projects. Especially Scipy and Jupyter seem to have similar quite good models addressing a formal and tested governance structure. I would vote for adapting the structure to have a Benevolent Dictator for Life and decisions are generally made with consensus of core developers. I am not sure if we need a steering council considering the size of our project. maybe we can adapt this later when the contributor base skyrockets ;) (I feel we already have that structure just did not find the matching name yet). I am happy to reformulate this for PySAL so we can discuss it with everyone else.

What we wrote during the meeting seems to maybe in retrospect fit more under the submodule template how a release has to be done. I can include some additional comments on how different packages interact under the project umbrella.

Has PySAL ever been funded or are we in general open to funding, then I would include a funding/ collaboration part.

[jGaboardi]

@slumnitz excellent! Do you have this written up in a googledoc or hackmd so that we can get a look at it?

[sjsrey]

Hello @jGaboardi and @sjsrey,

I took some time looking through governance structures of other projects. Especially Scipy and Jupyter seem to have similar quite good models addressing a formal and tested governance structure. I would vote for adapting the structure to have a Benevolent Dictator for Life and decisions are generally made with consensus of core developers. I am not sure if we need a steering council considering the size of our project. maybe we can adapt this later when the contributor base skyrockets ;) (I feel we already have that structure just did not find the matching name yet). I am happy to reformulate this for PySAL so we can discuss it with everyone else.

Sounds great to me.

What we wrote during the meeting seems to maybe in retrospect fit more under the submodule template how a release has to be done. I can include some additional comments on how different packages interact under the project umbrella.

+1

Has PySAL ever been funded or are we in general open to funding, then I would include a funding/ collaboration part.

Yes, see the bottom of the landing page.

[jGaboardi]

cross references pysal/pysal.github.io#81

[sjsrey]

Updates:

March 9 - we applied for Affiliated Project status
April 10 - we were notified we would hear back in 2-3 weeks.

[slumnitz]

closing, since PySAL has been approved for NumFOCUS affiliation, @sjsrey finalises informations exchange now.