Thank you for help and your work! I might send a mail to this list again
when the time comes and I need some guidance :).
On Mon, Jul 7, 2014 at 5:31 PM, Rich Megginson <rmeggins(a)redhat.com> wrote:
On 07/07/2014 08:37 AM, Vincent Gerris wrote:
I would love to patch it, but like I tried to indicate it would be more
It's probably just some CSS that needs modernizing.
In my case, choosing another frontend was more viable.
I personally do not know who is using dsgw and for what, I know it has
more capabilities than just resetting a user password.
Yes, much more. http://port389.org/wiki/WebApps_Overview
I would love to contribute, but if nobody is using the functionality,
it would be a bit of a wate of time from my point of view.
Next time I need a change, I will try to contribute.
I saw the last patch was 11 months ago:
Since your name is on most versions, can you say something about usage and
what parts users would like to see improved?
Everything should be in the fedorahosted 389 trac. The two Web Apps
related components are "UI Gateway/Phonebook" and "UI Org Chart"
On Mon, Jul 7, 2014 at 4:02 PM, Rich Megginson <rmeggins(a)redhat.com>
> On 07/07/2014 06:54 AM, Dave Page wrote:
>> On Mon, Jul 7, 2014 at 1:38 PM, Vincent Gerris <vgerris(a)gmail.com>
>>> If you mean that the layout is messed up, you are right.
>>> It is terrible and looks different on about any browser.
>>> I filed a bug for the ubuntu package where I found it too:
>>> There has been no reaction yet, it actually should have been reported
>>> upstream too I suppose.
> Oh, that's disappointing.
>> Given the (un)usability of the interface, I ended up completely using a
>>> different front-end, because we just wanted a self service portal for
>>> I think dsgw has not been touched for some time, would be usefull if it
>>> using modern code and a good ui to include at least a decent self
>>> webportal by default.
>> Patches are welcome.
> This is what I ended up using instead :
>> Thanks. We can use our existing UI for password changes, but I was
>> hoping for something I could let our HR people use to manage user info
>> with - one of the reasons why 389 seemed like a good choice.
> 389 users mailing list
389 users mailing
389 users mailing list