<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
My $0.02 contribution to the discussion:<br>
<br>
Which platform rather depends on intended use. If it's going to be
an active site with lots of different functions needing multiple
permission levels and a complex database, then probably better to
use Drupal. If it's fairly simple with a bunch of documents, then
anything will do :)<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 26/01/16 09:36, Jos Poortvliet
wrote:<br>
</div>
<blockquote
cite="mid:CAABAGrVLiQiH3ehwQqHdU0J8o48DG9KJOwz39E5jzJWu+hmfRQ@mail.gmail.com"
type="cite">
<p dir="ltr">If you decide to move to WordPress I can help out a
bit too, I have plenty experience maintaining ownCloud.org :-)</p>
<p dir="ltr">replying on phone. blame faulty text
completion/correction for any rudeness!</p>
<div class="gmail_quote">On Jan 25, 2016 11:02 PM, "farid
abdelnour" <<a moz-do-not-send="true"
href="mailto:snd.noise@gmail.com">snd.noise@gmail.com</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div>
<div>
<div>
<div>hi guys,<br>
<br>
</div>
i am one of the people interested in helping out with
the website. i guess the first step would be to choose
if we are gonna stick to the current platform (<span
style="background:yellow none repeat scroll 0% 0%">drupal</span>)
and update it since there might be some security flaws
or switch to a different one (<span
style="background:yellow none repeat scroll 0% 0%">wordpress</span>?).
our lead designer here at the studio can take care of
all the design of the website and if we choose <span
style="background:yellow none repeat scroll 0% 0%">wordpress</span>
i can apply it (i am not familiar with <span
style="background:yellow none repeat scroll 0% 0%">drupal</span>).
eventually we will do a research and develop a design
best suited for everyone's demands and needs. i did a
quick look around at other video, audio and graphics
programs to start getting an idea about what is out
there:<br>
<br>
</div>
<div>proprietary:<br>
<a moz-do-not-send="true" href="http://www.lwks.com/"
target="_blank">http://www.lwks.com/</a><br>
<a moz-do-not-send="true"
href="http://www.avid.com/US/products/Media-Composer"
target="_blank">http://www.avid.com/US/products/Media-Composer</a><br>
<a moz-do-not-send="true"
href="http://www.sonycreativesoftware.com/vegaspro"
target="_blank">http://www.sonycreativesoftware.com/vegaspro</a><br>
<a moz-do-not-send="true"
href="https://www.apple.com/final-cut-pro/"
target="_blank">https://www.apple.com/final-cut-pro/</a><br>
<a moz-do-not-send="true"
href="https://www.adobe.com/products/premiere.html"
target="_blank">https://www.adobe.com/products/premiere.html</a><br>
<br>
</div>
<div>free:<br>
<a moz-do-not-send="true" href="http://natron.fr/"
target="_blank">http://natron.fr/</a><br>
<a moz-do-not-send="true" href="http://ardour.org/"
target="_blank">http://ardour.org/</a><br>
<a moz-do-not-send="true"
href="https://www.blender.org/" target="_blank">https://www.blender.org/</a><br>
<a moz-do-not-send="true"
href="https://inkscape.org/en/" target="_blank">https://inkscape.org/en/</a><br>
<a moz-do-not-send="true" href="http://www.gimp.org/"
target="_blank">http://www.gimp.org/</a><br>
<br>
</div>
<div>parallel to this we can start thinking about
writing/organizing the content and structure. (which
is the most important thing.) like ttguy said, i agree
that content is the most important but it should be
well presented to the visitors. we can point to the
forum, wiki and bug tracker from the website and users
eventually will use the other services if necessary. <br>
</div>
<br>
</div>
if you'd like to continue this conversation here it is
fine by me, otherwise we can switch to the forum.<br>
<br>
</div>
cheers<br>
<div>
<div><br>
<br>
<div><br>
</div>
</div>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2016-01-21 19:50 GMT-02:00 Roger
Morton <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:ttguy1@gmail.com" target="_blank">ttguy1@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">I have
been involved in doing some maintenance of the content
on both<br>
the <a moz-do-not-send="true"
href="http://kdenlive.org" rel="noreferrer"
target="_blank">kdenlive.org</a> web site and on the
userbase.kde wiki.<br>
Historically the <a moz-do-not-send="true"
href="http://kdenlive.org" rel="noreferrer"
target="_blank">kdenlive.org</a> site was where
everything happened. It<br>
was the manual, the forum, the place to make
anouncements and to<br>
advertise how to get Kdenlive.<br>
<br>
Then for various reasons - as have already been
mentioned - we moved a<br>
lot of this functionality to kde infra structure and
closed the<br>
<a moz-do-not-send="true" href="http://kdenlive.org"
rel="noreferrer" target="_blank">kdenlive.org</a> web
site to new user registration. Now if we are thinking<br>
of putting more content back on the <a
moz-do-not-send="true" href="http://kdenlive.org"
rel="noreferrer" target="_blank">kdenlive.org</a>
website we need to<br>
consider the future maintenance burden.<br>
<br>
The way to limit maintenance burden is to have a large
number of<br>
contributors to the maintenance task. We can get this
on the<br>
userbase.kde wiki since new user registrations are open.
We can't get<br>
this so easily on <a moz-do-not-send="true"
href="http://kdenlive.org" rel="noreferrer"
target="_blank">kdenlive.org</a> because new automatic
registrations are<br>
closed. We could try opening up <a
moz-do-not-send="true" href="http://kdenlive.org"
rel="noreferrer" target="_blank">kdenlive.org</a>
again to new user<br>
registrations but I have to tell you that last time we
had this open<br>
we were getting 5 or more fake spammer account
registrations per day.<br>
I believe that the security on the registrations system
had been<br>
exploited somehow because I would see authorised users
that had never<br>
been sent a confirmation email. This the reason we
turned off<br>
registration completely. Maybe this exploit has been
fixed. I dunno.<br>
But this just something to consider in all this.<br>
<br>
While I agree that the attractiveness of the site is
important I<br>
believe the accuracy of the content on the site is more
important.<br>
And I don't think we should duplicate information.<br>
<br>
We have <a moz-do-not-send="true"
href="https://userbase.kde.org/Special:MyLanguage/Kdenlive/Manual/Installation"
rel="noreferrer" target="_blank">https://userbase.kde.org/Special:MyLanguage/Kdenlive/Manual/Installation</a><br>
to speak to installation<br>
and we have <a moz-do-not-send="true"
href="https://userbase.kde.org/Kdenlive/Manual/Tutorials"
rel="noreferrer" target="_blank">https://userbase.kde.org/Kdenlive/Manual/Tutorials</a>
for tutorials<br>
<br>
So I am thinking more on the lines that Vincent
mentioned. The<br>
<a moz-do-not-send="true" href="http://kdenlive.org"
rel="noreferrer" target="_blank">kdenlive.org</a> site
can have some nice looking promotional material that<br>
is fairly generic in nature and not requiring too much
maintanance. It<br>
should link to the more dynamic information at the
userbase.kde manual<br>
pages.<br>
<span><br>
<br>
>(3) Direct the viewer easily to a web page or
location where they can get it... or at least show how
they can get it.<br>
<br>
</span>This is of course one of our biggest issues and
has been for ages.<br>
There is no way to have simple instructions on how to
get it because<br>
everyone must rely on the package managers of their
various linux<br>
distros. But if we had more contributors to the doco
then we might<br>
have users from all different distros updating the doco
to tell people<br>
how to install it on their flavor of linux.<br>
<br>
While we there is a mood about helping out with doco I
would make a<br>
plea to people to help out on the userbase.kde manual. I
did a lot of<br>
work on it a few years ago and got it to a point where
it was pretty<br>
comprehensive. I had pages covering every menu item (not
every effect<br>
or transition had a page - but a skeleton link to create
a page was<br>
there). But now - with the major overall that kdenlive
has undergone<br>
- it is out of date in many places. So if people have
"documentation<br>
fever" they could help out on the <a
moz-do-not-send="true" href="http://userbase.org"
rel="noreferrer" target="_blank">userbase.org</a>
wiki. - register a kde<br>
identity account here <a moz-do-not-send="true"
href="https://identity.kde.org/?r=registration/index/"
rel="noreferrer" target="_blank">https://identity.kde.org/?r=registration/index/</a><br>
<br>
I summary my plea to people is to not focus too much on
the sexiness<br>
of the websites but to focus on getting the content
right. If you see<br>
something wrong just fix it !<br>
<div>
<div>_______________________________________________<br>
kdenlive mailing list<br>
<a moz-do-not-send="true"
href="mailto:kdenlive@kde.org" target="_blank">kdenlive@kde.org</a><br>
<a moz-do-not-send="true"
href="https://mail.kde.org/mailman/listinfo/kdenlive"
rel="noreferrer" target="_blank">https://mail.kde.org/mailman/listinfo/kdenlive</a><br>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
<div>1111.1010.r.i.1101|n.o.i.s.1110|i.m.1010.g.1110|مقاومة<br>
fsf member #5439<br>
usuario GNU/Linux #471966<br>
|_|0|_|<br>
|_|_|0|<br>
|0|0|0|<br>
<a href="<a moz-do-not-send="true"
href="http://www.gunga.com.br" target="_blank">http://www.gunga.com.br</a>">gunga</a><br>
<a href="<a moz-do-not-send="true"
href="http://www.tempoecoarte.com.br" target="_blank">http://www.tempoecoarte.com.br</a>">tempoecoarte</a>
<div><a href="<a moz-do-not-send="true"
href="http://www.atelier-labs.org" target="_blank">http://www.atelier-labs.org</a>">atelier-labs</a></div>
<div><a href="<a moz-do-not-send="true"
href="http://www.mocambos.net" target="_blank">http://www.mocambos.net</a>">rede
mocambos</a><br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
kdenlive mailing list<br>
<a moz-do-not-send="true" href="mailto:kdenlive@kde.org">kdenlive@kde.org</a><br>
<a moz-do-not-send="true"
href="https://mail.kde.org/mailman/listinfo/kdenlive"
rel="noreferrer" target="_blank">https://mail.kde.org/mailman/listinfo/kdenlive</a><br>
<br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
kdenlive mailing list
<a class="moz-txt-link-abbreviated" href="mailto:kdenlive@kde.org">kdenlive@kde.org</a>
<a class="moz-txt-link-freetext" href="https://mail.kde.org/mailman/listinfo/kdenlive">https://mail.kde.org/mailman/listinfo/kdenlive</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
David McQuire
0418 310312</pre>
</body>
</html>