Hi Eduardo, I've been in contact jezdez - one of the Jazzband roadies to discuss this in the #jazzband IRC channel.
Jazzband exists to lower the barrier of entry for maintenance and remove the single-developer-problem that we currently have. It's not a guarantee of maintenance but it should help simplify releases and would give us the opportunity to get more eyes on the upgrade to 2.2 that we so drastically need. As a next step he has encouraged us to create an issue <https://jazzband.co/roadies/issue?labels=question> proposing the transfer and mention Stephen and any other contributors that may be interested in helping with the transfer and future maintenance, I expect you or Stephen may be the best person to do this as you will have the required level of access. On Thursday, 12 December 2019 23:47:47 UTC, Eduardo Rivas wrote: > > Hi Pete, > > > > Thanks for bringing this over to the mailing list. I’m one of the > contributors to Mezzanine and still use it almost daily. I’m glad others > still want to see the project move forward. > > > > Do Jazzband or Code Shelter have contributors on standby ready to take in > projects and perform maintenance tasks? I’m not entirely clear on how they > work, just want to make sure I understand correctly. > > > > *From: *Pete Dermott <javascript:> > *Sent: *Tuesday, December 10, 2019 8:24 AM > *To: *Mezzanine Users <javascript:> > *Subject: *[mezzanine-users] Migration to Jazzband / Code Shelter > > > > Following on from the discussion on GitHub issue #1928 > <https://github.com/stephenmcd/mezzanine/issues/1928> > > > > Throughout 2019 there has been 1 commit to the master Github repo, we > haven't had a full release since August 2018 and there are a number > outstanding changes that are waiting to go into a new release. We still > don't have Django 2 support despite it being released in December 2018 and > Django 3 is now out and available for development. > > > > I use Mezzanine a lot in my day to day projects but I don't feel like I > personally have the skill to take it forward and make it fully compatible > with the changes to Django and jQuery that are required. > > > > Basically, I feel that this project needs a bit of help to keep it > relevant. Thankfully there are maintainer communities in Jazzband > <https://jazzband.co/>and Code Shelter <https://www.codeshelter.co/> that > may be able to help us. I feel that handing the project over to them should > at least ensure that active Mezzanine projects are not left exposed when > 1.11 is deprecated in April 2020. > > > > Also - just to note - this is in no way mean to denigrate the hard work > that Stephen and others have done over the years with this project, it > speaks volumes about the quality of the codebase that Mezzanine is still my > Django CMS of choice after all this time. > > -- > You received this message because you are subscribed to the Google Groups > "Mezzanine Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/mezzanine-users/476a90bc-1e21-4cfe-8039-b72a6e1748eb%40googlegroups.com > > <https://groups.google.com/d/msgid/mezzanine-users/476a90bc-1e21-4cfe-8039-b72a6e1748eb%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > > -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mezzanine-users/6d2e5528-9522-480f-bd8d-ea3dd4336a30%40googlegroups.com.
