Re: [DISCUSS] Graduation - Prepare Board Resolution

[Andy Kurth]

On Thu, May 31, 2012 at 11:03 AM, Aaron Coburn  wrote:
>>> ...
>> will propose it on the general incubator list.  The areas we need to
>> work on are in bold.  We need to define the project description and
>> scope.  I wrote this as "dynamically provisioning and brokering remote
>> access to compute resources".  Thoughts?

 I'm not sure I would not really understand the scope of VCL from that 
 statement.
>>>
>>> I agree more should be added.  I kept it short since the example
>>> resolutions suggested on the graduation guide page are very short and
>>> general:
>>> ofbiz: "open-source software related to enterprise automation"
>>>
>>> Can we just use the description then?:
>>> "open-source software related to a modular cloud computing platform
>>> which dynamically provisions and brokers remote access to compute
>>> resources"
>>
>>  I think this is reasonable - but have a *minor* quibble -
>>
>>  The bulk of what the VCL does (auth/auth, reservations, image
>> storage, image loading, ...) seems to me to be fall under the
>> "provisions" concept - but "brokers" seems to be getting equal
>> emphasis even though it is an added capability. It's an important
>> added capability, but perhaps this slight revision might help:
>
> I don't have a strong opinion about this, but I have always understood 
> "provisioning" to relate to the infrastructure for image storage, capture and 
> loading while "brokering" relates to connecting the virtualization or blade 
> back-end to a user's request, which would include such things as 
> authentication, authorization, reservations, scheduling, etc. I think the two 
> are pretty equal in importance.
>
> Just my $0.02
>
> -Aaron C

That's what I was thinking.
-Andy

Re: [DISCUSS] Graduation - Prepare Board Resolution

[Aaron Coburn]

>> ...
> will propose it on the general incubator list.  The areas we need to
> work on are in bold.  We need to define the project description and
> scope.  I wrote this as "dynamically provisioning and brokering remote
> access to compute resources".  Thoughts?
>>> 
>>> I'm not sure I would not really understand the scope of VCL from that 
>>> statement.
>> 
>> I agree more should be added.  I kept it short since the example
>> resolutions suggested on the graduation guide page are very short and
>> general:
>> ofbiz: "open-source software related to enterprise automation"
>> 
>> Can we just use the description then?:
>> "open-source software related to a modular cloud computing platform
>> which dynamically provisions and brokers remote access to compute
>> resources"
> 
>  I think this is reasonable - but have a *minor* quibble -
> 
>  The bulk of what the VCL does (auth/auth, reservations, image
> storage, image loading, ...) seems to me to be fall under the
> "provisions" concept - but "brokers" seems to be getting equal
> emphasis even though it is an added capability. It's an important
> added capability, but perhaps this slight revision might help:

I don't have a strong opinion about this, but I have always understood 
"provisioning" to relate to the infrastructure for image storage, capture and 
loading while "brokering" relates to connecting the virtualization or blade 
back-end to a user's request, which would include such things as 
authentication, authorization, reservations, scheduling, etc. I think the two 
are pretty equal in importance.

Just my $0.02

-Aaron C


> "open-source software related to a modular cloud computing platform
> which dynamically provisions (and brokers) remote access to compute
> resources"
> 
> --henry
> 
>> ...



smime.p7s
Description: S/MIME cryptographic signature

Re: [DISCUSS] Graduation - Prepare Board Resolution

[Henry Schaffer]

>...
 will propose it on the general incubator list.  The areas we need to
 work on are in bold.  We need to define the project description and
 scope.  I wrote this as "dynamically provisioning and brokering remote
 access to compute resources".  Thoughts?
>>
>> I'm not sure I would not really understand the scope of VCL from that 
>> statement.
>
> I agree more should be added.  I kept it short since the example
> resolutions suggested on the graduation guide page are very short and
> general:
> ofbiz: "open-source software related to enterprise automation"
>
> Can we just use the description then?:
> "open-source software related to a modular cloud computing platform
> which dynamically provisions and brokers remote access to compute
> resources"

  I think this is reasonable - but have a *minor* quibble -

  The bulk of what the VCL does (auth/auth, reservations, image
storage, image loading, ...) seems to me to be fall under the
"provisions" concept - but "brokers" seems to be getting equal
emphasis even though it is an added capability. It's an important
added capability, but perhaps this slight revision might help:

 "open-source software related to a modular cloud computing platform
which dynamically provisions (and brokers) remote access to compute
resources"

--henry

>...

Re: [DISCUSS] Graduation - Prepare Board Resolution

[Andy Kurth]

>> On Fri, May 18, 2012 at 10:06 AM, Andy Kurth  wrote:
>>> I have created a Confluence page which we can use to work out the
>>> board resolution:
>>> https://cwiki.apache.org/confluence/display/VCL/Graduation+Board+Resolution
>>>
>>> Once we are comfortable with the resolution, one of the PPMC members
>>> will propose it on the general incubator list.  The areas we need to
>>> work on are in bold.  We need to define the project description and
>>> scope.  I wrote this as "dynamically provisioning and brokering remote
>>> access to compute resources".  Thoughts?
>
> I'm not sure I would not really understand the scope of VCL from that 
> statement.

I agree more should be added.  I kept it short since the example
resolutions suggested on the graduation guide page are very short and
general:
ofbiz: "open-source software related to enterprise automation"

Can we just use the description then?:
"open-source software related to a modular cloud computing platform
which dynamically provisions and brokers remote access to compute
resources"

I have updated the wiki to include this text and also added Alan to
the list of members:
https://cwiki.apache.org/confluence/display/VCL/Graduation+Board+Resolution

I haven't seen a tally message for the chairperson vote.  Once the
vote is closed I'll add my name to the page.

-Andy

Re: [DISCUSS] Graduation - Prepare Board Resolution

[Kevan Miller]

We need to move this resolution along, if we want to be ready for the next 
board meeting…

On May 18, 2012, at 10:51 AM, Mark Gardner wrote:

> Andy,
> 
> I believe one of the strengths of VCL is in its ability to manage
> software license issues and use roles to manage who has access to
> what. Is this something that should be included or should we save that
> for a later and longer description further down the page.

The resolution does not need to list *all* attributes (or call out particular 
strengths). It needs to describe the scope of the project. Not overly broad, 
not overly narrow. Just right… ;-). You don't need to market yourselves. You've 
proven that there's a community around VCL. That's the important part.

> 
> Mark
> 
> On Fri, May 18, 2012 at 10:06 AM, Andy Kurth  wrote:
>> I have created a Confluence page which we can use to work out the
>> board resolution:
>> https://cwiki.apache.org/confluence/display/VCL/Graduation+Board+Resolution
>> 
>> Once we are comfortable with the resolution, one of the PPMC members
>> will propose it on the general incubator list.  The areas we need to
>> work on are in bold.  We need to define the project description and
>> scope.  I wrote this as "dynamically provisioning and brokering remote
>> access to compute resources".  Thoughts?

I'm not sure I would not really understand the scope of VCL from that 
statement. 



