From: Carsten H. (T. R. <ra...@ra...> - 2007-04-22 06:41:49
|
OK... First. If you didn't already know, the new E servers are up and running. Anonymous CVS has been server off one of them now for several weeks. The other is having a whole bunch of web "services" put up. But we now need help. I need help filling in the main website. It is all in CVS in the www module. just need to edit and commit and the website auto-updates. Currently it's available on http://web.enlightenment.org I have put up most of a skeleton and have started filling in content. If anyone wants to help fill in content - please tell me. if you have CVS write access, you can already help. all those people wanting to help, but who "can't code" - this is your chance :) In addition there is a wiki, forums and bugtracker up too - linked too already. once web.enlightenment.org is filled - we will switch www.enlightenment.org over and be all 100% up on the new site. -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ra...@ra... 裸好多 Tokyo, Japan (東京 日本) |
From: Luchezar P. <luc...@gm...> - 2007-04-22 08:07:46
|
Carsten Haitzler (The Rasterman) wrote: > OK... > > First. If you didn't already know, the new E servers are up and running. > Anonymous CVS has been server off one of them now for several weeks. The other > is having a whole bunch of web "services" put up. But we now need help. > > I need help filling in the main website. It is all in CVS in the www module. > just need to edit and commit and the website auto-updates. > > Currently it's available on http://web.enlightenment.org > > I have put up most of a skeleton and have started filling in content. If anyone > wants to help fill in content - please tell me. if you have CVS write access, > you can already help. all those people wanting to help, but who "can't code" - > this is your chance :) > > In addition there is a wiki, forums and bugtracker up too - linked too already. > once web.enlightenment.org is filled - we will switch www.enlightenment.org > over and be all 100% up on the new site. > > I'm in. You may want to correct my english mistakes if any and to format the text if needed. |
From: Carsten H. (T. R. <ra...@ra...> - 2007-04-24 11:08:55
|
On Sun, 22 Apr 2007 10:06:56 +0300 Luchezar Petkov <luc...@gm...> babbled: > Carsten Haitzler (The Rasterman) wrote: > > OK... > > > > First. If you didn't already know, the new E servers are up and running. > > Anonymous CVS has been server off one of them now for several weeks. The > > other is having a whole bunch of web "services" put up. But we now need > > help. > > > > I need help filling in the main website. It is all in CVS in the www module. > > just need to edit and commit and the website auto-updates. > > > > Currently it's available on http://web.enlightenment.org > > > > I have put up most of a skeleton and have started filling in content. If > > anyone wants to help fill in content - please tell me. if you have CVS > > write access, you can already help. all those people wanting to help, but > > who "can't code" - this is your chance :) > > > > In addition there is a wiki, forums and bugtracker up too - linked too > > already. once web.enlightenment.org is filled - we will switch > > www.enlightenment.org over and be all 100% up on the new site. > > > > > I'm in. > You may want to correct my english mistakes if any and to format the > text if needed. going to worry about unimportant things like correct english .... later :) > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > enlightenment-devel mailing list > enl...@li... > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ra...@ra... 裸好多 Tokyo, Japan (東京 日本) |
From: Luchezar P. <luc...@gm...> - 2007-04-25 20:06:09
|
Carsten Haitzler (The Rasterman) wrote: > OK... > > Ok.. As you may noticed, I've putted some content. I need your opinion on it - is it nice, are the images nice - are they too big or too small or are they nice at all. And... About the content of the site.. We need a small plan. My ideas are: 2) Separate the documentation - User documentation and Developers documentation 1) Rewrite/update the user guide on get-e.org and move it in the official site as user documentation. It will cover ONLY e17 itself and the official modules (ibar, ibox, etc etc) 2) Anything that is outside of E17 itself should have it's documentation on the wiki. All maintained stuff in apps/ and e_modules/. Bigger projects such as Etk and Ewl can have their own web sites if wiki page is not enough for them - etk.enlightenment.org, ewl.enlightenment.org or with their own domains. 3) Rewrite/update the current developers documentation for core EFL. Libraries that are outside of core EFL should have their documentation on the wiki. I can't help here, unfortunately - I'm not a hacker myself. The question here is: should the themeing docs be in this section or they should stay in the wiki? Should we include documentation for translation? 4) Make get-e.org a site only for resources - themes, wallpapers, unoffical modules, maybe. Just like now, but without the documentation. (it will be pointless if we move the docs on e.org) Tell me what you think and I'll start working on it as far as I can. |
From: Florent T. <ft...@gm...> - 2007-04-26 08:52:35
|
Hello > My ideas are: > 2) Separate the documentation - User documentation and Developers > documentation > 1) Rewrite/update the user guide on get-e.org and move it in the > official site as user documentation. It will cover ONLY e17 itself and > the official modules (ibar, ibox, etc etc) > 2) Anything that is outside of E17 itself should have it's documentation > on the wiki. All maintained stuff in apps/ and e_modules/. Bigger > projects such as Etk and Ewl can have their own web sites if wiki page > is not enough for them - etk.enlightenment.org, ewl.enlightenment.org or > with their own domains. Why not putting everything into the wiki, and keep small static separate pages only for main projects? The wiki will allow really easy and collaborative content editing, the best of the content can be compiled on a dedicated webpage, leading to the wiki for details... For instance, the theming will need links towards the core doc. > 3) Rewrite/update the current developers documentation for core EFL. > Libraries that are outside of core EFL should have their documentation > on the wiki. I can't help here, unfortunately - I'm not a hacker myself. > The question here is: should the themeing docs be in this section or > they should stay in the wiki? Should we include documentation for > translation? I think that the theming case is special, and should be presented separately (theming.enlightenment.org), wih a full theming tutorial. > 4) Make get-e.org a site only for resources - themes, wallpapers, > unoffical modules, maybe. And snapshots & binary repositories links (or reciepes). I always found it quite hard to find this info in edevelop.org Also, why not creating a planet site? As all the main devs have blogs, this would be quite straightforward. Florent |
From: Carsten H. (T. R. <ra...@ra...> - 2007-04-30 04:46:56
|
On Wed, 25 Apr 2007 22:05:04 +0300 Luchezar Petkov <luc...@gm...> babbled: > Carsten Haitzler (The Rasterman) wrote: > > OK... > > > > > Ok.. > As you may noticed, I've putted some content. I need your opinion on it > - is it nice, are the images nice - are they too big or too small or are > they nice at all. > And... About the content of the site.. We need a small plan. > My ideas are: > 2) Separate the documentation - User documentation and Developers > documentation definitely. devs have need of different info than users. > 1) Rewrite/update the user guide on get-e.org and move it in the > official site as user documentation. It will cover ONLY e17 itself and > the official modules (ibar, ibox, etc etc) as an "enlightenment" user guide - absolutely. if people want OTHER guides (ewl guide, rage guide, entrance guide etc.) then definitely write those. but i think we need to split things up. have some overall documentation that tells you which is which (e is a wm, entrance a login manager, etc. etc.) > 2) Anything that is outside of E17 itself should have it's documentation > on the wiki. All maintained stuff in apps/ and e_modules/. Bigger > projects such as Etk and Ewl can have their own web sites if wiki page > is not enough for them - etk.enlightenment.org, ewl.enlightenment.org or > with their own domains. even e17 itself should be on the wiki - the www site is for now only a "brochure" site and being set up to hold content for when a release happens. any apps that get enough developer support and maintenance behind them and have a good level of quality could become "official" too. > 3) Rewrite/update the current developers documentation for core EFL. > Libraries that are outside of core EFL should have their documentation > on the wiki. I can't help here, unfortunately - I'm not a hacker myself. > The question here is: should the themeing docs be in this section or > they should stay in the wiki? Should we include documentation for > translation? wiki is good. for theme docs too. and for translation. > 4) Make get-e.org a site only for resources - themes, wallpapers, > unoffical modules, maybe. Just like now, but without the documentation. > (it will be pointless if we move the docs on e.org) sounds good to me - a resource site :) > Tell me what you think and I'll start working on it as far as I can. > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > enlightenment-devel mailing list > enl...@li... > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ra...@ra... 裸好多 Tokyo, Japan (東京 日本) |
From: Mathieu T. <mat...@fr...> - 2007-04-30 16:47:58
|
Hello, > wiki is good. for theme docs too. and for translation. > I can probably handle the French translation if you want. Mathieu |
From: Luchezar P. <luc...@gm...> - 2007-04-26 12:31:20
|
dan sinclair wrote: > > On 25-Apr-07, at 3:05 PM, Luchezar Petkov wrote: >> Ok.. >> As you may noticed, I've putted some content. I need your opinion on it >> - is it nice, are the images nice - are they too big or too small or are >> they nice at all. > > I think their a bit on the big side. A few images are fine but I don't > think we want to go off and add images for every single section title > that we'll have on the site. Do we really need a performance image? > Isn't the header good enough? > > Don't get me wrong, the images look good, we just don't want to over > clutter the site. Ends up looking too busy. Ok, I'll try to fix it. > > >> And... About the content of the site.. We need a small plan. >> My ideas are: >> 2) Separate the documentation - User documentation and Developers >> documentation > > This is essentially done. docs.e.org needs to be re-written but it's > already split into sections for EFL docs, the books and the wm docs. Good. > > >> 1) Rewrite/update the user guide on get-e.org and move it in the >> official site as user documentation. It will cover ONLY e17 itself and >> the official modules (ibar, ibox, etc etc) > > We can cover other applications as we see fit. There is no reason it has > to be just e17. enlightenment isn't only the wm. What about entrance or > other applications we create. Their just as much a part of the > enlightenment project. > > >> 2) Anything that is outside of E17 itself should have it's documentation >> on the wiki. All maintained stuff in apps/ and e_modules/. Bigger >> projects such as Etk and Ewl can have their own web sites if wiki page >> is not enough for them - etk.enlightenment.org, ewl.enlightenment.org or >> with their own domains. > > This I disagree with. Enlightenment isn't just the WM. We want product > pages for the different libs on the main site that not everyone can > change. The currently setup works well with the libraries having a page > under the about libraries section. This should stay. We might also want > to add entrance or other apps as they become useful to the site. > > Adding a subdomain per library is going to get unwieldy pretty quick. > Sure they'll all have wiki sites as well. Ewl has a lot of information > on the wiki. We still want it on the main site. Everything in apps/ (except E and perhaps Entrance) and in e_modules/ is just hosted on our CVS. Anyone can write an app and host it somewhere else. Imagine this situation: we work hardly we release E. Great. But when people start to write modules and apps using EFL they will be using their own places to host their work. The fact that Ephoto, Exhibit and Extract (for example) are hosted on E CVS does not make them "special" or essential parts of the project. They are separate projects. They are all important because they are some of the first good and working apps written using EFL. Nothing more. Thus, in my opinion, we have to document their features in the wiki - as every new application that will pop up in the future (if the author(s) wants to use E's wiki). > > >> 3) Rewrite/update the current developers documentation for core EFL. >> Libraries that are outside of core EFL should have their documentation >> on the wiki. I can't help here, unfortunately - I'm not a hacker myself. >> The question here is: should the themeing docs be in this section or >> they should stay in the wiki? Should we include documentation for >> translation? > > > Define core EFL. Do you mean just what the WM requires as that cuts out > a large chunk of the enlightenment code. Anything in libs, that isn't > dead, should be game to have a section on the website. Well, the biggest and maintained libraries can have their subdomains and separate websites with docs, wikis and whatever you want.Etk had its own web site, but seems that it's currently offline. But I just don't see a reason to include, for example, Engrave - small library, not much maintained, don't need big documentation, so a wiki page(s) perhaps will be the proper choice for it. If you really want all working/maintained libs documented on the site - ok, no problem. Yet, read above what I've said about the apps and modules - imo, its the same situation with the libs that E does not depend on. > > Themeing and translation docs should appear on the wiki as they'll > inherently have a lot of changes. Agreed. > > > dan > > > > |
From: Luchezar P. <luc...@gm...> - 2007-04-30 17:49:28
|
Mathieu Taillefumier wrote: > Hello, >> wiki is good. for theme docs too. and for translation. >> > I can probably handle the French translation if you want. we're talking about translation documentation, not to translate the documentation :-) ie how to translate E, who translate is, etc And if you want, wait until the user guide and the site content is finished and translate them. You can also translate other articles in the wiki. > > Mathieu > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > enlightenment-users mailing list > enl...@li... > https://lists.sourceforge.net/lists/listinfo/enlightenment-users > |
From: Andres <and...@gm...> - 2007-04-30 20:26:09
|
El Lunes 30 Abril 2007 13:48, Luchezar Petkov escribi=F3: > Mathieu Taillefumier wrote: > > Hello, > > > >> wiki is good. for theme docs too. and for translation. > > > > I can probably handle the French translation if you want. > > we're talking about translation documentation, not to translate the > documentation :-) ie how to translate E, Like this? http://wiki.enlightenment.org/index.php/Translating_Enlightenment |