Re: Wiki contributions from individuals who have not signed the CLA

2009-11-12 Thread Alan D. Cabrera

Website generation occurs in two phases.

1) auto-export exports on changes to pages
2) a committers personal cron job copies the exported files to the  
proper place for the web server to pick them up


To set this up we need someone to work out a template.  I recommend  
that you peruse the existing websites and start w/ one that is close  
to how you want it to look.  I'll get their template and you can then  
fiddle with it.


I can send the cron tab entry for who ever volunteers to host the  
export copy.



Regards,
Alan

On Nov 12, 2009, at 7:10 AM, Josh Thompson wrote:


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Thanks for setting it up with a different name.

We'd like to use the auto export from the CLA-only wiki for the  
project's
site.  I think it would be a good idea to use the templating feature  
of the

auto export.  How do we go about setting that up?

Thanks,
Josh

On Thursday November 12, 2009, Alan D. Cabrera wrote:

Created.

BTW, what's going to be done for the project's site.  Some projects
create the pages themselves others auto-export a space from the
Confluence wiki.  The auto export allows for templating of the wiki
content.


Regards,
Alan

On Nov 11, 2009, at 10:07 AM, Josh Thompson wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Sorry to have not said this before you created it, but would it be
easy to
rename VCLPUB to something like VCLDOCS and use it as the CLA only
space?
We've already had non-CLA people create content in the existing
space; so,
we're thinking it would be easier to restrict who adds stuff to a
new space
instead of cleaning stuff out of the existing space.

Thanks,
Josh

On Tuesday November 10, 2009, Alan D. Cabrera wrote:

Ok, I get it.  Let me create VCLPUB.


Regards,
Alan

On Nov 10, 2009, at 1:02 PM, Josh Thompson wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Alan,

- From what I can tell, anyone can go to the confluence site,  
create

an account,
and start adding/modifying content.  This makes sense, because  
it is

desirable for people to be able to easily join the community and
help with
documentation.  However, from what I understand about ASF policy,
any
documentation that is distributed with a release artifact can only
be
contributed by people who have signed a CLA.  So, what we've been
asking for
is to have a separate space that is limited such that only people
who have
signed a CLA have access to contribute content.  Then, that  
content

would be
exported and bundled with releases as official documentation.

For more information see the section titled Can we use the
autoexport site as
part of our main web site? at http://cwiki.apache.org/CWIKI/

Josh

On Tuesday November 10, 2009, Alan D. Cabrera wrote:

As noted in the May 2009 report -- questions were asked of the
mentors
regarding the rules governing wiki contributions from individuals
who
have not signed the CLA. It is the community's understanding  
that a

separate wiki will be needed -- one for official documentation
included with releases and one containing contributions from
individual who have not signed the CLA.  A request has been  
made to

one of the mentors who had offered to create a 2nd wiki instance.
This has not been completed yet.

I've never heard of ASF hosting Wiki's where no CLA has been
signed.
Does anyone have an example of an existing ASF project that does
this?  If not, can someone point me to the VCL archive thread  
so I

can
catch up?


Regards,
Alan


- --
- ---
Josh Thompson
Systems Programmer
Advanced Computing | VCL Developer
North Carolina State University

josh_thomp...@ncsu.edu
919-515-5323

my GPG/PGP key can be found at pgp.mit.edu
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD4DBQFK+dT+V/LQcNdtPQMRAnBkAJ9DpICNDAnbbC8aUkhFbN8t5JSceACTBMrV
F879qntPWZnyrJtUnBY2UA==
=iwqY
-END PGP SIGNATURE-


- --
- ---
Josh Thompson
Systems Programmer
Advanced Computing | VCL Developer
North Carolina State University

josh_thomp...@ncsu.edu
919-515-5323

my GPG/PGP key can be found at pgp.mit.edu
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFK+v1YV/LQcNdtPQMRAjs0AJ9iKgYDoro97j252sSEdibalA9C2ACfUmmT
BGfxlr5FF8fld0rA2jntaNg=
=I1op
-END PGP SIGNATURE-

- --
- ---
Josh Thompson
Systems Programmer
Advanced Computing | VCL Developer
North Carolina State University

josh_thomp...@ncsu.edu
919-515-5323

my GPG/PGP key can be found at pgp.mit.edu
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFK/CVaV/LQcNdtPQMRAkNyAJ4q74bltiTzdsbM+GU7hKXUTD6tUQCcC8ul
fDB202uzoAmnXZiZu8oEDyU=
=k0ah
-END PGP SIGNATURE-




