django-newsletter
django-newsletter copied to clipboard
jazzband
We need YOU to maintain this package!
Dear users/contributors,
This issue is quite serious indeed: as you might have notices the project has not been properly maintained, a new release is long overdue. Which is a real pity. Development and contributions have continued but are (slightly) fragmented. And only I am to blame. ;)
There are some ideas of adopting the project and several people have taken very active roles in contributing, like @pcraston and @dsanders11. However, a project like this needs someone or someones (one or two people) to:
- Roll out releases
- Maintain infrastructure (Travis and Landscape)
- Make architecture and design decisions
- Review pull requests or at least coordinate their review
If you would like to take on (some of) these responsibilities or have some ideas or feedback to share, please don't hesitate. Please do be aware, though, that ideas are not enough: you would likely have to execute your ideas yourself, so consider whether it's worth your time.
Kind regards, Mathijs
Happy to help where I can but I don't have time to be maintainer unfortunately.
@pcraston Nevertheless, all your contributions are greatly valued and appreciated! :)
Hey,
I propose myself as a new maintainer.
Could you transfer it on my account in github or give me the right to push in your repository?
Hey @bashu,
Great! You help is very welcome.
Maintaining a project like this carries with it a significant responsibility, both with regards to architecture decisions as well as community management. In order to assure that the project remains in good hands, I would like to welcome you to become an active contributor first, by reviewing existing pull requests and/or creating them (for inspiration, please see the list of outstanding issues).
As soon as I feel comfortable with the role you take, I would gladly give you push access (as I did before with other active contributors). When the time is right, some time after the release I might transfer ownership as well. In this case the previously suggested approach of setting up an organization as the proper owner seems sensible.
So, what do you think about it? :)
Regards, Mathijs
Hey,
I am starting tomorrow
On 22 Jul 2015, at 19:37, Mathijs de Bruin wrote:
As soon as I feel comfortable with the role you take, I would gladly give you push access (as I did before with other active contributors). When the time is right, some time after the release I might transfer ownership as well. In this case the previously suggested approach of setting up an organization as the proper owner seems sensible.
So, what do you think about it? :)
Hello dokterbob
We are using your django module for our newsletter and are happy with it. If we find time, we will support you. (https://github.com/QuantumBytesInc)
Greets
Hey @ManuelGysin , @bashu, @pcraston,
So we're pretty close to the 0.6 release. However, there is one outstanding security issue and another quite serious bug I'd like to have solved before shipping.
https://github.com/dokterbob/django-newsletter/milestones/0.6
Should anyone be able to work on one of them (please assign to yourself) this would be greatly appreciated. Of course I would be happy to provide guidance, feedback and reviews of your patches and will try to pick up one of them if I can.
Mathijs
I'm still around, but in a very limited capacity to take on any work here other than minor stuff like #146. I'll try to keep an eye on this project as time permits, though.
