On Thu, 26 Apr 2007 08:56:58 -0400 dan sinclair <[EMAIL PROTECTED]> babbled:
yup :) also remember - the website is not static - it's an evolving thing, but the www site compared to wiki is meant to be much more static. if people wish to collaborate on documentation and guides to start with the wiki is a great place. as dan says - once things settle they can be "release on gold" on the main site - but that also depends on the code and projects they document getting a release. > Luchezar Petkov wrote: > > dan sinclair wrote: > >> > >> On 25-Apr-07, at 3:05 PM, Luchezar Petkov wrote: > >>> 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). > > > > > Being hosted in _our_ cvs makes it very much a part of the enlightenment > project (and somethings that aren't). Some of those apps make really > good examples of e code. Elicit for example. They also don't change > enough for them to need a wiki. > > The wiki and the website have two completly different purposes. The > website is our broucheor we want to be able to show people what we can > do and what we've got available. The wiki is for changing documentation. > Stuff that needs to be updated a lot. The e user guide should go on the > wiki for now. At release we'll port it to the main site. > > Just because an app _uses_ the efl doesn't mean it's part of > enlightenment. We don't have to host them on our site and they should, > at most, have a mention in our wiki. We don't want our wiki used to > support random project X. It can be linked but they should deal with > their own infrastructure. Unless their part of e. > > Being in cvs is the main definition of being part of the enlightenment > project. We are our cvs. > > The enlightement wiki is for enlightenment and enlightenment projects. > Ruby-EFL is a good example of an external project that fits on our 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. > >> > > > Even if Engrave isn't a major lib it shoudl still appear on the site as > it serves a purpose. You should go back and read what I said. > Enlightenment isn't just the window manager. Let me repeat that, > Enlightenment isn't just the window manager. We are our code. All of the > current libs. > > Engrave doesn't need much maintenance at the moment. It's been kept up > to date with most edje changes recently. > > Should we not have eet on there as it's small and doesn't get a lot of > changes.... > > The wiki is handy but it isn't hte catch all you want it to be and it > really shouldn't be. > > > dan > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [EMAIL PROTECTED] 裸好多 Tokyo, Japan (東京 日本) ------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
