Hi Guys,
I am wondering where to post an Artwork SIG ToDo list. A place for people to request artwork things, something that could be used as a list of task or something like that. Distribution needs, users need, developers need, whatever ...
Any suggestion ?
Thanks, al.
Alain Reguera Delgado wrote:
Hi Guys,
I am wondering where to post an Artwork SIG ToDo list. A place for people to request artwork things, something that could be used as a list of task or something like that. Distribution needs, users need, developers need, whatever ...
Any suggestion ?
Trac? I've never really worked with it, but it seems to have a place for Roadmaps and similar stuff. Problem with trac is, that not all content is in one place.
Did you get to do the stuff you wanted to do before we announce the Artwork SIG properly?
Cheers,
Ralph
On 9/17/08, Ralph Angenendt ra+centos@br-online.de wrote:
Alain Reguera Delgado wrote:
Hi Guys,
I am wondering where to post an Artwork SIG ToDo list. A place for people to request artwork things, something that could be used as a list of task or something like that. Distribution needs, users need, developers need, whatever ...
Any suggestion ?
Trac? I've never really worked with it, but it seems to have a place for Roadmaps and similar stuff. Problem with trac is, that not all content is in one place.
Did you get to do the stuff you wanted to do before we announce the Artwork SIG properly?
Yes, it is wiki. But maybe it should be on Trac instead, as Marcus suggested, so the content be in a single place, and the trac roadmaps and tickets could be used. What do you think Ralph ? Do we move the content ?
Cheers, al.
On Wed, 17 Sep 2008, Ralph Angenendt wrote:
Alain Reguera Delgado wrote:
Hi Guys,
I am wondering where to post an Artwork SIG ToDo list. A place for people to request artwork things, something that could be used as a list of task or something like that. Distribution needs, users need, developers need, whatever ...
Any suggestion ?
Trac? I've never really worked with it, but it seems to have a place for Roadmaps and similar stuff. Problem with trac is, that not all content is in one place.
Did you get to do the stuff you wanted to do before we announce the Artwork SIG properly?
I would prefer if something like the TODO list is easily accessible. Where it is located should not matter that much, but the SIG pages should have some identical structure, and the TODO list belongs on that SIG wiki page.
The main reason is that we need to make it easy for people visiting the pages to find things like TODO items. And a list of TODO lists could be then referenced from the Contribute page.
On 9/17/08, Dag Wieers dag@centos.org wrote:
On Wed, 17 Sep 2008, Ralph Angenendt wrote:
Alain Reguera Delgado wrote:
Hi Guys,
I am wondering where to post an Artwork SIG ToDo list. A place for people to request artwork things, something that could be used as a list of task or something like that. Distribution needs, users need, developers need, whatever ...
Any suggestion ?
Trac? I've never really worked with it, but it seems to have a place for Roadmaps and similar stuff. Problem with trac is, that not all content is in one place.
Did you get to do the stuff you wanted to do before we announce the Artwork SIG properly?
I would prefer if something like the TODO list is easily accessible. Where it is located should not matter that much, but the SIG pages should have some identical structure, and the TODO list belongs on that SIG wiki page.
Thinking in your requested download page redesign http://isoredirect.centos.org/centos/5/isos/i386/ I updated the page http://wiki.centos.org/SpecialInterestGroup/Artwork/Status so an artwork TODO list could be filled there.
The main reason is that we need to make it easy for people visiting the pages to find things like TODO items. And a list of TODO lists could be then referenced from the Contribute page.
If we keep content on the wiki, the Artwork SIG can already be announced.
Cheers, al.
Dear Alain.
Yes, it is wiki. But maybe it should be on Trac instead, as Marcus suggested, so the content be in a single place, and the trac roadmaps
I have not really suggested to use this or that. I just wantet to make clear that we should keep the content in one single place for better maintainance.
There are some disadvantages in using trac which I have already lined out. One is the 'bad url' to access the trac pages. If artwork.centos.org (or something like that) would link to trac and the wiki just points there, all content could be kept in the trac wiki.
Best Regards Marcus
On 9/17/08, Marcus Moeller mm@gcug.de wrote:
Dear Alain.
Yes, it is wiki. But maybe it should be on Trac instead, as Marcus suggested, so the content be in a single place, and the trac roadmaps
I have not really suggested to use this or that.
Ohh! ... please accept my apologies Marcus, I misunderstood your lines.
I just wantet to make clear that we should keep the content in one single place for better maintainance.
I agree with that.
Cheers, al.
Marcus Moeller wrote:
I have not really suggested to use this or that. I just wantet to make clear that we should keep the content in one single place for better maintainance.
I agree. And trac provides a very good mechanism for this. Given that its in use such widely, a lot of people are already familiar with the milestones / aims / features and the fact that you can url into the scm from the wiki makes in-revision tracking trivial. You can also assocated issues with milestones and releases and handle wiki content within the same context.
So it can be as easy as you want, but it can also easily do more complex things if you need it to.
There are some disadvantages in using trac which I have already lined out. One is the 'bad url' to access the trac pages. If artwork.centos.org (or something like that) would link to trac and the wiki just points there, all content could be kept in the trac wiki.
the URL issue does not look like anything major to me personally, also I dont see much of a differences in https://projects.centos.org/ and http://artwork.centos.org. Specially since the trac wiki is only 1 click away from the https://projects.centos.org link. The wiki.centos.org page at http://wiki.centos.org/Projects can have a few more comments about each project if so required.
- KB
On 9/17/08, Karanbir Singh mail-lists@karan.org wrote:
Marcus Moeller wrote:
I have not really suggested to use this or that. I just wantet to make clear that we should keep the content in one single place for better maintainance.
I agree. And trac provides a very good mechanism for this. Given that its in use such widely, a lot of people are already familiar with the milestones / aims / features and the fact that you can url into the scm from the wiki makes in-revision tracking trivial. You can also assocated issues with milestones and releases and handle wiki content within the same context.
So it can be as easy as you want, but it can also easily do more complex things if you need it to.
There are some disadvantages in using trac which I have already lined out. One is the 'bad url' to access the trac pages. If artwork.centos.org (or something like that) would link to trac and the wiki just points there, all content could be kept in the trac wiki.
the URL issue does not look like anything major to me personally, also I dont see much of a differences in https://projects.centos.org/ and http://artwork.centos.org. Specially since the trac wiki is only 1 click away from the https://projects.centos.org link. The wiki.centos.org page at http://wiki.centos.org/Projects can have a few more comments about each project if so required.
Ok. I believe we should move the http://wiki.centos.org/ArtWork content to https://projects.centos.org/trac/artwork/wiki ... if there is no one against that. So the Trac facilities on projects management could be used.
If that is ok ... some help would be nice :D
Cheers, al.
Dear Alain.
Ok. I believe we should move the http://wiki.centos.org/ArtWork content to https://projects.centos.org/trac/artwork/wiki ... if there is no one against that. So the Trac facilities on projects management could be used.
If that is ok ... some help would be nice :D
We should just start. Please tell me which subsites I should migrate.
Btw. do you think that the new Trac design could already be set up?
Best Regards Marcus
On 9/19/08, Marcus Moeller mm@gcug.de wrote:
Dear Alain.
Ok. I believe we should move the http://wiki.centos.org/ArtWork content to https://projects.centos.org/trac/artwork/wiki ... if there is no one against that. So the Trac facilities on projects management could be used.
If that is ok ... some help would be nice :D
We should just start. Please tell me which subsites I should migrate.
Well initially I thought to move the http://wiki.centos.org/ArtWork pages and subpages ... but I am a little worried .... I tried to enter http://wiki.centos.org/ and a "Operation timed out" was the response to me :(. www.centos.org is in the same situation.
Btw. do you think that the new Trac design could already be set up?
I guess it could, if someone could test it and confirm it is ready for that.
Cheers, al.
On 9/19/08, Alain Reguera Delgado alain.reguera@gmail.com wrote:
but I am a little worried .... I tried to enter http://wiki.centos.org/ and a "Operation timed out" was the response to me :(. www.centos.org is in the same situation.
Lets go now! ... they are back again :).
Thanks, al.
Alain Reguera Delgado wrote:
Well initially I thought to move the http://wiki.centos.org/ArtWork pages and subpages ... but I am a little worried .... I tried to enter http://wiki.centos.org/ and a "Operation timed out" was the response to me :(. www.centos.org is in the same situation.
there was a glitch in the universe, all fixed for now. A longer term fix is in the planning stages.
- KB
On 9/19/08, Marcus Moeller mm@gcug.de wrote:
Dear Alain.
Ok. I believe we should move the http://wiki.centos.org/ArtWork content to https://projects.centos.org/trac/artwork/wiki ... if there is no one against that. So the Trac facilities on projects management could be used.
If that is ok ... some help would be nice :D
We should just start. Please tell me which subsites I should migrate.
In the http://wiki.centos.org/ArtWork :
Could you start migrating links from bottom to top ? I'll go from top to bottom ... or in reverse ?
Cheers, al.
Dear Alain.
In the http://wiki.centos.org/ArtWork :
Could you start migrating links from bottom to top ? I'll go from top to bottom ... or in reverse ?
Formatting on the Trac Wiki seems to be slightly different. Have you already figured out if it's possible to add style/rowstyle definitions?
Best Regards Marcus
On 9/19/08, Marcus Moeller mm@gcug.de wrote:
Dear Alain.
...
Formatting on the Trac Wiki seems to be slightly different. Have you already figured out if it's possible to add style/rowstyle definitions?
That's something that I could look in after CentOSify the punbb application presentation to get a common look for each lang.centos.org/forum/. punbb is just a proposition for that section of course. After that, and if Puntal tar.gz file continue lost ... we can give another Trac style round to see these kind of things, if no urgent or top level need appears. Maybe this is a good moment to start ticketing on artwork trac environment ;) so the roadmap be created.
Also attachment seems to be handled differently. Did you already manage to upload attachments?
Well as far as I've seen now, attachments are displayed at the end of the page, if the attachment are images we can use the Macro [[Image]] to refer the attachment so they can be used ... there are interesting things with that macro that I have not tested yet, like resizing a big image. If that is possible we can just upload the Screenshot-X.png and show them as small images ... just wondering about what https://projects.centos.org/trac/artwork/wiki/WikiMacros says.
If attachment are no images, we could leave them at the end of the page, and if possible refer to them where needed.
Maybe we start with a few errors at the beginning, but they could be fixed walking the way. Also Ralph and Karan seems to be near us to help :D.
Cheers, al.
Good Evening.
That's something that I could look in after CentOSify the punbb application presentation to get a common look for each lang.centos.org/forum/. punbb is just a proposition for that section of course. After that, and if Puntal tar.gz file continue lost ... we can give another Trac style round to see these kind of things, if no urgent or top level need appears. Maybe this is a good moment to start ticketing on artwork trac environment ;) so the roadmap be created.
Hmm, I did not even know you are already working on it.
Well as far as I've seen now, attachments are displayed at the end of the page, if the attachment are images we can use the Macro [[Image]] to refer the attachment so they can be used ... there are interesting things with that macro that I have not tested yet, like resizing a big image. If that is possible we can just upload the Screenshot-X.png and show them as small images ... just wondering about what https://projects.centos.org/trac/artwork/wiki/WikiMacros says.
Okay, I managed to upload and include images. Now I need to know it's possible to add col/rowspan to tables?
If attachment are no images, we could leave them at the end of the page, and if possible refer to them where needed.
I already found out that it's not very usable to have an edit button at the bottom of a page :/
Best Regards Marcus
Dear Alain.
Okay, I managed to upload and include images. Now I need to know it's possible to add col/rowspan to tables?
Styling Trac wiki pages seems to be nearly impossible. Trac wiki syntax has a number of deficiencies which cannot be solved easily. Eg. it simply does not support row/colspan on tables. The only way is to use plain HTML syntax like:
{{{ #!html <h1 style="text-align: right; color: blue">HTML Sucks</h1> }}}
which cannot be combined with the wiki syntax of course. This means we either cannot use the trac wiki or we have to hack most parts in HTML. This also means if you want to include attachments you have to use HTML style, too.
Best Regards Marcus
On 9/19/08, Marcus Moeller mm@gcug.de wrote:
Dear Alain.
Okay, I managed to upload and include images. Now I need to know it's possible to add col/rowspan to tables?
Styling Trac wiki pages seems to be nearly impossible. Trac wiki syntax has a number of deficiencies which cannot be solved easily. Eg. it simply does not support row/colspan on tables. The only way is to use plain HTML syntax like:
{{{ #!html
<h1 style="text-align: right; color: blue">HTML Sucks</h1> }}}
which cannot be combined with the wiki syntax of course. This means we either cannot use the trac wiki or we have to hack most parts in HTML. This also means if you want to include attachments you have to use HTML style, too.
I think we should update the actual content based on the actual Trac default wiki syntax, or if there is another way to make it ...
Guys ... would be possible to install some kind of photoblog under centos domain ? Something that let us upload a big image and generates thumbs of it for us to use ... something like http://www.pixelpost.org/. That way we could handle images/screenshots there and just refer them on Trac, Moin, wherever site ... That would be all about CentOS officially online images ... maybe contributors help with a section of personal screenshots ... a section for the artwork project (of course :D) ... and as many section as community consider helpful ... just a way to handle images and its sizes.
Some times attachments list on Trac could be quiet large ... and could look a bit ugly, for me at least.
Note: Tried to resize an image and there is no auto-resize with [[Image(file.png, 200px)]] :(
Cheers, al.
Dear Alain.
I think we should update the actual content based on the actual Trac default wiki syntax, or if there is another way to make it ...
This is nearly impossible if you do not want to reorganize all of the content. I am going to try to set up some parts in HTML (at least tables and image includes)
Guys ... would be possible to install some kind of photoblog under centos domain ? Something that let us upload a big image and generates thumbs of it for us to use ... something like http://www.pixelpost.org/. That way we could handle images/screenshots there and just refer them on Trac, Moin, wherever site ... That would be all about CentOS officially online images ... maybe contributors help with a section of personal screenshots ... a section for the artwork project (of course :D) ... and as many section as community consider helpful ... just a way to handle images and its sizes.
I do not think this is really necessary. Previews could be handled within the wiki. At least with HTML you could define the image size.
Some times attachments list on Trac could be quiet large ... and could look a bit ugly, for me at least.
Maybe we could hide the attachment list or add an 'view attachments' button to the bottom of the page.
Best Regards Marcus
On 9/19/08, Marcus Moeller mm@gcug.de wrote:
Dear Alain.
I think we should update the actual content based on the actual Trac default wiki syntax, or if there is another way to make it ...
This is nearly impossible if you do not want to reorganize all of the content.
Well, it seems to be something we need to assume if we want to keep Trac wiki page editing simple.
Guys ... would be possible to install some kind of photoblog under centos domain ? Something that let us upload a big image and generates thumbs of it for us to use ... something like http://www.pixelpost.org/. That way we could handle images/screenshots there and just refer them on Trac, Moin, wherever site ... That would be all about CentOS officially online images ... maybe contributors help with a section of personal screenshots ... a section for the artwork project (of course :D) ... and as many section as community consider helpful ... just a way to handle images and its sizes.
I do not think this is really necessary. Previews could be handled within the wiki. At least with HTML you could define the image size.
How could we show a full size image linked from its thumbnail without attach both the thumbed and the full size image ?
Cheers, al.
Alain Reguera Delgado wrote:
Guys ... would be possible to install some kind of photoblog under centos domain ? Something that let us upload a big image and generates thumbs of it for us to use ...
I dont mind that at all, but some of the other guys need to weigh in as well. Also Johnny was spotted in the wild recently.
Also, who wants to volunteer to be 'responsible' for it ?
Finally, almost anything we consider now should have ldap or sql based auth.
On 9/19/08, Karanbir Singh mail-lists@karan.org wrote: ...
Also, who wants to volunteer to be 'responsible' for it ?
I want, and if someone else wants to roll on it too... doors are opened.
Finally, almost anything we consider now should have ldap or sql based auth.
I need to verify this.
Thanks, al.
Dear Alain.
I think we should update the actual content based on the actual Trac default wiki syntax, or if there is another way to make it ...
I have tried to add some HTML code. Take a look at this example:
https://projects.centos.org/trac/artwork/wiki/DistroDesign/Wallpaper
As <style> definitions are not accepted I have to use dirty tricks to adjust table borders. I wonder if this really makes sense.
Maybe we should just stick with the capabilities of the Trac wiki (which definitly means col/rowspanning is impossible) and re-work the content.
Best Regards Marcus
Good Evening.
https://projects.centos.org/trac/artwork/wiki/DistroDesign/Wallpaper
I have now managed to make tables look similar to the ones on the wiki (using nearly plain html with some little style definitions).
Now I would like to suggest to include rendered images in SVN, e.g. in:
https://projects.centos.org/trac/artwork/browser/trunk/Main/img
and to link to them in the trac wiki instead of attaching the images to the wiki pages. This also makes sure we do not have to update all wiki pages on an artwork change.
Best Regards Marcus
On 9/20/08, Marcus Moeller mm@gcug.de wrote:
Good Evening.
https://projects.centos.org/trac/artwork/wiki/DistroDesign/Wallpaper
I have now managed to make tables look similar to the ones on the wiki (using nearly plain html with some little style definitions).
Now I would like to suggest to include rendered images in SVN, e.g. in:
https://projects.centos.org/trac/artwork/browser/trunk/Main/img
and what about thumbnails ... do we manage to render theme too there ? anyway we'll have two images the thumb and the real one ... What about a way of building thumbnails dynamically "on the fly" from the real images. A space for comments would be really nice too.
and to link to them in the trac wiki instead of attaching the images to the wiki pages. This also makes sure we do not have to update all wiki pages on an artwork change.
That's the idea ;)
Cheers, al.
Dear Alain.
and what about thumbnails ... do we manage to render theme too there ? anyway we'll have two images the thumb and the real one ... What about a way of building thumbnails dynamically "on the fly" from the real images. A space for comments would be really nice too.
I have figured out that there is a bug in Trac 0.10.4 preventing us from using [[Image(photo.jpg, 120px)]]:
http://trac.edgewall.org/ticket/6483
I already asked Karan to fix it but in the meantime I would suggest to use [[Image(photo.jpg, width=80px)]] for Thumbnail generation.
Best Regards Marcus
On 9/19/08, Marcus Moeller mm@gcug.de wrote:
Good Evening.
That's something that I could look in after CentOSify the punbb application presentation to get a common look for each lang.centos.org/forum/. punbb is just a proposition for that section of course. After that, and if Puntal tar.gz file continue lost ... we can give another Trac style round to see these kind of things, if no urgent or top level need appears. Maybe this is a good moment to start ticketing on artwork trac environment ;) so the roadmap be created.
Hmm, I did not even know you are already working on it.
Because I did'nt :D ... I started just a few days ago ;).
BTW. Does anyone knows the download link of the application we'll use in lang.centos.org sites ?
Cheers, al.
On 9/20/08, Alain Reguera Delgado alain.reguera@gmail.com wrote: ...
BTW. Does anyone knows the download link of the application we'll use in lang.centos.org sites ?
I found this: http://linux.softpedia.com/get/Information-Management/Puntal-17735.shtml
It seems that "Puntal does not modify any files of PunBB, but adds six standard modules (news, download, calendar, related pages, planet, and lexicon) ". If that is true, and if that Puntal is the right Puntal for the application we'll use in lang.centos.org ... We'll probably have the lang.centos.org theme very soon. I'll do some tests and tell you back.
Cheers, al.
Good Morning.
https://projects.centos.org/trac/artwork/wiki/DistroDesign/Wallpaper
I have now managed to make tables look similar to the ones on the wiki (using nearly plain html with some little style definitions).
Now I would like to suggest to include rendered images in SVN, e.g. in:
https://projects.centos.org/trac/artwork/browser/trunk/Main/img
and what about thumbnails ... do we manage to render theme too there ? anyway we'll have two images the thumb and the real one ... What about a way of building thumbnails dynamically "on the fly" from the real images. A space for comments would be really nice too.
I am not yet sure if this is really necessary. Downsizing images should be supported by Trac, too. We should take a look why it's not working, here.
So, could you please check in the rendered images and I will include them instead of the attached ones.
Best Regards Marcus
Hi,
I have now reworked the page to use plain wiki syntax (which is quite limited, but easier to handle). I even did not make use of RestructuredText.
So, could you please check in the rendered images and I will include them instead of the attached ones.
This is important as we could than link to images located in trunk using the:
[[Image(source:/trunk/trac/htdocs/trac_logo_mini.png)]]
syntax and get rid of the site attachments.
Best Regards Marcus
On 9/21/08, Marcus Moeller mm@gcug.de wrote: ...
So, could you please check in the rendered images and I will include them instead of the attached ones.
This is important as we could than link to images located in trunk using the:
[[Image(source:/trunk/trac/htdocs/trac_logo_mini.png)]]
syntax and get rid of the site attachments.
Sound good to me.
Cheers, al.
On 9/22/08, Alain Reguera Delgado alain.reguera@gmail.com wrote:
On 9/21/08, Marcus Moeller mm@gcug.de wrote: ...
So, could you please check in the rendered images and I will include them instead of the attached ones.
This is important as we could than link to images located in trunk using the:
[[Image(source:/trunk/trac/htdocs/trac_logo_mini.png)]]
syntax and get rid of the site attachments.
Sound good to me.
Maybe we could do a local render and tag it ... then use the tagged version of that render to display images in Trac, and other web sites. If so, which part of the artwork we tag ? Would it be too much space to store ?
Thanks, al.
2008/9/22 Alain Reguera Delgado alain.reguera@gmail.com:
On 9/22/08, Alain Reguera Delgado alain.reguera@gmail.com wrote:
On 9/21/08, Marcus Moeller mm@gcug.de wrote: ...
So, could you please check in the rendered images and I will include them instead of the attached ones.
This is important as we could than link to images located in trunk using the:
[[Image(source:/trunk/trac/htdocs/trac_logo_mini.png)]]
syntax and get rid of the site attachments.
Sound good to me.
Maybe we could do a local render and tag it ... then use the tagged version of that render to display images in Trac, and other web sites. If so, which part of the artwork we tag ? Would it be too much space to store ?
Why don't you just display the latest from Trunk so that users are informed about the current release state.
Otherwise import rendered images to Trunk on demand.
Best Regards Marcus
On 9/22/08, Marcus Moeller mm@gcug.de wrote:
2008/9/22 Alain Reguera Delgado alain.reguera@gmail.com:
On 9/22/08, Alain Reguera Delgado alain.reguera@gmail.com wrote:
Maybe we could do a local render and tag it ... then use the tagged version of that render to display images in Trac, and other web sites. If so, which part of the artwork we tag ? Would it be too much space to store ?
Why don't you just display the latest from Trunk so that users are informed about the current release state.
Initially the environment was conceived to render artwork locally by selection ... there was no imminent need to version rendered images. They could be created at any time.
Now, that we are planning to add rendered images in svn repo for Trac wiki (and maybe in other web sites) use ... someone will need to render the images and do upload them ... if we do it in trunk, each time the template change we'll need to update the imgs trunk too.
Don't know if it is correct but personally I would like to have a place where the images do no change each time the template change. I know we don't have to upload the new rendered result if we don't want it to, but in that case the content of imgs trunk wouldn't be reflecting templates as they are.
So in that point, and if we end up using the rendered images inside svn, is why I suggested to use some kind tag mechanism that let us keep a somehow static image for that use, something stable for a while, until the next modifications in trunk get ready to be referred to.
Maybe it is time to define the life cycle of artwork rendering.
Of course, that first tagged version is inexistent at this moment ... so maybe that's what we need to solve.
Otherwise import rendered images to Trunk on demand.
Again trunk doesn't seems to me to be the place for something relative stable we should refer to... at this moment it doesn't change to much but in a future it may do.
I would like to know your opinions, suggestions guys,
Cheers, al.
Dear Alain.
Otherwise import rendered images to Trunk on demand.
Again trunk doesn't seems to me to be the place for something relative stable we should refer to... at this moment it doesn't change to much but in a future it may do.
You could also place the images in branches or htdocs. Depends on what you want.
Uploading the rendered images somewhere to trunk (where they may not reflect the current development state) could still be an option in my POV as you may add a README containing the build version. But it's up to you.
Best Regards Marcus
Alain Reguera Delgado wrote:
On 9/20/08, Alain Reguera Delgado alain.reguera@gmail.com wrote: ...
BTW. Does anyone knows the download link of the application we'll use in lang.centos.org sites ?
I found this: http://linux.softpedia.com/get/Information-Management/Puntal-17735.shtml
It seems that "Puntal does not modify any files of PunBB, but adds six standard modules (news, download, calendar, related pages, planet, and lexicon) ". If that is true, and if that Puntal is the right Puntal for the application we'll use in lang.centos.org ... We'll probably have the lang.centos.org theme very soon. I'll do some tests and tell you back.
Stop there for a moment. We still do not know which application we'll use, as we need an application with an LDAP backend. We're still looking into that, expect a mail today or tomorrow with more details and a choice of applications.
Cheers,
Ralph
Alain Reguera Delgado wrote:
BTW. Does anyone knows the download link of the application we'll use in lang.centos.org sites ?
We just hit a slight hitch with that. More details in a new thread in 10 minutes.
- KB
-
Alain Reguera Delgado -
Dag Wieers -
Karanbir Singh -
Marcus Moeller -
Ralph Angenendt