On Thu, 27 Mar 2008, Joost Verburg wrote:
I think that's overkill. We should be happy when people keep the website
up-to-date and not add to much bureaucracy. Quick updates of download
links and things like that also become impossible if you have to wait
for an editor to press a button.
I'll
[EMAIL PROTECTED] wrote:
PS. For quality control of www.lyx.org, it might be good to also
introduce 'editors', which must approve modifications to a page before
it goes live. In other words, 'authors' would make changes and ask
someone else to proof read it and then publish that page. I don't
On Wednesday 26 March 2008 21:45:07 [EMAIL PROTECTED] wrote:
> PS. For quality control of www.lyx.org, it might be good to also introduce
> 'editors', which must approve modifications to a page before it goes live.
> In other words, 'authors' would make changes and ask someone else to proof
> read
On Wed, 26 Mar 2008, José Matos wrote:
Just a matter of convention I call developers those people that have
with write access to the lyx repository.
Ok, I'll go along with that for this thread (it's good to have a term for
that category, but 'developer' is to restritive, so later we could try
[EMAIL PROTECTED] wrote:
The skin Blog already has CMS stuff prepared. I could make the default
if we want.
For now it's a good one to use as default.
Joost
On Wednesday 26 March 2008 14:11:36 [EMAIL PROTECTED] wrote:
> I don't understand your point...? Does this have some bearing on access
> to the wiki and/or aussie? I'm probably confused because it _is_ possible
> to introduce "roles" in the wiki, letting different classes of users do
> different
On Wed, 26 Mar 2008, José Matos wrote:
On Tuesday 25 March 2008 22:13:56 [EMAIL PROTECTED] wrote:
I think it's important to have some pages look "official", and even more
important that e.g. the download pages are secure. For this reason I'd
like to have a distinction between them. However, we
On Tuesday 25 March 2008 22:13:56 [EMAIL PROTECTED] wrote:
> I think it's important to have some pages look "official", and even more
> important that e.g. the download pages are secure. For this reason I'd
> like to have a distinction between them. However, we could think about
> porting the pages
Andre Poenitz wrote:
Could you _please_ stop posting-on-top-and-full-quoting-below?
More than 50% of what you quote are not relevant to what you say,
and providing context _after_ comments to it is not the natural
flow of reading.
Andre'
PS: @everybody else: This is the second try ;-)
Sorry
On Tue, 25 Mar 2008, Edwin Leuven wrote:
[EMAIL PROTECTED] wrote:
and tell me like 3-4 of them you like, and then I can install those!
these look the least like ... wiki's
http: //www.pmwiki.org/wiki/Cookbook/ABitModernSkin
http: //www.pmwiki.org/wiki/Cookbook/BarthelmeSkin
http: //www.pmwi
On Wed, 26 Mar 2008, Peter Kümmel wrote:
Joost Verburg wrote:
Edwin Leuven wrote:
> http://www.pmwiki.org/wiki/Cookbook/ABitModernSkin
I've also used it for the Loki page (a bit smaller):
http://loki-lib.sourceforge.net/
I've installed ABitModernSkin, try this link:
http://www.lyx.org/~
On Wed, 26 Mar 2008, Andre Poenitz wrote:
Could you _please_ stop posting-on-top-and-full-quoting-below?
PS: @everybody else: This is the second try ;-)
Hi Rex,
If you're using Outlook or Outlook Expresse, the links here might help:
http://wiki.lyx.org/FAQ/ListNetiquette#toc9
c
On Tue, Mar 25, 2008 at 06:25:59PM -0400, Rex C. Eastbourne wrote:
> By the way, link to new wiki, again:
> http://www.lyx.org/~chr/www/org/index.php
>
> On Tue, Mar 25, 2008 at 6:12 PM, Rex C. Eastbourne <[EMAIL PROTECTED]>
> wrote:
>
> > I went ahead and ported a bit of lyx.org over to the new
Joost Verburg wrote:
Edwin Leuven wrote:
http://www.pmwiki.org/wiki/Cookbook/ABitModernSkin
I've also used it for the Loki page (a bit smaller):
http://loki-lib.sourceforge.net/
--
Peter Kümmel
On Tue, 25 Mar 2008, Edwin Leuven wrote:
[EMAIL PROTECTED] wrote:
and tell me like 3-4 of them you like, and then I can install those!
these look the least like ... wiki's
http: //www.pmwiki.org/wiki/Cookbook/ABitModernSkin
http: //www.pmwiki.org/wiki/Cookbook/BarthelmeSkin
http: //www.pmwi
Edwin Leuven wrote:
http://www.pmwiki.org/wiki/Cookbook/ABitModernSkin
With some different colors this one could look nice.
Joost
[EMAIL PROTECTED] wrote:
> and tell me like 3-4 of them you like, and then I can install those!
these look the least like ... wiki's
http://www.pmwiki.org/wiki/Cookbook/ABitModernSkin
http://www.pmwiki.org/wiki/Cookbook/BarthelmeSkin
http://www.pmwiki.org/wiki/Cookbook/SimpleTabSkin
Any cool skins we can try now?
Oh, when I think about it, a better idea if you look at skins at
http://www.pmwiki.org/wiki/Cookbook/Skins
and tell me like 3-4 of them you like, and then I can install those!
Note that you should be able to preview the skins at pmwiki.org, not just
read ab
On Tue, 25 Mar 2008, Rex C. Eastbourne wrote:
http://diberri.dyndns.org/wikipedia/html2wiki/index.html).
Nice!
One thing on my mind is the sidebar. Do you think people will view the
sidebar headers as clickable, or will they gravitate toward the elements
within them?.
Unfortunately people
By the way, link to new wiki, again:
http://www.lyx.org/~chr/www/org/index.php
On Tue, Mar 25, 2008 at 6:12 PM, Rex C. Eastbourne <[EMAIL PROTECTED]>
wrote:
> I went ahead and ported a bit of lyx.org over to the new wiki. This was a
> quick and dirty task (the links still point to the old site, a
On Mon, 24 Mar 2008, Joost Verburg wrote:
[EMAIL PROTECTED] wrote:
* wiki.lyx.org will remain the wiki - there is no integration of content.
It will be clear what is official and what is community.
The wiki may, or may not, keep it's current look.
Why not integrate the current wiki wit
On Mon, 24 Mar 2008, Andre Poenitz wrote:
restricted. Currently, protection is already in place for important
pages on wiki.lyx.org.
Note that many wiki pages are currently maintained by developers. The
only reason why they are on the wiki is because adding new pages and
content to www.lyx.o
I went ahead and ported a bit of lyx.org over to the new wiki. This was a
quick and dirty task (the links still point to the old site, and no content
has changed), but it should be enough to get a feel for what it'll look
like. All I did was modify the sidebar to re-create the same basic
structure,
[EMAIL PROTECTED] writes:
> Sounds like it should be possible, although I'm not sure what you mean.
> One way could be to have some kind of script run at commit of certain
> files, and this script would then generate the relevant data which in
> turned is inserted into wiki pages (or parsed furthe
On Tue, 25 Mar 2008, Jean-Marc Lasgouttes wrote:
[EMAIL PROTECTED] writes:
Ok, so no one seems to object to using the wiki engine for the framework.
We also seem to agree on the following:
* www.lyx.org will be replaced by something that uses a wiki engine for
the CMS.
It will not look li
On Tue, 25 Mar 2008, Jean-Marc Lasgouttes wrote:
"Dominik Böhm" <[EMAIL PROTECTED]> writes:
Having a look at www.lyx.com, I don't see very much dynamic content.
Everything looks pretty static -- the only thing that gets updated
frequently are the new and download section (and the (external) wi
On Mon, 24 Mar 2008, Rex C. Eastbourne wrote:
Great, Christian! Should we now manually copy and paste content over
from the current website and wikify it?
Yes, we can start doing that if we'd like. Actually, it's probably a good
idea to do so for at least two or three pages. Then, when we app
[EMAIL PROTECTED] writes:
> Ok, so no one seems to object to using the wiki engine for the framework.
> We also seem to agree on the following:
>
> * www.lyx.org will be replaced by something that uses a wiki engine for
> the CMS.
> It will not look like a wiki, although that's what it actuall
"Dominik Böhm" <[EMAIL PROTECTED]> writes:
> Having a look at www.lyx.com, I don't see very much dynamic content.
> Everything looks pretty static -- the only thing that gets updated
> frequently are the new and download section (and the (external) wiki
> of course). So, lyx.org looks to me like a
Great, Christian! Should we now manually copy and paste content over
from the current website and wikify it?
Rex
On Mon, Mar 24, 2008 at 4:48 PM, <[EMAIL PROTECTED]> wrote:
> On Mon, 24 Mar 2008, [EMAIL PROTECTED] wrote:
>
> > 1. Set up a framework
>
> I've started on the framework and there i
On Mon, Mar 24, 2008 at 10:36:33PM +0100, Joost Verburg wrote:
> Andre Poenitz wrote:
>> I don't think I agree. The "community" is much better at keeping vital
>> contents up-to-date then the "core developers" are. Look at what we have
>> now: The "developer maintained official pages" that are most
[EMAIL PROTECTED] wrote:
* wiki.lyx.org will remain the wiki - there is no integration of content.
It will be clear what is official and what is community.
The wiki may, or may not, keep it's current look.
Why not integrate the current wiki with the new site, so they can share
the same des
Andre Poenitz wrote:
I don't think I agree. The "community" is much better at keeping vital
contents up-to-date then the "core developers" are. Look at what we have
now: The "developer maintained official pages" that are mostly correct
when talking about last millenium's achievements, and a wiki
On Mon, Mar 24, 2008 at 03:52:12PM +0100, Joost Verburg wrote:
> Pavel Sanda wrote:
>>> An integration of the main site and the wiki is a great idea. If the wiki
>>> functions are hidden for the "official" content and only shown when an
>>> authenticated user is logged in, it still looks professi
On Mon, 24 Mar 2008, [EMAIL PROTECTED] wrote:
1. Set up a framework
I've started on the framework and there is now a basic wiki here:
http://www.lyx.org/~chr/www/org/index.php
This wiki, or rather, it's contents, will later become the new web site.
Feel free to start editing pages or
On Mon, 24 Mar 2008, Joost Verburg wrote:
I'm for the KISS approach here, but would also like to suggest that we use
some version of the wiki engine with a CMS extension. There are many users
skins you find everywhere. http://cms.ww-a.de/index.php/Main/HomePage for
Ok, so no one seems to
> In my opinion the current wiki content should be something like a separate
> "community" section, not a part of the official web. But I think using the
yes.
> I only wanted to say that we should keep it this way for the new wiki CMS
> accounts.
yes, it may be that wiki way of changing thing
Pavel Sanda wrote:
An integration of the main site and the wiki is a great idea. If the wiki
functions are hidden for the "official" content and only shown when an
authenticated user is logged in, it still looks professional and not too
much like a wiki.
then you have problem that many pages
> An integration of the main site and the wiki is a great idea. If the wiki
> functions are hidden for the "official" content and only shown when an
> authenticated user is logged in, it still looks professional and not too
> much like a wiki.
then you have problem that many pages in wiki which
[EMAIL PROTECTED] wrote:
I'm for the KISS approach here, but would also like to suggest that we
use some version of the wiki engine with a CMS extension. There are many
users that have taken this particular wiki engine and used it as a CMS.
The advantage is that I can help with setting it up, a
I like the PmWiki approach as well. I think it would work well as long as it
doesn't *look* like a wiki; the first website you linked to looks fine, so
if we can get something similar going, we'll be in good shape.
I'm not familiar with templates for PmWiki (or in general, really). Would we
want t
On Sun, 23 Mar 2008, Joost Verburg wrote:
Dominik Böhm wrote:
Honestly I think the website shouldn't be completely self made from
scratch. I would use a content management system, be it Python-, PHP-
or RoR-based. I personally have worked quite some times with Typo3
(PHP) and think that thi
Dominik Böhm wrote:
Honestly I think the website shouldn't be completely self made from
scratch. I would use a content management system, be it Python-, PHP-
or RoR-based. I personally have worked quite some times with Typo3
(PHP) and think that this is a great system that offers a lot of
functio
On Sun, Mar 23, 2008 at 1:09 PM, <[EMAIL PROTECTED]> wrote:
> Today it's a lot of php-scripts, and I don't even know who (besides Lars)
> that is familiar with it's structure. Do we want to stick with PHP and
> just make changes to the appearance, or is it ok for Rex to also change to
> a diff
Hi,
What kind of constraints do we have on the "backend" of the framework?
Today it's a lot of php-scripts, and I don't even know who (besides Lars)
that is familiar with it's structure. Do we want to stick with PHP and
just make changes to the appearance, or is it ok for Rex to also change to
45 matches
Mail list logo
