Ok thanks. I'll ask for an ICLA very soon.
Yes, you're right. I'd like to move on the dev@ side.
First, I'll try to propose my ideas on JIRA. It will be a good training
also.
Then, we will see.
I'll need time to read the code of the project to scale the code rules
and its phylosophy/design.
Le 29/05/2014 10:12, Francesco Chicchiriccò a écrit :
On 28/05/2014 22:47, SyncopeDev wrote:
Ok, I have created my id : syncopedev.
I have to take a look at the wiki.
I understand you need help specially on documentation. No problem, I
can try even if my english is not so good.
Before any contribution, please take a look at
http://syncope.apache.org/contributing.html
and send an ICLA (this weird acronym should look more familiar once
read the page above).
Helping with documentation is heavily appreciated and should be a
good way for you to get familiar with Syncope.
Could you give the url that point on the JIRA Syncope Project please ?
Sure: https://issues.apache.org/jira/browse/SYNCOPE
And then, I'll document my use cases with the 4 points you focus on.
Finally, what do you mean by discussion to @dev ? Sorry I'm a rookie.
No problem; you had to subscribe to user@syncope.apache.org before
posting here, right?
Now you need to also subscribe to d...@syncope.apache.org and we will
be discussing such topics there.
This because user@ is targeted to support people using Syncope, while
dev@ is targeted to support developers contributing to Syncope (and it
looks you want to move to this side).
HTH
Regards.
Le 28/05/2014 10:21, Francesco Chicchiriccò a écrit :
On 27/05/2014 17:23, Bruno SyncopeDev wrote:
[...]
Do you think you could be interested in proposals about developing
third party applications as part of Syncope with new functionnalities ?
Ah ok, now I got it: do you mean building specialized Syncope-based
solutions for targeting specific use cases? Great idea.
Examples :
- Implementing security perimeter
A security administrator is managing a perimeter. He is responsible
of users in this perimeter.
- Recertification of identities and access roles.
It could be the case to start collecting some of these use cases in
our wiki: please create an account at
http://cwiki.apache.org/confluence/display/SYNCOPE/
and then tell me your id so that I can grant you the write permission.
IMO, for each use case we should be able to provide at least:
1. high level description
2. detailed requirements
3. possible implementation with reference to current and / or
missing Syncope features
then finally generate a set of correspondent JIRA issues, to be
mapped to one of future releases in the roadmap.
Not sure to be very clear in my question. But I'm trying to
understand if Syncope will evolve in a way that non IT
administrator will have the capability to give and withdraw rights
without knowing the technical layer.
Like : I'm a bank agency manager. I'm responsible for security
administration for 5 persons. I allow a composed business role like
a package attached related to the function of the guy.
Finally, I'm ready to help on syncope if you need.
Oh, it's plenty of help we need here, ranging from our very poor and
sparse documentation to actual features (see JIRA).
Anyway, I'd say we need to move this discussion to dev@
Regards.
2014-05-27 8:51 GMT+02:00 Francesco Chicchiriccò
ilgro...@apache.org mailto:ilgro...@apache.org:
On 26/05/2014 20:40, Bruno SyncopeDev wrote:
Hi Francisco,
Hi Bruno,
Thanks a lot for you reply. I read the nlight ressources on
the subject a couple of months ago when I thought OpenIDM will
still be OpenSource in right terms.
Anyway, I seems there is another OpenSource project called
MidPoint by Evolveum.
I don't have any information about the stability of those
business model : will they still be OpenSource ? etc...
Eh eh eh, that's one of the reasons why Syncope is a project at
The Apache Software Foundation...
But the support of this product must be expensive.
Anyway, What surprising me, is the fact that there is no
implementation on common business process proposed in Syncope.
Maybe I'm wrong ?
What if you propose some kind of business patterns as the
Third party Applications ?
Could you please indicate some samples?
The provisioning system is something very technical. But each
IAM solutions is shy to propose high level scenarios with
delegated administrations or dynamic role base management.
Isn't there a lack on this point ?
What is your vision about that ?
I am not sure we are talking of something that you can decently
generalize: in my experience, even though some reference
patterns are available, implementing a IAM solution is often
more a tailor attach on customer's infrastructure than a
general, repeatable and fully standardized process.
Actually, this fact underlies most of the
