Re: [ANNOUNCE] Happy Graduation!
Very nice, gratz ... Kevan, thanks to you for goat herding all of the things I can't remember :) On Jun 20, 2012, at 2:04 PM, Kevan Miller wrote: All, The ASF Board has approved the resolution to establish Apache VCL as a top-level ASF project. Congratulations to all! --kevan signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [VOTE] Andy Kurth as PMC chair after graduation
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 signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Graduation
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. Matt Hogstrom m...@hogstrom.org A Day Without Nuclear Fusion Is a Day Without Sunshine On May 8, 2012, at 11:01 AM, Kevan Miller wrote: signature.asc Description: Message signed with OpenPGP using GPGMail
Graduation Thoughts
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? Matt Hogstrom m...@hogstrom.org A Day Without Nuclear Fusion Is a Day Without Sunshine
Re: code contribution licensing question
Kevan alluded to this, is your employer familiar with the ASL v2.0 ? Perhaps a quick review by the legal team would alleviate any concerns on your employers part. Also, Apache does not really recognize corporations as contributing code (apart from a corporate contribution which is generally more substantial than patches) so your work is considered as an individual. That said, you need to work out what you do on your time and if its acceptable with your employer. On Jan 18, 2011, at 3:31 PM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday January 12, 2011, Josh Thompson wrote: On Tuesday January 11, 2011, Noah Baker wrote: Hello, my question is for any licensing experts on the list. I would like to contribute code/fixes to the VCL project, but my employer prevents me from signing the ICLA. The only FOSS license I can release code under is the modified/new BSD license. I am wondering if there is any way for me to contribute code to VCL under this restriction. I have noticed that VCL's web front end code contains a distribution of Dojo, which is BSD (or AFL) licensed, and there are several other components with different licensing requirements in, or otherwise required by, the project. The code I would most like to contribute is highly self-contained (a full-featured KVM provisioning module with power_* functions, uses OS functions, etc). Could it be released separately under a BSD license and somehow included or merged into VCL? What about for other, less self-contained code, such as fixes? Thanks, and please forgive my licensing ignorance; I'm a dev, not a lawyer. Noah Baker Can anyone from the legal list answer these questions? Thanks, Josh Thompson Apache VCL Kevan's response reminded me I needed to forward the answers from the legal list. Here they are: - -- Forwarded Message -- Subject: Re: code contribution licensing question Date: Thursday January 13, 2011, 1:22:08 am From: Jennifer O'Neill jennifer...@gmail.com To: legal-disc...@apache.org The purpose of having all committers sign the ICLA is so that all Apache code is licensed uniformly and ASF is better protected if there's a challenge to the ownership of the IP. If a developer wishes to contribute some material amount of code but can't sign the ICLA, then his/her code contribution is evaluated just like any other third-party code licensed under terms other than the ASL v.2.0. I assume that by the modified BSD, you mean the newer version that excludes the advertising clause. This license is compatible with the ASL v.2.0 and there are certainly a number of Apache projects with dependencies on BSD-licensed code. Ultimately, though, it is up to the VCL project committers whether to use any third-party code. If a developer wants to contribute a patch or bug fix through Bugzilla or the developers' mailing list, both of those forums require that the developer first electronically agree that ASL v.2.0 will apply to the submission. Cheers, Jennifer - - - -- Forwarded Message -- Subject: Re: code contribution licensing question Date: Thursday January 13, 2011, 11:14:06 am From: Sam Ruby ru...@intertwingly.net To: legal-disc...@apache.org On Thu, Jan 13, 2011 at 1:22 AM, Jennifer O'Neill jennifer...@gmail.com wrote: The purpose of having all committers sign the ICLA is so that all Apache code is licensed uniformly and ASF is better protected if there's a challenge to the ownership of the IP. If a developer wishes to contribute some material amount of code but can't sign the ICLA, then his/her code contribution is evaluated just like any other third-party code licensed under terms other than the ASL v.2.0. I assume that by the modified BSD, you mean the newer version that excludes the advertising clause. This license is compatible with the ASL v.2.0 and there are certainly a number of Apache projects with dependencies on BSD-licensed code. Ultimately, though, it is up to the VCL project committers whether to use any third-party code. I'd like to draw attention to Jennifer's use of the word 'dependency' here. I agree: if VCL wanted to have an external dependency on a BSD-licensed KVM provisioning module then this would be no problem if the dependency was documented properly. 'Including' or 'merging' is a different matter entirely. One of the reasons for the ICLA is that section 3 makes an explicit grant of all of the necessary patent licenses that the Contributor may have on the combination of this code with the project to which they are contributing. Section 4 clarifies this with respect to individuals who have employers. The net of this is that 'including' or 'merging' of such code is not something that we would routinely allow. That is not to say that it can't be done -- if you look around you will find
Re: [VOTE] release VCL 2.2 - voting based on RC2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 +1 On Sep 24, 2010, at 11:44 AM, Kevan Miller wrote: Here's my +1. Signature/Checksums look good. Source and LICENSE looks good. One minor note: the NOTICE file contains: Copyright 2009 It's not required, but in the future, we probably want that to be Copyright 2009-2010 --kevan On Sep 22, 2010, at 6: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- -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) iEYEARECAAYFAkyc/k8ACgkQy66+OaRsTKEn/ACaAyRvmSmbiXF2km5h+tOcsTDJ 4+sAoMiiRHTT0l/QkE2UXo1NH7mcVZyW =TyPC -END PGP SIGNATURE-
Re: [mentors] guidelines for contributing large modifications
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-
Re: Incubator PMC/Board report for February 2010 (VCL Developers vcl-dev@incubator.apache.org)
concur On Feb 5, 2010, at 2:27 PM, Alan D. Cabrera wrote: 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- Matt Hogstrom m...@hogstrom.org A Day Without Nuclear Fusion Is a Day Without Sunshine
Graduation ... things to consider
There was a short discussion on the private list about graduation but this is a general topic for the community so I'm starting this thread in dev. VCL has been cooking for a little over a year and although we're not really ready to graduate its timely to start considering what people will be looking for to support a movement from Incubator to a Top Level Project (TLP). - Community Diversity This is a really significant area that will receive some attention. Apache wants the communities to thrive independent of the contribution of any single entity. In this case, the bulk of the commits and community are from NC State. There seems to be a lot of interest in consuming VCL by universities ... are there universities that students at other universities, companies or hobbyists that would be interested in contributing? How can we reach them? - Releases There is one release that was voted on. I think a few more would be good. Perhaps a release a quarter or six months ? Also, we should probably update the Wiki so people have a link on how to find the release. Those are the two big things off the top of my head. Perhaps one way to get other people interested in VCL would be to think about offering some of the internal components of VCL as consumable units in other projects. A lot of projects are looking at how to do reservations, package images and things like that. Perhaps some increased granularity would pull in more developers and contributors. Matt Hogstrom m...@hogstrom.org A Day Without Nuclear Fusion Is a Day Without Sunshine
Re: [mentors] CLA and accepting patches from the community
The normal way this is done is by having someone to submit an ILCA (http://www.apache.org/licenses/icla.txt). This makes it clear that their contributions are intended to be licensed appropriately and clarifies legally their intent. After that, they should submit patches to the project via JIRA so the code is open and transparent and has a clear chain of ownership. The project committers should vet new entries periodically (with the appropriate number of nag notes by the contributor if its sitting for a while). After reviewing the code and implementing it the committer would let the contributor know. After sustained contribution (project defined but probably several commits to demonstrate commitment and consistency) they can be nominated as a new committer. Normally, the PMC would make a recommendation for a new committer and vote on the private thread. If the PMC votes them in then they get notified. Of course this is something the project would need to discuss and decide on how they want to do this. On Dec 9, 2009, at 9:55 AM, Kevan Miller wrote: On Dec 8, 2009, at 10:36 AM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 How does it work (legally) for someone in the community to submit a patch? I've always viewed the process for someone to become a committer to be that they must first submit some code indirectly (meaning, an existing committer vets it and then checks it in to source control). After a few rounds of submitting code that way, the person can be approved by the community as a new committer (at which point they submit a CLA and gain write access to source control). Hi Josh, Different projects can have different ground rules for what they look for in new committers. Typically, a community will look for contributions from an individual, before considering to invite them to become a committer. You can submit a CLA to the ASF at anytime. You don't have to be invited to become a committer first. However, how do we know that the code they submit indirectly is clear of copyright and license restrictions? Is it up to the committer that actually checks it in to verify it is clear? If so, how do we go about verifying that? Patches submitted by a contributor should grant the ASF permission to apply the Apache License to their work. Contributors should only do this if they created the patch and they hold the copyright to the code. Having a CLA on file is also helpful in clarifying this... There's a radio button on Attach Files in Jira for this very purpose: Grant license to ASF for inclusion in ASF works (as per the Apache License) Contributions intended for inclusion in ASF products (eg. patches, code) must be licensed to ASF under the terms of the Apache License. Other attachments (eg. log dumps, test cases) need not be. In general, the expectation is on the contributor. If the committer suspects there is a problem (e.g. the contributor does not hold the copyright or that the code may have license restrictions), then this is something that the committer (and other project members) should investigate. --kevan Matt Hogstrom m...@hogstrom.org A Day Without Nuclear Fusion Is a Day Without Sunshine
Missing e-mail ?
Andy Rindos contacted me today and said there were some things people had asked me for but hadn't heard back. I'm checking my e-mail client to see if its been eating e-mails. While I do that, if there was something specific I was supposed to do, etc. Ping me and I'll follow it up. I'll search through the archives. Release related perhaps ?
Re: Mentors: health of project/community?
I've been out of band most of May due to some work commitments and I'm catching up. Apart from the name thing it looks like the dev list is increasing in activity and there are some good discussions / collaboration going on. I'm sorting through the thread so I may run into a note on this but I think a release is needed. I saw sometime back that Brian had released something outside of the Apache process. I expect it was to show something off and it was faster than getting a whole release done. Getting the 1.0 release out will help build the community as it will then be Apache VCL 1.0 which will bring people here. On May 19, 2009, at 11: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: Apache Board Report Due
No, you didn't miss anything. My brain was still on the monthly reporting schedule. My bad. On Apr 8, 2009, at 12:59 PM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to http://wiki.apache.org/incubator/ReportingSchedule and http://wiki.apache.org/incubator/FrontPage I didn't think our report is due until May 13th. Did I miss something? Thanks for bringing it up. Josh On Wednesday April 08, 2009, Matt Hogstrom wrote: Any volunteers to bring this together ? - -- - --- 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) iD8DBQFJ3NfZV/LQcNdtPQMRAhGOAJ9QVJMb6jWgQvVuDMhIPlHyvweudQCfTzfV IUDfDl0Bg3c/zNz+6zTM67U= =yPkd -END PGP SIGNATURE-
Re: CLA committers group for official documentation
Prolly not. I'll set up a group. On Apr 9, 2009, at 2:34 PM, Aaron Peeler wrote: Mentors, Is there a confluence user group of committers who have signed the cla? We'd like to start working on the official documentation and need to restrict editing. According to FAQ at http://cwiki.apache.org/CWIKI/ We need to restrict the official documentation space to the committers that have signed the CLA. Aaron
Re: VCL Appliance
Where is the download originiating from ? I assume this is not a build of VCL made from the Incubator since we have not released one yet. Is this from NCSU ? On Apr 6, 2009, at 4:40 PM, Mark Gardner wrote: I have been unable to download the VCL appliance. The torrent appears to not have any seeders and the http link appears to be broken. How do I download it? -- Mark Gardner --
Re: catchall JIRA issue for really minor changes
The process for the community is a community decision. There is no requirement on the Apache side. I think the right balance will vary on project. I agree with Alan's assessment. On Mar 27, 2009, at 10:55 AM, Aaron Peeler wrote: ok thanks. This makes sense. Some of us were (I know I was) under the impression we needed to tag a jira issue with every commit - no matter how big or small the changes. This makes it easier for the small typo changes. Thanks, Aaron On Thu, 26 Mar 2009, Kevan Miller wrote: On Mar 25, 2009, at 11:26 AM, Alan D. Cabrera wrote: 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? Totally agree. --kevan
Re: VCL, is this name kosher?
I think that this link hilights the issue. http://vcl.ncsu.edu/news/general-announcements/new-vcl-website-launched The project at NCSU is sen as being powered by the NC State Computing Platform. There is clearly more of a tie between the name of the project and its roots. Quite honestly, this can be word smithed in any number of ways but the relationship exists. Using Alan's example with a situation that I'm quite familiar with is the reltionship between Apache Geronimo and IBM's version which was called WebSphere Community Edition. It would certainly not be appropriate for IBM to call it WebSphere Geronimo Version. Apache owned the brand Geronimo and IBM, or anyone else for that matter, was free to do with the code what they wanted. It is far easier for the project here to change its name than it is to impose changes on NC State and it would not be appropriate for Apache to suggest or even try and do so. When the project is successful, it should be on its merits and keeping a sense of genealogy is fine, people will know it by its new name. On Mar 6, 2009, at 2:39 PM, Henry E Schaffer wrote: I share in Josh's puzzlement. Since we don't have and never have had a VCL Department, do we need to start one and then close it down? What we have is software which we call VCL, and this is reflected in the documentation and the URL to use our production system (vcl.ncsu.edu). At NC State we use a piece of software which we call Apache HTTP Server. This name is the same as the ASF project. We're not the only organization which does this. Ditto for other suftware, e.g. Tomcat. But using software is different than naming products. Not a good example. So I don't understand the following quoted material is consistent with our situation. There must be a name for the project at ASF that isn't used anywhere else in the world for any similar project, since we don't (now) have any VCL project except for the ASF one. This is a debateable point ... see the URL above. and anyone who downloads and installs said project isn't allowed to use the ASF name in any way. If ASF name means the name of our project at ASF, then for the other projects, how can people say they are running Apache HTTP Server or Tomcat? This isn't about use, its about branding. If ASF name means the name of the Foundation then there is the same conflict when people say they are running Apache HTTP Server or Tomcat. Am I missing something? --henry schaffer
Monthly Incubator Report - Late
I was reminded today that were missing the Incubator Status report for VCL. In the past I was doing this as the community was forming and I think the time has come to ask if someone from the more active community will take on this responsibility. Its basically pretty simple. About a week before the report is due pull together a strawman report on the Wiki and ask for people's input. What we're communicating up is a short set of detail on community related issues (new committers, etc.) and what we got done. Its fairly simple and straightforward. Despite the fact we're late we still need to get a report in and we should hilight that we're refining the process to be more timely. Any volunteers for this month ? Matt
Re: VCL developer call Thurs (2/5) from 1-3 PM
I saw Kevan's note (he pinged me and let me know what a great mentor I am :-P) First off, conference calls are not taboo. Some people work better via phone than they do with e-mail. And, often times it is faster to vet ideas via the phone. That said, it may not work for all people so this is a community decision and, as Kevan points out, can be problematic for folks. Consider a world wide community with people in multiple timezones. Ironically, I just finished a work related conference call with some colleagues in China; I scheduled it in the PM our time so it would be early morning their time. I'd go ahead with the call and see who can make it. Heck, your phone number is now Googleable which is kind of nice :) Take lots of notes and make sure to post the results back to the list so people can read what happened and comment. The fact that you posted the time and the meeting and what you wanted to discuss on the list is excellent. I'd be concerned if I saw an e-mail that said something like, We met over at NC State yesterday and decided that ... That would definitely not be good; decisions are made via e-mail with community input. Apache Geronimo had a spot of confusion a couple of years ago when a number of committers met at Java One and the meeting location and time we're not well communicated. One thing that is a good indicator of communication is the number of commits relative to the number of e-mails on vcl-...@. No hard and fast thing here but in general the amount of communication on the list is relative to the number of e-mails. I've seen some results of people doing a little analysis on that. Other thoughts from devs are welcome. Matt On Feb 3, 2009, at 4:55 PM, Brian Bouterse wrote: I'd like to have a VCL developers call, where the following agenda can be discussed with the community. If you'd like to join the discussion, it will be from 1-3pm EST on Thurs Feb 5th. To join, dial in to 919.515.7151. I apologize for the late notice; my invite a few days ago never made it onto the list. If you're reading this, my e-mail subscription problem has been resolved. Tentative Agenda (this gets us started, please add): 1) Update of the ESX provisioning module 2) Update of the OS modularization effort 3) Possibility of using NX as a connection protocol 4) insert your agenda item here
Incubator Statsus Report for VCL - January 2009
I updated this today. Next month we'll start earlier. http://wiki.apache.org/incubator/January2009
Happy New Year -- and what resolutions / plans do we have?
I wanted to kick start a conversation about some plans for this year to get people's blood flowing and brains coming out of the Christmas holiday time. I'm curious to get a levelset on the code status, 2.1 plans, Wiki ideas etc. I'm going to be updating the Incubator web sites this week and starting to figure out my plans for time investment so I'd like to hear what others are thinking.
Re: VCL, is this name kosher?
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
