Open georgejecook opened 5 years ago
Hi, @georgejecook. I mentioned somewhere already, but I do not work with Roku anymore and therefore had to transfer my time into other technologies. Would be happy to transfer ownership/ repo/packages if you interested in maintaining. Hit me up if any
I want to add more rules, and I’m gonna be active in roku for a while, so I’d be happy to take that on.
On November 20, 2018 at 4:53:59 PM, Igor Alpert (notifications@github.com) wrote:
Hi, @georgejecook https://github.com/georgejecook. I mentioned somewhere already, but I do not work with Roku anymore and therefore had to transfer my time into other technologies. Would be happy to transfer ownership/ repo/packages if you interested in maintaining. Hit me up if any
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/RokuRoad/eslint-plugin-roku/issues/36#issuecomment-440442868, or mute the thread https://github.com/notifications/unsubscribe-auth/ABKIUQ7b9uopHC61khhAk_gqZYq5jaUTks5uxHn3gaJpZM4YqIAb .
Hi, I'd like to contribute some rules; but a lot of them involve day to day programming tasks, like non-existent methods/mismatched function params/callbacks.. Those are xml scenegraph issues.
I think it is a good idea!
Hey ialpert @bleighty on the roku slack group, would be happy (and very capable imho) to take the maintenance of this project on. I'm really busy with 3 other roku open source projects; so I think that'd make more sense - he's already been contributing similar changes to the vscode-ide-project, and has some work queued up he'd like to get straight on with.
Perhaps you guys can chat about that?
This is @bleighty. I'd like to add the ability to ignore specific lines and as well find a way to work around then
causing warnings. Would like to fix these but want to make sure these can actually get used by more than just me.
Hey guys, can you PM / email me how I can be in help? transfer repo, tokens/project in NPM etc. cc @triwav @georgejecook
Hi, I'd like to contribute some rules; but a lot of them involve day to day programming tasks, like non-existent methods/mismatched function params/callbacks.. Those are xml scenegraph issues.