Edit: Thanks for all the responses, I didn’t expect we had so many webdevs here lol. To complete the brief, the first thing we’ll need to do I think is upgrade the PHP which is on an EOL version. What we are looking for is someone who shows initiative, it’s how we work at ProleWiki from the admins down to the newest editors. You’ll be able and encouraged to come up with your own solutions, ours may of course not be the best we could get. Our keywords are scalability, maintenance, and optimization, always to better serve the readers.
We have tons of ideas for the future, but every time we find a developer, either they don’t know PHP (I can’t blame them) or they bail.
I’m looking for a PHP dev who wants to help out with ProleWiki. We have tons of cool ideas to really bring this show on the road, but nobody to put them into action.
Can’t guarantee we can pay you (and if we can believe me it won’t be a wage), but you get tons of perks such as being part of a cool, chill, growing community, a project bigger than any of us, and I can even write you a letter of recommendation I don’t mind.
As we look towards the future and where ProleWiki can grow and better serve its readers, we come to the conclusion we need more tech. And for that we need at least one PHP dev.
ProleWiki runs on MediaWiki and a VPS. We’re thinking of getting an S3 bucket as that seems more and more needed every day (it’s just our processes make acquiring stuff a bit slow). One thing I would want to optimize for example is image delivery.
If you’re interested hit me up.
By the time you need a PHP dev to run a MediaWiki instance you should probably ditch it for something with a more attractive language. It will be less work.
I strongly disagree with this one.
20 years in the industry, and php is still the ak47 of web. Runs anywhere, ridiculously reliable for most projects, no extra frontend shenanigans, out of the box server side rendering.
I don’t know about mediawiki specifically, but laravel projects are generally acceptable from a modern development perspective, even though setting up the dev environment can be more tricky than an out of the box vscode/ts/react setup.
Sounds like we’ve got a volunteer!
Yea… just one problem: what?
I would simply write a superior wiki platform than Wikipedia’s from scratch in Rust /s
Rust is for newbies write it all in Haskell and BASIC
Just casually duplicate this labor rq. Techbros really creating jobs for each other.
Basically anything else will be easier if you need to write custom back end things. XWiki or wikijs, even.