-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Seeking contributers for reviving MeshAgent development #253
Comments
I am currently a maintainer, but I'm only a one man band! I have already merged a few issues/pr and done a few test builds, I just need people to try the new agent before I release them into meshcentral itself! I'm taking donations from people to help me carry on supporting the project! |
Thank you very much for your great work & support, Simon! I can confirm first hand how both capable and kind your are. My hope is to distribute the load - if possible - on a few more shoulders, including mine. Specifically, this means to start work on switching to OpenSSL 3.0 - I would be happy if a few people would join in, as this would make work easier and faster. |
Heyy I think I can help out when I have free cycles |
@aloisuz great! Checkout the meshagent repo/code and can u add any features at all? Like the multi screen mac support, Linux wayland support. |
Excellent. Personally I've started working on the OpenSSL 3.0 upgrade first. Linux wayland support sounds great as well. |
Hey , am learning C programing language, I went through all the basics. |
Wonderful, then let's join forces and tackle the open issues bit by bit. Do you have some time this week to discuss & plan? My timezone is CEST. I am quite flexible. |
Yeah I do, we can agree on time for a meeting and you can give me a task because am realy new in genral and I got to look for stuff |
Hey.Iv been waiting for a response from you |
Hi @Serajalhorany, Thanks for being patient. There are no full time employees working on MeshCentral, thus everybody also tackles work/business as well as private life. I'm available tomorrow afternoon. So, how about 1 pm CEST? Please contact me by email at contact-via-github@schories.com so that we may share meeting information. All you need for the meeting is a computer with a modern browser, no client software. Looking forward to meeting you tomorrow! :-) |
Hi, I meanwhile received 3 mails from you and already answered 2 of them. However, you doesn't seem to recognize them as your mails are getting longer, but never answer my question when is a good time for you. So, please
Thank you! :-) |
I apologise for the consecutive emails, I thought so too, but I was concerned that you didn't receive my emails. |
Quick update:
|
@schories, yes, u can start test building if you like! I would stick to Windows 7+, and server 2012r2+ |
1 similar comment
@schories, yes, u can start test building if you like! I would stick to Windows 7+, and server 2012r2+ |
I support this idea. We are already having some private meetings to coordinate on I think we should start with one community meeting per month, and see how it goes. |
@marclaporte Excellent, let's do this. |
@Ndaboom has volunteered. He'll start with a proposal on a wiki page. |
@schories @aloisuz @Serajalhorany @krayon007: Going forward, we will have monthly community meetings. 1st meeting is planned for 2024-10-31:
I look forward ro meeting all of you! |
The recording is available: https://github.com/Ylianst/MeshCentral/wiki/Community-Monthly-Meetings |
@marclaporte I regret not being able to make it last time. Thank you for the link and thank @Ndaboom for the structure. |
MeshAgent is a crucial part of MeshCentral. With
it makes sense to gather & focus some development capacity also on MeshAgent.
Who is willing to actively contribute to MeshAgent and tackle some of the above topics? I'm willing to contribute, but neither I can do it alone nor it would be wise to make lonely design decisions.
Thus I'd highly appreciate replies in this thread, offering support in the above topics - coding, testing, etc.
Thank you all very much!
The text was updated successfully, but these errors were encountered: