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

Maintain community fork #153

Closed
daniel-sc opened this issue Jan 4, 2019 · 16 comments
Closed

Maintain community fork #153

daniel-sc opened this issue Jan 4, 2019 · 16 comments

Comments

@daniel-sc
Copy link
Member

Hello everyone,

as there are quite some people that actively use this PHP Podio client and this repo is not officially maintained any more, I'd suggest to create a community fork. Anyone motivated to step forward as maintainer?

hoping for feedback

Daniel

@daniel-sc
Copy link
Member Author

@bajarang-agarwal @timosillander @rafaelmb @carlfredrikhero @jackparnell @jeff-goodman @benk-cogapp @daviferreira

anyone interested in maintaining a community fork?

(I just added active people I found in issues/PRs from 2018 here, please feel free to add more potential maintainer/contributors!)

@rafaelmb
Copy link
Member

I definitely can help

@bajarang-agarwal
Copy link
Contributor

I am also happy to help and maintaining community fork

@carlfredrikhero
Copy link
Member

I would really like to see a community fork!

@timosillander
Copy link
Contributor

I only just noticed the No Maintenance Intended badge on Podio PHP client. Damn.
I too would love to see a community fork. Not much of a coder, so not sure how much I'd be of help, mind.

@daniel-sc
Copy link
Member Author

Ok - anyone stepping forward to get this going?
If not, I can do it, but that might be slow paced.. ;-)

@daniel-sc
Copy link
Member Author

@cmchase I see you were the last one maintaining this repository - would it be possible to transfer this repository to the new podio-commmunity organization I created, so that we can maintain this php client there? Alternatively we could as well simply fork this repo, but this would mean loosing all PRs and issues and you'd need to add a reference to the community project to be well visible in the readme (a community fork that no one knows of is probably not much help..). There is some interest in a community fork - see the comments above in this issue - so it would be really cool if you could help us kicking it off!

Let me know what you think!

See: https://help.github.com/en/articles/transferring-a-repository

@jakemwp
Copy link

jakemwp commented Mar 7, 2019

I'd be happy to help maintain a community fork. I have some rough custom functions I've built on top of the existing PHP client, so feel free to reach out if this gets off the ground.

@npphases
Copy link

npphases commented Mar 8, 2019

I'm happy to help since I have been using this wrapper from the beginning of its development.

@dylannadon
Copy link

Hi @daniel-sc et al,
We are discussing this internally and will get back to you.

@dylannadon
Copy link

Hi @daniel-sc we will transfer this repo to the Podio Community organization. Could you please add me to the organization with create repo permissions?

@daniel-sc
Copy link
Member Author

Hi @dylannadon, thanks for deciding on this. I invited you to the org. If there is something else you need for this please let me know.

@dylannadon
Copy link

Done!

@ubani
Copy link
Contributor

ubani commented Mar 15, 2019

happy to help, too.

@bajarang-agarwal
Copy link
Contributor

Thanks @dylannadon

@daniel-sc Thank you for taking this initiative and we can see a lot of people are interested to help to maintain this.

@daniel-sc
Copy link
Member Author

Ok - the transfer is completed (big thanks @dylannadon !) so I'll close this issue. Thanks everyone for your offered help and support!
For discussions about (updated) contribution guidlines and other stuff, we should create new issues/PRs.

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

9 participants