Re: [VOTE] Andy Kurth as PMC chair after graduation
+1 Just so Matt doesn't look so bad.. :) Regards, Alan On May 31, 2012, at 12:48 PM, Matt Hogstrom wrote: Add my +1 ... late as it is Matt Hogstrom m...@hogstrom.org A Day Without Nuclear Fusion Is a Day Without Sunshine On May 31, 2012, at 10:11 AM, Andy Kurth wrote: Thanks Aaron and everyone else who voted! I updated the wiki page: https://cwiki.apache.org/confluence/display/VCL/Graduation+Board+Resolution -Andy On Thu, May 31, 2012 at 10:07 AM, Aaron Coburn acob...@amherst.edu wrote: +1 And with that, the tally for this vote is: 16 positive votes 1 neutral vote 0 negative votes At this point, with such a positive display of support from the community, I believe we can now add Andy's name to the Graduation Board Resolution. Aaron Coburn -- Aaron Coburn Systems Administrator and Programmer Academic Technology Services, Amherst College acob...@amherst.edumailto:acob...@amherst.edu On May 24, 2012, at 11:03 AM, Aaron Coburn wrote: All, I would like to nominate Andy Kurth as the first VCL chair. This is a position that is responsible for the proper operation of the VCL project. Selecting someone for this position is also a necessary step in the process of graduating from incubator status to a top-level Apache project. For those of you interested in the details, they can be found here: http://incubator.apache.org/guides/graduation.html#tlp-resolution The process is like so: anyone can nominate a person to serve in this role, and these nominations are discussed and voted upon in the community. Based on the consensus from the community, the PPMC (Podling Project Management Committee) makes a recommendation to the ASF Board, which actually appoints the chair. -Aaron Coburn -- Aaron Coburn Systems Administrator and Programmer Academic Technology Services, Amherst College acob...@amherst.edumailto:acob...@amherst.edu
Re: Graduation
On May 12, 2012, at 5:37 PM, Matt Hogstrom wrote: To record my perspective -- I will support graduation as a TLP. I do not, however, intend to continue my participation in the community. I may monitor mailing lists from time-to-time, but do not wish to be a committer/PMC member. I too think its time and support graduation to TLP. Kevan also represents my intention wrt to involvement. It's customary for a mentor to stay on for a quarter or two to monitor the project and make sure that there's a smooth transition. It's not clear to me that this is the role that you and Kevan intend to fulfill. If so, great. If not, I can hang around until the apron strings are fully cut. Regards, Alan
Re: [VOTE] Apache VCL Ready to Graduate
+1 Whoot! Regards, Alan On May 10, 2012, at 8:01 AM, Andy Kurth wrote: This vote is to determine if the Apache VCL community believes the project is ready to graduate from the incubator to a top level project. Everyone in the community is encouraged to vote. Please reply expressing one of the following: +1 : yes, Apache VCL is ready to graduate to a top level project 0 : ambivalent -1 : no, Apache VCL is not ready to graduate to a top level project This vote will be closed on Tuesday, May 15, 2012 at 5:00 pm EST. If this vote passes, the community will draft a board resolution and present it to the IPMC. Thank You, Andy Kurth
Re: Incubator PMC/Board report for May 2012 ([ppmc])
Any takers? Regards, Alan On May 7, 2012, at 8:25 AM, Marvin wrote: Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 16 May 2012, 10:00:00 PST. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, May 2nd). Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/May2012 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC
Re: Graduation Thoughts
On Mar 16, 2012, at 1:36 PM, Matt Hogstrom wrote: Guys, I've been an absent mentor and am catching up on e-mail. In looking at VCL it seems like you're kinda past time to graduate. Kind of like a 26-year-old college Student living at home :) Thoughts on kicking off the process? Do you feel there's sufficient diversity? It seems to me that if NCSU pulls their engineers off the project it will be dead in the water. I'd like to know what your opinion is on this. Other than that I feel that it's an excellent project and ready for graduation. Regards, Alan
Re: mailing list moderators
Added. Regards, Alan On Feb 20, 2012, at 6:48 AM, Josh Thompson wrote: Same for me. Josh On Monday 20 February 2012 9:37:55 AM Andy Kurth wrote: I'm not. Please add me. Thanks, Andy On Sun, Feb 19, 2012 at 11:29 AM, Alan D. Cabrera l...@toolazydogs.com wrote: Who of you are email list moderators for this project? I want to make sure it's not just the mentors. 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 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
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
Re: VCL board report due on Nov 9th
We may still be able to squeak in. Any takers? Regards, Alan On Nov 3, 2011, at 5:43 AM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The November board report is due this coming Wednesday. It is really pretty easy to do and a simple way to get a little more involved with the VCL community. The following page explains what needs to be done to create it, including explaining how to just copy the last one so that you can just make a few changes to it instead of having to write it from scratch. https://cwiki.apache.org/confluence/display/VCL/Board+Reports Josh - -- - --- Josh Thompson VCL Developer North Carolina State University my GPG/PGP key can be found at pgp.mit.edu -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (GNU/Linux) iEYEARECAAYFAk6yjGkACgkQV/LQcNdtPQPiUACfbPP92dHrvBiYH32EyzbIprTW U5sAnieYhlSUySnfhmVMxT0G3GbfbG7y =4H51 -END PGP SIGNATURE-
Re: November 2011 Board Report
On Nov 10, 2011, at 1:44 PM, Andy Kurth wrote: The Apache VCL board report for 11/2011 is available at: https://cwiki.apache.org/confluence/display/VCL/2011-11+Incubator+VCL+Report Please review it and reply with any comments/suggestions/etc ASAP. I will submit it tomorrow morning. Our last report was from August. I'm not sure we should be reporting things from earlier events. Otherwise, looks good to me. Regards, Alan
Re: Graduation?
On Sep 6, 2011, at 10:22 AM, James O'Dell wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 9/4/2011 4:55 PM, Alan D. Cabrera wrote: On Sep 4, 2011, at 7:07 AM, Kevan Miller wrote: It's been a while since we've had a graduation discussion. I've seen good progress in the community. Would be interested in hearing the thoughts of others. Do we feel the community is ready for graduation? Or is additional work required? If there are requirements to be met, what is being done to address these requirements? incubation is not a permanent process. If we're lacking aspects required for graduation and not making progressing on addressing these issues, we need to consider the alternative of ending the graduation process… I think that the community activity on this group is pretty good. I wish there were some diversity. This project has most of it's members being NCSU employees and I'l worried that if NCSU pulled the plug on their efforts the project would not survive. As it stands the project would not have my support for graduation. I'm not intransigent on this and am willing to discuss other viewpoints, if there are any. Regards, Alan I certainly see NCSU as the leader in VCL, and I do see their continued support as key to the success of the project. I'm just wondering if the project were to graduate(It certainly seems stable enough to), if that wouldn't generate more diversity via greater exposure. Unfortunately the diversity must be there before it graduates. We can't graduate the polling and hope for the best, this is what the Incubator is all about. As a point, our vice president of information technology is scheduled to give a presentation at EduCause this October. VCL is his the topic. I'm hoping this will generate some buzz. I'm happy to wait until October to see if the rest of the project does as well. However, I think we face the fact that this project has been around for quite a long time and has not attracted new committers. Maybe the project could park at GitHub, or somewhere, and if and when the it becomes diverse enough it could come back; if it still wanted to. Regards, Alan
Re: Graduation?
On Sep 4, 2011, at 7:07 AM, Kevan Miller wrote: It's been a while since we've had a graduation discussion. I've seen good progress in the community. Would be interested in hearing the thoughts of others. Do we feel the community is ready for graduation? Or is additional work required? If there are requirements to be met, what is being done to address these requirements? incubation is not a permanent process. If we're lacking aspects required for graduation and not making progressing on addressing these issues, we need to consider the alternative of ending the graduation process… I think that the community activity on this group is pretty good. I wish there were some diversity. This project has most of it's members being NCSU employees and I'l worried that if NCSU pulled the plug on their efforts the project would not survive. As it stands the project would not have my support for graduation. I'm not intransigent on this and am willing to discuss other viewpoints, if there are any. Regards, Alan
Re: Board report due -- reminder
Looks good. Thanks! Can you add this to the Incubator Wiki? Regards, Alan On Aug 9, 2011, at 11:06 AM, Aaron Peeler wrote: This has been created: http://cwiki.apache.org/VCL/2011-08-incubator-vcl-report.html If anyone has suggestions/updates or corrections please let me know or update the page. I'll add the report to the Incubator page first thing in the morning. Aaron On Mon, Aug 8, 2011 at 8:34 AM, Aaron Peeler aaron_pee...@ncsu.edu wrote: Any one want to take stab at our August board report? It's due this Wednesday. 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. -- 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: EC2 Provisioning Module
It would be a great way to get more community members involved. :) Regards, Alan On Jul 29, 2011, at 5:54 AM, Aaron Peeler wrote: There was some work done a couple of years ago by either Xianqing or Milan (or both) not sure. I believe it was under IBM control just as a proof of concept and wasn't contributed. We should be able to easily re-create it. If there is strong interest in VCL requesting resources from EC2, sounds like there is -:) , I can help kickstart it. Aaron On Wed, Jul 27, 2011 at 10:21 AM, Alan D. Cabrera l...@toolazydogs.com wrote: That sounds like a fun thing to work on. Who's working on it? Regards, Alan On Jul 27, 2011, at 7:09 AM, Everett Toews wrote: How goes the work on open sourcing the EC2 Provisioning Module? Thanks, Everett -- 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: EC2 Provisioning Module
That sounds like a fun thing to work on. Who's working on it? Regards, Alan On Jul 27, 2011, at 7:09 AM, Everett Toews wrote: How goes the work on open sourcing the EC2 Provisioning Module? Thanks, Everett
Re: Re-doing our homework: reverify our copyright sign-off
Yep. Thanks! Regards, Alan On Jul 18, 2011, at 10:19 AM, Aaron Peeler wrote: Hello Alan, I've found a copy of the Software Grant and Corporate Contributor License Agreement signed by NCSU. Who should I send it to? Aaron On Sun, Jul 17, 2011 at 8:41 PM, Alan D. Cabrera l...@toolazydogs.com wrote: We have been asked to verify our copyright sign-off. I can't find my old emails so we have to double check this. Some of the steps are outlined here: http://incubator.apache.org/guides/mentor.html#initial-ip-clearance I think that since this body of code came from NCSU we need a copy of the SGA on file. It would probably be a good idea to create a documents directory in our SVN and check in a copy of the SGA in there as well. This effort is as serious as a heart attack and it would be good if we could get this done as soon as possible. Regards, Alan -- 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: Re-doing our homework: reverify our copyright sign-off
Received. Many thanks! I'l check this in and update the status files. Regards, Alan On Jul 18, 2011, at 10:22 AM, Alan D. Cabrera wrote: Yep. Thanks! Regards, Alan On Jul 18, 2011, at 10:19 AM, Aaron Peeler wrote: Hello Alan, I've found a copy of the Software Grant and Corporate Contributor License Agreement signed by NCSU. Who should I send it to? Aaron On Sun, Jul 17, 2011 at 8:41 PM, Alan D. Cabrera l...@toolazydogs.com wrote: We have been asked to verify our copyright sign-off. I can't find my old emails so we have to double check this. Some of the steps are outlined here: http://incubator.apache.org/guides/mentor.html#initial-ip-clearance I think that since this body of code came from NCSU we need a copy of the SGA on file. It would probably be a good idea to create a documents directory in our SVN and check in a copy of the SGA in there as well. This effort is as serious as a heart attack and it would be good if we could get this done as soon as possible. Regards, Alan -- 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: Podlings needing copyright sign-off
I think we just need to confirm that the paperwork was collected and update the incubator status page. Regards, Alan On Jul 11, 2011, at 12:40 PM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wow - I would have thought that happened with everything else when we moved the code to ASF. What kind of paperwork do we need to make this happen? Josh On Friday July 08, 2011, Kevan Miller wrote: Begin forwarded message: From: Henri Yandell flame...@gmail.com Date: July 7, 2011 10:20:51 PM EDT To: general-incubator gene...@incubator.apache.org Subject: Podlings needing copyright sign-off Reply-To: gene...@incubator.apache.org Here's a list of the projects in the Incubator who need to sign off their copyright item; namely: Check and make sure that the papers that transfer rights to the ASF been received. It is only necessary to transfer rights for the package, the core code, and any new code produced by the project. The list is: 2007-10-06 jspwiki 2008-01-06 rat 2008-04-15 bluesky (pending retirement) 2008-08-01 empire-db 2008-09-23 etch 2008-09-29 olio 2008-10-01 vcl 2008-10-23 droids 2008-11-12 tashi 2009-02-09 kato 2009-02-13 stonehenge 2009-05-08 ace 2009-05-13 socialsite 2009-06-25 wink 2009-08-07 vxquery 2009-11-08 hise 2009-12-15 clerezza 2010-01-27 manifoldcf 2010-05-19 amber 2010-05-21 deltacloud 2010-05-24 zetacomponents 2010-07-19 chukwa 2010-09-05 nuvem 2010-09-27 alois 2010-11-02 celix 2010-11-12 kitty 2010-11-24 stanbol 2010-12-02 jena 2010-12-02 opennlp 2010-12-08 wave 2011-01-03 mesos 2011-02-01 easyant 2011-02-05 lucene.net 2011-04-30 ognl 2011-06-13 flume 2011-06-13 openofficeorg 2011-06-13 sqoop Some are new podlings, so no huge surprise, but others have been around for a long time. I think each podling needs to focus on getting this checklist item resolved. Hen - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - -- - --- Josh Thompson VCL Developer North Carolina State University my GPG/PGP key can be found at pgp.mit.edu -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (GNU/Linux) iEYEARECAAYFAk4bUb4ACgkQV/LQcNdtPQNb/gCfWsqXlRY7AgWtlLcT9hrk+3xP +ysAn0rVAn2tSkE2Nhz+oKXJypwOtyp3 =wCvr -END PGP SIGNATURE-
Re: Podlings needing copyright sign-off
Should be in our old mail archives I think. Regards, Alan On Jul 11, 2011, at 12:45 PM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ah, okay. Who do we ask to check for the paperwork? Josh On Monday July 11, 2011, Alan D. Cabrera wrote: I think we just need to confirm that the paperwork was collected and update the incubator status page. Regards, Alan On Jul 11, 2011, at 12:40 PM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wow - I would have thought that happened with everything else when we moved the code to ASF. What kind of paperwork do we need to make this happen? Josh On Friday July 08, 2011, Kevan Miller wrote: Begin forwarded message: From: Henri Yandell flame...@gmail.com Date: July 7, 2011 10:20:51 PM EDT To: general-incubator gene...@incubator.apache.org Subject: Podlings needing copyright sign-off Reply-To: gene...@incubator.apache.org Here's a list of the projects in the Incubator who need to sign off their copyright item; namely: Check and make sure that the papers that transfer rights to the ASF been received. It is only necessary to transfer rights for the package, the core code, and any new code produced by the project. The list is: 2007-10-06jspwiki 2008-01-06rat 2008-04-15bluesky (pending retirement) 2008-08-01empire-db 2008-09-23etch 2008-09-29olio 2008-10-01vcl 2008-10-23droids 2008-11-12tashi 2009-02-09kato 2009-02-13stonehenge 2009-05-08ace 2009-05-13socialsite 2009-06-25wink 2009-08-07vxquery 2009-11-08hise 2009-12-15clerezza 2010-01-27manifoldcf 2010-05-19amber 2010-05-21deltacloud 2010-05-24zetacomponents 2010-07-19chukwa 2010-09-05nuvem 2010-09-27alois 2010-11-02celix 2010-11-12kitty 2010-11-24stanbol 2010-12-02jena 2010-12-02opennlp 2010-12-08wave 2011-01-03mesos 2011-02-01easyant 2011-02-05lucene.net 2011-04-30ognl 2011-06-13flume 2011-06-13openofficeorg 2011-06-13sqoop Some are new podlings, so no huge surprise, but others have been around for a long time. I think each podling needs to focus on getting this checklist item resolved. Hen - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - -- - --- Josh Thompson VCL Developer North Carolina State University my GPG/PGP key can be found at pgp.mit.edu -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (GNU/Linux) iEYEARECAAYFAk4bUb4ACgkQV/LQcNdtPQNb/gCfWsqXlRY7AgWtlLcT9hrk+3xP +ysAn0rVAn2tSkE2Nhz+oKXJypwOtyp3 =wCvr -END PGP SIGNATURE- - -- - --- Josh Thompson VCL Developer North Carolina State University my GPG/PGP key can be found at pgp.mit.edu -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (GNU/Linux) iEYEARECAAYFAk4bUucACgkQV/LQcNdtPQPgIwCffNAFbuIL1wWYFsLn2TA8U42U S1EAn0cKDZyRk5Nu1oiEU/UPW4Uhjv5E =kwYw -END PGP SIGNATURE-
Re: [mentors] question about release process
On Mar 30, 2011, at 9:47 AM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 So, the vote on the IPMC list passed. However, due to a question on the vcl- user list, I discovered a very small bug, but one that would be nice to have fixed in the release. The problem is in a javascript file. There are two arrays that have a comma after the final element. Firefox is okay with that; IE gives a parse error. The result is that no graphs show up under IE on the statistics page. The fix is to remove the 2 commas. I don't feel like removing them necessitates a full cycle of cutting another RC, having a vote on our list, and then having a vote on the IPMC list. I'd like fix it in trunk, in the final release tag, and in the release archive, but I don't know if that's allowed without doing the full cycle again. Do we need to go through the whole process again, or can I just fix it and cut the release? Yes, any change requires a new vote. This is because of the changes in signatures etc. Regards, Alan
Fwd: Incubator report reminders sent for February 2011
It's our turn to participate in the Incubator report. :) Regards, Alan Begin forwarded message: From: no-re...@apache.org Date: February 1, 2011 6:00:14 AM PST To: priv...@incubator.apache.org Subject: Incubator report reminders sent for February 2011 Reply-To: priv...@incubator.apache.org The next board meeting is scheduled for Wed, 16 February 2011, 10 am Pacific. I have just sent reminder emails to these addresses, requesting them to supply board reports one week before the above date: Amber Developers amber-...@incubator.apache.org Bluesky Developers bluesky-...@incubator.apache.org Celix Developers celix-...@incubator.apache.org Clerezza Developers clerezza-...@incubator.apache.org Deltacloud Developers deltacloud-...@incubator.apache.org Droids Developers droids-...@incubator.apache.org EasyAnt Developers gene...@incubator.apache.org HISE Developers hise-...@incubator.apache.org Jena Developers jena-...@incubator.apache.org Kitty Developers kitty-...@incubator.apache.org Libcloud Developers libcl...@incubator.apache.org Mesos Developers mesos-...@incubator.apache.org NPanday Developers npanday-...@incubator.apache.org Nuvem Developers nuvem-...@incubator.apache.org OpenNLP Developers opennlp-...@incubator.apache.org PhotArk Developers photark-...@incubator.apache.org SIS Developers sis-...@incubator.apache.org Stanbol Developers stanbol-...@incubator.apache.org Stonehenge Developers stonehenge-...@incubator.apache.org VCL Developers vcl-dev@incubator.apache.org Wave Developers wave-...@incubator.apache.org Whirr Developers whirr-...@incubator.apache.org Wink Developers wink-...@incubator.apache.org Wookie Developers wookie-...@incubator.apache.org Zeta Components Developers zeta-...@incubator.apache.org Marvin - To unsubscribe, e-mail: private-unsubscr...@incubator.apache.org For additional commands, e-mail: private-h...@incubator.apache.org
Re: [VOTE] release VCL 2.2 - voting based on RC2
+1 Regards, Alan On Sep 22, 2010, at 3:47 PM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm starting a different thread to vote again based on RC2 to make it easier to tally votes. This is basically the same email as before except with RC1 changed to RC2. There were a few JIRA issues touched for RC2. VCL-386 was a completely new one. VCL-145, VCL-196, VCL-298, and VCL-303 were already resolved but had code modified related to them 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.2-RC2: http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.2-RC2/ The artifact is an export from that tag with the addition of Dojo Toolkit version 1.5.0 bundled in the web code. 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.2-RC2-incubating/ The list of resolved JIRA issues associated with this release can be found on the VCL 2.2 release page: http://cwiki.apache.org/VCL/vcl-22-unreleased.html 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. The directory created by extracting the RC1 artifact is apache-VCL-2.2-RC2- incubating. Licensing information about perl and its required modules, php and its required modules, and mysql are stated as system requirements according to the information under System Requirements on http://www.apache.org/legal/3party.html. Please vote by the end of the day on Monday, Sept. 27th 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.2 [ ] 0 dunno [ ] -1 no, don't release VCL 2.2 (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.14 (GNU/Linux) iD8DBQFMmoeWV/LQcNdtPQMRAhNtAJ47EYt4ufvLr7n2DTt/M6GWLA7oUACeLmoS CU/ElAKOl8VlBzChNdDlTOw= =kXRB -END PGP SIGNATURE-
Re: [mentors] guidelines for contributing large modifications
Did you get your questions answered? Regards, Alan On Jun 2, 2010, at 10:26 AM, Kiran N wrote: The plan sounds good to me! I have a question regarding the development phase of the code changes. Since the changes are huge, do we maintain different revisions of the complete code or just the changed modules are recorded/maintained. Also, what would be the procedure for the testing of the submitted code. Do we have anything called as unit test plans anywhere in the repository? If yes, that would be helpful..! On Tue, Jun 1, 2010 at 2:13 PM, Matt Hogstrom m...@hogstrom.org wrote: Great start Josh ... +1 On Jun 1, 2010, at 11:26 AM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 (This message is to everyone in the community. I added [mentors] to the subject to help our mentors know it is of particular importance for them to read.) After reading Reg: JIRA issue VCL-202 by Kiran N sent on May 28, I realized we need some guidelines for contributing large modifications to the project. This is the general work flow I'd like to see happen for large modifications. Please provide comments and suggestions. Everyone's input is welcome (and desired) -- if you are interested in becoming a committer, this would be a great place to step up involvement. (1) State on the vcl-dev list what modification you'd like to make. Some background on why the existing codebase doesn't work in your situation would be useful. Remember, when you modify existing code, it affects work being done by other contributors, which can result in imposing additional work on them. (2) Propose a plan on the vcl-dev list for making the modification. There may be others that want the same modification or something similar that can be incorporated at the same time. Those people can help develop the modification. On the other hand, the modification may have a very negative affect on some other part of the project. Also, this provides an opportunity for existing contributors (those who know the codebase well) to provide input on your plan. The plan needs to include how the modification will be maintained in the future - will you continue to maintain it; will existing contributors have to pick it up and maintain it? (3) Create a JIRA issue to track implementation of the plan and start developing. This provides a way for others to track work being done on the modification and ensures information about the modification will be added to the CHANGELOG when the next release is cut. Thanks Josh - -- - --- Josh Thompson Systems Programmer Advanced Computing | VCL Developer North Carolina State University josh_thomp...@ncsu.edu my GPG/PGP key can be found at pgp.mit.edu -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAkwFJr0ACgkQV/LQcNdtPQNZqwCfYyeB99JT3vxuBs9+gpn+v5vs BWYAn2D5HK/Cvo1Kd5CtpEqFpsJBR8bo =dYgS -END PGP SIGNATURE- -- Thanks, Kiran
Re: [mentors] guidelines for contributing large modifications
On Jun 1, 2010, at 8:26 AM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 (This message is to everyone in the community. I added [mentors] to the subject to help our mentors know it is of particular importance for them to read.) After reading Reg: JIRA issue VCL-202 by Kiran N sent on May 28, I realized we need some guidelines for contributing large modifications to the project. This is the general work flow I'd like to see happen for large modifications. Please provide comments and suggestions. Everyone's input is welcome (and desired) -- if you are interested in becoming a committer, this would be a great place to step up involvement. (1) State on the vcl-dev list what modification you'd like to make. Some background on why the existing codebase doesn't work in your situation would be useful. Remember, when you modify existing code, it affects work being done by other contributors, which can result in imposing additional work on them. (2) Propose a plan on the vcl-dev list for making the modification. There may be others that want the same modification or something similar that can be incorporated at the same time. Those people can help develop the modification. On the other hand, the modification may have a very negative affect on some other part of the project. Also, this provides an opportunity for existing contributors (those who know the codebase well) to provide input on your plan. The plan needs to include how the modification will be maintained in the future - will you continue to maintain it; will existing contributors have to pick it up and maintain it? (3) Create a JIRA issue to track implementation of the plan and start developing. This provides a way for others to track work being done on the modification and ensures information about the modification will be added to the CHANGELOG when the next release is cut. Seems reasonable to me. Regards, Alan
Re: Incubator PMC/Board report for May 2010 (vcl-dev@incubator.apache.org)
Who's going to volunteer? :) On May 1, 2010, at 7:00 AM, no-re...@apache.org wrote: Dear VCL Developers, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for . The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted one week before the board meeting, to allow sufficient time for review. Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is one week prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/May2010 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC
Re: Incubator PMC/Board report for February 2010 (VCL Developers vcl-dev@incubator.apache.org)
Looks great. Many thanks! Regards, Alan On Feb 8, 2010, at 6:31 AM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The report has been added to the Incubator February 2010 page. Josh On Friday February 05, 2010, Josh Thompson wrote: This has been created. http://cwiki.apache.org/VCL/2010-02-incubator-vcl-report.html If anyone has suggestions/updates/corrections please let me know or update the page yourself. I'll add the report to the Incubator page on Monday. Josh On Thu February 4 2010 1:02:07 pm Josh Thompson wrote: I'll get it. Josh On Thursday February 04, 2010, Alan D. Cabrera wrote: Anyone want to take a crack at this? Regards, Alan On Feb 1, 2010, at 6:00 AM, Incubator PMC wrote: Dear VCL Developers, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 17 February 2010, 12 pm Pacific. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted one week before the board meeting, to allow sufficient time for review. Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is one week prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/February2010 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC - -- - --- 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) iD8DBQFLcCAwV/LQcNdtPQMRAux1AJ9v++YBtFKKDMcfsUfdSY4c/dLKRwCfZ9Xo fe8q7/ke4Wfh1S03ECCq7uQ= =7D1v -END PGP SIGNATURE-
Re: Incubator PMC/Board report for February 2010 (VCL Developers vcl-dev@incubator.apache.org)
I would list the people that were added to the PPMC. Other than that it looks good to me. Thanks! Regards, Alan On Feb 5, 2010, at 7:39 AM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This has been created. http://cwiki.apache.org/VCL/2010-02-incubator-vcl-report.html If anyone has suggestions/updates/corrections please let me know or update the page yourself. I'll add the report to the Incubator page on Monday. Josh On Thu February 4 2010 1:02:07 pm Josh Thompson wrote: I'll get it. Josh On Thursday February 04, 2010, Alan D. Cabrera wrote: Anyone want to take a crack at this? Regards, Alan On Feb 1, 2010, at 6:00 AM, Incubator PMC wrote: Dear VCL Developers, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 17 February 2010, 12 pm Pacific. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted one week before the board meeting, to allow sufficient time for review. Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is one week prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/February2010 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC - -- - --- 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) iD8DBQFLbDvUV/LQcNdtPQMRAlFLAJ42Se1NVked/wgHeuD5uvQY7M8/sgCfccQU IiY5UPAk8NAA77sAPC7Y82g= =hCam -END PGP SIGNATURE-
Re: Wiki contributions from individuals who have not signed the CLA
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-
Re: Board report reminder emails
I'm going to send this off today. Regards, Alan On Nov 10, 2009, at 11:30 AM, Alan D. Cabrera wrote: Looks pretty good. I'll sign off. Not sure if that is needed. I see that there's a number of outstanding items waiting on the mentors. I'll follow up w/ clean emails on them. Regards, Alan On Nov 10, 2009, at 10:39 AM, Andy Kurth wrote: I have created a draft of this month's report: http://cwiki.apache.org/confluence/display/VCL/2009-11+Incubator+VCL+Report Please review it and bring up anything you think should be changed on this list. I will post this to the monthly page tomorrow if no objections are expressed. Mentors, can one of you please complete the signed off line at the bottom? I also added instructions to the following page: http://cwiki.apache.org/confluence/display/VCL/Board+Reports Thanks, Andy Alan D. Cabrera wrote: Anyone want to take a crack at this? Regards, Alan On Nov 6, 2009, at 6:07 AM, Upayavira wrote: Every month, a third of incubator podlings must submit reports to the incubator PMC. I have written and am about to test a script that will run at the beginning of each month to send out reminders to those podlings that are due to report. As your report is due this month, if everything goes to plan you'll see a reminder mail soon after this one. When you do, please let me know if you see any errors. Please note, I'm likely not subscribed to this list. Upayavira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Andy Kurth Virtual Computing Lab Office of Information Technology North Carolina State University andy_ku...@ncsu.edu 919.513.4090
Re: Jira perms
The link is not in an obvious place. It's below the project description on the left hand side. It should be between the Create a new issue in project VCL and Release Notes. Regards, Alan On Nov 11, 2009, at 6:35 AM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm not seeing that link anywhere. Aaron and Andy said they don't see it either. Is there something we're supposed to do to make it show up? Josh On Tuesday November 10, 2009, Alan D. Cabrera wrote: Ahh, yeah. That's the uber admin link that is now reserved for infra people. To get to the VCL admin there should be an Administer Project link on page https://issues.apache.org/jira/browse/VCL. Regards, Alan On Nov 10, 2009, at 1:44 PM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 For some reason, we're not seeing the Administration link in the top bar on the JIRA site. Even though you're seeing that we have the administrative role, we can't do administrative things without being able to get to that part of the JIRA site. To be clear, previously, the top bar of the site had HOME, BROWSE PROJECT, FIND ISSUES, CREATE NEW ISSUE, and ADMINISTRATION. But now, we're only seeing HOME, BROWSE PROJECT, FIND ISSUES, and CREATE NEW ISSUE. Josh On Tuesday November 10, 2009, Alan D. Cabrera wrote: I see that a number of people have admin permissions for the VCL project. These include: Users in Project Role Aaron Peeler Andy Kurth Brian Bouterse Josh Thompson What problems are we encountering. BTW, previously a few of us had full Jira admin privs. These have been now reserved for infra people. However we have the admin role for the above people. I think that this should be sufficient. Will this work? 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) iD8DBQFK+d7SV/LQcNdtPQMRAlYgAJ9mznhCelJcv26I5khpxk0ut+6cCgCcDCrz kb4nZAbUortlKDfPeGQoPbo= =lpRK -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) iD4DBQFK+su0V/LQcNdtPQMRAmHFAJjN1Tz0Cl2IZOD4k9FvqOTnh5EVAJ429w9O yot7UOwYIze5Uh8pvJFbbg== =Qnh3 -END PGP SIGNATURE-
Re: Jira perms
Cool. Can you check to see if you can edit the project roles? On Nov 11, 2009, at 8:26 AM, Andy Kurth wrote: It shows up now. Thank You! -Andy Alan D. Cabrera wrote: Try it now. Regards, Alan On Nov 11, 2009, at 7:59 AM, Andy Kurth wrote: Hmm, something ate my attachment. Try this page: http://vcl.ncsu.edu/jira-permission-issue Andy Kurth wrote: Hi Alan, Thanks for looking into this. That link isn't appearing. Screenshot attached. Thanks, Andy Alan D. Cabrera wrote: The link is not in an obvious place. It's below the project description on the left hand side. It should be between the Create a new issue in project VCL and Release Notes. Regards, Alan -- Andy Kurth Virtual Computing Lab Office of Information Technology North Carolina State University andy_ku...@ncsu.edu 919.513.4090
Re: Board report reminder emails
Looks pretty good. I'll sign off. Not sure if that is needed. I see that there's a number of outstanding items waiting on the mentors. I'll follow up w/ clean emails on them. Regards, Alan On Nov 10, 2009, at 10:39 AM, Andy Kurth wrote: I have created a draft of this month's report: http://cwiki.apache.org/confluence/display/VCL/2009-11+Incubator+VCL+Report Please review it and bring up anything you think should be changed on this list. I will post this to the monthly page tomorrow if no objections are expressed. Mentors, can one of you please complete the signed off line at the bottom? I also added instructions to the following page: http://cwiki.apache.org/confluence/display/VCL/Board+Reports Thanks, Andy Alan D. Cabrera wrote: Anyone want to take a crack at this? Regards, Alan On Nov 6, 2009, at 6:07 AM, Upayavira wrote: Every month, a third of incubator podlings must submit reports to the incubator PMC. I have written and am about to test a script that will run at the beginning of each month to send out reminders to those podlings that are due to report. As your report is due this month, if everything goes to plan you'll see a reminder mail soon after this one. When you do, please let me know if you see any errors. Please note, I'm likely not subscribed to this list. Upayavira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Andy Kurth Virtual Computing Lab Office of Information Technology North Carolina State University andy_ku...@ncsu.edu 919.513.4090
Confluence committers group that contains the Apache VCL community members with a CLA
A request has been made to the mentors to create a Confluence committers group that contains the Apache VCL community members with a CLA on file. Many committers on VCL have admin privs for this space. What problem are we trying to solve? Regards, Alan
Re: Wiki contributions from individuals who have not signed the CLA
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-
Jira perms
I see that a number of people have admin permissions for the VCL project. These include: Users in Project Role Aaron Peeler Andy Kurth Brian Bouterse Josh Thompson What problems are we encountering. BTW, previously a few of us had full Jira admin privs. These have been now reserved for infra people. However we have the admin role for the above people. I think that this should be sufficient. Will this work? Regards, Alan
Re: Jira perms
Ahh, yeah. That's the uber admin link that is now reserved for infra people. To get to the VCL admin there should be an Administer Project link on page https://issues.apache.org/jira/browse/VCL. Regards, Alan On Nov 10, 2009, at 1:44 PM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 For some reason, we're not seeing the Administration link in the top bar on the JIRA site. Even though you're seeing that we have the administrative role, we can't do administrative things without being able to get to that part of the JIRA site. To be clear, previously, the top bar of the site had HOME, BROWSE PROJECT, FIND ISSUES, CREATE NEW ISSUE, and ADMINISTRATION. But now, we're only seeing HOME, BROWSE PROJECT, FIND ISSUES, and CREATE NEW ISSUE. Josh On Tuesday November 10, 2009, Alan D. Cabrera wrote: I see that a number of people have admin permissions for the VCL project. These include: Users in Project Role Aaron Peeler Andy Kurth Brian Bouterse Josh Thompson What problems are we encountering. BTW, previously a few of us had full Jira admin privs. These have been now reserved for infra people. However we have the admin role for the above people. I think that this should be sufficient. Will this work? 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) iD8DBQFK+d7SV/LQcNdtPQMRAlYgAJ9mznhCelJcv26I5khpxk0ut+6cCgCcDCrz kb4nZAbUortlKDfPeGQoPbo= =lpRK -END PGP SIGNATURE-
Re: [VOTE] release VCL 2.1
I don't have time to double check this release until this weekend. Normally votes are 72 hours. I request that we don't count the votes until Monday, if that's ok. Regards, Alan On Oct 21, 2009, at 10:27 AM, Josh Thompson wrote: -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-RC1: http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.1-RC1/ 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-RC1-incubating/ The list of resolved JIRA issues associated with this release can be found on the VCL 2.1 release page: 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. Please vote to publish this release. (Question to mentors: Do I need to vote in a successive email in this thread, or is this post an implicit vote?) - -- - --- 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) iD8DBQFK30SGV/LQcNdtPQMRAhk8AJsGL4m0J1v0DC7U9Yyc31TIRjKXFACdE0bM 827++1u0XH9c2GqKP/pAE80= =QrMV -END PGP SIGNATURE-
Re: VCL project name
On May 29, 2009, at 5:34 AM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday May 28, 2009, Henri Yandell wrote: On Thu, May 28, 2009 at 5:01 PM, William A. Rowe, Jr. wr...@rowe-clan.net wrote: Alan D. Cabrera wrote: Take for example the donation of ServiceMix by LogicBlaze. LogicBlaze renamed its product offering of ServiceMix to FUSE. Reread the request! They aren't asking to brand a fork of the software, or similar that you are citing. They are asking if they provide the VCL Server will we be mad? No more than if they hosted an Apache HTTP Server or Tomcat Server. If they shipped software they called VCL then yes, we would take issue. Nope - they're asking if they brand a service VCL will we be mad. Akin to my setting up a hosting service called Tomcat (or DimSum Tomcat) that lets people log in and run their own Tomcat servers. Plus if I decide to throw out Tomcat and use Jetty instead, I still get to call it DimSum Tomcat. Hen Hen is correct about it being a service. The VCL software is designed to be run as a service. The software was initially developed at NCSU, and they have a service that was initially known as VCL. As other institutions started using the software, NCSU changed their service to be NCSU VCL and allowed others to brand their services as institution name VCL (i.e. GMU VCL). It was assumed that with moving the development of the software to ASF, it would be named Apache VCL and that people using it would have the option to name their services institution name VCL. There was much discussion on the vcl-...@incubator.a.o list about whether or not there were legal issues with that; thus, the discussion was brought up on legal-disc...@. Also, there's a possibility that it may be technically legal, but ASF would frown on it. People at NCSU have thought that using the name Apache VCL would bring those that already knew about VCL while it was developed at NCSU to the ASF community. Thus, it has been confusing that an action that was motivated by the goal of building Apache VCL community would be frowned upon. As a new project that is trying to make it in the ASF Way, we want to avoid being frowned upon. :) What about the VCL community, https://vcl.ncsu.edu/vcl-community. What are the future plans for that community? Regards, Alan
Re: VCL project name
On May 27, 2009, at 6:45 PM, Lawrence Rosen wrote: Alan Cabrera asked: Let's say that IBM donates Websphere to the ASF. They acquiesce in our calling our software Apache Webshpere. Would it still be ok if they had IBM Websphere? Yes. (I presume you meant to type Websphere!) The key is acquiescence. It would mean that IBM has acquiesced to the use of Websphere as a common name for a variety of software products from different vendors, and they would no longer be able to defend it as their exclusive trademark for their own specific brand of software. But they could still use that name, because we and others couldn't challenge IBM's continued use either. I think that I was not clear. While it may be perfectly legal for this situation to happen, the ASF would frown upon such an arrangement. This is because there are a myriad of companies that wish to leverage their marketing efforts off of the cache of the Apache Software Foundation. It is my understanding that we require that the donation organization cease using the brand. Take for example the donation of ServiceMix by LogicBlaze. LogicBlaze renamed its product offering of ServiceMix to FUSE. Regards, Alan /Larry -Original Message- From: Alan D. Cabrera [mailto:l...@toolazydogs.com] Sent: Wednesday, May 27, 2009 6:27 PM To: legal-disc...@apache.org Cc: vcl-dev@incubator.apache.org Subject: Re: VCL project name On May 27, 2009, at 3:58 PM, Lawrence Rosen wrote: From those on the legal-discuss list, there's one thing NCSU would like to get clarification on. If NCSU more clearly donates the name VCL to Apache, would NCSU still be allowed to run a service that contains VCL in the name of the service? Yes. We can't and won't expressly trademark VCL. NCSU doesn't need to donate anything, merely acquiesce in our calling our software Apache VCL. Let's say that IBM donates Websphere to the ASF. They acquiesce in our calling our software Apache Webshpere. Would it still be ok if they had IBM Websphere? Regards, Alan /Larry (with ASF attorney hat on) -Original Message- From: Josh Thompson [mailto:josh_thomp...@ncsu.edu] Sent: Wednesday, May 27, 2009 8:07 AM To: legal-disc...@apache.org Cc: vcl-dev@incubator.apache.org Subject: Re: VCL project name -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bump. Is there anyone out there that could give us some direction about our project name? Thanks, Josh On Monday May 04, 2009, Josh Thompson wrote: To the legal-discuss list: From those on the legal-discuss list, there's one thing NCSU would like to get clarification on. If NCSU more clearly donates the name VCL to Apache, would NCSU still be allowed to run a service that contains VCL in the name of the service? Whether or not the Apache project name changes, the NCSU site (http://vcl.ncsu.edu) will be updated to clearly reflect that the code powering the service is from Apache. As a bit of background, while development of VCL was at NCSU, NCSU had no problems with other universities using the code to run a service named VCL at their own site. It was just asked that somewhere on the site, NCSU was credited with the development of VCL. When moving the code to Apache, it was assumed that this same arrangement would be allowed (i.e. Apache credited with the development of VCL). It's okay if that's not the case, but it would be helpful to have some legal reasons explaining why. To the vcl-dev list: If using VCL in the name of the service would not be allowed, what do people in the VCL community think of changing the Apache project name to VCloud? That name was previously mentioned by Sam in this message: http://mail-archives.apache.org/mod_mbox/incubator-vcl- dev/200903.mbox/001 701c99c40$87f1a390$97d4eab0$%40edu Thanks, Josh On Friday May 01, 2009, aaron_pee...@ncsu.edu wrote: Matt, Alan, Kevan, Any additional information on the project name ? I found this in the archives: http://mail-archives.apache.org/mod_mbox/www-legal- discuss/200904.mbox/%3 C4 d6e71c2-396a-4b02-afa9-041edd94f...@sun.com%3e In particular: If you want to continue to use VCL, I'd recommend asking NCSU to make more obvious their donation to Apache and their intent to donate not only the code but the name. This would allow us to claim historic use of the name. If not, find another name. How do we donate the name? NCSU is taking efforts to make the donation more obvious at the ncsu site. Thanks for any advice, Aaron - -- - --- 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 pgp.mit.edu -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFKHVcfV/LQcNdtPQMRAmhVAJ9AbkQrMQPQmAUbzqU1RWTC+BQfxQCeJAYX nQc36WzLTUwAfkXuu94sAoU= =3CVv -END PGP SIGNATURE
Re: VCL project name
On May 28, 2009, at 5:01 PM, William A. Rowe, Jr. wrote: Alan D. Cabrera wrote: Take for example the donation of ServiceMix by LogicBlaze. LogicBlaze renamed its product offering of ServiceMix to FUSE. Reread the request! They aren't asking to brand a fork of the software, or similar that you are citing. They are asking if they provide the VCL Server will we be mad? No more than if they hosted an Apache HTTP Server or Tomcat Server. If they shipped software they called VCL then yes, we would take issue. And if LogicBlaze offered ServiceMix as SaaS would there not be confusion that ServiceMix is actually developed at LogicBlaze and Apache ServiceMix is merely an off shoot project? If LogicBlaze had things on their site like - ServiceMix News - ServiceMix Email notifications - ServiceMix Community - a community which has nothing to do with Apache ServiceMix you don't think that would be confusing? Frankly I am baffled as to why we can't just change our project name. But then NCSU staff and executives argue against that. Doesn't that seem like they are attempting to keep the brand association? If they are do we care? Don't get me wrong, NCSU VCL is bending over backwards to be accommodating; the project is doing well. Since this is not a legal issue, per Larry's trusted opinion, and if no one else has problems with this then, I guess, neither do I. If no one objects I'm happy to let lazy consensus dictate that the name is ok. Regards, Alan
Re: VCL project name
On May 27, 2009, at 3:58 PM, Lawrence Rosen wrote: From those on the legal-discuss list, there's one thing NCSU would like to get clarification on. If NCSU more clearly donates the name VCL to Apache, would NCSU still be allowed to run a service that contains VCL in the name of the service? Yes. We can't and won't expressly trademark VCL. NCSU doesn't need to donate anything, merely acquiesce in our calling our software Apache VCL. Let's say that IBM donates Websphere to the ASF. They acquiesce in our calling our software Apache Webshpere. Would it still be ok if they had IBM Websphere? Regards, Alan /Larry (with ASF attorney hat on) -Original Message- From: Josh Thompson [mailto:josh_thomp...@ncsu.edu] Sent: Wednesday, May 27, 2009 8:07 AM To: legal-disc...@apache.org Cc: vcl-dev@incubator.apache.org Subject: Re: VCL project name -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bump. Is there anyone out there that could give us some direction about our project name? Thanks, Josh On Monday May 04, 2009, Josh Thompson wrote: To the legal-discuss list: From those on the legal-discuss list, there's one thing NCSU would like to get clarification on. If NCSU more clearly donates the name VCL to Apache, would NCSU still be allowed to run a service that contains VCL in the name of the service? Whether or not the Apache project name changes, the NCSU site (http://vcl.ncsu.edu) will be updated to clearly reflect that the code powering the service is from Apache. As a bit of background, while development of VCL was at NCSU, NCSU had no problems with other universities using the code to run a service named VCL at their own site. It was just asked that somewhere on the site, NCSU was credited with the development of VCL. When moving the code to Apache, it was assumed that this same arrangement would be allowed (i.e. Apache credited with the development of VCL). It's okay if that's not the case, but it would be helpful to have some legal reasons explaining why. To the vcl-dev list: If using VCL in the name of the service would not be allowed, what do people in the VCL community think of changing the Apache project name to VCloud? That name was previously mentioned by Sam in this message: http://mail-archives.apache.org/mod_mbox/incubator-vcl- dev/200903.mbox/001 701c99c40$87f1a390$97d4eab0$%40edu Thanks, Josh On Friday May 01, 2009, aaron_pee...@ncsu.edu wrote: Matt, Alan, Kevan, Any additional information on the project name ? I found this in the archives: http://mail-archives.apache.org/mod_mbox/www-legal- discuss/200904.mbox/%3 C4 d6e71c2-396a-4b02-afa9-041edd94f...@sun.com%3e In particular: If you want to continue to use VCL, I'd recommend asking NCSU to make more obvious their donation to Apache and their intent to donate not only the code but the name. This would allow us to claim historic use of the name. If not, find another name. How do we donate the name? NCSU is taking efforts to make the donation more obvious at the ncsu site. Thanks for any advice, Aaron - -- - --- 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 pgp.mit.edu -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFKHVcfV/LQcNdtPQMRAmhVAJ9AbkQrMQPQmAUbzqU1RWTC+BQfxQCeJAYX nQc36WzLTUwAfkXuu94sAoU= =3CVv -END PGP SIGNATURE- - To unsubscribe, e-mail: legal-discuss-unsubscr...@apache.org For additional commands, e-mail: legal-discuss-h...@apache.org - To unsubscribe, e-mail: legal-discuss-unsubscr...@apache.org For additional commands, e-mail: legal-discuss-h...@apache.org
Re: Mentors: health of project/community?
What's being done poorly is my ability to scraping the time to keep up. I'm sorry. Things seem to be going well. Some of the big issues seem to be diversity and NCSU's use of the VCL name. Please remember that you can still perform releases while still being in the incubator. Regards, Alan On May 19, 2009, at 8:31 AM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mentors, Could you provide some idea of how you think we are doing as a project and how you think the community is developing? I know we haven't had a lot of contributions from people outside of NCSU, but there have been some. We're still trying to get more. Other than just the diversity of the community, what do you think of how well we are getting the Apache Way? What have we done well? What have we done poorly? Thanks, 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 pgp.mit.edu -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFKEtDLV/LQcNdtPQMRAoa+AJ9t3Ojh/w0WaFaKqr9u01bRQx07pACfUtsY Gpg+d+FkHC6+FdsXPHKzAJQ= =USix -END PGP SIGNATURE-
Re: catchall JIRA issue for really minor changes
On Mar 20, 2009, at 12:51 PM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sometimes, we run across a really minor issue while working on a separate issue. Rather than creating a JIRA issue for each of these minor items, what do you think about creating a catchall issue for each component/ version combination (i.e., issue for frontend v2.1, issue for backend v2.1, issue for frontend v2.2, etc). Then, when something minor comes up, the subversion commit is tagged with the catchall issue number for that version. This way, the bugs are still tracked, but we don't have to create a separate issue for things like a regular expression that should have used a + instead of the * that was already being used. I'd also suggest that the catchall issue not be created for a component/version until it is needed. Thoughts? That strikes me as a bit of an overkill. For example, if you see a variable that can be named a little better or if there's a spelling error then I don't see the need to file a Jira at all. In my opinion Jira is, in addition to a tracking mechanism for what's going into which release, a communication mechanism for developers to announce what they feel needs to be done and who intends to work on it; it's kinda a macroscopic thing. It is also a mechanism for the community to officially make its wishes known as well as the usual bug reporting thing. Mentors? Thoughts? Regards, Alan
Re: VCL, is this name kosher?
On Mar 6, 2009, at 11:03 AM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri March 6 2009 1:09:20 pm Alan D. Cabrera wrote: On Mar 6, 2009, at 7:14 AM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri March 6 2009 9:37:03 am Alan D. Cabrera wrote: So what you are saying is that it doesn't matter what the name, either formal or common, AFS rules require a different name? Correct, our project name has to be different. This is the message I keep hearing (and by hearing, I mean it is how I am interpreting what I read) that doesn't make any sense to me: There must be a name for the project at ASF that isn't used anywhere else in the world for any similar project, and anyone who downloads and installs said project isn't allowed to use the ASF name in any way. That doesn't make sense to me because t's a normal business model to produce software that is to be sold and used by other people /without/ changing the name of the software, in fact, it would generally be considered wrong to change the name. An example similar to ours that I can think of is Blackboard software used for online courses. www.blackboard.com is the site for the company that develops it. If you do a google search for allinurl:blackboard you'll find many sites that have Blackboard installed and actually use blackboard in the URL. You are missing the point. I am not advocating changing the name just for the sake of changing the name. There is a conflict in naming between NCSU VCL and this project. It's that simple. I'm sorry, I'm just not understanding what you're saying - I need you to restate it using different wording rather than just repeating yourself. I don't understand the naming conflict between ASF VCL and NCSU's install of VCL (keep in mind the content at vcl.ncsu.edu will be changed to refer to development of VCL being at ASF and stuff at vcl.ncsu.edu to just be an install of it). It's the name your department name, NCSU VCL, and the name of this incubating project, ASF VCL, that is the problem. They cannot be the same. It doesn't matter if the stuff at the NCSU VCL department is just an installation of the ASF VCL project. It doesn't matter if there's attribution at the NCSU VCL department that they have installed ASF VCL software. There is a naming conflict and that has to be resolved. Umm, there is no NCSU VCL department. There are people from two different groups at NCSU that are involved in development of VCL. The main group being the Office of Information Technology. There is a group within that named Advanced Computing. Aaron, Andy, and I are in that group. There is a completely separate group named Centennial Networking Lab that has a fair amount of interest in VCL as well. Brian and Andrew work for them. Other than the content at vcl.ncsu.edu discussing development of VCL that will be changed to reflect development being done at ASF, the only thing - organizational unit or otherwise - at NCSU that exists using the name VCL is the installation of this project. Ok, so now we may be making some progress here. When I go to http://vcl.ncsu.edu/ VCL is all over the place. It really gives the impression that there's a lab over at NCSU called VCL. I see Virtual Computing Lab, powered by NC STATE's Virtual Computing Platform. Even if the powered by clause were changed as mentioned in previous posts to: Virtual Computing Lab, powered by ASF VCL I don't see how that would fly. If however, *every* reference to VCL and Virtual Computing Lab were replaced with, say, WolfPack. Then this would definitely work: WolfPack, powered by ASF VCL Are you saying that *all* VCL and Virtual Computing Lab terms will be scrubbed at NCSU? It seems to me, the Blackboard example I gave above exactly matches our situation. If it can work for them, why can it not work for VCL? If you don't think it matches our situation, please clearly state how and why you don't think it matches. It does not match our situation. In your example you have a *single* corporation. In our situation we have two separate institutions, one of them being a non-profit software foundation. The project at the ASF cannot share a name with it's progenitor, an external institution. I mention branding because it's obvious that the NCSU staff is vociferously attempting to keep the branding connection between the NCSU department and the ASF incubator project by keeping the same name, regardless of what that name is. I'm not trying to keep a branding connection between NCSU and VCL. I'm trying to keep a project that's been known by the name VCL for almost 5 years, having had many presentations and papers published about it from having to be renamed to something else that no one has heard of. This is the *only* reason I am interested in keeping the VCL name. There were discussions at NCSU a little while ago about changing
Re: VCL, is this name kosher?
What does VCL stand for then? Regards, Alan On Feb 17, 2009, at 7:35 AM, Brian Bouterse wrote: I wanted to revisit this thread, because no conclusion was reached. The current status is that after much discussion on the list, no name changes were proposed, or ratified. There are ASF naming guidelines located here. Personally, I interpret this as a non-issue because the NCSU service is called the Virtual Computing Lab, and the ASF project name is VCL which is not the same. What do you think? my 2 cents, Brian Brian Bouterse Secure Open Systems Initiative 919.698.8796 On Jan 6, 2009, at 11:18 AM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Maybe we should look at this from a different angle - is there anything that *can* happen for the name to continue as VCL at ASF? Josh On Tuesday January 06, 2009, Alan D. Cabrera wrote: Thanks for your comments Matt. Well, it's after the holidays. Time to pick this thread back up. This issue needs to be resolved before we graduate. Regards, Alan On Dec 19, 2008, at 1:01 PM, Matt Hogstrom wrote: Alan, Thanks for starting the discussion about this. I think there are a few different issues so I'll try to separate them. The issues we need to address is the trademark of VCL and the other is the identity of the community. Perhaps we should talk about these in reverse order. First is the identity of the community. The move of the development for the VCL codebase from NC State to Apache marked the formation of a community outside of NC State. So, what NC State decides to do or not to do is not particularly relevant to the community collaborating at Apache. Given this separation, perhaps a different name is appropriate so their is a clear distinction between NC State's use of VCL and the Apache Incubator's community. As far as the name goes. Since Virtualization and hosting is, well, virtual, perhaps a name like spectre or Casper would be good :) (ya, I already can see the naming police coming). On Dec 19, 2008, at 10:19 AM, Henry E Schaffer wrote: Alan writes: ... If VCL is a trademark owned by NCSU then they would have to assign the trademark to the ASF or we would have to change our project's name. OK - I think we've reached a very clear question to be resolved. I think here's what needs to be resolved (at least in my mind): If VCL is a trademark owned by NCSU, and If NCSU assigns the ownership to the ASF - then would ASF give NCSU permission to continue its web site as is (possibly with an acknowledgement to the ASF)? Alternatively: If VCL is a trademark owned by NCSU, and If NCSU doesn't assign the ownership to the ASF, but gives permission to ASF to use VCL as part of naming this ASF project - could, and would the ASF use AVCL (Apache VCL) as the name? (Or some other formulation which would be an Apache name but clearly portray to users and potential users that it's the same project.) Does the above make sense? -- --henry schaffer - -- - --- 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 pgp.mit.edu -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFJY4RhV/LQcNdtPQMRAtNJAJ9CViggEk5XIPl5DH/Q+cL2JerOoQCbBHsv O7WjXdHQWfQ6B3uUTkTr9+g= =iwnz -END PGP SIGNATURE-
Re: svn commit: r730210 - /incubator/vcl/branches/before-modularized-os/
You've made a good point. Rather than generating the process in an ad hoc fashion, we should whip one up as soon as possible. There are no standard development processes in the ASF. There are rules about releases and what can go into them. The ASF likes to let projects define the specifics how they want to work. There are, however, guiding principles that influence how projects define their process. The top priority is building and maintaining community. This priority takes precedence over everything else. It can be frustrating at times and this is usually the hardest for new projects to grok. But it is so important that building and maintaining community takes equal weight in the eyes of the Incubator PMC to code base vetting. So important that this is the usual reason that incubated projects take longer than expected to graduate or, worse, are withdrawn. So with that in mind, here's a phrase that has me worries We have a lot of work/submissions over the next couple of months. There's been no discussion on this list about architectural/feature additions and modifications. This worries me. We're not a SourceForge where code can be developed externally then dumped into our repositories when it's done. With that said, I invite the current project team to come up with a development process that makes planning and development transparent. You should be thinking of ways to get more members of the community involved in this project. Part of this is requiring architectural and development conversations in public on this list. Simply posting roadmaps and Jira issues won't do. You should not be having development meetings at your office as you previously have done. It precludes involvement of the community. Finally, some tactical advice. Never work on anything unless there's a Jira issue for it. When you check in your code place the Jira issue number in the checkin comment, e.g. VCL-325 added SNMP MIBs to storage management. This allows products such as Fisheye to index the two together. Road maps are great. Architectural diagrams are great. Creating Jira issues for everything that you will do or want to do is great. It allows people to volunteer to pick up work or offer to help. I will remind you that community is the raison d'etre for VCL being here. This means that no person owns a chunk of technology. If a person is working on a a corner of this project and someone else wants to help that person must be accommodating and share the work; there is no such thing as dibs on an area of architecture. Whew! That's a lot of words to swallow. Thanks for sticking with us so far! Regards, Alan On Jan 6, 2009, at 6:02 AM, Aaron Peeler wrote: Alan, Could you define the process for checking in new code, modifications, or bug fixes. This is the first we've seen or heard of having to add Jira issue numbers. Also, we've not found anything yet in the Apache guides which defines this process, so if you have any links, please forward them. We're willing and wanting to do this right but we would like to know the specific process. We have a lot of work/submissions over the next couple of months, so if we could get the process nailed down on our end that will save a lot of time and reduce the frustration on changing our work habits. Regards, Aaron --On January 5, 2009 4:30:44 PM -0800 Alan D. Cabrera l...@toolazydogs.com wrote: Andy, I'm seeing more checkins w/out Jira issue numbers in them. Would you mind making sure that everything on your plate has a Jira issue and that all your checkins have their corresponding Jira # in the checkin comments? Regards, Alan On Dec 30, 2008, at 12:10 PM, Andy Kurth wrote: Hi Alan, This is to add management node support for Windows Vista. I have been working on getting VCL to support Vista and it's now in a working state. We will use Vista as a proof of concept for the OS modularization design since its initial use will be minimal. OS modularization is an extension to the major changes made from version 1.x to 2.0. Prior to 2.0, calls to interact with different components which VCL utilizes or supports were intermingled throughout the code and controlled by if/else statements. This made the task of adding support for additional components difficult. Starting with version 2.0, we modularized the parts of the code which interact with the provisioning engines. We use the term provisioning engine to mean the systems which can perform the basic tasks to prepare a machine. The provisioning engines currently supported are xCAT 1.3, VMWare, and an interface to utilize NCSU's Solaris lab machines when the labs are closed. Each provisioning engine module, xCAT.pm for example, implements a common set of generically-named subroutines. These are called by the core VCL modules such as new.pm or image.pm. Also for version 2.0, the predictive
Re: VCL, is this name kosher?
Thanks for your comments Matt. Well, it's after the holidays. Time to pick this thread back up. This issue needs to be resolved before we graduate. Regards, Alan On Dec 19, 2008, at 1:01 PM, Matt Hogstrom wrote: Alan, Thanks for starting the discussion about this. I think there are a few different issues so I'll try to separate them. The issues we need to address is the trademark of VCL and the other is the identity of the community. Perhaps we should talk about these in reverse order. First is the identity of the community. The move of the development for the VCL codebase from NC State to Apache marked the formation of a community outside of NC State. So, what NC State decides to do or not to do is not particularly relevant to the community collaborating at Apache. Given this separation, perhaps a different name is appropriate so their is a clear distinction between NC State's use of VCL and the Apache Incubator's community. As far as the name goes. Since Virtualization and hosting is, well, virtual, perhaps a name like spectre or Casper would be good :) (ya, I already can see the naming police coming). On Dec 19, 2008, at 10:19 AM, Henry E Schaffer wrote: Alan writes: ... If VCL is a trademark owned by NCSU then they would have to assign the trademark to the ASF or we would have to change our project's name. OK - I think we've reached a very clear question to be resolved. I think here's what needs to be resolved (at least in my mind): If VCL is a trademark owned by NCSU, and If NCSU assigns the ownership to the ASF - then would ASF give NCSU permission to continue its web site as is (possibly with an acknowledgement to the ASF)? Alternatively: If VCL is a trademark owned by NCSU, and If NCSU doesn't assign the ownership to the ASF, but gives permission to ASF to use VCL as part of naming this ASF project - could, and would the ASF use AVCL (Apache VCL) as the name? (Or some other formulation which would be an Apache name but clearly portray to users and potential users that it's the same project.) Does the above make sense? -- --henry schaffer
Re: VCL 2.1 goals
For the Wiki you have to add your own account. Regards, Alan On Dec 19, 2008, at 12:54 PM, Brian Bouterse wrote: I went to add content to the wiki, but it says my account 'bmbouter' isn't active (nor any accounts tied to bmbou...@ncsu.edu). I'm listed as a committer on the VCL incubator; does anyone know how I can see the status on my account? Best, Brian Brian Bouterse Secure Open Systems Initiative 919.698.8796 On Dec 19, 2008, at 12:23 PM, Alan D. Cabrera wrote: Wiki is up! :) http://cwiki.apache.org/confluence/display/VCL/Index Regards, Alan On Dec 19, 2008, at 6:40 AM, Aaron Peeler wrote: Until the wiki is up, below is a list of goals for VCL 2.1. Some are done or in progress and marked as such. 1. xCAT 2.0 module * testing 2. Get rid of preferredimage from image table, use nextimage instead 3. Clean up data base - removed unused variables 4. Shibboleth support * Testing stage * Need migrate to new web server 5. Web server load balance 6. healthcheck.pl - improve / bring up to date, add support for vms, try to reinstall nodes. 7. Clean up / re-write blockrequest module, planning to use api calls to web site. 8. Modularize OS code 9. Polish cluster reservation process 10. Allow dynamic change of predictive load module - currently have to restart vcld after change in database. * testing, before committing to repos 11. Pull out check_ssh dep - binary from nagios - Done, committed to repos 12. Additional management node configuration web tools. 13. image retrieval between management nodes - allow for defined ssh ports. Store which port in db management node table 14. Add check for existence of image libraries and take appropriate action, in case /install gets dropped for some reason. -A Aaron Peeler OIT Advanced Computing College of Engineering-NCSU 919.513.4571 http://vcl.ncsu.edu
Re: import of v2.0 code
Our new home: http://cwiki.apache.org/confluence/display/VCL/Index Regards, Alan On Dec 18, 2008, at 12:14 PM, Brian Bouterse wrote: Yes, confluence is perfect. I'll be populating the wiki as soon as it's up. I'd install it myself, except I don't have the access to the server hosting the confluence environment. Best, Brian Brian Bouterse Secure Open Systems Initiative 919.698.8796 On Dec 17, 2008, at 10:08 PM, Alan D. Cabrera wrote: I take it that Confluence is ok? Regards, Alan On Dec 12, 2008, at 12:22 PM, Brian Bouterse wrote: Would it be possible for us to get a wiki to start documenting around this code? I am happy to help set it up, but lack the access. Who can I talk to about this? Best, Brian Brian Bouterse Secure Open Systems Initiative 919.698.8796 On Dec 12, 2008, at 2:54 PM, Matt Hogstrom wrote: Great news that the code is flowing. Note that the tags dir by convention is not changeable. I'm short of time so I'd like to as Alan to comment on the procedures for clearing the code and getting it cleaned up in trunk. Looking forward to looking at the code. Thanks On Dec 12, 2008, at 1:31 PM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 All, We've just imported VCL v2.0 code into the ASF subversion repository. We imported it under https://svn.apache.org/repos/asf/incubator/vcl/tags/import and copied from there to tags/VCL-2.0.0 and to trunk. There are several dependencies that still need to be documented on how to setup a fully operational system (things like setting up an image library, configuration setups to manage various provisioning engines - xcat, vmware, standalone unix machines - 3rd party utilities and drivers, etc). We'll be working on that documentation a little next week, but focusing on it more after the Christmas break. Josh, Aaron, and Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFJQq4gV/LQcNdtPQMRAkZOAJ9TI2cYI8WArJo/jaD6fdpDYpk09ACeI2CW lVmivYWWPd3HiRjd9ZGhZ40= =5tnj -END PGP SIGNATURE-
