Call for maintainers

[zol]

Since I'm no longer actively developing an app that uses synced-cron, I've lost touch with the codebase and the project. I'm looking for folks to take over development and maintenance, please raise your hand if you're interested.

[adrianbadarau]

I'm interested

[zol]

Thanks very much @adrianbadarau . I've given you commit access to the repo. A good place to start might be to clean up the issues/PRs. If things go well we'll call you out as the official maintainer. Please let me know your Meteor Developer Account so I can give you permission to publish new releases.

[rpesciotta]

Hi @zol, I will start using the package this week, and will analyze the codebase. I would like to volunteer to maintain the package, but I first need to have a look and check my availabilty - just wanted to give you an early feedback. I'll get back with a final answer.

[TheGame2500]

I'm interested!

[zol]

Thanks @TheGame2500 . I've given you commit access. Please co-ordinate with @adrianbadarau on tasks and releases.

[tomtom87]

I'm interested also guys, currently using this package in a production app so would love to keep it maintened

[zol]

Thanks @tomtom87, I've given you write access to the repo.

[tomtom87]

@zol very appreciated will start looking at issues when I have some time later

[rudza]

Hi! :)

Any progress with maintaining this repo?

[tomtom87]

Sure, I didnt get to a PR yet but been answering some usage issues people where having.. what are you enquiring regarding?

On 26 Aug 2016, at 19:56, RJ notifications@github.com wrote:

Hi! :)

Any progress with maintaining this repo?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/percolatestudio/meteor-synced-cron","title":"percolatestudio/meteor-synced-cron","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/percolatestudio/meteor-synced-cron"}},"updates":{"snippets":[{"icon":"PERSON","message":"@rudza in #91: Hi! :) \r\n\r\nAny progress with maintaining this repo? "}],"action":{"name":"View Issue","url":"https://github.com/percolatestudio/meteor-synced-cron/issues/91#issuecomment-242727858"}}}

[spawn-guy]

@tomtom87 persistent storage for Jobs, maybe? ;)

[cwebbdesign]

I'd be interested in helping with the repo, although my time is limited. @tomtom87 can someone review this pull request: #112 and merge it in, if happy with it? Thanks!

[Pushplaybang]

Hey Guys,

Also super keen as we're using this in production, and will likely use it on at least two other production apps this year. Let me know if you're in need of another set of helping hands.

P:)

[ElegantSudo]

@spawn-guy how could we implement this? Doesn't the cronHistory already take care of this?

[spawn-guy]

@ElegantSudo cronHistory is exactly for what is in the name. for History and Sync -ing

Jobs are added and held in memory. When the "schedule" function result time is right - the Job is fired. When the job is fired - the document is added to cronHistory collection. If you have multiple backend servers running - they all check for that document existence. and if there is already one and "running" - the other servers do not fire this same Job.

good thing is when you write your Jobs in the Code - if server restarts jobs are reloaded.
bad thing is when you Generate Jobs on the fly in the runtime - if the server is restarted you have to regenerate(re-add) all the Jobs.

obstacles:

1. i dunno how to load/save Closure functions from the database
2. maybe not all the Jobs need to be stored in cronJobs collection, as you might have a bunch of "recurring jobs" in the code and another bunch of "delayed one-timers".
   2.1. also "one-timers" should be cleaned up from memory/cllection after firing.

[ElegantSudo]

@spawn-guy this is an interesting problem. I'll likely fork this repo sometime within the next month and solve it.

[paolo-g]

+1 @cwebbdesign @tomtom87 #112

[MrBitMaster]

I'm interested!

[msavin]

Not quite the same, but I've almost finished a Meteor-first jobs queue that could address the same needs as this package. Maybe we could direct people to it as a replacement.

https://github.com/msavin/stevejobs

Update: package is nice and stable now

[amanagarwal2189]

Is anyone still maintaining this project?
I am using SyncedCron and find it amazing. I am facing a few issues though...

[etyp]

@zol have you passed Meteor account access to anybody yet? If not, I think @TheGame2500 is actively looking to maintain and release

[zol]

I've given admin access to all maintainers including @TheGame2500

[zol]

Thanks everyone!