Le 02/12/14 15:57, Mark van Reijn a écrit : > Hello Emmanuel, > > I can answer your questions right away > >> <legal and practical aspects> >> That raises at least two questions though : >> - Who will maintain the code ? >> - Is the code ready for a donation ? >> >> The second question is fairly easy to deal with : if Mark is the unique >> author of this code, then a donation to Apache can be done easily. There >> is only one thing that needs to be checked : are those extensions >> developped during Mark's day job ? (ie, was he paid to develop those >> extensions ?) In this case, I think we need an agreement from his >> company too. But that is just paperwork... > > I am the sole author of this code, and I am co-owner of my company. > This solves two issues in one go ;-)
We will still need a CCLA (Corporate Contributor License Agreement) in this very case, just because you have a co-owner ;-) Seriously, not a show stopper, by far. > >> Regarding the code maintenance, this is more a concern. There are 3 use >> cases here : >> - the code is simple, and we can absorb the load >> - the code is complex, or very specific, and requires some deep >> eDirectory knowledge, but Mark can be made a committer easily, assuming >> Mark wants to assume the maintenanc (and why not helping us in other >> peices of the code ;-) >> - Mark just want to donate the code, we have nobody to maintain it. > > I would not mind to maintain this code. Attribute syntaxes rarely change, and > the eDirectory / IdM knowledge is part of my daily work. > Also, I am thinking about an enhancement to the main code with regards to DN > resolving using F3. That would be easier to research and test as a committer. Atm, I would suggest you create a JIRA, associate the code you want to propose to it. Same for the DN resolving.
