[mezzanine-users] Re: new release?

[Asif Saifuddin]

Why not a version 3.2 with dj 1.7 and 1.8 support?

On Tuesday, March 24, 2015 at 9:52:17 AM UTC+6, Eduardo Rivas wrote:
>
> Hi. I'm sharing my personal viewpoint (wait for Steve to give a official 
> statement):
>
>- My appreciation is that catching up with Django 1.7 is taking a lot 
>because it introduces a lot of backwards-incompatible changes AND 
> Mezzanine 
>wants to keep supporting Django 1.6 too. With 1.8 we might not have the 
>same problem, because we probably won't be seeing so many breaking 
> changes. 
>Also, the next release will have Model translation support, which is huge 
>too!
>- A warning related to the Fabric script: it will only work if you 
>have sudo privileges on the remote server. I'm mentioning this because 
>shared hosting accounts often lack this privilege.
>
>

-- 
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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Re: new release?

[Ken Bolton]

On Tue, Mar 24, 2015 at 8:46 AM, Asif Saifuddin  wrote:

> Why not a version 3.2 with dj 1.7 and 1.8 support?
>

Django has a glorious history of supporting the three most recent point
releases. Mezzanine, appropriately, continues that by releasing versions
that support the currently-supported versions of Django. This has always
been, in my opinion, the sensible way to approach releases. Right now,
support for Django 1.5 is far more important. If support were dropped for
1.5, this would make Mezzanine much less valuable for those of us who have
relied on stable releases for five years.

If you absolutely need some feature in 1.7, you have two options: 1. use
master or 2. fix the outstanding issues that are blocking a release.

1.8 support is right out. Asking for it is a distraction from the important
work of the contributors and maintainers.

- ken

-- 
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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Hosted solutions for Mezzanine

[Luke Plant]

Hi all,

Are there any hosted solutions for Mezzanine? I'm talking about something 
oriented at people with zero web development skills - an equivalent to 
something like Dreamhost for installing WordPress 
http://www.dreamhost.com/wordpress-hosting/

Unlike most WordPress hosting, the solution I have in mind would 
automatically manage things like all security updates, and allow 
point-and-click selecting of different themes.

An ideal solution would allow users to export their project so that they 
can continue to develop it themselves, on hosting of their choice.

Does such a thing exist, or something close?

Thanks,

Luke

-- 
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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Hosted solutions for Mezzanine

[Graham]

Hi Luke
As far as I know, no such thing exists.
The Mezzanine 'friendly' places I have heard of are

1. Webfaction - https://www.webfaction.com/
2. Digital Ocean - https://www.digitalocean.com/
3. Python Anywhere - https://www.pythonanywhere.com/

However, 'getting your hands dirty' with things like 'fab files' and the 
command line, is I believe a requirement.


On a more general level, the issue of who Mezzanine is for, is something 
that I am trying to get clear in my own mind. I know from listening to 
Stephen McDonald talk about the birth of Mezzanine - 
https://vimeo.com/103614826 that it was in response to his management 
wanting to 'go with Wordpress'


My working hypothesis is that creating websites with Mezzanine is *not* 
for non-developers. Other things would be better...


Cheers
G

On 25/03/15 04:55, Luke Plant wrote:

Hi all,

Are there any hosted solutions for Mezzanine? I'm talking about 
something oriented at people with zero web development skills - an 
equivalent to something like Dreamhost for installing WordPress 
http://www.dreamhost.com/wordpress-hosting/


Unlike most WordPress hosting, the solution I have in mind would 
automatically manage things like all security updates, and allow 
point-and-click selecting of different themes.


An ideal solution would allow users to export their project so that 
they can continue to develop it themselves, on hosting of their choice.


Does such a thing exist, or something close?

Thanks,

Luke

--
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 mezzanine-users+unsubscr...@googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.


--
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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Hosted solutions for Mezzanine

[Ken Bolton]

Hi Luke,

Thank you for all your hard work on Django! Without Django, we would have
no Mezzanine.

I have not come across any Mezzanine hosting services a la WordPress.com or
Dreamhost's offering. I don't know of any services that do hosted and
maintained Django, either.

Cheers,
Ken

On Tue, Mar 24, 2015 at 11:55 AM, Luke Plant  wrote:

> Hi all,
>
> Are there any hosted solutions for Mezzanine? I'm talking about something
> oriented at people with zero web development skills - an equivalent to
> something like Dreamhost for installing WordPress
> http://www.dreamhost.com/wordpress-hosting/
>
> Unlike most WordPress hosting, the solution I have in mind would
> automatically manage things like all security updates, and allow
> point-and-click selecting of different themes.
>
> An ideal solution would allow users to export their project so that they
> can continue to develop it themselves, on hosting of their choice.
>
> Does such a thing exist, or something close?
>
> Thanks,
>
> Luke
>
>  --
> 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 mezzanine-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Hosted solutions for Mezzanine

