Re: [DISCUSS] Graduation - Prepare Board Resolution

2012-05-18 Thread 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 andy_ku...@ncsu.edu 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 - Prepare Board Resolution

2012-05-18 Thread 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

2012-05-18 Thread Kevan Miller
Oops. Moving to vcl-dev rather than vcl-user.

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?

Im 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

2012-05-09 Thread Kevan Miller

On May 9, 2012, at 12:46 AM, Alan D. Cabrera wrote:

 
 On May 1, 2012, at 9:44 AM, 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 can update this tomorrow.

I think I got this, already. But if I missed anything/made any mistakes, please 
let Alan know… ;-)

--kevan

Re: [DISCUSS] Graduation

2012-05-08 Thread Josh Thompson
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I meant to send this earlier and then got bogged down working on the release.

I definitely think we should start the process of graduating.  I really feel 
like we have enough of a community now that if NCSU were to pull out of the 
project (very unlikely to happen), VCL would continue to survive.

The web site definitely needs work either before graduating or very soon 
after.  I have some ideas about how to organize things based on what type of 
information a person may be looking for when visiting the site.  I'll try to 
get that framework put in place now that Andy has created the stub files for 
using the new CMS system.

As soon as we get a release candidate cut, I'll have more time to work on 
things like the status page and the web site.

Josh

On Wednesday, May 02, 2012 9:14:25 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 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/project
  s/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
- -- 
- ---
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+pJnkACgkQV/LQcNdtPQPgRACfb1JU4fGKWAr5xs2xmVrSZiMc
OlAAnA5LzE3Ng1W8t7XveW6wnefyiZ6m
=ICsu
-END PGP SIGNATURE-



RE: [DISCUSS] Graduation

2012-05-04 Thread 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-u...@incubator.apache.org; vcl-dev@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 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



--
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

2012-05-04 Thread Sanders, Arbin D
I would like to also approve the graduation of VCL.

Sent from my Motorola Smartphone on the Now Network from Sprint!


-Original message-
From: Waldron, Michael H mwald...@email.unc.edu
To: vcl-dev@incubator.apache.org vcl-dev@incubator.apache.org, 
vcl-u...@incubator.apache.org vcl-u...@incubator.apache.org
Sent: Fri, May 4, 2012 10:17:59 EDT
Subject: RE: [DISCUSS] Graduation

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-u...@incubator.apache.org; vcl-dev@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 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



--
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.

__
This email has been scanned by the Symantec Email Security.cloud service.
For more

Re: [DISCUSS] Graduation

2012-05-04 Thread 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.orghttp://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.edumailto: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 
andy_ku...@ncsu.edumailto: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,

RE: [DISCUSS] Graduation

2012-05-04 Thread 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, IST
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: vcl-dev@incubator.apache.org; aaron_pee...@ncsu.edu
Cc: vcl-u...@incubator.apache.org
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.orghttp://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.edumailto: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 
andy_ku...@ncsu.edumailto: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

Re: [DISCUSS] Graduation

2012-05-04 Thread 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
projectname.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

2012-05-04 Thread 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
 projectname.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

2012-05-02 Thread 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 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



-- 
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.


[DISCUSS] Graduation

2012-05-01 Thread Andy Kurth
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 ? next steps

2012-02-02 Thread Aaron Peeler
Hi Mike,

This is great. Thank you, thank you, thank you

So the next steps (I think) are for you to file your ICLA.

Then we can discuss how we want the documentation and website to go.

Confluence is our current wiki, but that is fading. So we may want to
take this time to request a new CMS and start migrating. When we
graduate, we'll need to migrate anyway so might as well start thinking
about it now.

Aaron


On Wed, Feb 1, 2012 at 3:56 PM, Mike Haudenschild m...@longsight.com wrote:
 I'm all about good karma.  I owe the VCL guys.  Besides, I'm one of the
 sick ones that actually ENJOY writing documentation.  Don't judge me!

 --
 *Mike Haudenschild*
 Education Systems Manager
 Longsight Group
 (740) 599-5005 x809
 m...@longsight.com
 www.longsight.com



 On Wed, Feb 1, 2012 at 14:30, Kevan Miller kevan.mil...@gmail.com wrote:


 On Feb 1, 2012, at 9:36 AM, Mike Haudenschild wrote:

  Hi, Aaron et al. --
 
  I'm heavily invested in VCL for two large production projects.  I'm not a
  developer, but I have extensive experience writing documentation and
 would
  be happy to help in that regard.
 
  Most of my recent technical writing is proprietary, but a couple years
 ago
  I wrote a Moodle install doc that you could review here:
 
  http://mhauden.com/moodle

 Cool! Your contributions would be most welcome. I multiple Apache projects
 with committers who have earned their commit karma via documentation
 contributions (not code).

 --kevan