[VOTE] release VCL 2.1

2009-11-12 Thread Josh Thompson
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I created a release artifact based off of trunk.  I copied trunk to a tag 
under the tags area of the repo that is named release-2.1-RC2:

http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.1-RC2/

The artifact is an export from that tag.  The artifact, MD5 and SHA1 sums, and 
my GPG signature of it are available from my space on people.a.o:

http://people.apache.org/~jfthomps/apache-VCL-2.1-RC2-incubating/

The list of resolved JIRA issues associated with this release can be found on 
the VCL 2.1 release page (this has been regenerated for RC2):

http://cwiki.apache.org/VCL/vcl-21-unreleased.html#VCL2.1%2528unreleased%2529-ChangeLog

Installation instructions are on the Confluence site and in the INSTALLATION 
file included in the artifact.

Aaron, Andy, and I have completed a test install of all parts and were able to 
successfully create and capture a base image (we did not repeat this for RC2 
because there were only a few very minor bugfixes).

The directory created by extracting the RC2 artifact 
is apache-VCL-2.1-RC2-incubating.  Licensing information about perl and its 
required modules, php and its required modules, and mysql has been restated 
that they are system requirements according to the information 
under System Requirements on http://www.apache.org/legal/3party.html.  It's 
also worth noting that the roadmap has been slightly updated.

Please vote by the end of the day on Tuesday, Nov 17th to publish this release 
(this allows for 3 business days to vote).  Please note that anyone in the 
VCL community is allowed to vote.

[ ] +1 yes, release VCL 2.1
[ ] 0 dunno
[ ] -1 no, don't release VCL 2.1 (provide reasons if this is your vote)

Josh
- -- 
- ---
Josh Thompson
Systems Programmer
Advanced Computing | VCL Developer
North Carolina State University

josh_thomp...@ncsu.edu
919-515-5323

my GPG/PGP key can be found at pgp.mit.edu
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFK/IMBV/LQcNdtPQMRAps5AJ9EGLEgeRNcksx3Ujv5NrGGrv8eEwCfRZs8
SRm+5RkM+YFse8wY8UruVao=
=Sdi4
-END PGP SIGNATURE-


Re: [VOTE] release VCL 2.1 - RC2

2009-11-12 Thread Josh Thompson
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I forgot to add RC2 to the subject in my first message.

Josh

On Thu November 12 2009 4:49:51 pm Josh Thompson wrote:
 I created a release artifact based off of trunk.  I copied trunk to a tag
 under the tags area of the repo that is named release-2.1-RC2:

 http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.1-RC2/

 The artifact is an export from that tag.  The artifact, MD5 and SHA1 sums,
 and my GPG signature of it are available from my space on people.a.o:

 http://people.apache.org/~jfthomps/apache-VCL-2.1-RC2-incubating/

 The list of resolved JIRA issues associated with this release can be found
 on the VCL 2.1 release page (this has been regenerated for RC2):

 http://cwiki.apache.org/VCL/vcl-21-unreleased.html#VCL2.1%2528unreleased%25
29-ChangeLog

 Installation instructions are on the Confluence site and in the
 INSTALLATION file included in the artifact.

 Aaron, Andy, and I have completed a test install of all parts and were able
 to successfully create and capture a base image (we did not repeat this for
 RC2 because there were only a few very minor bugfixes).

 The directory created by extracting the RC2 artifact
 is apache-VCL-2.1-RC2-incubating.  Licensing information about perl and
 its required modules, php and its required modules, and mysql has been
 restated that they are system requirements according to the information
 under System Requirements on http://www.apache.org/legal/3party.html. 
 It's also worth noting that the roadmap has been slightly updated.

 Please vote by the end of the day on Tuesday, Nov 17th to publish this
 release (this allows for 3 business days to vote).  Please note that anyone
 in the VCL community is allowed to vote.

 [ ] +1 yes, release VCL 2.1
 [ ] 0 dunno
 [ ] -1 no, don't release VCL 2.1 (provide reasons if this is your vote)

 Josh



- -- 
- ---
Josh Thompson
Systems Programmer
Virtual Computing Lab (VCL)
North Carolina State University

josh_thomp...@ncsu.edu
919-515-5323

my GPG/PGP key can be found at www.keyserver.net
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.11 (GNU/Linux)

iD8DBQFK/KTFV/LQcNdtPQMRAkyXAJ41ayT97g8h9W8L7JnTUxovQiQQCwCggCFw
VG7CQj8PRKMezDGhitCaCJE=
=PjNC
-END PGP SIGNATURE-