The ol-tech list is probably the right place to engage with potential developers. We had a brief period of re-invigoration a couple of years ago where a group of developers were granted commit privileges to the developer pages on the wiki and started getting things cleaned up.
Forking the code isn't a big deal. Forking the website is a huge deal. If there's no path to get bug fixes and enhancements (in the form of pull requests) reviewed and integrated into the deployed web site, it doesn't make any sense to invest in doing the work. The reason I, and I suspect some others, stopped being interested was that there wasn't even any way to have a conversation with the IA folks, let alone get any decisions made. There's a bunch of stuff that could be done to streamline the spam flagging and processing, do more automated spam detection, etc. The current web form reporting and lone pioneer cleaning up doesn't scale and OpenLibrary will either continue to be more and more a victim of broken window syndrome or more and more parts of the web site will get locked down until it becomes a read-only wasteland. It's sad to see because it wouldn't really take that much effort to make it a thriving and vibrant site, but IA just doesn't care. Tom On Mon, Jun 29, 2015 at 1:00 PM, jessamyn c. west <jessa...@gmail.com> wrote: > Apologies for a late reply, it seems like you've done some great work. > We can work to update the documentation. > > > What should people like me who want to contribute to the codebase be > working > > on, and who should we liaise with at OL/IA to make sure we are making > useful > > contributions? > > I'm probably the right liasing person. Right now there is no active OL > development, the main developer left in December and the backup > developer is on his way out if he hasn't left already (not really > project related afaict) and it's unclear whether even maintenance > requests/tickets are being worked on, so I've been doing triage on > bugs in addition to mostly just answering the support email that > continues to come,. > > The biggest challenge I have facing me now is the spam issue. We have > a bunch of people adding spammy entries in Korean and no good way to > either keep them out or even go back and bulk delete pattern-matched > spam. I'd love to have a tool that does this. I'm not sure if a person > working on the code would also need admin privs in terms of their > account so please let me know if that's a stumbling block. > > Just getting a group of developers looking at the code would be > incredibly helpful on my end, to have someone to bounce minor issues > off of. Let me know how I can help. > > Jessamyn > _______________________________________________ > Ol-discuss mailing list - Ol-discuss@archive.org > http://mail.archive.org/cgi-bin/mailman/listinfo/ol-discuss > Archives: http://www.mail-archive.com/ol-discuss@archive.org/ > To unsubscribe from this mailing list, send email to > ol-discuss-unsubscr...@archive.org >
_______________________________________________ Ol-discuss mailing list - Ol-discuss@archive.org http://mail.archive.org/cgi-bin/mailman/listinfo/ol-discuss Archives: http://www.mail-archive.com/ol-discuss@archive.org/ To unsubscribe from this mailing list, send email to ol-discuss-unsubscr...@archive.org
