You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@esme.apache.org by Gianugo Rabellino <g....@sourcesense.com> on 2009/03/27 09:41:37 UTC
Re: Requirements for a developer to be able to collaborate on ESME.
On Fri, Mar 27, 2009 at 9:25 AM, Hirsch, Richard
<ri...@siemens.com> wrote:
> Hi,
>
> We've been having some debate internally concerning what sort of
> development skills are necessary for a developer to be able to
> collaborate in apache ESME
>
> I've started a list. Does anyone else have any suggestions?
Er - I thought this was open source, not a job board. I would say you
should focus on whether patches are good quality, which sort-of
automatically would mean being knowledgeable about the stuff below.
Let natural selection do its job: your list is fine from an
informative standpoint, but I think it would convey the wrong message
if set up as a set of pre-requisites for joining.
Ciao,
--
Gianugo Rabellino
M: +44 779 5364 932 / +39 389 44 26 846
Sourcesense - making sense of Open Source: http://www.sourcesense.com
Re: Requirements for a developer to be able to collaborate on ESME.
Posted by Robert Burrell Donkin <ro...@gmail.com>.
On Fri, Mar 27, 2009 at 9:41 AM, Gianugo Rabellino
<g....@sourcesense.com> wrote:
> On Fri, Mar 27, 2009 at 9:25 AM, Hirsch, Richard
> <ri...@siemens.com> wrote:
>> Hi,
>>
>> We've been having some debate internally concerning what sort of
>> development skills are necessary for a developer to be able to
>> collaborate in apache ESME
>>
>> I've started a list. Does anyone else have any suggestions?
>
> Er - I thought this was open source, not a job board. I would say you
> should focus on whether patches are good quality, which sort-of
> automatically would mean being knowledgeable about the stuff below.
> Let natural selection do its job: your list is fine from an
> informative standpoint, but I think it would convey the wrong message
> if set up as a set of pre-requisites for joining.
+1
it would be more positive to list skills as a way to link to
contributions which could be made with people with each skill
- robert
RE: Other authentication besides OpenID
Posted by "Hirsch, Richard" <ri...@siemens.com>.
I just found a most recent discussion that talks about authentication on the lift Google group: http://www.mail-archive.com/liftweb@googlegroups.com/msg04205.html
D.
________________________________
From: Hirsch, Richard
Sent: Sun 29.03.2009 09:15
To: esme-dev@incubator.apache.org
Subject: Other authentication besides OpenID
I'm involved in a variety of different development projects in different roles (consultant, deployment manager, project manager, etc.) and I'd like to use ESME as a tool in these projects - private ESME instances. I have two project in particular where I could use ESME to publish status messages from deployments, server exceptions, tests, svn check-outs, etc. These projects are currently in progress and I'd love to have the micro-blogging functionality to make the projects more efficient. They would also provide us with two references.
Many of these projects are internal and protected by firewalls prohibting Internet access and, thus, have no access to external OpenID sites. As I have discovered with our internal pilot, there is a certain overhead and complexity of hosting and using internal OpenID sites. Furthermore, corporate users (irregardless of whether developer or business user) are unnaccustomed to using OpenID - despite its benefits. The necesity of using OpenID is thus a definite hurdle for potential corporate users.
Therefore, I'd like to purpose that we support other forms of authentication. Although I'd love to have container-based authentication but I'd be happy with username/password. If you look at Buy A Feature (http://buyafeature.com/index <http://buyafeature.com/index> ) which is also lift-based, you'll see that this authentication -type is obviously supported.
If you look at the lift mailing list, there was some suggestions about possible solutions (http://www.mail-archive.com/liftweb@googlegroups.com/msg01611.html <http://www.mail-archive.com/liftweb@googlegroups.com/msg01611.html> ) but I have no idea if this made it into Lift 1.0 or not or whether this would help us.
I'm willing to use ESME in my own development projects but without forcing the users to use OpenID.
I've added a JIRA item to deal with this issue: https://issues.apache.org/jira/browse/ESME-52 <https://issues.apache.org/jira/browse/ESME-52>
D.
Other authentication besides OpenID
Posted by "Hirsch, Richard" <ri...@siemens.com>.
I'm involved in a variety of different development projects in different roles (consultant, deployment manager, project manager, etc.) and I'd like to use ESME as a tool in these projects - private ESME instances. I have two project in particular where I could use ESME to publish status messages from deployments, server exceptions, tests, svn check-outs, etc. These projects are currently in progress and I'd love to have the micro-blogging functionality to make the projects more efficient. They would also provide us with two references.
Many of these projects are internal and protected by firewalls prohibting Internet access and, thus, have no access to external OpenID sites. As I have discovered with our internal pilot, there is a certain overhead and complexity of hosting and using internal OpenID sites. Furthermore, corporate users (irregardless of whether developer or business user) are unnaccustomed to using OpenID - despite its benefits. The necesity of using OpenID is thus a definite hurdle for potential corporate users.
Therefore, I'd like to purpose that we support other forms of authentication. Although I'd love to have container-based authentication but I'd be happy with username/password. If you look at Buy A Feature (http://buyafeature.com/index <http://buyafeature.com/index> ) which is also lift-based, you'll see that this authentication -type is obviously supported.
If you look at the lift mailing list, there was some suggestions about possible solutions (http://www.mail-archive.com/liftweb@googlegroups.com/msg01611.html <http://www.mail-archive.com/liftweb@googlegroups.com/msg01611.html> ) but I have no idea if this made it into Lift 1.0 or not or whether this would help us.
I'm willing to use ESME in my own development projects but without forcing the users to use OpenID.
I've added a JIRA item to deal with this issue: https://issues.apache.org/jira/browse/ESME-52 <https://issues.apache.org/jira/browse/ESME-52>
D.
Re: Requirements for a developer to be able to collaborate on ESME.
Posted by J Aaron Farr <fa...@apache.org>.
On Fri 27 Mar 2009 15:29, Erik Engbrecht <er...@gmail.com> wrote:
> Perhaps it should be more of a "getting with contributing to ESME" than a
> "skills needed to contribute to ESME". Having a list of key technologies
> used in ESME is a good thing.
Yes. It's a good idea to have a document on "How to get involved" or
"How to contribute." For the most part, this document should give
suggestions on what someone interested in ESME can do such as:
- How to write up documentation
- Steps for submitting a patch
- How to sign up for mailing lists, etc.
Skills are then self-evident. Clearly to submit a patch, someone needs
to learn how to use svn, scala, etc.
--
J Aaron Farr jadetower.com [US] +1 724-964-4515
馮傑仁 cubiclemuses.com [HK] +852 8123-7905
Re: Requirements for a developer to be able to collaborate on ESME.
Posted by Erik Engbrecht <er...@gmail.com>.
Perhaps it should be more of a "getting with contributing to ESME" than a
"skills needed to contribute to ESME". Having a list of key technologies
used in ESME is a good thing.
On Fri, Mar 27, 2009 at 10:22 AM, Hirsch, Richard <
richard.hirsch@siemens.com> wrote:
> Imagine this:
>
> You've heard of ESME and think it is a cool idea. You'd like to contribute
> but don't know where to start. My idea was to get a basic list of skills
> that might be useful as a starting point.
>
> My intention was not to have the list to be a "required" skills list for
> potential contributors. I'd like to each have each "skill" be connected
> with a list of links that should enable those interested to get started.
> Each skill might be linked to particular JIRA items.
>
> D.
>
> -----Ursprüngliche Nachricht-----
> Von: Gianugo Rabellino [mailto:g.rabellino@sourcesense.com]
> Gesendet: Freitag, 27. März 2009 09:42
> An: esme-dev@incubator.apache.org
> Betreff: Re: Requirements for a developer to be able to collaborate on
> ESME.
>
> On Fri, Mar 27, 2009 at 9:25 AM, Hirsch, Richard
> <ri...@siemens.com> wrote:
> > Hi,
> >
> > We've been having some debate internally concerning what sort of
> > development skills are necessary for a developer to be able to
> > collaborate in apache ESME
> >
> > I've started a list. Does anyone else have any suggestions?
>
> Er - I thought this was open source, not a job board. I would say you
> should focus on whether patches are good quality, which sort-of
> automatically would mean being knowledgeable about the stuff below.
> Let natural selection do its job: your list is fine from an
> informative standpoint, but I think it would convey the wrong message
> if set up as a set of pre-requisites for joining.
>
> Ciao,
>
> --
> Gianugo Rabellino
> M: +44 779 5364 932 / +39 389 44 26 846
> Sourcesense - making sense of Open Source: http://www.sourcesense.com
>
--
http://erikengbrecht.blogspot.com/
AW: Requirements for a developer to be able to collaborate on ESME.
Posted by "Hirsch, Richard" <ri...@siemens.com>.
Imagine this:
You've heard of ESME and think it is a cool idea. You'd like to contribute but don't know where to start. My idea was to get a basic list of skills that might be useful as a starting point.
My intention was not to have the list to be a "required" skills list for potential contributors. I'd like to each have each "skill" be connected with a list of links that should enable those interested to get started. Each skill might be linked to particular JIRA items.
D.
-----Ursprüngliche Nachricht-----
Von: Gianugo Rabellino [mailto:g.rabellino@sourcesense.com]
Gesendet: Freitag, 27. März 2009 09:42
An: esme-dev@incubator.apache.org
Betreff: Re: Requirements for a developer to be able to collaborate on ESME.
On Fri, Mar 27, 2009 at 9:25 AM, Hirsch, Richard
<ri...@siemens.com> wrote:
> Hi,
>
> We've been having some debate internally concerning what sort of
> development skills are necessary for a developer to be able to
> collaborate in apache ESME
>
> I've started a list. Does anyone else have any suggestions?
Er - I thought this was open source, not a job board. I would say you
should focus on whether patches are good quality, which sort-of
automatically would mean being knowledgeable about the stuff below.
Let natural selection do its job: your list is fine from an
informative standpoint, but I think it would convey the wrong message
if set up as a set of pre-requisites for joining.
Ciao,
--
Gianugo Rabellino
M: +44 779 5364 932 / +39 389 44 26 846
Sourcesense - making sense of Open Source: http://www.sourcesense.com