-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Meeting proposal to organize the project #6778
Comments
I'm in! Despite the current state of affairs, OSRM is still the best open-source option out there for some use-cases, plus it has a somewhat huge user-base, so we probably have some margin to make things move forward. |
I'm in as well. |
@DennisOSRM @danpat @mjjbell @SiarheiFedartsou interested as well ? |
👍🏽 |
I'd love to sit in. Never really had the chance to work myself into OSRM, the interest is still there though |
Definitely 👍 |
I'm interested, but honestly my current level of participation is about my limit, so I'm not sure I have a lot to offer these days. Raising small children and spare-time open source contributions are not very compatible. |
I know that feeling :) But yes, definitely up for this. |
I think it would be a good idea! Maybe some map-companies would be interested to support the further development of this project. |
Sorry for the late response. On a practical note, it looks like the Discussions tab is enabled now, so we can encourage the use of that to alleviate Issue pollution. |
I am interested in this meeting, if it has not happened yet. Let me know! |
I am interested too! |
I'm interested too! |
I'm interested too! let me in. |
I would like to propose a meting to state on the project and see what we can do to organize a bit.
I have in mind how we can merge acceptable long stating PR, and more. Like make new release new, fix CI, enable the Github community forum to avoid stacking help requests in the issues...
I don’t know if it is the case, but maybe we can raise some fund from company using it to this pay this maintenance job, or even make new devs.
The text was updated successfully, but these errors were encountered: