René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Looking for a maintainer","articleBody":"Development of angular-gettext has up till now always been funded by companies I work with, for which I'm very grateful. Sadly the last of those projects will be coming to an end in a couple of months.\r\n\r\nWith no further sponsoring and a need to feed both my family (with a new kid on the way), it's becoming rather hard for me to find the time to maintain a project that I no longer use myself.\r\n\r\nNot that angular-gettext needs much maintenance: as far as I can tell it's feature-complete. Angular (1.x) itself is also frozen, so no large changes will come in Angular are expected. But one never knows what might pop up: unforeseen browser breakage might necessitate changes and fixes, which have to be done with proper QA.\r\n\r\nFor that reason, if you are an active user of angular-gettext: **we need a new maintainer**. Give me a sign (here or via e-mail) if you are interested.\r\n\r\nSome ground rules though:\r\n\r\n* Guaranteed backwards compatibility and no breakage *ever*. Unless for a major and critical security problem, all existing projects should keep on working.\r\n\r\n* No new features, unless there's an extremely good reason for it (something that's absolutely impossible right now). But no nice-to-haves: simplicity is key.\r\n\r\nI'll still keep an eye on things, but I can't spend the required time on this project anymore. On the other hand, I don't want anyone that depends on angular-gettext to be blocked by my lack of time, so I'm happy to relinquish control.\r\n","author":{"url":"https://github.com/rubenv","@type":"Person","name":"rubenv"},"datePublished":"2018-11-30T12:26:01.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/365/angular-gettext/issues/365"}