>> The description is currently "VCL is a management framework for
>> building, dispensing and managing virtual machine images across a set
>> of bare metal machines or systems with an installed virtual machine
>> hypervisor."  I don't think this is quite accurate.  How about "VCL is
>> a modular cloud computing platform which dynamically provisions and
>> brokers remote access to compute resources."?

I understand that.

--kevan

Re: [DISCUSS] Graduation - Prepare Board Resolution

[Josh Thompson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I'd say to include that part in a longer description.

Josh

On Friday, May 18, 2012 10:51:58 AM Mark Gardner wrote:
> Andy,
> 
> I believe one of the strengths of VCL is in its ability to manage
> software license issues and use roles to manage who has access to
> what. Is this something that should be included or should we save that
> for a later and longer description further down the page.
> 
> Mark
> 
> On Fri, May 18, 2012 at 10:06 AM, Andy Kurth  wrote:
> > I have created a Confluence page which we can use to work out the
> > board resolution:
> > https://cwiki.apache.org/confluence/display/VCL/Graduation+Board+Resolutio
> > n
> > 
> > Once we are comfortable with the resolution, one of the PPMC members
> > will propose it on the general incubator list.  The areas we need to
> > work on are in bold.  We need to define the project description and
> > scope.  I wrote this as "dynamically provisioning and brokering remote
> > access to compute resources".  Thoughts?
> > 
> > Please check the list of initial members to make sure I didn't leave
> > anyone out.  This list includes both PPMC members and committers,
> > correct?  If we are in agreement that the list will be the committers
> > after graduation, should the status file be changed now?
> > 
> > The PPMC members also need to appoint a chair for the project.  I
> > would be willing to do this.  Anyone else interested?
> > 
> > Also, 2 more issues regarding the status file:
> > The stock bullets under "Project info" should be removed.
> > 
> > The description is currently "VCL is a management framework for
> > building, dispensing and managing virtual machine images across a set
> > of bare metal machines or systems with an installed virtual machine
> > hypervisor."  I don't think this is quite accurate.  How about "VCL is
> > a modular cloud computing platform which dynamically provisions and
> > brokers remote access to compute resources."?
> > 
> > Thanks,
> > Andy
- -- 
- ---
Josh Thompson
VCL Developer
North Carolina State University

my GPG/PGP key can be found at pgp.mit.edu

All electronic mail messages in connection with State business which
are sent to or received by this account are subject to the NC Public
Records Law and may be disclosed to third parties.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (GNU/Linux)

iEYEARECAAYFAk+6owAACgkQV/LQcNdtPQNhqwCcCy/A4TivQtowaSZW2+1vYam1
MxcAnj1NH/69bvr85r5VDxXYFp4WZ5LR
=YL7p
-END PGP SIGNATURE-

Re: [DISCUSS] Graduation - Prepare Board Resolution

[Josh Thompson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Friday, May 18, 2012 10:06:57 AM Andy Kurth wrote:
> I have created a Confluence page which we can use to work out the
> board resolution:
> https://cwiki.apache.org/confluence/display/VCL/Graduation+Board+Resolution

The resolution looks good to me.

> Once we are comfortable with the resolution, one of the PPMC members
> will propose it on the general incubator list.  The areas we need to
> work on are in bold.  We need to define the project description and
> scope.  I wrote this as "dynamically provisioning and brokering remote
> access to compute resources".  Thoughts?

What you have works for me.

> Please check the list of initial members to make sure I didn't leave
> anyone out.  This list includes both PPMC members and committers,
> correct?  If we are in agreement that the list will be the committers
> after graduation, should the status file be changed now?

(Aaron P. - thanks for contacting Brian B. about his continued interest.)

> The PPMC members also need to appoint a chair for the project.  I
> would be willing to do this.  Anyone else interested?

I'd support you doing this.  It may be a good idea to include a term length in 
our bylaws so that whoever is in the chair position has a definite end to 
their commitment (with the option to continue).  I'd just like to avoid the 
case where someone volunteers and then gets stuck in a position because no one 
else wants to do it.

> Also, 2 more issues regarding the status file:
> The stock bullets under "Project info" should be removed.
> 
> The description is currently "VCL is a management framework for
> building, dispensing and managing virtual machine images across a set
> of bare metal machines or systems with an installed virtual machine
> hypervisor."  I don't think this is quite accurate.  How about "VCL is
> a modular cloud computing platform which dynamically provisions and
> brokers remote access to compute resources."?

How about adding a little on the end about our simple end user self-service 
interface?  Something like:

VCL is a modular cloud computing platform which dynamically provisions and 
brokers remote access to compute resources while providing a simple self-
service interface for end users.

I'm certainly not a grammar expert, but I don't think a comma is needed before 
the 'which' in this case.

Josh
- -- 
- ---
Josh Thompson
VCL Developer
North Carolina State University

my GPG/PGP key can be found at pgp.mit.edu

All electronic mail messages in connection with State business which
are sent to or received by this account are subject to the NC Public
Records Law and may be disclosed to third parties.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (GNU/Linux)

iEYEARECAAYFAk+6otcACgkQV/LQcNdtPQM3LwCfSOIqw8NQMFPZvKWSt3RNdF6i
x28An0e1o46/VhiXJM58ge1AEr7ENMED
=H18A
-END PGP SIGNATURE-

Re: [DISCUSS] Graduation - Prepare Board Resolution

[Kevan Miller]

On May 18, 2012, at 10:06 AM, Andy Kurth wrote:

> I have created a Confluence page which we can use to work out the
> board resolution:
> https://cwiki.apache.org/confluence/display/VCL/Graduation+Board+Resolution
> 
> Once we are comfortable with the resolution, one of the PPMC members
> will propose it on the general incubator list.  The areas we need to
> work on are in bold.  We need to define the project description and
> scope.  I wrote this as "dynamically provisioning and brokering remote
> access to compute resources".  Thoughts?
> 
> Please check the list of initial members to make sure I didn't leave
> anyone out.  This list includes both PPMC members and committers,
> correct?  If we are in agreement that the list will be the committers
> after graduation, should the status file be changed now?

It would be good to list all current "committers" who aren't on this list. From 
a quick scan, it looks like bmbouter made some commits in 2009 and isn't 
included. Which is OK. But from my experience, best to be explicit on these 
matters, and discuss the criteria used to determine the list. Make sure you're 
including documentation contributions and mailing list discussions etc. 

Alan said he'd follow the project to help insure a smooth graduation. So, I'd 
add him. You can leave me on the list, also.

No. Don't change status file. Technically, that would require a vote…


> 
> The PPMC members also need to appoint a chair for the project.  I
> would be willing to do this.  Anyone else interested?

I"m happy with the choice of the community.

> 
> Also, 2 more issues regarding the status file:
> The stock bullets under "Project info" should be removed.
> 
> The description is currently "VCL is a management framework for
> building, dispensing and managing virtual machine images across a set
> of bare metal machines or systems with an installed virtual machine
> hypervisor."  I don't think this is quite accurate.  How about "VCL is
> a modular cloud computing platform which dynamically provisions and
> brokers remote access to compute resources."?

I'll look at details of the text later… May be next week...

--kevan

Re: [DISCUSS] Graduation - Prepare Board Resolution

[Aaron Coburn]

On May 18, 2012, at 10:06 AM, Andy Kurth wrote:

> I have created a Confluence page which we can use to work out the
> board resolution:
> https://cwiki.apache.org/confluence/display/VCL/Graduation+Board+Resolution
> 
> Once we are comfortable with the resolution, one of the PPMC members
> will propose it on the general incubator list.  The areas we need to
> work on are in bold.  We need to define the project description and
> scope.  I wrote this as "dynamically provisioning and brokering remote
> access to compute resources".  Thoughts?

Thanks for writing this. It sounds great.

> Please check the list of initial members to make sure I didn't leave
> anyone out.  This list includes both PPMC members and committers,
> correct?  If we are in agreement that the list will be the committers
> after graduation, should the status file be changed now?
> 
> The PPMC members also need to appoint a chair for the project.  I
> would be willing to do this.  Anyone else interested?

I would support having Andy serve as chair.

> Also, 2 more issues regarding the status file:
> The stock bullets under "Project info" should be removed.
> 
> The description is currently "VCL is a management framework for
> building, dispensing and managing virtual machine images across a set
> of bare metal machines or systems with an installed virtual machine
> hypervisor."  I don't think this is quite accurate.  How about "VCL is
> a modular cloud computing platform which dynamically provisions and
> brokers remote access to compute resources."?

That sounds much better (though I believe a comma should precede 'which').

Aaron Coburn


--
Aaron Coburn
Systems Administrator and Programmer
Academic Technology Services, Amherst College
acob...@amherst.edu








smime.p7s
Description: S/MIME cryptographic signature

Re: [DISCUSS] Graduation - Prepare Board Resolution

[Mark Gardner]

Andy,

I believe one of the strengths of VCL is in its ability to manage
software license issues and use roles to manage who has access to
what. Is this something that should be included or should we save that
for a later and longer description further down the page.

Mark

On Fri, May 18, 2012 at 10:06 AM, Andy Kurth  wrote:
> I have created a Confluence page which we can use to work out the
> board resolution:
> https://cwiki.apache.org/confluence/display/VCL/Graduation+Board+Resolution
>
> Once we are comfortable with the resolution, one of the PPMC members
> will propose it on the general incubator list.  The areas we need to
> work on are in bold.  We need to define the project description and
> scope.  I wrote this as "dynamically provisioning and brokering remote
> access to compute resources".  Thoughts?
>
> Please check the list of initial members to make sure I didn't leave
> anyone out.  This list includes both PPMC members and committers,
> correct?  If we are in agreement that the list will be the committers
> after graduation, should the status file be changed now?
>
> The PPMC members also need to appoint a chair for the project.  I
> would be willing to do this.  Anyone else interested?
>
> Also, 2 more issues regarding the status file:
> The stock bullets under "Project info" should be removed.
>
> The description is currently "VCL is a management framework for
> building, dispensing and managing virtual machine images across a set
> of bare metal machines or systems with an installed virtual machine
> hypervisor."  I don't think this is quite accurate.  How about "VCL is
> a modular cloud computing platform which dynamically provisions and
> brokers remote access to compute resources."?
>
> Thanks,
> Andy



-- 
Mark Gardner
--

Re: [DISCUSS] Graduation

[Alan D. Cabrera]

On May 1, 2012, at 9:44 AM, Andy Kurth wrote:

> This thread is to discuss whether the Apache VCL community feels that
> this incubating project is ready to proceed with the process to
> graduate to a top level ASF project.  There are several requirements
> which must be met and steps completed in order to graduate.   This
> discussion thread is the first step towards graduation.  Please review
> the following pages.
> http://incubator.apache.org/guides/graduation.html
> http://incubator.apache.org/incubation/Incubation_Policy.html#Graduating+from+the+Incubator
> 
> There are many items described in the ASF graduation documentation
> which we have obviously satisfied (create a release, etc).  The
> following are issues that I feel either need to be addressed, would be
> concerned about regarding board/mentor approval, or have been brought
> up before.  Please share your thoughts.  Also, please review the ASF
> graduation documentation and bring up anything else which might be a
> concern.
> 
> Status File:
> (https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/vcl.xml)
> This is not up to date and is missing information.  Previous board
> reports need to be added.  News items need to be added containing the
> string "new committer".  Doing this will cause the numberCommittersNew
> column on the "Status of the Clutch" page to turn green
> (http://incubator.apache.org/clutch.html).
> 
> Also, the list of commiters in the status file and project page hasn't
> changed since Apache VCL started.  The new committers obviously need
> to be added.  I'm not sure how the original list was decided upon, but
> I feel several names should be removed since they have not contributed
> any code and some have not been involved in the community at all.  I
> think the list should be Aaron Coburn, David Hutchins, Andy Kurth,
> James O'Dell, Aaron Peeler, Josh Thompson.  Also, Brian Bouterse
> contributed some code a while ago.  I'm not sure if he is still
> interested in being a committer.

I can update this tomorrow.

> Diversity:
> ASF requirement: "The project is not highly dependent on any single
> contributor (there are at least 3 legally independent committers and
> there is no single company or entity that is vital to the success of
> the project)."
> This issue has been raised before.  I feel we meet this requirement
> and that the community is generally diverse, can govern itself, and be
> self-sufficient.

I agree.

> Website:
> This is not necessarily a requirement for graduation but I feel that
> it should be addressed prior to graduation.  Our website/documentation
> is pretty rough and really should be redesigned.  I'm guessing the
> board members will look at it prior to voting.  In addition, there
> will likely be a press release if/when we graduate and website views
> will spike.  This shouldn't hold up the graduation process, but I
> would like agreement that this should be completed by graduation.


Up to you guys.

I support this project's graduation.


Regards,
Alan

 

RE: [DISCUSS] Graduation

[Miller, Tony]

Let's graduate, already!

-- 
Tony Miller
Technology Consultant, ITCS
Austin 106N /\ 737-1515 /\ mill...@ecu.edu /\ http://blog.ecu.edu/techtips

-Original Message-
From: Kevan Miller [mailto:kevan.mil...@gmail.com] 
Sent: Monday, May 07, 2012 3:41 PM
To: vcl-user@incubator.apache.org
Subject: Re: [DISCUSS] Graduation


So far, I've seen input from 4 committers and 4 community members (unless I 
have names mixed up). Would be great to hear from more people (especially 
committers). Even if it's "let's graduate, already!"

--kevan

Re: [DISCUSS] Graduation

[Kevan Miller]

On May 7, 2012, at 3:53 PM, Alexander Patterson wrote:

> I would love to see 2.3 to graduate :) I will enjoy many of the bug fixes

Thanks Alexander. Minor point - a 2.3 release is orthogonal to the graduation 
process. A 2.3 release can happen before or after graduation…

There's a 'status of 2.3 release' thread on the vcl-dev list. You're more than 
welcome to voice your 2.3 desires, there...

--kevan

Re: [DISCUSS] Graduation

[Karuna P Joshi]

Let's graduate.

On Mon, May 7, 2012 at 3:40 PM, Kevan Miller  wrote:

>
> So far, I've seen input from 4 committers and 4 community members (unless
> I have names mixed up). Would be great to hear from more people (especially
> committers). Even if it's "let's graduate, already!"
>
> --kevan




