Call for Maintainers - Githubissues

mAAdhaTTah commented 6 years ago

As you may have noticed, I have not had a lot of time to spend on WPGHS lately. I've been primarily focused on wp-gistpen and getting that plugin out of beta and finalized. Given that, plus other life obligations, it's been tough to find time to work on WPGHS. While I would consider it feature-complete at this point, there are certainly some lingering issues that could use some love and attention.

Given all this, I'm looking for people would be interested in working on and maintaining WPGHS. I still use the plugin on my personal site, so I'm not going anywhere, but I could use some help. Please comment below if you'd be interested in pitching in.

In addition to the current open issues, there are a few areas that I think need work:

[ ] Developer documentation
- Currently, the filters are documented in the wiki but I think that could use some work. I've been kind of assuming developer-focused userbase but I don't think that's fair, so the documentation would benefit from being more user-friendly.
[ ] Testing infrastructure
- Part of my reluctance to working on WPGHS is testing new changes can be very time consuming. There's a lot of manual testing required to make sure imports & exports continue to function as expected. I've often dreamed of setting up some kind of integration / scenario testing, run in TravisCI, that would add posts to WP and check if they appear in a GitHub repo, and add stuff to the repo and check if they appeared on the WP site. I don't know how (or if) this is feasible, but it would be extremely helpful for the plugin's continued development.
[ ] Performance
- There are a few areas where batching things together could avoid some timeouts (#167 & #94). We're also relying on the cache quite a bit, which may not be appropriate if the sites don't have an object cache installed. This may be worth revisiting.

Plus obviously there are some open issues worth investigating.

If you're interested, please comment below. The only rule I have is any code that gets committed should be reviewed and approved by one other committer before being merged (and obviously don't commit directly to master :) ).

mAAdhaTTah commented 6 years ago

@litefeel I noticed you have a fork of sorts. Any interest in combing efforts here?

zcourts commented 5 years ago

@mAAdhaTTah - just starting to try and use this, happy to try and help but first I'm more interested in adding better controls over what gets exported and over reverse deletes, see #206.

It'll be a backburner task in our sprints but I'll be adding some stuff to our fork in the next sprint. (PHP's rusty but should only need a weekend refresher)

mAAdhaTTah commented 4 years ago

@zcourts Hey I totally missed this comment at the time. Are you still interested in becoming a maintainer?

rfm-bot commented 4 years ago

🚧 Is this repo looking for support? Hello, we created this issue becuase the user @sospedra told us you are calling for maintainers. ✅ If you're looking for collaborators no action is required. 👮🏻‍♂️ If this repo is well-supported please put a comment here https://github.com/sospedra/rfm/issues/59 and we'll close it immediately. Sorry for any inconvinience. We understand this message can feel spammy but we really think is good to double-check first with the current owners :)

olivierbenard commented 1 year ago

Hello @mAAdhaTTah and first, thank you for this very cool project 👍🏻

Looking at the dates, I assume the project is no longer maintained and not working anymore?

E.g. if I look at my webhooks recent deliveries, I can see the following response body:

{"success":false,"data":[]}

but it seems that I got the configuration correctly set up though. Thus, my confusion.

Kind regards, Olivier

mAAdhaTTah commented 1 year ago

@olivierbenard Honestly, no idea. I haven't worked in WordPress or PHP in a while now, sorry.

olivierbenard commented 1 year ago

Thank you for your response @mAAdhaTTah :)

At the end I decided to go down a different road, using Python and the Wordpress API since I wanted to avoid dealing with PHP. I do not have 100% coverage e.g. there is no WP -> Github synchronisation yet but if you're curious you can have a look there: https://github.com/olivierbenard/wordpress-github-sync.

HammyHavoc commented 5 months ago

Thank you for your response @mAAdhaTTah :)

At the end I decided to go down a different road, using Python and the Wordpress API since I wanted to avoid dealing with PHP. I do not have 100% coverage e.g. there is no WP -> Github synchronisation yet but if you're curious you can have a look there: https://github.com/olivierbenard/wordpress-github-sync.

Got a 404 on your repository link.

mAAdhaTTah / wordpress-github-sync

Call for Maintainers #193