Wanna join the gang?

[simison]

Hello @keyvan-m-sadeghi 👋

You've done some impressive work here! 👍 👍

We're working on Agenda and Agendash — latter one has built-in API like yours. It would be awesome if the API would be separate (like your package), somewhat "official" and Agendash could use that then instead.

What do you think? Would you be interested helping out with such project? :-) We could move this package to @agenda org and it would get more attention from the awesome Agenda community.

We have Slack channel if you wanna join and discuss this more. :-)

Have a good one!

[simison]

Pinging @naterkane here as well, because of similar but a bit older package https://github.com/naterkane/rest-scheduler :-)

[keyvan-m-sadeghi]

Hi @simison 🖐️
Sure, sounds like a great idea. We can start with moving this repo to @agenda, then I can apply the changes needed for Agendash to use this package if someone directs me how in an issue.

[keyvan-m-sadeghi]

I just tried to transfer the ownership, seems it needs a permission.

[OmgImAlexis]

Could you transfer it to one of us and we can the move it?

[simison]

Sure, sounds like a great idea. We can start with moving this repo to @agenda, then I can apply the changes needed for Agendash to use this package if someone directs me how in an issue.

This is awesome! 🎉

Could you transfer it to one of us and we can the move it?

I'll just add @keyvan-m-sadeghi to org and we can move it directly to @agenda then. (Update: done, check email or visit org site)

[keyvan-m-sadeghi]

Done

[naterkane]

I have some updates to the rest-scheduler that I'm not sure ever got pushed. Haven't looked at it in about 18 months though iirc.

[simison]

@naterkane yup! would be great if you can have a look at this repo (now transferred to /agenda/agenda-rest) to see if there's something in your work that could be brought over to there — for joint effort! 💪

I picked this repository initially for @agenda because had more recent work than yours. ;-) No hard feelings.

[naterkane]

I'm not offended. The one I put together had a specific strategy. Send ANY payload to a url, at a given time. I used it to fire payloads to rest endpoints within a large, complicated SoA application.. our implementation ended up not using Mongo, but something that could provide atomicity at scale and use less resources.

…

On Feb 1, 2018 9:12 AM, "Mikael Korpela" ***@***.***> wrote: @naterkane <https://github.com/naterkane> yup! would be great if you can have a look at this repo (now transferred to /agenda/agenda-rest) to see if there's something in your work that could be brought over to there — for joint effort! 💪 I picked *this* repository initially for @agenda <https://github.com/agenda> because had more recent work than yours. ;-) No hard feelings. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABVqsgv4vhLb_fp8HZq414eoyJBHTmbks5tQcZmgaJpZM4R1QvG> .

[simison]

Great! :-)