-- 
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 ? next steps

2012-02-02 Thread Mike Haudenschild
Hi Aaron,

No problem, I'm looking forward to this work!  I submitted my contributor
agreement this morning to Apache and asked that they notify you.

If you're getting close to a 2.3 release, this will be a great time to
start developing and revising docs.  We should probably set up a time to
talk offline...?

Regards,
Mike

--
*Mike Haudenschild*
Education Systems Manager
Longsight Group
(740) 599-5005 x809
m...@longsight.com
www.longsight.com



On Thu, Feb 2, 2012 at 10:40, Aaron Peeler aaron_pee...@ncsu.edu wrote:

 Hi Mike,

 This is great. Thank you, thank you, thank you

 So the next steps (I think) are for you to file your ICLA.

 Then we can discuss how we want the documentation and website to go.

 Confluence is our current wiki, but that is fading. So we may want to
 take this time to request a new CMS and start migrating. When we
 graduate, we'll need to migrate anyway so might as well start thinking
 about it now.

 Aaron


 On Wed, Feb 1, 2012 at 3:56 PM, Mike Haudenschild m...@longsight.com
 wrote:
  I'm all about good karma.  I owe the VCL guys.  Besides, I'm one of the
  sick ones that actually ENJOY writing documentation.  Don't judge me!
 
  --
  *Mike Haudenschild*
  Education Systems Manager
  Longsight Group
  (740) 599-5005 x809
  m...@longsight.com
  www.longsight.com
 
 
 
  On Wed, Feb 1, 2012 at 14:30, Kevan Miller kevan.mil...@gmail.com
 wrote:
 
 
  On Feb 1, 2012, at 9:36 AM, Mike Haudenschild wrote:
 
   Hi, Aaron et al. --
  
   I'm heavily invested in VCL for two large production projects.  I'm
 not a
   developer, but I have extensive experience writing documentation and
  would
   be happy to help in that regard.
  
   Most of my recent technical writing is proprietary, but a couple years
  ago
   I wrote a Moodle install doc that you could review here:
  
   http://mhauden.com/moodle
 
  Cool! Your contributions would be most welcome. I multiple Apache
 projects
  with committers who have earned their commit karma via documentation
  contributions (not code).
 
  --kevan



 --
 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 ? next steps

2012-02-01 Thread Mike Haudenschild
Hi, Aaron et al. --

I'm heavily invested in VCL for two large production projects.  I'm not a
developer, but I have extensive experience writing documentation and would
be happy to help in that regard.

Most of my recent technical writing is proprietary, but a couple years ago
I wrote a Moodle install doc that you could review here:

http://mhauden.com/moodle

Regards,
Mike
--
*Mike Haudenschild*
Education Systems Manager
Longsight Group
(740) 599-5005 x809
m...@longsight.com
www.longsight.com



On Mon, Jan 30, 2012 at 13:52, Aaron Peeler aaron_pee...@ncsu.edu wrote:

 Hi Folks,

 We are getting close to being able to ask for graduation. Based on the
 checklist:
 http://incubator.apache.org/guides/graduation.html#checklist

 We've meet many of the goals:
 - the community is growing
 - cut official releases, soon to be another one
 - good communication on user/dev mailing lists and irc channel.
 - more diversity in committers, hopefully over next month or so we can
 bring one or two more.

 Our current active committers are:
 Andy kurth - NCSU
 Josh Thompson - NCSU
 David Hutchins -  Not-NCSU
 Aaron Coburn - Not-NCSU
 myself(Aaron Peeler) - NCSU

 Part of our challenge in not graduating yet has been the diversity
 among our committers. It is/was heavily weighted with NCSU only
 committers. In order to move quicker to graduation, it would be great
 to attract one more committer. Which means being active on the list
 and submitting code for review. Other areas to be a committer can be
 with the web site or documentation, in case you are not comfortable
 with writing code.

 Mentors, Can you advise on other areas or issues that your think we
 need to address before we apply for graduation?

 Best Regards,
 Aaron


 --
 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 ? next steps

2012-02-01 Thread Mike Haudenschild
I'm all about good karma.  I owe the VCL guys.  Besides, I'm one of the
sick ones that actually ENJOY writing documentation.  Don't judge me!

--
*Mike Haudenschild*
Education Systems Manager
Longsight Group
(740) 599-5005 x809
m...@longsight.com
www.longsight.com



