-
Notifications
You must be signed in to change notification settings - Fork 33
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
Maintainers wanted #93
Comments
Thank you for your excellent work. It was a nice package to work with back
in the day.
B2
…On Mon, Oct 19, 2020 at 11:32 AM John Whitlock ***@***.***> wrote:
I've been the sole maintainer of the django-multi-gtfs / multigtfs
project, but an inactive maintainer since 2018. I no longer use it in my
own projects, and haven't had as much time for open source maintenance in
recent years. It would be good to add more active maintainers, and
eventually transition the project to those who actively use it.
This will probably involve creating a new GitHub organization and
transferring it out of tulsawebdevs.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#93>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABME7VOVFAEDPZ3RR2OF3LSLRYBJANCNFSM4SWNYHEQ>
.
|
Hello @jwhitlock, |
Thanks @jspetrak! I'm starting with giving you access to the current project, and then we'll work out future steps in this and other issues. It looks like I need to write a few... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've been the sole maintainer of the django-multi-gtfs / multigtfs project, but an inactive maintainer since 2018. I no longer use it in my own projects, and haven't had as much time for open source maintenance in recent years. It would be good to add more active maintainers, and eventually transition the project to those who actively use it.
This will probably involve creating a new GitHub organization and transferring it out of tulsawebdevs.
The text was updated successfully, but these errors were encountered: