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.
Not everything is open source. MediaWiki is, the theme we use is, but the content on ProleWiki or the stuff ProleWiki makes is not always, for example our self-made templates (which are like functions that you can use on wiki pages to display content). We've made some contributions to our own git when we've had to change some plugins code (the plugins are open source and so are our contributions there) but the ideas we would be developing would likely not be open source just yet.
Complexity depends on how familiar with MediaWiki one is, but I think the main difficulty will be resource management so as not to overwhelm the server.
I see. I mentioned it more to know if I could look at the code you wanted to expand on sometime.
It would be completely custom code being created ๐