-- 
regards,
Karuna

Karuna Pande Joshi
PhD Candidate,
CSEE Dept, UMBC
kjos...@umbc.edu,  karuna.jo...@umbc.edu

Re: [DISCUSS] Graduation

[Alexander Patterson]

I would love to see 2.3 to graduate :) I will enjoy many of the bug fixes
-Alex CSUEB

On Mon, May 7, 2012 at 12:51 PM, Mark Gardner  wrote:

> On Mon, May 7, 2012 at 3:40 PM, Kevan Miller 
> wrote:
> >
> > So far, I've seen input from 4 committers and 4 community members
> (unless I have names mixed up). Would be great to hear from more people
> (especially committers). Even if it's "let's graduate, already!"
> >
> > --kevan
>
> "Let's graduate, already!" :-)
>
> Mark
>
> --
> Mark Gardner
> --
>



-- 
Thanks,
Alex  Patterson
User Support Services
Operating System Analyst
California State University, East Bay

Re: [DISCUSS] Graduation

[Mark Gardner]

On Mon, May 7, 2012 at 3:40 PM, Kevan Miller  wrote:
>
> So far, I've seen input from 4 committers and 4 community members (unless I 
> have names mixed up). Would be great to hear from more people (especially 
> committers). Even if it's "let's graduate, already!"
>
> --kevan