[Sam Kingston]

Hi everyone,

I would like to gauge some support for this - does the community as a whole 
think it would be worthwhile to have a "one-click-to-run" host that allows 
Mezzanine support?

I've hacked on something similar previously that was designed to do the 
same thing - hosted Mezzanine with no development knowledge required. It's 
currently lacking a web interface and targets a much older version of 
Mezzanine/Django.

Would be happy to try and turn it into a usable system and throw it out 
there if there is a want/need for it?

What do you all think?

Sam

On Wednesday, 25 March 2015 06:53:17 UTC+10, Kenneth Bolton wrote:
>
> Hi Luke,
>
> Thank you for all your hard work on Django! Without Django, we would have 
> no Mezzanine.
>
> I have not come across any Mezzanine hosting services a la WordPress.com 
> or Dreamhost's offering. I don't know of any services that do hosted and 
> maintained Django, either.
>
> Cheers,
> Ken
>
> On Tue, Mar 24, 2015 at 11:55 AM, Luke Plant  > wrote:
>
>> Hi all,
>>
>> Are there any hosted solutions for Mezzanine? I'm talking about something 
>> oriented at people with zero web development skills - an equivalent to 
>> something like Dreamhost for installing WordPress 
>> http://www.dreamhost.com/wordpress-hosting/
>>
>> Unlike most WordPress hosting, the solution I have in mind would 
>> automatically manage things like all security updates, and allow 
>> point-and-click selecting of different themes.
>>
>> An ideal solution would allow users to export their project so that they 
>> can continue to develop it themselves, on hosting of their choice.
>>
>> Does such a thing exist, or something close?
>>
>> Thanks,
>>
>> Luke
>>
>>  -- 
>> 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 mezzanine-use...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] new release?

[Stephen McDonald]

Apologies for the delay, I'm currently on vacation overseas with my wife
and children over the next month.


On Tue, Mar 24, 2015 at 10:06 AM, elguavas  wrote:

> given that django 1.8 will be released soon, how are things going for a
> new pip installable release of mezzanine that supports django 1.7?
>


The so-far skipping of an official release against Django 1.7 is a valid
concern. Basically as Ed mentioned, the breaking changes from Django 1.6 to
1.7 were much larger than normal. I vaguely recall that around the time the
first Django 1.8 alpha release was made, we still had outstanding 1.7
incompatibilities, so at that point the question (in my head at least) was
raised around how worthwhile it would be to spend time on working toward an
official release against 1.7 given that the 1.8 release would be coming
soon. The alternative being that we just focus effort on compatibility with
1.8, and hopefully everything would line up compatibility-wise in time for
the official 1.8 release. As of a few weeks ago, we actually have 1.8
compatibility working - that may have changed since then, but given that
sign, it appears that the transition from 1.7 to 1.8 will require much less
effort.

As Ken said this would normally not be a consideration right now, but given
how things have turned out, we will most likely release Mezzanine 3.2 with
support for Django 1.7 and 1.8, along with the new modeltranslation work,
right after the release of Django 1.8.



>
> i'm also very interested in the new fabfile stuff for shared host installs.
>
> i'm also wondering, with mezz almost missing a whole django version
> without a pip installable release, are things on the mezz release front
> likely to continue to be very slow in staying up to date with changes in
> mezz git?
>
> not intending to be critical, not at all, just looking for an honest
> assessment of how the project is faring with respect to official releases.
> cheers.
>

I don't mean to sound critical either, and I appreciate the desire for some
clarity here, but I always find this type of question misguided.

There's no corporate entity behind Mezzanine with a fixed schedule of time
and resources that can be dedicated to it, which is precisely what would be
required to answer this question definitively. Its development relies on
the always-varying amount of free time myself and the other contributors
can make available to it. I simply don't have a crystal ball I can peek
into to provide you with any more clarity than that.

As mentioned above, the move from Django 1.6 to 1.7 required a non-trivial
amount of effort, which was a huge setback. Meanwhile the move from 1.7 to
1.8 has been almost seamless. So really you could flip a coin as to what
the future looks like - we're really at the mercy of Django's development.

That said, there are a couple of things *you* can do to make our timelines
less erratic. As often requested, please help out in resolving these
incompatibilities when new alphas/betas/RCs of Django are made available.
If enough people were to identify and resolve these issues earlier on,
sailing would be much smoother. Another idea is that we only really see
these problems very late into the Django development cycle. What we really
need is a voice within the Django development space - if someone was there
early on enough to say "hey this is going to be a huge breaking change",
perhaps more care for backward compatibility could be taken. I hope this
doesn't sound like a criticism of Django, they can't know what they're
breaking if no one tells them.

