Chandan,

First we have to create a charter and then vote on this. This is not a
voting thread. But it doesn't hinder to reply with +1 as short form of
agreement.

- Stephan

On 21.02.14 06:52, "V.A, Chandan" <[email protected]> wrote:

>Hello all,
>I too agree with the progress that we have made thus far. It's great.
>But before giving my vote just a second thought, is this mail chain
>related to vote for graduation or just a discussion.
>
>Thanks,
>Kind Regards
>Chandan VA
>
>
>-----Original Message-----
>From: Bolz, Michael [mailto:[email protected]]
>Sent: Friday, February 21, 2014 11:05 AM
>To: [email protected]
>Subject: Re: [DISCUSSION] Graduation of Apache Olingo
>
>* PGP Signature not checked
>
>I totally agree.
>.great feedback and work.
>.hence +1 for graduation of Olingo.
>
>Kind regards,
>Michael
>
>On 20 Feb 2014, at 16:56, Carl Mosca <[email protected]> wrote:
>
>> Ditto
>> 
>> +1
>> 
>> Great work everyone!!
>> 
>> Carl
>> 
>> 
>> On Thu, Feb 20, 2014 at 10:51 AM, Amend, Christian
>> <[email protected]>wrote:
>> 
>>> Hi,
>>> 
>>> that`s great feedback :)
>>> 
>>> +1 from me to go for graduation.
>>> 
>>> Best Regards,
>>> Christian
>>> 
>>> -----Original Message-----
>>> From: Florian Müller [mailto:[email protected]]
>>> Sent: Donnerstag, 20. Februar 2014 10:14
>>> To: [email protected]
>>> Subject: Re: [DISCUSSION] Graduation of Apache Olingo
>>> 
>>> I agree with Dave. The podling is ready for graduation. Go for it!
>>> 
>>> 
>>> Regards,
>>> 
>>> Florian
>>> 
>>> 
>>> 
>>>>> Hi,
>>>>> 
>>>>> Apache Olingo did join incubator in July 2013. Meantime we have
>>>>> produced two releases [4] and I would say we have a healthy
>>>>>community.
>>>>> Its time to graduate. Graduation means Olingo will went out of the
>>>>> incubator and will become an official Apache top level project.
>>>>> 
>>>>> I had a look at the graduation guide [1] and come up here with a
>>>>> summary and further details. Looking at Olingos status file [2] all
>>>>> tasks are done and we have just to update it with latest project
>>>>> changes. In the clutch report [3] Olingo is completely green and also
>>>>> the name search [5] did take place.
>>>>> 
>>>>> Graduation requires a community vote, Olingo has to prepare a
>>>>> charter [6], needs then a recommendation vote on the general
>>>>>incubator
>>>>> list. The charter names a PMC with initial members and requires a
>>>>> chair for the project. The resolution goes finally to the board which
>>>>> will handle the graduation in their board meeting.
>>>>> 
>>>>> After graduation there are some duties for chair and the PMC and
>>>>> last but not least the step out of the incubator requires some more
>>>>> work [7].
>>>>> 
>>>>> Before we start a graduation process I would encourage you to
>>>>> comment.
>>>>> 
>>>>> @mentors: Do you see any issues that hinder us to graduate? Your
>>>>> feedback is very welcome.
>>>> 
>>>> I see no issues. I am very impressed with how this team has both
>>>> worked together and absorbed more developers along with an important
>>>> code donation.
>>>> 
>>>> Some podlings will ask one or two mentors to stay on the PMC and
>>>> others do not. This is often done for oversight, to help the podling
>>>> as transition to a TLP occurs and to make sure that the project
>>>> continues with governance that continues to follow the "Apache Way" -
>>>> particularly release policy.
>>>> 
>>>> Regards,
>>>> Dave
>>>> 
>>>> 
>>>>> 
>>>>> Regards,
>>>>> Stephan
>>>>> 
>>>>> 
>>>>> [1] http://incubator.apache.org/guides/graduation.html
>>>>> [2] http://incubator.apache.org/projects/olingo.html
>>>>> [3] http://incubator.apache.org/clutch.html
>>>>> [4] http://olingo.incubator.apache.org/download.html
>>>>> [5] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-42
>>>>> [6]
>>>>> 
>>> 
>>>https://svn.apache.org/repos/private/committers/board/templates/podling-
>>>tlp-resolution.txt
>>>>> [7]
>>>>> 
>>> 
>>>http://incubator.apache.org/guides/graduation.html#life-after-graduation
>>>>> 
>>> 
>>> 
>> 
>> 
>> -- 
>> Carl J. Mosca
>
>
>* Signature checking is off by policy

Reply via email to