"Let's graduate, already!" :-)

Mark

-- 
Mark Gardner
--

Re: [DISCUSS] Graduation

[Kevan Miller]

So far, I've seen input from 4 committers and 4 community members (unless I 
have names mixed up). Would be great to hear from more people (especially 
committers). Even if it's "let's graduate, already!"

--kevan

Re: [DISCUSS] Graduation

[Kevan Miller]

On May 1, 2012, at 12:44 PM, Andy Kurth wrote:

> Status File:
> (https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/vcl.xml)
> This is not up to date and is missing information.  Previous board
> reports need to be added.  News items need to be added containing the
> string "new committer".  Doing this will cause the numberCommittersNew
> column on the "Status of the Clutch" page to turn green
> (http://incubator.apache.org/clutch.html).
> 
> Also, the list of commiters in the status file and project page hasn't
> changed since Apache VCL started.  The new committers obviously need
> to be added.  I'm not sure how the original list was decided upon, but
> I feel several names should be removed since they have not contributed
> any code and some have not been involved in the community at all.  I
> think the list should be Aaron Coburn, David Hutchins, Andy Kurth,
> James O'Dell, Aaron Peeler, Josh Thompson.  Also, Brian Bouterse
> contributed some code a while ago.  I'm not sure if he is still
> interested in being a committer.

I've added news items and updated the committers list for: David Hutchins, 
Aaron Coburn, and James O'dell.

Andrew Kurth, Josh Thompson, and Aaron Peeler were all on the initial 
committers list. If you are implying that that list should be the current 
committers list -- as a podling graduates, the committers/PMC members of the 
podling are named in the graduation proposal. That list is not necessarily all 
of the committers on the podling committers list. It's not uncommon for initial 
committers to have very little/no participation in the podling. The podling 
should discuss this and propose the list of committers for the new project.

If you feel Brian Bouterse's contributions merit consideration for committer, 
please bring this up on private@ and let's discuss…

--kevan

RE: [DISCUSS] Graduation

[Hayashi, Daiyu]

Greetings,

I would agree with James about a good set of how to guides around a simple set 
of hardware. Make it a VCL for dummies guide which goes step by step. Break it 
into pieces, maybe a YouTube video series. Maybe the whole environment could be 
done in a virtual sandbox environment.

This may sound blunt and apologize in advance but I've had other local 
university and college groups say that it is difficult to setup due to the lack 
of documentation, "holes" in the documentation and lack of examples and I agree 
with them.

Daiyu Hayashi
Lead Information Technology Consultant
Mihaylo College of Business and Economics
Cal State University Fullerton
657-278-7347

-Original Message-
From: James O'Dell [mailto:jod...@fullerton.edu] 
Sent: Friday, May 04, 2012 9:12 AM
To: vcl-user@incubator.apache.org
Subject: Re: [DISCUSS] Graduation

Hi,

I support graduation. The project has a good group of supporters, and has 
demonstrated continued growth over time. It's a stable project, and should 
graduate.

In the future, I hope it becomes easier to install and maintain (i.e. yum 
package management). I've been looking into what it would take to post it to 
EPEL. After graduation, this seems like a natural progression.

Also, after meeting with representatives from other campuses, I found that they 
really had a problem configuring VCL the first time (Most of the off campus 
calls I receive about VCL were asking for help configuring VCL. In particular, 
what equipment to use, how to setup DHCP, how to configure Shibboleth, how to 
make it work under windows - as for the last one, please don't!).
If there had been some examples of actual equipment configurations, and some 
screen shots of configuration pages, it would have been nice.

IMHO, it think it would be helpful to setup a demo system on the VCL website.
Just to help people who haven't had any exposure to VCL get an idea what to 
expect. From what I've experienced, people want to compare it to things like 
Citrix, but give up because they have trouble setting up a test bed.

Just my 2 cents worth,

__Jim O'Dell

On 5/1/2012 9:44 AM, Andy Kurth wrote:
> This thread is to discuss whether the Apache VCL community feels that 
> this incubating project is ready to proceed with the process to 
> graduate to a top level ASF project.  There are several requirements
> which must be met and steps completed in order to graduate.   This
> discussion thread is the first step towards graduation.  Please review 
> the following pages.
> http://incubator.apache.org/guides/graduation.html
> http://incubator.apache.org/incubation/Incubation_Policy.html#Graduati
> ng+from+the+Incubator
>
> There are many items described in the ASF graduation documentation 
> which we have obviously satisfied (create a release, etc).  The 
> following are issues that I feel either need to be addressed, would be 
> concerned about regarding board/mentor approval, or have been brought 
> up before.  Please share your thoughts.  Also, please review the ASF 
> graduation documentation and bring up anything else which might be a 
> concern.
>
> Status File:
> (https://svn.apache.org/repos/asf/incubator/public/trunk/content/proje
> cts/vcl.xml) This is not up to date and is missing information.  
> Previous board reports need to be added.  News items need to be added 
> containing the string "new committer".  Doing this will cause the 
> numberCommittersNew column on the "Status of the Clutch" page to turn 
> green (http://incubator.apache.org/clutch.html).
>
> Also, the list of commiters in the status file and project page hasn't 
> changed since Apache VCL started.  The new committers obviously need 
> to be added.  I'm not sure how the original list was decided upon, but 
> I feel several names should be removed since they have not contributed 
> any code and some have not been involved in the community at all.  I 
> think the list should be Aaron Coburn, David Hutchins, Andy Kurth, 
> James O'Dell, Aaron Peeler, Josh Thompson.  Also, Brian Bouterse 
> contributed some code a while ago.  I'm not sure if he is still 
> interested in being a committer.
>
> Diversity:
> ASF requirement: "The project is not highly dependent on any single 
> contributor (there are at least 3 legally independent committers and 
> there is no single company or entity that is vital to the success of 
> the project)."
> This issue has been raised before.  I feel we meet this requirement 
> and that the community is generally diverse, can govern itself, and be 
> self-sufficient.
>
> Website:
> This is not necessarily a requirement for graduation but I feel that 
> it should be addressed prior to graduation.  Our website/documentation 
> is pretty rough and really sho

Re: [DISCUSS] Graduation

[Andy Kurth]

Hi Aaron,
Thanks for the info.  I started a "Rework the Apache VCL website?"
thread a few months ago.  I'm going to reply in that thread regarding
the technical website details in order to keep this thread focused on
graduation issues.

As for the timeline, if the graduation process continues I'm guessing
we would shoot for acceptance at the June 20 or July 18 board meeting.
 If accepted, I'm not sure how long it will take to perform the
handover tasks 
(http://incubator.apache.org/guides/graduation.html#life-after-graduation)
but I think the website should be updated by then.

-Andy

On Fri, May 4, 2012 at 12:44 PM, Aaron Coburn  wrote:
> I looked through a number of existing top-level ASF project websites, and 
> they all appear to be serving up static HTML pages. Some of them use a wiki 
> at http://wiki.apache.org/{project name}; otherwise, the sites appear to be 
> generated by some sort of script/template combination. If there is a choice, 
> I would recommend following this model: using static pages as much as 
> possible will effectively eliminate almost all security and maintenance 
> issues.
>
> Most ASF sites do not have a search feature, and those that do rely on third 
> parties (e.g. google). It would be easy enough to follow that model, though 
> if we use Sphinx, it has a built-in (javascript-based) search engine.
>
> There are a lot of template-based options for building sites, and I am 
> completely unfamiliar with most of them. Velocity is another ASF project, but 
> I have never worked with it. Several years ago I used Template::Toolkit quite 
> a bit, which is written in perl. Since so much of the VCL uses perl, this 
> might be a good option -- not that one actually needs to know perl to use it. 
> It would also be possible to use an XSLT-based engine, but I XSL syntax can 
> be very unforgiving. My current favorite is Sphinx, which relies on python to 
> generate the HTML.
>
> Aaron Coburn
>
>
>
> On May 4, 2012, at 11:51 AM, Aaron Peeler wrote:
>
>>>
>>> As for the website, I agree that some design work would be really useful. I
>>> am assuming that ASF would provide a hosting arrangement, i.e. a domain like
>>> vcl.apache.org? Would that also include server space to run any type of CMS?
>>> Confluence is a nice all-in-one package, though if you are considering a
>>> complete overhaul of the site, I could also recommend a system like Drupal
>>> (MySQL + PHP). Drupal has a lot of bells and whistles that can make for a
>>> very nice, highly interactive site. The downside of drupal is that it is not
>>> specifically designed to handle software documentation. On the other hand,
>>> if we only need to serve static html pages that focus on documentation, etc,
>>> I can also recommend Sphinx. The downside of Sphinx is that it is really
>>> best for Python and C++ projects, and it doesn't support web-based updates
>>> -- it does create excellent sites, though.
>>
>> I  believe we can run anything we like. ASF does provide the hosting
>> and the top-level projects do have their own url
>> .apache.org.
>>
>> I'm not up-to speed yet on what our options are or what the other
>> projects are using. The Apache infrastructure team is recommending
>> projects to migrate away from confluence. Has anyone else had a chance
>> to research which cms tools are available supported/recommended by
>> ASF?
>>
>>>
>>> I am also a little unclear on the timeframe for modifying the website -- it
>>> this something that would be done prior to graduation or upon graduation?
>>
>> I don't think it is a requirement, but ideally it would be nice to at
>> least have a start on a new site by graduation time.
>>
>>
>> Aaron Peeler
>

Re: [DISCUSS] Graduation

[Aaron Coburn]

I looked through a number of existing top-level ASF project websites, and they 
all appear to be serving up static HTML pages. Some of them use a wiki at 
http://wiki.apache.org/{project name}; otherwise, the sites appear to be 
generated by some sort of script/template combination. If there is a choice, I 
would recommend following this model: using static pages as much as possible 
will effectively eliminate almost all security and maintenance issues.

Most ASF sites do not have a search feature, and those that do rely on third 
parties (e.g. google). It would be easy enough to follow that model, though if 
we use Sphinx, it has a built-in (javascript-based) search engine.

There are a lot of template-based options for building sites, and I am 
completely unfamiliar with most of them. Velocity is another ASF project, but I 
have never worked with it. Several years ago I used Template::Toolkit quite a 
bit, which is written in perl. Since so much of the VCL uses perl, this might 
be a good option -- not that one actually needs to know perl to use it. It 
would also be possible to use an XSLT-based engine, but I XSL syntax can be 
very unforgiving. My current favorite is Sphinx, which relies on python to 
generate the HTML. 

Aaron Coburn



On May 4, 2012, at 11:51 AM, Aaron Peeler wrote:

>> 
>> As for the website, I agree that some design work would be really useful. I
>> am assuming that ASF would provide a hosting arrangement, i.e. a domain like
>> vcl.apache.org? Would that also include server space to run any type of CMS?
>> Confluence is a nice all-in-one package, though if you are considering a
>> complete overhaul of the site, I could also recommend a system like Drupal
>> (MySQL + PHP). Drupal has a lot of bells and whistles that can make for a
>> very nice, highly interactive site. The downside of drupal is that it is not
>> specifically designed to handle software documentation. On the other hand,
>> if we only need to serve static html pages that focus on documentation, etc,
>> I can also recommend Sphinx. The downside of Sphinx is that it is really
>> best for Python and C++ projects, and it doesn't support web-based updates
>> -- it does create excellent sites, though.
> 
> I  believe we can run anything we like. ASF does provide the hosting
> and the top-level projects do have their own url
> .apache.org.
> 
> I'm not up-to speed yet on what our options are or what the other
> projects are using. The Apache infrastructure team is recommending
> projects to migrate away from confluence. Has anyone else had a chance
> to research which cms tools are available supported/recommended by
> ASF?
> 
>> 
>> I am also a little unclear on the timeframe for modifying the website -- it
>> this something that would be done prior to graduation or upon graduation?
> 
> I don't think it is a requirement, but ideally it would be nice to at
> least have a start on a new site by graduation time.
> 
> 
> Aaron Peeler

Re: [DISCUSS] Graduation

[James O'Dell]

Hi,

I support graduation. The project has a good group of supporters, and
has demonstrated continued growth over time. It's a stable project,
and should graduate.

In the future, I hope it becomes easier to install and maintain
(i.e. yum package management). I've been looking into what it would
take to post it to EPEL. After graduation, this seems like a
natural progression.

Also, after meeting with representatives from other campuses, I found that
they really had a problem configuring VCL the first time (Most of the
off campus
calls I receive about VCL were asking for help configuring VCL. In
particular,
what equipment to use, how to setup DHCP, how to configure Shibboleth,
how to make it work under windows - as for the last one, please don't!).
If there had been some examples of actual equipment configurations, and
some screen
shots of configuration pages, it would have been nice.

IMHO, it think it would be helpful to setup a demo system on the VCL
website.
Just to help people who haven't had any exposure to VCL get an idea
what to expect. From what I've experienced, people want to compare it to
things like Citrix, but give up because they have trouble setting up a
test bed.

Just my 2 cents worth,

__Jim O'Dell

On 5/1/2012 9:44 AM, Andy Kurth wrote:
> This thread is to discuss whether the Apache VCL community feels that
> this incubating project is ready to proceed with the process to
> graduate to a top level ASF project.  There are several requirements
> which must be met and steps completed in order to graduate.   This
> discussion thread is the first step towards graduation.  Please review
> the following pages.
> http://incubator.apache.org/guides/graduation.html
> http://incubator.apache.org/incubation/Incubation_Policy.html#Graduating+from+the+Incubator
>
> There are many items described in the ASF graduation documentation
> which we have obviously satisfied (create a release, etc).  The
> following are issues that I feel either need to be addressed, would be
> concerned about regarding board/mentor approval, or have been brought
> up before.  Please share your thoughts.  Also, please review the ASF
> graduation documentation and bring up anything else which might be a
> concern.
>
> Status File:
> (https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/vcl.xml)
> This is not up to date and is missing information.  Previous board
> reports need to be added.  News items need to be added containing the
> string "new committer".  Doing this will cause the numberCommittersNew
> column on the "Status of the Clutch" page to turn green
> (http://incubator.apache.org/clutch.html).
>
> Also, the list of commiters in the status file and project page hasn't
> changed since Apache VCL started.  The new committers obviously need
> to be added.  I'm not sure how the original list was decided upon, but
> I feel several names should be removed since they have not contributed
> any code and some have not been involved in the community at all.  I
> think the list should be Aaron Coburn, David Hutchins, Andy Kurth,
> James O'Dell, Aaron Peeler, Josh Thompson.  Also, Brian Bouterse
> contributed some code a while ago.  I'm not sure if he is still
> interested in being a committer.
>
> Diversity:
> ASF requirement: "The project is not highly dependent on any single
> contributor (there are at least 3 legally independent committers and
> there is no single company or entity that is vital to the success of
> the project)."
> This issue has been raised before.  I feel we meet this requirement
> and that the community is generally diverse, can govern itself, and be
> self-sufficient.
>
> Website:
> This is not necessarily a requirement for graduation but I feel that
> it should be addressed prior to graduation.  Our website/documentation
> is pretty rough and really should be redesigned.  I'm guessing the
> board members will look at it prior to voting.  In addition, there
> will likely be a press release if/when we graduate and website views
> will spike.  This shouldn't hold up the graduation process, but I
> would like agreement that this should be completed by graduation.
>
> Thank You,
> Andy


-- 
Jim O'Dell
Network Analyst
California State University Fullerton
Email: jod...@fullerton.edu
Phone: (657) 278-2256

Re: [DISCUSS] Graduation

[Aaron Peeler]

>
> As for the website, I agree that some design work would be really useful. I
> am assuming that ASF would provide a hosting arrangement, i.e. a domain like
> vcl.apache.org? Would that also include server space to run any type of CMS?
> Confluence is a nice all-in-one package, though if you are considering a
> complete overhaul of the site, I could also recommend a system like Drupal
> (MySQL + PHP). Drupal has a lot of bells and whistles that can make for a
> very nice, highly interactive site. The downside of drupal is that it is not
> specifically designed to handle software documentation. On the other hand,
> if we only need to serve static html pages that focus on documentation, etc,
> I can also recommend Sphinx. The downside of Sphinx is that it is really
> best for Python and C++ projects, and it doesn't support web-based updates
> -- it does create excellent sites, though.

I  believe we can run anything we like. ASF does provide the hosting
and the top-level projects do have their own url
.apache.org.

I'm not up-to speed yet on what our options are or what the other
projects are using. The Apache infrastructure team is recommending
projects to migrate away from confluence. Has anyone else had a chance
to research which cms tools are available supported/recommended by
ASF?

>
> I am also a little unclear on the timeframe for modifying the website -- it
> this something that would be done prior to graduation or upon graduation?

I don't think it is a requirement, but ideally it would be nice to at
least have a start on a new site by graduation time.


Aaron Peeler

RE: [DISCUSS] Graduation

[Arthur Vandenberg]

I concur that VCL graduation is warranted. GSU has been running VCL for nearly 
two years.  The VCL community has been helpful to Georgia State in getting our 
VCL instance going and supported.

The related VCL discussions as well as the VCL Virtual Office Hours indicate, 
in my opinion, a strong and diverse community implementing, using and 
supporting VCL.

Graduation to next level is my vote.

Art


Art Vandenberg
Account Manager/Research Function
Customer Relations, IS&T
Information Systems & Technology
Georgia State University
avandenb...@gsu.edu
+1 404 413 4743
MS Information & Computer Science, Georgia Tech
MVA Painting & Drawing, Georgia State
Web page: http://www.gsu.edu/ist/acs/25735.html


From: Aaron Coburn [acob...@amherst.edu]
Sent: Friday, May 04, 2012 10:46 AM
To: ; 
Cc: 
Subject: Re: [DISCUSS] Graduation

We began working with the VCL software about two years ago at Amherst College, 
and in that time, the community has grown well beyond its NCSU roots. I am 
seeing significantly more activity on the lists as well as more JIRA issues and 
contributed code from the wider community. I would also support a vote for 
graduation.

As for the website, I agree that some design work would be really useful. I am 
assuming that ASF would provide a hosting arrangement, i.e. a domain like 
vcl.apache.org<http://vcl.apache.org>? Would that also include server space to 
run any type of CMS? Confluence is a nice all-in-one package, though if you are 
considering a complete overhaul of the site, I could also recommend a system 
like Drupal (MySQL + PHP). Drupal has a lot of bells and whistles that can make 
for a very nice, highly interactive site. The downside of drupal is that it is 
not specifically designed to handle software documentation. On the other hand, 
if we only need to serve static html pages that focus on documentation, etc, I 
can also recommend Sphinx. The downside of Sphinx is that it is really best for 
Python and C++ projects, and it doesn't support web-based updates -- it does 
create excellent sites, though.

I am also a little unclear on the timeframe for modifying the website -- it 
this something that would be done prior to graduation or upon graduation?

Aaron Coburn



--
Aaron Coburn
Systems Administrator and Programmer
Academic Technology Services, Amherst College
acob...@amherst.edu<mailto:acob...@amherst.edu>






On May 2, 2012, at 9:14 AM, Aaron Peeler wrote:

I feel we have meet our diversity issue and also expect to add more
committers over the next couple of months. I would positively support
a vote for graduation.


I agree on the other points mentioned.

Status page needs to be updated. We can work on this part easily.

The web site needs to be migrated off confluence. Has anyone
researched other CMS options for the website. I think this would be a
good community discussion thread. Which CMS, the layout, (content,
documentation, design ideas, etc.)

Aaron


On Tue, May 1, 2012 at 12:44 PM, Andy Kurth 
mailto:andy_ku...@ncsu.edu>> wrote:
This thread is to discuss whether the Apache VCL community feels that
this incubating project is ready to proceed with the process to
graduate to a top level ASF project.  There are several requirements
which must be met and steps completed in order to graduate.   This
discussion thread is the first step towards graduation.  Please review
the following pages.
http://incubator.apache.org/guides/graduation.html
http://incubator.apache.org/incubation/Incubation_Policy.html#Graduating+from+the+Incubator

There are many items described in the ASF graduation documentation
which we have obviously satisfied (create a release, etc).  The
following are issues that I feel either need to be addressed, would be
concerned about regarding board/mentor approval, or have been brought
up before.  Please share your thoughts.  Also, please review the ASF
graduation documentation and bring up anything else which might be a
concern.

Status File:
(https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/vcl.xml)
This is not up to date and is missing information.  Previous board
reports need to be added.  News items need to be added containing the
string "new committer".  Doing this will cause the numberCommittersNew
column on the "Status of the Clutch" page to turn green
(http://incubator.apache.org/clutch.html).

Also, the list of commiters in the status file and project page hasn't
changed since Apache VCL started.  The new committers obviously need
to be added.  I'm not sure how the original list was decided upon, but
I feel several names should be removed since they have not contributed
any code and some have not been involved in the community at all.  I
think the list should be Aaron Coburn, David Hutchins, Andy Kurth,
James O'Dell, Aaron Peeler, Josh Thompson.  Also, Brian Bouterse
contributed some code a while ago.  I&

Re: [DISCUSS] Graduation

[Aaron Coburn]

We began working with the VCL software about two years ago at Amherst College, 
and in that time, the community has grown well beyond its NCSU roots. I am 
seeing significantly more activity on the lists as well as more JIRA issues and 
contributed code from the wider community. I would also support a vote for 
graduation.

As for the website, I agree that some design work would be really useful. I am 
assuming that ASF would provide a hosting arrangement, i.e. a domain like 
vcl.apache.org? Would that also include server space to 
run any type of CMS? Confluence is a nice all-in-one package, though if you are 
considering a complete overhaul of the site, I could also recommend a system 
like Drupal (MySQL + PHP). Drupal has a lot of bells and whistles that can make 
for a very nice, highly interactive site. The downside of drupal is that it is 
not specifically designed to handle software documentation. On the other hand, 
if we only need to serve static html pages that focus on documentation, etc, I 
can also recommend Sphinx. The downside of Sphinx is that it is really best for 
Python and C++ projects, and it doesn't support web-based updates -- it does 
create excellent sites, though.

I am also a little unclear on the timeframe for modifying the website -- it 
this something that would be done prior to graduation or upon graduation?

Aaron Coburn



--
Aaron Coburn
Systems Administrator and Programmer
Academic Technology Services, Amherst College
acob...@amherst.edu






On May 2, 2012, at 9:14 AM, Aaron Peeler wrote:

I feel we have meet our diversity issue and also expect to add more
committers over the next couple of months. I would positively support
a vote for graduation.


I agree on the other points mentioned.

Status page needs to be updated. We can work on this part easily.

The web site needs to be migrated off confluence. Has anyone
researched other CMS options for the website. I think this would be a
good community discussion thread. Which CMS, the layout, (content,
documentation, design ideas, etc.)

Aaron


On Tue, May 1, 2012 at 12:44 PM, Andy Kurth 
mailto:andy_ku...@ncsu.edu>> wrote:
This thread is to discuss whether the Apache VCL community feels that
this incubating project is ready to proceed with the process to
graduate to a top level ASF project.  There are several requirements
which must be met and steps completed in order to graduate.   This
discussion thread is the first step towards graduation.  Please review
the following pages.
http://incubator.apache.org/guides/graduation.html
http://incubator.apache.org/incubation/Incubation_Policy.html#Graduating+from+the+Incubator

There are many items described in the ASF graduation documentation
which we have obviously satisfied (create a release, etc).  The
following are issues that I feel either need to be addressed, would be
concerned about regarding board/mentor approval, or have been brought
up before.  Please share your thoughts.  Also, please review the ASF
graduation documentation and bring up anything else which might be a
concern.

Status File:
(https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/vcl.xml)
This is not up to date and is missing information.  Previous board
reports need to be added.  News items need to be added containing the
string "new committer".  Doing this will cause the numberCommittersNew
column on the "Status of the Clutch" page to turn green
(http://incubator.apache.org/clutch.html).

Also, the list of commiters in the status file and project page hasn't
changed since Apache VCL started.  The new committers obviously need
to be added.  I'm not sure how the original list was decided upon, but
I feel several names should be removed since they have not contributed
any code and some have not been involved in the community at all.  I
think the list should be Aaron Coburn, David Hutchins, Andy Kurth,
James O'Dell, Aaron Peeler, Josh Thompson.  Also, Brian Bouterse
contributed some code a while ago.  I'm not sure if he is still
interested in being a committer.

Diversity:
ASF requirement: "The project is not highly dependent on any single
contributor (there are at least 3 legally independent committers and
there is no single company or entity that is vital to the success of
the project)."
This issue has been raised before.  I feel we meet this requirement
and that the community is generally diverse, can govern itself, and be
self-sufficient.

Website:
This is not necessarily a requirement for graduation but I feel that
it should be addressed prior to graduation.  Our website/documentation
is pretty rough and really should be redesigned.  I'm guessing the
board members will look at it prior to voting.  In addition, there
will likely be a press release if/when we graduate and website views
will spike.  This shouldn't hold up the graduation process, but I
would like agreement that this should be completed by graduation.

Thank You,
Andy

RE: [DISCUSS] Graduation

[Waldron, Michael H]

I also support graduation. There has been consistent active development work 
and a good roadmap for future releases. There is an active community of users 
that have exchanged a lot of good ideas and provided assistance to the 
community in resolving problems associated with VCL.

It's a solid project and stable application which is getting increasing use at 
our institution and I foresee it continuing to grow in the future.

Mike Waldron
Systems Specialist
ITS Research Computing
University of North Carolina at Chapel Hill


From: Aaron Peeler [aaron_pee...@ncsu.edu]
Sent: Wednesday, May 02, 2012 9:14 AM
To: vcl-user@incubator.apache.org; vcl-...@incubator.apache.org
Subject: Re: [DISCUSS] Graduation

I feel we have meet our diversity issue and also expect to add more
committers over the next couple of months. I would positively support
a vote for graduation.


I agree on the other points mentioned.

Status page needs to be updated. We can work on this part easily.

The web site needs to be migrated off confluence. Has anyone
researched other CMS options for the website. I think this would be a
good community discussion thread. Which CMS, the layout, (content,
documentation, design ideas, etc.)

Aaron


On Tue, May 1, 2012 at 12:44 PM, Andy Kurth  wrote:
> This thread is to discuss whether the Apache VCL community feels that
> this incubating project is ready to proceed with the process to
> graduate to a top level ASF project.  There are several requirements
> which must be met and steps completed in order to graduate.   This
> discussion thread is the first step towards graduation.  Please review
> the following pages.
> http://incubator.apache.org/guides/graduation.html
> http://incubator.apache.org/incubation/Incubation_Policy.html#Graduating+from+the+Incubator
>
> There are many items described in the ASF graduation documentation
> which we have obviously satisfied (create a release, etc).  The
> following are issues that I feel either need to be addressed, would be
> concerned about regarding board/mentor approval, or have been brought
> up before.  Please share your thoughts.  Also, please review the ASF
> graduation documentation and bring up anything else which might be a
> concern.
>
> Status File:
> (https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/vcl.xml)
> This is not up to date and is missing information.  Previous board
> reports need to be added.  News items need to be added containing the
> string "new committer".  Doing this will cause the numberCommittersNew
> column on the "Status of the Clutch" page to turn green
> (http://incubator.apache.org/clutch.html).
>
> Also, the list of commiters in the status file and project page hasn't
> changed since Apache VCL started.  The new committers obviously need
> to be added.  I'm not sure how the original list was decided upon, but
> I feel several names should be removed since they have not contributed
> any code and some have not been involved in the community at all.  I
> think the list should be Aaron Coburn, David Hutchins, Andy Kurth,
> James O'Dell, Aaron Peeler, Josh Thompson.  Also, Brian Bouterse
> contributed some code a while ago.  I'm not sure if he is still
> interested in being a committer.
>
> Diversity:
> ASF requirement: "The project is not highly dependent on any single
> contributor (there are at least 3 legally independent committers and
> there is no single company or entity that is vital to the success of
> the project)."
> This issue has been raised before.  I feel we meet this requirement
> and that the community is generally diverse, can govern itself, and be
> self-sufficient.
>
> Website:
> This is not necessarily a requirement for graduation but I feel that
> it should be addressed prior to graduation.  Our website/documentation
> is pretty rough and really should be redesigned.  I'm guessing the
> board members will look at it prior to voting.  In addition, there
> will likely be a press release if/when we graduate and website views
> will spike.  This shouldn't hold up the graduation process, but I
> would like agreement that this should be completed by graduation.
>
> Thank You,
> Andy



--
Aaron Peeler
Program Manager
Virtual Computing Lab
NC State University

All electronic mail messages in connection with State business which
are sent to or received by this account are subject to the NC Public
Records Law and may be disclosed to third parties.

Re: [DISCUSS] Graduation

[Aaron Peeler]

I feel we have meet our diversity issue and also expect to add more
committers over the next couple of months. I would positively support
a vote for graduation.


I agree on the other points mentioned.

Status page needs to be updated. We can work on this part easily.

The web site needs to be migrated off confluence. Has anyone
researched other CMS options for the website. I think this would be a
good community discussion thread. Which CMS, the layout, (content,
documentation, design ideas, etc.)

Aaron


On Tue, May 1, 2012 at 12:44 PM, Andy Kurth  wrote:
> This thread is to discuss whether the Apache VCL community feels that
> this incubating project is ready to proceed with the process to
> graduate to a top level ASF project.  There are several requirements
> which must be met and steps completed in order to graduate.   This
> discussion thread is the first step towards graduation.  Please review
> the following pages.
> http://incubator.apache.org/guides/graduation.html
> http://incubator.apache.org/incubation/Incubation_Policy.html#Graduating+from+the+Incubator
>
> There are many items described in the ASF graduation documentation
> which we have obviously satisfied (create a release, etc).  The
> following are issues that I feel either need to be addressed, would be
> concerned about regarding board/mentor approval, or have been brought
> up before.  Please share your thoughts.  Also, please review the ASF
> graduation documentation and bring up anything else which might be a
> concern.
>
> Status File:
> (https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/vcl.xml)
> This is not up to date and is missing information.  Previous board
> reports need to be added.  News items need to be added containing the
> string "new committer".  Doing this will cause the numberCommittersNew
> column on the "Status of the Clutch" page to turn green
> (http://incubator.apache.org/clutch.html).
>
> Also, the list of commiters in the status file and project page hasn't
> changed since Apache VCL started.  The new committers obviously need
> to be added.  I'm not sure how the original list was decided upon, but
> I feel several names should be removed since they have not contributed
> any code and some have not been involved in the community at all.  I
> think the list should be Aaron Coburn, David Hutchins, Andy Kurth,
> James O'Dell, Aaron Peeler, Josh Thompson.  Also, Brian Bouterse
> contributed some code a while ago.  I'm not sure if he is still
> interested in being a committer.
>
> Diversity:
> ASF requirement: "The project is not highly dependent on any single
> contributor (there are at least 3 legally independent committers and
> there is no single company or entity that is vital to the success of
> the project)."
> This issue has been raised before.  I feel we meet this requirement
> and that the community is generally diverse, can govern itself, and be
> self-sufficient.
>
> Website:
> This is not necessarily a requirement for graduation but I feel that
> it should be addressed prior to graduation.  Our website/documentation
> is pretty rough and really should be redesigned.  I'm guessing the
> board members will look at it prior to voting.  In addition, there
> will likely be a press release if/when we graduate and website views
> will spike.  This shouldn't hold up the graduation process, but I
> would like agreement that this should be completed by graduation.
>
> Thank You,
> Andy



-- 
Aaron Peeler
Program Manager
Virtual Computing Lab
NC State University

All electronic mail messages in connection with State business which
are sent to or received by this account are subject to the NC Public
Records Law and may be disclosed to third parties.

Re: [DISCUSS] Graduation

[Kevan Miller]

On May 1, 2012, at 12:44 PM, Andy Kurth wrote:

> Status File:
> (https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/vcl.xml)
> This is not up to date and is missing information.  Previous board
> reports need to be added.  News items need to be added containing the
> string "new committer".  Doing this will cause the numberCommittersNew
> column on the "Status of the Clutch" page to turn green
> (http://incubator.apache.org/clutch.html).
> 
> Also, the list of commiters in the status file and project page hasn't
> changed since Apache VCL started.  The new committers obviously need
> to be added.  I'm not sure how the original list was decided upon, but
> I feel several names should be removed since they have not contributed
> any code and some have not been involved in the community at all.  I
> think the list should be Aaron Coburn, David Hutchins, Andy Kurth,
> James O'Dell, Aaron Peeler, Josh Thompson.  Also, Brian Bouterse
> contributed some code a while ago.  I'm not sure if he is still
> interested in being a committer.

Going to be a busy week for me. I can start looking at these over the 
weekend/next week. Cool if another mentor could have a look…

--kevan