You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Alex Karasulu <ak...@apache.org> on 2011/03/01 14:59:06 UTC
[Community] Proposals for those interested in participating
Hi all,
<disclaimer>
Please excuse the cross post to both dev and user mailing lists.
</disclaimer>
<marketing-mode-on/>
If you're a lurker, and are interested in getting involved in the Apache
Directory Project but just don't know what to work on. Here are some
proposals that might interest you.
(1) LDAP Web Administration and/or Self Service Application[s]
What is it?
--------------
The name says it all. A simple web based (Servlet) administrative
application which uses the new LDAP API to administer your own profile or
the entire server.
Purpose
------------
We're breaking with JNDI and coming out with a new and modern LDAP API.
We want to know how useful it is.
We want to know if certain problems arise using it.
We want general feedback to improve the API.
We want a sample application that shows people how to use it and all its
features.
We want to grow community and to work with more cool peeps.
This mini-project and those working on would achieve some of these aims.
(2) LDAP Command Line Interface
What is it?
--------------
A main program that might be attached to an ldap-all jar as the java -jar
executable with commands to execute the standard set of LDAP operations like
add, del, modify, modifyDn etc.
Purpose
------------
Same purpose as in #1 plus we have something that we can ship with ApacheDS
that can be used from the command line without requiring other executables
for administrators to use.
(3) LDAP Interactive Command Line Shell
What is it?
--------------
A slick bash like shell that can be triggered from the same ldap-all jar's
java -jar executable with perhaps a shell command. The idea is to take the
shell motif in FS land over to LDAP land. This way all standard UNIX
commands like ls, cd, cat, etc can have analogs to navigate and manipulate
the Directory Information Tree (DIT).
Purpose
------------
Same purpose as in #1 and #2.
It's a cool concept, lots of fun to implement. Use OSGi to have plugins for
new commands.
We might package it with ADS for sys admins who hate using UI's or have
nothing but a shell available in front of them in a data center.
Might be something we can also put inside studio.
Can use commands like script to record scripts that can be loaded as stored
procedures or replayed for tests. Who knows?
On going project that can advance over time with more shell grammar
constructs like script control flow. That means more people will work on the
project for a long time. Once you get in you can never leave :-). Can use
scripting languages like groovy and Zoerner's awesome groovy ldap api.
<marketing-mode-off/>
If other folks have some ideas as well please add to this list. Based on the
progress of this thread we can add to the page of potential projects on our
site/wiki.
Best,
Alex
Fwd: [Community] Proposals for those interested in participating
Posted by Pierre Smits <pi...@gmail.com>.
FYI
---------- Forwarded message ----------
From: Pierre Smits <pi...@gmail.com>
Date: 2011/3/2
Subject: Re: [Community] Proposals for those interested in participating
To: users@directory.apache.org, user@ofbiz.apache.org
Hi Alex,
Up to now I have been a user of APACHE Directory and Studio in mij company,
but haven't been very active on this mailing list. But I want to complement
the team with both products.
Regarding #1
Apache OFBiz has already an interface to create and maintain party
information, and can use an LDAP engine for authentication. (I use both in
my company) However, it does not have the api's incorporated to maintain
LDAP data. Your java and groovy api's could fulfill that gap in OFBIz
functionality and OFBiz could fill the void regarding a web based
administrative application.
As Directory and OFBiz are APACHE projects both can leverage each others
insights, knowledge and succes.
Regards,
Pierre Smits
2011/3/1 Alex Karasulu <ak...@apache.org>
Hi all,
>
> <disclaimer>
> Please excuse the cross post to both dev and user mailing lists.
> </disclaimer>
>
> <marketing-mode-on/>
>
> If you're a lurker, and are interested in getting involved in the Apache
> Directory Project but just don't know what to work on. Here are some
> proposals that might interest you.
>
>
> (1) LDAP Web Administration and/or Self Service Application[s]
>
> What is it?
> --------------
>
> The name says it all. A simple web based (Servlet) administrative
> application which uses the new LDAP API to administer your own profile or
> the entire server.
>
> Purpose
> ------------
>
> We're breaking with JNDI and coming out with a new and modern LDAP API.
>
> We want to know how useful it is.
>
> We want to know if certain problems arise using it.
>
> We want general feedback to improve the API.
>
> We want a sample application that shows people how to use it and all its
> features.
>
> We want to grow community and to work with more cool peeps.
>
> This mini-project and those working on would achieve some of these aims.
>
>
> (2) LDAP Command Line Interface
>
> What is it?
> --------------
>
> A main program that might be attached to an ldap-all jar as the java -jar
> executable with commands to execute the standard set of LDAP operations
> like
> add, del, modify, modifyDn etc.
>
> Purpose
> ------------
>
> Same purpose as in #1 plus we have something that we can ship with ApacheDS
> that can be used from the command line without requiring other executables
> for administrators to use.
>
>
> (3) LDAP Interactive Command Line Shell
>
> What is it?
> --------------
>
> A slick bash like shell that can be triggered from the same ldap-all jar's
> java -jar executable with perhaps a shell command. The idea is to take the
> shell motif in FS land over to LDAP land. This way all standard UNIX
> commands like ls, cd, cat, etc can have analogs to navigate and manipulate
> the Directory Information Tree (DIT).
>
> Purpose
> ------------
>
> Same purpose as in #1 and #2.
>
> It's a cool concept, lots of fun to implement. Use OSGi to have plugins for
> new commands.
>
> We might package it with ADS for sys admins who hate using UI's or have
> nothing but a shell available in front of them in a data center.
>
> Might be something we can also put inside studio.
>
> Can use commands like script to record scripts that can be loaded as stored
> procedures or replayed for tests. Who knows?
>
> On going project that can advance over time with more shell grammar
> constructs like script control flow. That means more people will work on
> the
> project for a long time. Once you get in you can never leave :-). Can use
> scripting languages like groovy and Zoerner's awesome groovy ldap api.
>
> <marketing-mode-off/>
>
> If other folks have some ideas as well please add to this list. Based on
> the
> progress of this thread we can add to the page of potential projects on our
> site/wiki.
>
>
> Best,
> Alex
>
Re: [Community] Proposals for those interested in participating
Posted by Alex Karasulu <ak...@apache.org>.
On Wed, Mar 2, 2011 at 12:15 PM, Pierre Smits <pi...@gmail.com>wrote:
> Hi Alex,
>
> Up to now I have been a user of APACHE Directory and Studio in mij company,
> but haven't been very active on this mailing list. But I want to complement
> the team with both products.
>
> Regarding #1
>
> Apache OFBiz has already an interface to create and maintain party
> information, and can use an LDAP engine for authentication. (I use both in
> my company) However, it does not have the api's incorporated to maintain
> LDAP data. Your java and groovy api's could fulfill that gap in OFBIz
> functionality and OFBiz could fill the void regarding a web based
> administrative application.
>
> As Directory and OFBiz are APACHE projects both can leverage each others
> insights, knowledge and succes.
>
>
Feel free to use the API in OFBiz. Regarding using OFBiz in ApacheDS, may be
that would be heavy. Plus in the end we're going to have our own permissions
management API at some point for doing RBAC. Maybe we'll piggy back on an
existing API and back the model in LDAP. Who knows but OFBiz seems like over
kill. maybe you were thinking about some of its components?
Regards,
Alex
> 2011/3/1 Alex Karasulu <ak...@apache.org>
>
> > Hi all,
> >
> > <disclaimer>
> > Please excuse the cross post to both dev and user mailing lists.
> > </disclaimer>
> >
> > <marketing-mode-on/>
> >
> > If you're a lurker, and are interested in getting involved in the Apache
> > Directory Project but just don't know what to work on. Here are some
> > proposals that might interest you.
> >
> >
> > (1) LDAP Web Administration and/or Self Service Application[s]
> >
> > What is it?
> > --------------
> >
> > The name says it all. A simple web based (Servlet) administrative
> > application which uses the new LDAP API to administer your own profile or
> > the entire server.
> >
> > Purpose
> > ------------
> >
> > We're breaking with JNDI and coming out with a new and modern LDAP API.
> >
> > We want to know how useful it is.
> >
> > We want to know if certain problems arise using it.
> >
> > We want general feedback to improve the API.
> >
> > We want a sample application that shows people how to use it and all its
> > features.
> >
> > We want to grow community and to work with more cool peeps.
> >
> > This mini-project and those working on would achieve some of these aims.
> >
> >
> > (2) LDAP Command Line Interface
> >
> > What is it?
> > --------------
> >
> > A main program that might be attached to an ldap-all jar as the java -jar
> > executable with commands to execute the standard set of LDAP operations
> > like
> > add, del, modify, modifyDn etc.
> >
> > Purpose
> > ------------
> >
> > Same purpose as in #1 plus we have something that we can ship with
> ApacheDS
> > that can be used from the command line without requiring other
> executables
> > for administrators to use.
> >
> >
> > (3) LDAP Interactive Command Line Shell
> >
> > What is it?
> > --------------
> >
> > A slick bash like shell that can be triggered from the same ldap-all
> jar's
> > java -jar executable with perhaps a shell command. The idea is to take
> the
> > shell motif in FS land over to LDAP land. This way all standard UNIX
> > commands like ls, cd, cat, etc can have analogs to navigate and
> manipulate
> > the Directory Information Tree (DIT).
> >
> > Purpose
> > ------------
> >
> > Same purpose as in #1 and #2.
> >
> > It's a cool concept, lots of fun to implement. Use OSGi to have plugins
> for
> > new commands.
> >
> > We might package it with ADS for sys admins who hate using UI's or have
> > nothing but a shell available in front of them in a data center.
> >
> > Might be something we can also put inside studio.
> >
> > Can use commands like script to record scripts that can be loaded as
> stored
> > procedures or replayed for tests. Who knows?
> >
> > On going project that can advance over time with more shell grammar
> > constructs like script control flow. That means more people will work on
> > the
> > project for a long time. Once you get in you can never leave :-). Can use
> > scripting languages like groovy and Zoerner's awesome groovy ldap api.
> >
> > <marketing-mode-off/>
> >
> > If other folks have some ideas as well please add to this list. Based on
> > the
> > progress of this thread we can add to the page of potential projects on
> our
> > site/wiki.
> >
> >
> > Best,
> > Alex
> >
>
Re: [Community] Proposals for those interested in participating
Posted by Pierre Smits <pi...@gmail.com>.
Hi Alex,
Up to now I have been a user of APACHE Directory and Studio in mij company,
but haven't been very active on this mailing list. But I want to complement
the team with both products.
Regarding #1
Apache OFBiz has already an interface to create and maintain party
information, and can use an LDAP engine for authentication. (I use both in
my company) However, it does not have the api's incorporated to maintain
LDAP data. Your java and groovy api's could fulfill that gap in OFBIz
functionality and OFBiz could fill the void regarding a web based
administrative application.
As Directory and OFBiz are APACHE projects both can leverage each others
insights, knowledge and succes.
Regards,
Pierre Smits
2011/3/1 Alex Karasulu <ak...@apache.org>
> Hi all,
>
> <disclaimer>
> Please excuse the cross post to both dev and user mailing lists.
> </disclaimer>
>
> <marketing-mode-on/>
>
> If you're a lurker, and are interested in getting involved in the Apache
> Directory Project but just don't know what to work on. Here are some
> proposals that might interest you.
>
>
> (1) LDAP Web Administration and/or Self Service Application[s]
>
> What is it?
> --------------
>
> The name says it all. A simple web based (Servlet) administrative
> application which uses the new LDAP API to administer your own profile or
> the entire server.
>
> Purpose
> ------------
>
> We're breaking with JNDI and coming out with a new and modern LDAP API.
>
> We want to know how useful it is.
>
> We want to know if certain problems arise using it.
>
> We want general feedback to improve the API.
>
> We want a sample application that shows people how to use it and all its
> features.
>
> We want to grow community and to work with more cool peeps.
>
> This mini-project and those working on would achieve some of these aims.
>
>
> (2) LDAP Command Line Interface
>
> What is it?
> --------------
>
> A main program that might be attached to an ldap-all jar as the java -jar
> executable with commands to execute the standard set of LDAP operations
> like
> add, del, modify, modifyDn etc.
>
> Purpose
> ------------
>
> Same purpose as in #1 plus we have something that we can ship with ApacheDS
> that can be used from the command line without requiring other executables
> for administrators to use.
>
>
> (3) LDAP Interactive Command Line Shell
>
> What is it?
> --------------
>
> A slick bash like shell that can be triggered from the same ldap-all jar's
> java -jar executable with perhaps a shell command. The idea is to take the
> shell motif in FS land over to LDAP land. This way all standard UNIX
> commands like ls, cd, cat, etc can have analogs to navigate and manipulate
> the Directory Information Tree (DIT).
>
> Purpose
> ------------
>
> Same purpose as in #1 and #2.
>
> It's a cool concept, lots of fun to implement. Use OSGi to have plugins for
> new commands.
>
> We might package it with ADS for sys admins who hate using UI's or have
> nothing but a shell available in front of them in a data center.
>
> Might be something we can also put inside studio.
>
> Can use commands like script to record scripts that can be loaded as stored
> procedures or replayed for tests. Who knows?
>
> On going project that can advance over time with more shell grammar
> constructs like script control flow. That means more people will work on
> the
> project for a long time. Once you get in you can never leave :-). Can use
> scripting languages like groovy and Zoerner's awesome groovy ldap api.
>
> <marketing-mode-off/>
>
> If other folks have some ideas as well please add to this list. Based on
> the
> progress of this thread we can add to the page of potential projects on our
> site/wiki.
>
>
> Best,
> Alex
>
Re: [Community] Proposals for those interested in participating
Posted by Alex Karasulu <ak...@apache.org>.
On Tue, Mar 1, 2011 at 4:16 PM, Stefan Seelmann <ma...@stefan-seelmann.de>wrote:
> Should we consider to offer those as Google Summer of Code projects?
Yeah that's an option as well but why wait I thought. The API is coming
along and I thought the input while using it could help us out to better
enhance it.
But yes we should also list these projects in GSoC as well if no one takes
em up.
Regards,
Alex
> On Mar 1, 2011 2:59 PM, "Alex Karasulu" <ak...@apache.org> wrote:
> > Hi all,
> >
> > <disclaimer>
> > Please excuse the cross post to both dev and user mailing lists.
> > </disclaimer>
> >
> > <marketing-mode-on/>
> >
> > If you're a lurker, and are interested in getting involved in the Apache
> > Directory Project but just don't know what to work on. Here are some
> > proposals that might interest you.
> >
> >
> > (1) LDAP Web Administration and/or Self Service Application[s]
> >
> > What is it?
> > --------------
> >
> > The name says it all. A simple web based (Servlet) administrative
> > application which uses the new LDAP API to administer your own profile or
> > the entire server.
> >
> > Purpose
> > ------------
> >
> > We're breaking with JNDI and coming out with a new and modern LDAP API.
> >
> > We want to know how useful it is.
> >
> > We want to know if certain problems arise using it.
> >
> > We want general feedback to improve the API.
> >
> > We want a sample application that shows people how to use it and all its
> > features.
> >
> > We want to grow community and to work with more cool peeps.
> >
> > This mini-project and those working on would achieve some of these aims.
> >
> >
> > (2) LDAP Command Line Interface
> >
> > What is it?
> > --------------
> >
> > A main program that might be attached to an ldap-all jar as the java -jar
> > executable with commands to execute the standard set of LDAP operations
> like
> > add, del, modify, modifyDn etc.
> >
> > Purpose
> > ------------
> >
> > Same purpose as in #1 plus we have something that we can ship with
> ApacheDS
> > that can be used from the command line without requiring other
> executables
> > for administrators to use.
> >
> >
> > (3) LDAP Interactive Command Line Shell
> >
> > What is it?
> > --------------
> >
> > A slick bash like shell that can be triggered from the same ldap-all
> jar's
> > java -jar executable with perhaps a shell command. The idea is to take
> the
> > shell motif in FS land over to LDAP land. This way all standard UNIX
> > commands like ls, cd, cat, etc can have analogs to navigate and
> manipulate
> > the Directory Information Tree (DIT).
> >
> > Purpose
> > ------------
> >
> > Same purpose as in #1 and #2.
> >
> > It's a cool concept, lots of fun to implement. Use OSGi to have plugins
> for
> > new commands.
> >
> > We might package it with ADS for sys admins who hate using UI's or have
> > nothing but a shell available in front of them in a data center.
> >
> > Might be something we can also put inside studio.
> >
> > Can use commands like script to record scripts that can be loaded as
> stored
> > procedures or replayed for tests. Who knows?
> >
> > On going project that can advance over time with more shell grammar
> > constructs like script control flow. That means more people will work on
> the
> > project for a long time. Once you get in you can never leave :-). Can use
> > scripting languages like groovy and Zoerner's awesome groovy ldap api.
> >
> > <marketing-mode-off/>
> >
> > If other folks have some ideas as well please add to this list. Based on
> the
> > progress of this thread we can add to the page of potential projects on
> our
> > site/wiki.
> >
> >
> > Best,
> > Alex
>
Re: [Community] Proposals for those interested in participating
Posted by Alex Karasulu <ak...@apache.org>.
On Tue, Mar 1, 2011 at 4:16 PM, Stefan Seelmann <ma...@stefan-seelmann.de>wrote:
> Should we consider to offer those as Google Summer of Code projects?
Yeah that's an option as well but why wait I thought. The API is coming
along and I thought the input while using it could help us out to better
enhance it.
But yes we should also list these projects in GSoC as well if no one takes
em up.
Regards,
Alex
> On Mar 1, 2011 2:59 PM, "Alex Karasulu" <ak...@apache.org> wrote:
> > Hi all,
> >
> > <disclaimer>
> > Please excuse the cross post to both dev and user mailing lists.
> > </disclaimer>
> >
> > <marketing-mode-on/>
> >
> > If you're a lurker, and are interested in getting involved in the Apache
> > Directory Project but just don't know what to work on. Here are some
> > proposals that might interest you.
> >
> >
> > (1) LDAP Web Administration and/or Self Service Application[s]
> >
> > What is it?
> > --------------
> >
> > The name says it all. A simple web based (Servlet) administrative
> > application which uses the new LDAP API to administer your own profile or
> > the entire server.
> >
> > Purpose
> > ------------
> >
> > We're breaking with JNDI and coming out with a new and modern LDAP API.
> >
> > We want to know how useful it is.
> >
> > We want to know if certain problems arise using it.
> >
> > We want general feedback to improve the API.
> >
> > We want a sample application that shows people how to use it and all its
> > features.
> >
> > We want to grow community and to work with more cool peeps.
> >
> > This mini-project and those working on would achieve some of these aims.
> >
> >
> > (2) LDAP Command Line Interface
> >
> > What is it?
> > --------------
> >
> > A main program that might be attached to an ldap-all jar as the java -jar
> > executable with commands to execute the standard set of LDAP operations
> like
> > add, del, modify, modifyDn etc.
> >
> > Purpose
> > ------------
> >
> > Same purpose as in #1 plus we have something that we can ship with
> ApacheDS
> > that can be used from the command line without requiring other
> executables
> > for administrators to use.
> >
> >
> > (3) LDAP Interactive Command Line Shell
> >
> > What is it?
> > --------------
> >
> > A slick bash like shell that can be triggered from the same ldap-all
> jar's
> > java -jar executable with perhaps a shell command. The idea is to take
> the
> > shell motif in FS land over to LDAP land. This way all standard UNIX
> > commands like ls, cd, cat, etc can have analogs to navigate and
> manipulate
> > the Directory Information Tree (DIT).
> >
> > Purpose
> > ------------
> >
> > Same purpose as in #1 and #2.
> >
> > It's a cool concept, lots of fun to implement. Use OSGi to have plugins
> for
> > new commands.
> >
> > We might package it with ADS for sys admins who hate using UI's or have
> > nothing but a shell available in front of them in a data center.
> >
> > Might be something we can also put inside studio.
> >
> > Can use commands like script to record scripts that can be loaded as
> stored
> > procedures or replayed for tests. Who knows?
> >
> > On going project that can advance over time with more shell grammar
> > constructs like script control flow. That means more people will work on
> the
> > project for a long time. Once you get in you can never leave :-). Can use
> > scripting languages like groovy and Zoerner's awesome groovy ldap api.
> >
> > <marketing-mode-off/>
> >
> > If other folks have some ideas as well please add to this list. Based on
> the
> > progress of this thread we can add to the page of potential projects on
> our
> > site/wiki.
> >
> >
> > Best,
> > Alex
>
Re: [Community] Proposals for those interested in participating
Posted by Stefano Gargiulo <ra...@gmail.com>.
Yes i think also that RAP application will be:
1) not so useful: apache directory studio is a MUST to manage LDAP servers,
but a web version of it is not a great added value IMHO (administrators, a
limited number of person, can easly install it on their OS to do that)
2) too heavy: RAP is one of the many java2webapp frameworks that IMHO will
not rock. This kind of frameworks (see Jaxcent, Echo2 etc.): the idea
behind is to use the server to compute the rendering and the behaivor of
most of the UI components and this really not scales (you will need a
superserver to run it) in this is much better GWT or Dojo+DWR (you need to
rewrite the entiere UI but you will achieve a real RPC architecture over the
web)
But having a project like this directly using the LDAP API
> will I think be lighter and might even be embedded as an optional
> application in the Jetty server running inside ApacheDS. The idea is not
> just administration but also to use the application for self service.
Yes i mean this: i wrote a php application to manage things regarding
accounts like:
-User registration to services (a web interface to register a new account
with the authz attributes needed for a service)
-User password change, rescue, and reminders to change password
periodically
-User management (simplified, not intended to be used by LDAP system
administrators, but by projects and application managers) - manage
user profiles and authz attributes in a simple way
- approve/reject registration and access request
- invite users by email
ecc.
For now all this is a bit harcoded, but i'm looking for a good java api to
achieve more flexibility (e.g. possibility to dynamically define user
profile templates, using any schema and attribute, and map the attribute
with some rules (e.g. regexp for UI editing, authZ meaning for applications
ect.)
Best regards,
Stefano
2011/3/1 Alex Karasulu <ak...@apache.org>
> On Tue, Mar 1, 2011 at 6:50 PM, Stefano Gargiulo <ra...@gmail.com>
> wrote:
>
> > Very interesting! Proposal #1 Will rock (world need this kind of webapps)
> > and also the new api is a great thing for who wants to write a custom
> user
> > management interface (i need this, for now i wrote one in php but i will
> be
> > very happy to switch to your ldap api when mature)
> >
> >
> Hi Stefano,
>
> It would be great to have you involved. Just one point, the API is pretty
> close to being solid at least with M2. There might be another milestone or
> two but the changes will not be that massive so you can start using M2 as
> soon as we release it here in a few days.
>
> The idea is to use as many of the API features as you can in your
> application. Should be fun!
>
> Also Emmanuel posted about a RAP application. Let me address both of you
> here. The RAP application I think will be pretty heavy. Then again it might
> not be who knows. But having a project like this directly using the LDAP
> API
> will I think be lighter and might even be embedded as an optional
> application in the Jetty server running inside ApacheDS. The idea is not
> just administration but also to use the application for self service.
>
> Plus a part of this is for you to push us on the LDAP API. If it cannot do
> some things for you you need to complain and force us to rectify it.
>
> Regards,
> Alex
>
>
> > Il giorno 01/mar/2011 15:25, "Emmanuel Lecharny" <el...@gmail.com>
> ha
> > scritto:
> >
> > On 3/1/11 3:16 PM, Stefan Seelmann wrote:
> > >
> > > Should we consider to offer those as Google Summer of ...
> > Definitively, yes.
> >
> >
> > --
> > Regards,
> > Cordialement,
> > Emmanuel Lécharny
> > www.iktek.com
> >
>
Re: [Community] Proposals for those interested in participating
Posted by Alex Karasulu <ak...@apache.org>.
On Tue, Mar 1, 2011 at 6:50 PM, Stefano Gargiulo <ra...@gmail.com> wrote:
> Very interesting! Proposal #1 Will rock (world need this kind of webapps)
> and also the new api is a great thing for who wants to write a custom user
> management interface (i need this, for now i wrote one in php but i will be
> very happy to switch to your ldap api when mature)
>
>
Hi Stefano,
It would be great to have you involved. Just one point, the API is pretty
close to being solid at least with M2. There might be another milestone or
two but the changes will not be that massive so you can start using M2 as
soon as we release it here in a few days.
The idea is to use as many of the API features as you can in your
application. Should be fun!
Also Emmanuel posted about a RAP application. Let me address both of you
here. The RAP application I think will be pretty heavy. Then again it might
not be who knows. But having a project like this directly using the LDAP API
will I think be lighter and might even be embedded as an optional
application in the Jetty server running inside ApacheDS. The idea is not
just administration but also to use the application for self service.
Plus a part of this is for you to push us on the LDAP API. If it cannot do
some things for you you need to complain and force us to rectify it.
Regards,
Alex
> Il giorno 01/mar/2011 15:25, "Emmanuel Lecharny" <el...@gmail.com> ha
> scritto:
>
> On 3/1/11 3:16 PM, Stefan Seelmann wrote:
> >
> > Should we consider to offer those as Google Summer of ...
> Definitively, yes.
>
>
> --
> Regards,
> Cordialement,
> Emmanuel Lécharny
> www.iktek.com
>
Re: [Community] Proposals for those interested in participating
Posted by Emmanuel Lécharny <el...@apache.org>.
On 3/1/11 11:10 PM, Stefan Seelmann wrote:
> On Tue, Mar 1, 2011 at 5:58 PM, Emmanuel Lécharny<el...@apache.org> wrote:
>> On 3/1/11 5:50 PM, Stefano Gargiulo wrote:
>>> Very interesting! Proposal #1 Will rock (world need this kind of webapps)
>>> and also the new api is a great thing for who wants to write a custom user
>>> management interface (i need this, for now i wrote one in php but i will
>>> be
>>> very happy to switch to your ldap api when mature)
>> I would add something regarding the Web UI : we would be very interested in
>> using Eclipse RAP [1] to get the current Apache Studio application available
>> as a Web UI, with the same look and feel. We have already conducted some
>> experiments the last two years, and we know we aren't too far from being
>> able to provide a single applications which can be used either as a
>> standalone application, or as a plugin inside eclipse, or thanks to RAP, as
>> a web UI.
>>
>> What would be absolutely great would be to see if this can be done with the
>> current version (RAP 1.4-M6 is announced for march 18), and what are the
>> impacts on the current application.
> I think RAPification of Studio is a bit special.
>
> First, as Alex already mentioned, it will be a heavy web application.
>
> Second, Studio uses shared and Server components, they are heavily
> modified, I don't foresee stability here within the next months. It
> would be necessary to deal with changed packages and dependencies all
> the time. That doesn't make it easy to work on a RAP version.
>
> Last not least, IMHO it is required to have deep knowledge of Eclipse
> RCP and Plugin development. Also experience with RAP would be good. I
> don't think that it is possible to get it working with 'only' Java
> skills within a fair time, this is really a big task.
Yeah, you are most certainly right. Thinking about it again, I think we
should proceed in another way regarding any RCP/RAP application :
starting with RAP first, and see if it does not limit too much the RCP
application.
In any case, none of those approach fits with Studio, and it's better to
start from scratch with a simpler Web UI.
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
Re: [Community] Proposals for those interested in participating
Posted by Stefan Seelmann <se...@apache.org>.
On Tue, Mar 1, 2011 at 5:58 PM, Emmanuel Lécharny <el...@apache.org> wrote:
> On 3/1/11 5:50 PM, Stefano Gargiulo wrote:
>>
>> Very interesting! Proposal #1 Will rock (world need this kind of webapps)
>> and also the new api is a great thing for who wants to write a custom user
>> management interface (i need this, for now i wrote one in php but i will
>> be
>> very happy to switch to your ldap api when mature)
>
> I would add something regarding the Web UI : we would be very interested in
> using Eclipse RAP [1] to get the current Apache Studio application available
> as a Web UI, with the same look and feel. We have already conducted some
> experiments the last two years, and we know we aren't too far from being
> able to provide a single applications which can be used either as a
> standalone application, or as a plugin inside eclipse, or thanks to RAP, as
> a web UI.
>
> What would be absolutely great would be to see if this can be done with the
> current version (RAP 1.4-M6 is announced for march 18), and what are the
> impacts on the current application.
I think RAPification of Studio is a bit special.
First, as Alex already mentioned, it will be a heavy web application.
Second, Studio uses shared and Server components, they are heavily
modified, I don't foresee stability here within the next months. It
would be necessary to deal with changed packages and dependencies all
the time. That doesn't make it easy to work on a RAP version.
Last not least, IMHO it is required to have deep knowledge of Eclipse
RCP and Plugin development. Also experience with RAP would be good. I
don't think that it is possible to get it working with 'only' Java
skills within a fair time, this is really a big task.
Kind Regards,
Stefan
Re: [Community] Proposals for those interested in participating
Posted by Emmanuel Lécharny <el...@apache.org>.
On 3/1/11 5:50 PM, Stefano Gargiulo wrote:
> Very interesting! Proposal #1 Will rock (world need this kind of webapps)
> and also the new api is a great thing for who wants to write a custom user
> management interface (i need this, for now i wrote one in php but i will be
> very happy to switch to your ldap api when mature)
I would add something regarding the Web UI : we would be very interested
in using Eclipse RAP [1] to get the current Apache Studio application
available as a Web UI, with the same look and feel. We have already
conducted some experiments the last two years, and we know we aren't too
far from being able to provide a single applications which can be used
either as a standalone application, or as a plugin inside eclipse, or
thanks to RAP, as a web UI.
What would be absolutely great would be to see if this can be done with
the current version (RAP 1.4-M6 is announced for march 18), and what are
the impacts on the current application.
Maybe Pierre-Arnaud or Stefan can elaborate a bit more on this.
Thanks !
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
Re: [Community] Proposals for those interested in participating
Posted by Stefano Gargiulo <ra...@gmail.com>.
Very interesting! Proposal #1 Will rock (world need this kind of webapps)
and also the new api is a great thing for who wants to write a custom user
management interface (i need this, for now i wrote one in php but i will be
very happy to switch to your ldap api when mature)
Il giorno 01/mar/2011 15:25, "Emmanuel Lecharny" <el...@gmail.com> ha
scritto:
On 3/1/11 3:16 PM, Stefan Seelmann wrote:
>
> Should we consider to offer those as Google Summer of ...
Definitively, yes.
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
Re: [Community] Proposals for those interested in participating
Posted by Emmanuel Lecharny <el...@gmail.com>.
On 3/1/11 3:16 PM, Stefan Seelmann wrote:
> Should we consider to offer those as Google Summer of Code projects?
Definitively, yes.
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
Re: [Community] Proposals for those interested in participating
Posted by Stefan Seelmann <ma...@stefan-seelmann.de>.
Should we consider to offer those as Google Summer of Code projects?
On Mar 1, 2011 2:59 PM, "Alex Karasulu" <ak...@apache.org> wrote:
> Hi all,
>
> <disclaimer>
> Please excuse the cross post to both dev and user mailing lists.
> </disclaimer>
>
> <marketing-mode-on/>
>
> If you're a lurker, and are interested in getting involved in the Apache
> Directory Project but just don't know what to work on. Here are some
> proposals that might interest you.
>
>
> (1) LDAP Web Administration and/or Self Service Application[s]
>
> What is it?
> --------------
>
> The name says it all. A simple web based (Servlet) administrative
> application which uses the new LDAP API to administer your own profile or
> the entire server.
>
> Purpose
> ------------
>
> We're breaking with JNDI and coming out with a new and modern LDAP API.
>
> We want to know how useful it is.
>
> We want to know if certain problems arise using it.
>
> We want general feedback to improve the API.
>
> We want a sample application that shows people how to use it and all its
> features.
>
> We want to grow community and to work with more cool peeps.
>
> This mini-project and those working on would achieve some of these aims.
>
>
> (2) LDAP Command Line Interface
>
> What is it?
> --------------
>
> A main program that might be attached to an ldap-all jar as the java -jar
> executable with commands to execute the standard set of LDAP operations
like
> add, del, modify, modifyDn etc.
>
> Purpose
> ------------
>
> Same purpose as in #1 plus we have something that we can ship with
ApacheDS
> that can be used from the command line without requiring other executables
> for administrators to use.
>
>
> (3) LDAP Interactive Command Line Shell
>
> What is it?
> --------------
>
> A slick bash like shell that can be triggered from the same ldap-all jar's
> java -jar executable with perhaps a shell command. The idea is to take the
> shell motif in FS land over to LDAP land. This way all standard UNIX
> commands like ls, cd, cat, etc can have analogs to navigate and manipulate
> the Directory Information Tree (DIT).
>
> Purpose
> ------------
>
> Same purpose as in #1 and #2.
>
> It's a cool concept, lots of fun to implement. Use OSGi to have plugins
for
> new commands.
>
> We might package it with ADS for sys admins who hate using UI's or have
> nothing but a shell available in front of them in a data center.
>
> Might be something we can also put inside studio.
>
> Can use commands like script to record scripts that can be loaded as
stored
> procedures or replayed for tests. Who knows?
>
> On going project that can advance over time with more shell grammar
> constructs like script control flow. That means more people will work on
the
> project for a long time. Once you get in you can never leave :-). Can use
> scripting languages like groovy and Zoerner's awesome groovy ldap api.
>
> <marketing-mode-off/>
>
> If other folks have some ideas as well please add to this list. Based on
the
> progress of this thread we can add to the page of potential projects on
our
> site/wiki.
>
>
> Best,
> Alex
Re: [Community] Proposals for those interested in participating
Posted by Stefan Seelmann <ma...@stefan-seelmann.de>.
Should we consider to offer those as Google Summer of Code projects?
On Mar 1, 2011 2:59 PM, "Alex Karasulu" <ak...@apache.org> wrote:
> Hi all,
>
> <disclaimer>
> Please excuse the cross post to both dev and user mailing lists.
> </disclaimer>
>
> <marketing-mode-on/>
>
> If you're a lurker, and are interested in getting involved in the Apache
> Directory Project but just don't know what to work on. Here are some
> proposals that might interest you.
>
>
> (1) LDAP Web Administration and/or Self Service Application[s]
>
> What is it?
> --------------
>
> The name says it all. A simple web based (Servlet) administrative
> application which uses the new LDAP API to administer your own profile or
> the entire server.
>
> Purpose
> ------------
>
> We're breaking with JNDI and coming out with a new and modern LDAP API.
>
> We want to know how useful it is.
>
> We want to know if certain problems arise using it.
>
> We want general feedback to improve the API.
>
> We want a sample application that shows people how to use it and all its
> features.
>
> We want to grow community and to work with more cool peeps.
>
> This mini-project and those working on would achieve some of these aims.
>
>
> (2) LDAP Command Line Interface
>
> What is it?
> --------------
>
> A main program that might be attached to an ldap-all jar as the java -jar
> executable with commands to execute the standard set of LDAP operations
like
> add, del, modify, modifyDn etc.
>
> Purpose
> ------------
>
> Same purpose as in #1 plus we have something that we can ship with
ApacheDS
> that can be used from the command line without requiring other executables
> for administrators to use.
>
>
> (3) LDAP Interactive Command Line Shell
>
> What is it?
> --------------
>
> A slick bash like shell that can be triggered from the same ldap-all jar's
> java -jar executable with perhaps a shell command. The idea is to take the
> shell motif in FS land over to LDAP land. This way all standard UNIX
> commands like ls, cd, cat, etc can have analogs to navigate and manipulate
> the Directory Information Tree (DIT).
>
> Purpose
> ------------
>
> Same purpose as in #1 and #2.
>
> It's a cool concept, lots of fun to implement. Use OSGi to have plugins
for
> new commands.
>
> We might package it with ADS for sys admins who hate using UI's or have
> nothing but a shell available in front of them in a data center.
>
> Might be something we can also put inside studio.
>
> Can use commands like script to record scripts that can be loaded as
stored
> procedures or replayed for tests. Who knows?
>
> On going project that can advance over time with more shell grammar
> constructs like script control flow. That means more people will work on
the
> project for a long time. Once you get in you can never leave :-). Can use
> scripting languages like groovy and Zoerner's awesome groovy ldap api.
>
> <marketing-mode-off/>
>
> If other folks have some ideas as well please add to this list. Based on
the
> progress of this thread we can add to the page of potential projects on
our
> site/wiki.
>
>
> Best,
> Alex
Re: [Community] Proposals for those interested in participating
Posted by Pierre Smits <pi...@gmail.com>.
Hi Alex,
Up to now I have been a user of APACHE Directory and Studio in mij company,
but haven't been very active on this mailing list. But I want to complement
the team with both products.
Regarding #1
Apache OFBiz has already an interface to create and maintain party
information, and can use an LDAP engine for authentication. (I use both in
my company) However, it does not have the api's incorporated to maintain
LDAP data. Your java and groovy api's could fulfill that gap in OFBIz
functionality and OFBiz could fill the void regarding a web based
administrative application.
As Directory and OFBiz are APACHE projects both can leverage each others
insights, knowledge and succes.
Regards,
Pierre Smits
2011/3/1 Alex Karasulu <ak...@apache.org>
> Hi all,
>
> <disclaimer>
> Please excuse the cross post to both dev and user mailing lists.
> </disclaimer>
>
> <marketing-mode-on/>
>
> If you're a lurker, and are interested in getting involved in the Apache
> Directory Project but just don't know what to work on. Here are some
> proposals that might interest you.
>
>
> (1) LDAP Web Administration and/or Self Service Application[s]
>
> What is it?
> --------------
>
> The name says it all. A simple web based (Servlet) administrative
> application which uses the new LDAP API to administer your own profile or
> the entire server.
>
> Purpose
> ------------
>
> We're breaking with JNDI and coming out with a new and modern LDAP API.
>
> We want to know how useful it is.
>
> We want to know if certain problems arise using it.
>
> We want general feedback to improve the API.
>
> We want a sample application that shows people how to use it and all its
> features.
>
> We want to grow community and to work with more cool peeps.
>
> This mini-project and those working on would achieve some of these aims.
>
>
> (2) LDAP Command Line Interface
>
> What is it?
> --------------
>
> A main program that might be attached to an ldap-all jar as the java -jar
> executable with commands to execute the standard set of LDAP operations
> like
> add, del, modify, modifyDn etc.
>
> Purpose
> ------------
>
> Same purpose as in #1 plus we have something that we can ship with ApacheDS
> that can be used from the command line without requiring other executables
> for administrators to use.
>
>
> (3) LDAP Interactive Command Line Shell
>
> What is it?
> --------------
>
> A slick bash like shell that can be triggered from the same ldap-all jar's
> java -jar executable with perhaps a shell command. The idea is to take the
> shell motif in FS land over to LDAP land. This way all standard UNIX
> commands like ls, cd, cat, etc can have analogs to navigate and manipulate
> the Directory Information Tree (DIT).
>
> Purpose
> ------------
>
> Same purpose as in #1 and #2.
>
> It's a cool concept, lots of fun to implement. Use OSGi to have plugins for
> new commands.
>
> We might package it with ADS for sys admins who hate using UI's or have
> nothing but a shell available in front of them in a data center.
>
> Might be something we can also put inside studio.
>
> Can use commands like script to record scripts that can be loaded as stored
> procedures or replayed for tests. Who knows?
>
> On going project that can advance over time with more shell grammar
> constructs like script control flow. That means more people will work on
> the
> project for a long time. Once you get in you can never leave :-). Can use
> scripting languages like groovy and Zoerner's awesome groovy ldap api.
>
> <marketing-mode-off/>
>
> If other folks have some ideas as well please add to this list. Based on
> the
> progress of this thread we can add to the page of potential projects on our
> site/wiki.
>
>
> Best,
> Alex
>