Where to start contributing?

[christopher-john-czettel]

I've noticed there are no open issues on this Github project, nor was I able to find a roadmap or something like it (I took a look at the CONTRIBUTING file which suggests improving on the developer documentation, but no concrete tasks/plans/vision.)

After taking a look at stunt.io I noticed not much has been going on recently - even though it seems to be one of the most promising forks of LambdaMOO, IMHO that is. ;-)

Are there any plans how to further this project in the future? Do you want to keep the "for hackers only" label, or develop stunt into something more accessible for non-hardcore C/C++ hackers? Like, make it easier for MOO-developers to start their own new MOOs or help existing MOOs to "upgrade"/migrate to Stunt?

Some ideas that come to mind (just spitballing here):

• switch over to a more flexible and modern (possibly) cmake-based build system
• get in contact with Linux distributions to package stunt.io
• make vagrant/docker/lxc/whatever containers for new users to try stunt.io out/deploy it easily in the cloud
• providing a "sexy" and more modern GUI/IDE (with git support) for MOOcode developers
• create a cross-platform client for mobile and PC leveraging Stunt's RESTful/JSON capabilities
• implementing other DB backend stores (maybe something cloud-friendly?)
• develop an automated continuous build/test platform
• write a tutorial/roadmap for existing MOOs to switch from vanilla LambdaMOO 1.8.1/1.8.2/1.8.3
• help interested existing MOOs in porting their worlds
• do some social/networking stuff to increase awareness about Stunt

Maybe you could give me some feedback if any of those things interest you - I don't wanna start developing something, just to have my pull-request denied because it does not fit the vision of the project. (While we're at it - what is the vision of this project?) ;-))

Is there any kind of mailing list, IRC channel, etc. for this project?

I can offer some free server resources if needed - just say so.

Any input is highly appreciated!

[SpiraMirabilis]

- Convert MOO's main loop to a asynchronous event queue, like with either boost asio or libuv

…

On Tue, Jan 2, 2018 at 9:55 AM, Christopher John CZETTEL < ***@***.***> wrote: I've noticed there are no open issues on this Github project, nor was I able to find a roadmap or something like it (I took a look at the CONTRIBUTING file which suggests improving on the developer documentation, but no concrete tasks/plans/vision.) After taking a look at stunt.io I noticed not much has been going on recently - even though it seems to be one of the most promising forks of LambdaMOO, IMHO that is. ;-) Are there any plans how to further this project in the future? Do you want to keep the "for hackers only" label, or develop stunt into something more accessible for non-hardcore C/C++ hackers? Like, make it easier for MOO-developers to start their own new MOOs or help existing MOOs to "upgrade"/migrate to Stunt? Some ideas that come to mind (just spitballing here): - switch over to a more flexible and modern (possibly) cmake-based build system - get in contact with Linux distributions to package stunt.io - make vagrant/docker/lxc/whatever containers for new users to try stunt.io out/deploy it easily in the cloud - providing a "sexy" and more modern GUI/IDE (with git support) for MOOcode developers - create a cross-platform client for mobile and PC leveraging Stunt's RESTful/JSON capabilities - implementing other DB backend stores (maybe something cloud-friendly?) - develop an automated continuous build/test platform - write a tutorial/roadmap for existing MOOs to switch from vanilla LambdaMOO 1.8.1/1.8.2/1.8.3 - help interested existing MOOs in porting their worlds - do some social/networking stuff to increase awareness about Stunt Maybe you could give me some feedback if any of those things interest you - I don't wanna start developing something, just to have my pull-request denied because it does not fit the vision of the project. (While we're at it - what *is* the vision of this project?) ;-)) Is there any kind of mailing list, IRC channel, etc. for this project? I can offer some free server resources if needed - just say so. Any input is highly appreciated! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#24>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABf2gKX31u7CpAzwMNSJUApOg0_IKoUiks5tGl-SgaJpZM4RQ1PJ> .

[tvdijen]

create a cross-platform client for mobile and PC leveraging Stunt's RESTful/JSON capabilities

This, and maybe the git-like support would be the only things that users will actually benefit from.
Things like different backend stores, continuous testing, async event queues.... It's nice, and if MOO were to be developed in 2018 we'd definitely put in all of that, but it's all 'under the hood' so to speak...
I think the focus should be much more on the business-end of MOO (i.e. the end-user perspective) if we want to make MOO 'sexy' again..