On Wed, Feb 1, 2012 at 14:30, Kevan Miller kevan.mil...@gmail.com wrote:


 On Feb 1, 2012, at 9:36 AM, Mike Haudenschild wrote:

  Hi, Aaron et al. --
 
  I'm heavily invested in VCL for two large production projects.  I'm not a
  developer, but I have extensive experience writing documentation and
 would
  be happy to help in that regard.
 
  Most of my recent technical writing is proprietary, but a couple years
 ago
  I wrote a Moodle install doc that you could review here:
 
  http://mhauden.com/moodle

 Cool! Your contributions would be most welcome. I multiple Apache projects
 with committers who have earned their commit karma via documentation
 contributions (not code).

 --kevan


[Discuss] Graduation ? next steps

2012-01-30 Thread Aaron Peeler
Hi Folks,

We are getting close to being able to ask for graduation. Based on the
checklist:
http://incubator.apache.org/guides/graduation.html#checklist

We've meet many of the goals:
- the community is growing
- cut official releases, soon to be another one
- good communication on user/dev mailing lists and irc channel.
- more diversity in committers, hopefully over next month or so we can
bring one or two more.

Our current active committers are:
Andy kurth - NCSU
Josh Thompson - NCSU
David Hutchins -  Not-NCSU
Aaron Coburn - Not-NCSU
myself(Aaron Peeler) - NCSU

Part of our challenge in not graduating yet has been the diversity
among our committers. It is/was heavily weighted with NCSU only
committers. In order to move quicker to graduation, it would be great
to attract one more committer. Which means being active on the list
and submitting code for review. Other areas to be a committer can be
with the web site or documentation, in case you are not comfortable
with writing code.

Mentors, Can you advise on other areas or issues that your think we
need to address before we apply for graduation?

Best Regards,
Aaron


-- 
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 ? next steps

2012-01-30 Thread Kevan Miller

On Jan 30, 2012, at 1:52 PM, Aaron Peeler wrote:

 Hi Folks,
 
 We are getting close to being able to ask for graduation. Based on the
 checklist:
 http://incubator.apache.org/guides/graduation.html#checklist
 
 We've meet many of the goals:
 - the community is growing
 - cut official releases, soon to be another one
 - good communication on user/dev mailing lists and irc channel.
 - more diversity in committers, hopefully over next month or so we can
 bring one or two more.
 
 Our current active committers are:
 Andy kurth - NCSU
 Josh Thompson - NCSU
 David Hutchins -  Not-NCSU
 Aaron Coburn - Not-NCSU
 myself(Aaron Peeler) - NCSU
 
 Part of our challenge in not graduating yet has been the diversity
 among our committers. It is/was heavily weighted with NCSU only
 committers. In order to move quicker to graduation, it would be great
 to attract one more committer. Which means being active on the list
 and submitting code for review. Other areas to be a committer can be
 with the web site or documentation, in case you are not comfortable
 with writing code.
 
 Mentors, Can you advise on other areas or issues that your think we
 need to address before we apply for graduation?

Diversity is the only sticking point that I have. 

I've been happy with the increased communication (one minor point -- try not to 
substitute Jira posts with mailing list communication) and overall progress of 
the community. I'd recommend that you continue to encourage and mentor new 
contributors. So that they can become committers on the project.

--kevan



Re: [Discuss] Graduation ? next steps

2012-01-30 Thread Alan D. Cabrera

On Jan 30, 2012, at 10:52 AM, Aaron Peeler wrote:

 Hi Folks,
 
 We are getting close to being able to ask for graduation. Based on the
 checklist:
 http://incubator.apache.org/guides/graduation.html#checklist
 
 We've meet many of the goals:
 - the community is growing
 - cut official releases, soon to be another one
 - good communication on user/dev mailing lists and irc channel.
 - more diversity in committers, hopefully over next month or so we can
 bring one or two more.
 
 Our current active committers are:
 Andy kurth - NCSU
 Josh Thompson - NCSU
 David Hutchins -  Not-NCSU
 Aaron Coburn - Not-NCSU
 myself(Aaron Peeler) - NCSU
 
 Part of our challenge in not graduating yet has been the diversity
 among our committers. It is/was heavily weighted with NCSU only
 committers. In order to move quicker to graduation, it would be great
 to attract one more committer. Which means being active on the list
 and submitting code for review. Other areas to be a committer can be
 with the web site or documentation, in case you are not comfortable
 with writing code.
 
 Mentors, Can you advise on other areas or issues that your think we
 need to address before we apply for graduation?

I think this is a great podling.  Diversity is the only sticking point that I 
have.  

Are their any lurkers out there who would be willing to step up?  :)

Sometimes writing or re-writing a sub-system is enough to attract fresh blood.  
What kinds of things would people like to see added to VCL?


Regards,
Alan