Thanks for bringing this up - I hope I've been able to make things a tiny
bit clearer for everyone who has been questioning the lapse in releasing.



>
>  --
> 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 mezzanine-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Stephen McDonald
http://jupo.org

-- 
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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Filetypes for Media Library

[Danny]

Hi all,

Probably a very simple question, but where are the filetypes for the 
Media Library defined, and can I override them?


If I go into my Media Library, and choose to Upload a file, the file 
browser window I'm presented with has the following options:


*.html; *.py; *.js; *.css; *.jpg; *.jpeg; ... and several more

However, some useful ones are missing (like MS Word's docx) and
even this selected list fails to show up PDFs in my current directory 
even though *.pdf is one of the options (I suspect it's too long for 
Windows liking).


The other bad thing is that the file type drop down doesn't have the 
"All Files (*.*)" option that you may be used to seeing.


I'm sure that there would be a nice easy setting somewhere that controls
this, the question is: where is it?

Thanks,

Seeya. Danny.

--
Email: molo...@gmail.com

--
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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] new release?

[Asif Saifuddin]

I thing could be maiking 3.1.x series LTS and Having a 3.2 release after
1.8 release and other work arrounds. like wagtail-cms team is doing.

enjoy the vacation!

Thank you for all your effort behind mezzanine.

Kind regards

On Wed, Mar 25, 2015 at 8:47 AM, Stephen McDonald  wrote:

> Apologies for the delay, I'm currently on vacation overseas with my wife
> and children over the next month.
>
>
> On Tue, Mar 24, 2015 at 10:06 AM, elguavas  wrote:
>
>> given that django 1.8 will be released soon, how are things going for a
>> new pip installable release of mezzanine that supports django 1.7?
>>
>
>
> The so-far skipping of an official release against Django 1.7 is a valid
> concern. Basically as Ed mentioned, the breaking changes from Django 1.6 to
> 1.7 were much larger than normal. I vaguely recall that around the time the
> first Django 1.8 alpha release was made, we still had outstanding 1.7
> incompatibilities, so at that point the question (in my head at least) was
> raised around how worthwhile it would be to spend time on working toward an
> official release against 1.7 given that the 1.8 release would be coming
> soon. The alternative being that we just focus effort on compatibility with
> 1.8, and hopefully everything would line up compatibility-wise in time for
> the official 1.8 release. As of a few weeks ago, we actually have 1.8
> compatibility working - that may have changed since then, but given that
> sign, it appears that the transition from 1.7 to 1.8 will require much less
> effort.
>
> As Ken said this would normally not be a consideration right now, but
> given how things have turned out, we will most likely release Mezzanine 3.2
> with support for Django 1.7 and 1.8, along with the new modeltranslation
> work, right after the release of Django 1.8.
>
>
>
>>
>> i'm also very interested in the new fabfile stuff for shared host
>> installs.
>>
>> i'm also wondering, with mezz almost missing a whole django version
>> without a pip installable release, are things on the mezz release front
>> likely to continue to be very slow in staying up to date with changes in
>> mezz git?
>>
>> not intending to be critical, not at all, just looking for an honest
>> assessment of how the project is faring with respect to official releases.
>> cheers.
>>
>
> I don't mean to sound critical either, and I appreciate the desire for
> some clarity here, but I always find this type of question misguided.
>
> There's no corporate entity behind Mezzanine with a fixed schedule of time
> and resources that can be dedicated to it, which is precisely what would be
> required to answer this question definitively. Its development relies on
> the always-varying amount of free time myself and the other contributors
> can make available to it. I simply don't have a crystal ball I can peek
> into to provide you with any more clarity than that.
>
> As mentioned above, the move from Django 1.6 to 1.7 required a non-trivial
> amount of effort, which was a huge setback. Meanwhile the move from 1.7 to
> 1.8 has been almost seamless. So really you could flip a coin as to what
> the future looks like - we're really at the mercy of Django's development.
>
> That said, there are a couple of things *you* can do to make our timelines
> less erratic. As often requested, please help out in resolving these
> incompatibilities when new alphas/betas/RCs of Django are made available.
> If enough people were to identify and resolve these issues earlier on,
> sailing would be much smoother. Another idea is that we only really see
> these problems very late into the Django development cycle. What we really
> need is a voice within the Django development space - if someone was there
> early on enough to say "hey this is going to be a huge breaking change",
> perhaps more care for backward compatibility could be taken. I hope this
> doesn't sound like a criticism of Django, they can't know what they're
> breaking if no one tells them.
>
> Thanks for bringing this up - I hope I've been able to make things a tiny
> bit clearer for everyone who has been questioning the lapse in releasing.
>
>
>
>>
>>  --
>> 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 mezzanine-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Stephen McDonald
> http://jupo.org
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Mezzanine Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/mezzanine-users/_QWfFVB3RVc/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> mezzanine-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"