Re: Incubator PMC/Board report for Nov 2012 ([ppmc])

[Michael MacFadden]

I also have the wave report ready to go, but I don't seem to be able to
edit the wiki page.

Can I please be added.  My username is: MichaelMacFadden

On 11/1/12 9:54 AM, "Marvin"  wrote:

>* 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/November2012
>
>Note: This manually populated. You may need to wait a little before this
>page is
>  created from a template.



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: "Obfuscating' 3rd party jars

[Michael MacFadden]

Benson,

Yes, Angus had been working this issue for us and found a few third party
Jars.  Here is an extract from his email:

--
There's a couple of things going on at once at the moment:
-i'm in contact with the libIDN author, who is happy to release the
software under the Apache license, which means we can keep using that once
a new release comes out
-the other two libraries junit and emma both think the best option is to
obfuscate the code somehow like ant, if anyone has any experience in doing
it speaking up would be greatly appreciated
---


Apparently, there is some precedent for obfuscating third party jars.  My
assumption is that something about the license views distributing Java
jars as being akin to a source distribution do to the ease of
decompilation.

Angus, 

Can you she some light on this?

~Michael

On 12/3/12 12:54 PM, "Benson Margulies"  wrote:

>Dear Wave,
>
>I don't understand the remark in your report about the need to
>'obfuscate' third party jar files. Could you please elaborate? Do you
>have problems with dependencies with incompatible licenses, or
>something else?
>
>Thanks,
>Benson
>
>-
>To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>For additional commands, e-mail: general-h...@incubator.apache.org
>



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: "Obfuscating' 3rd party jars

[Michael MacFadden]

Benson,

I agree.  There was some progress in mavenizing the build.  I suspect that
that solution will take some time.  The build process is somewhat
complicated at the moment, if this is the long term solution, we may need
to do something simpler to start off with.

In the case of Junit, we should probably be able to remove it from a
binary release.  There is no reason to include it in my mind since it's
only used during the build.  Not sure on emma.  Regardless a temporary
work around would be to remove them and simply required the users to
download them.  We could even provide a simple script to do that.

~Michael



On 12/3/12 3:45 PM, "Benson Margulies"  wrote:

>On Mon, Dec 3, 2012 at 4:39 PM, Michael MacFadden
> wrote:
>> Benson,
>>
>> Yes, Angus had been working this issue for us and found a few third
>>party
>> Jars.  Here is an extract from his email:
>>
>> --
>> There's a couple of things going on at once at the moment:
>> -i'm in contact with the libIDN author, who is happy to release the
>> software under the Apache license, which means we can keep using that
>>once
>> a new release comes out
>> -the other two libraries junit and emma both think the best option is to
>> obfuscate the code somehow like ant, if anyone has any experience in
>>doing
>> it speaking up would be greatly appreciated
>> ---
>>
>>
>> Apparently, there is some precedent for obfuscating third party jars.
>>My
>> assumption is that something about the license views distributing Java
>> jars as being akin to a source distribution do to the ease of
>> decompilation.
>
>I cannot think of any reason why any Apache project should be
>concerned with obfuscation or decompilation. We are open source, and
>our dependencies are open source. Junit is a testing tool, so you
>should never need to redistribute it, just arrange to have it
>available for builds, and maven or ant/ivy will do that, and the same
>with emma, which is another development tool.
>
>There are many examples of this at other project. If it would be
>helpful, I could join the dev list to help with the discussion here.
>
>
>
>>
>> Angus,
>>
>> Can you she some light on this?
>>
>> ~Michael
>>
>> On 12/3/12 12:54 PM, "Benson Margulies"  wrote:
>>
>>>Dear Wave,
>>>
>>>I don't understand the remark in your report about the need to
>>>'obfuscate' third party jar files. Could you please elaborate? Do you
>>>have problems with dependencies with incompatible licenses, or
>>>something else?
>>>
>>>Thanks,
>>>Benson
>>>
>>>-
>>>To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>>For additional commands, e-mail: general-h...@incubator.apache.org
>>>
>>
>>
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>
>-
>To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>For additional commands, e-mail: general-h...@incubator.apache.org
>



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Wave 0.4 based on RC3

[Michael MacFadden]

Joe,

Thanks for your comments. Can you clarify for us the PPMC comment. I think we 
are a bit confused between the concepts of a top level project PMC, the 
incubator IPMC, the PPMC you have mentioned, and piddling mentors. I don't 
think we had ever discussed nominating a PPMC assuming that first p stands for 
podling. 

I think we were under the inkers soon that the mentors were the management 
committe for the podling. Is there a good document on this somewhere?

~Michael

On Jun 20, 2013, at 5:01 PM, Joe Brockmeier  wrote:

> I should have added: please do address the problems here and re-roll and
> I will be sure to examine that release in a timely fashion. Don't let a
> -1 discourage you, as most incubating projects have to go through a
> learning curve. 
> 
> On Thu, Jun 20, 2013, at 06:59 PM, Joe Brockmeier wrote:
>> Hi Ali, 
>> 
>> Comments inline. 
>> 
>> On Sat, Jun 15, 2013, at 05:24 PM, Ali Lown wrote:
>> 
>>> The result from the wave-dev vote can be found at:
>>> https://mail-archives.apache.org/mod_mbox/incubator-wave-dev/201306.mbox/%3CCABRGrVfPOwN3E8N-uScruYbxdezpfZzAJHMp8dN%2BUfpF6s%2BDGw%40mail.gmail.com%3E
>> 
>> I find this slightly confusing as I expected at least 3 PPMC votes, but
>> I guess Wave has opted for the committer == PPMC model? 
>> 
>>> Wave 0.4 RC3 artefacts are available at:
>>> https://people.apache.org/~al/wave_rc/0.4-rc3/
>>> Note: The checksums are SHA-512's
>> 
>> A couple of things:
>> 
>> - Preferably, you'd only include *one* set of artifacts to vote on. Am I
>> voting on the zip, the bz2? I'm uncomfortable voting without checking
>> out all the source releases as I have no way of knowing that the zip ==
>> the bz2 release without inspecting both.
>> 
>> - Preferably, there'd be no binary release in the artifacts you're
>> asking to have voted on. Convenience binaries are fine, but they're not
>> an official release, so it'd be better not to include them with the
>> files we're meant to be voting on. 
>> 
>> - I have to -1 this as there are several binary (.jar) files included in
>> the release that don't belong in a source release. (under
>> third_party/codegen/*) 
>> 
>> Best,
>> 
>> jzb
>> -- 
>> Joe Brockmeier
>> j...@zonker.net
>> Twitter: @jzb
>> http://www.dissociatedpress.net/
> 
> 
> Best,
> 
> jzb
> -- 
> Joe Brockmeier
> j...@zonker.net
> Twitter: @jzb
> http://www.dissociatedpress.net/
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [PROPOSAL] Accept Wave for incubation

[Michael MacFadden]

The lightwave project I was referring to is over at google code:

http://code.google.com/p/lightwave/

~Michael 

On Nov 24, 2010, at 12:44 AM, Marcel Offermans wrote:

> On 24 Nov 2010, at 4:29 , Michael MacFadden wrote:
> 
>> I agree, there are other wave implementations popping up, some of which 
>> include "wave" in the name and some don't.  "Lightwave" for example is one 
>> such project.  I think that Apache Wave and the Wave in a Box product should 
>> be fine.
> 
> Lightwave? http://www.newtek.com/lightwave/
> 
> Greetings, Marcel
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

Re: [VOTE] Accept Wave into the incubator

[Michael MacFadden]

+1 (non-binding)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept Wave into the incubator

[Michael MacFadden]

to the US Navy's usage of wave, startups
>> in
>>> the wave ecosystem, and many independent individuals.
>>> 
>>> == Alignment ==
>>> 
>>> The developers of WIAB want to work with the Apache Software Foundation
>>> because Apache has proven to provide a strong foundation with good
>>> infrastructure and support for developing projects in an open community.
>> As
>>> WIAB continues to grow, the community will look to both reuse available
>>> Apache projects as well as look for opportunities to contribute back to
>> the
>>> larger Apache community.
>>> 
>>> = Known Risks =
>>> 
>>> == Orphaned products ==
>>> 
>>> Wave is a new means for communication, and thus it is still maturing.
>> While
>>> the initial implementation (Google Wave) did not gain sufficient traction
>>> for it to continue as a standalone Google product, there are other
>> related
>>> projects (e.g. Novell Vibe, SAP StreamWork), and several startups in the
>>> space that are continuing to build on the technology. In addition, the US
>>> Navy has contracted with four companies as part of evaluating using wave
>>> technology on every ship. The community itself is still growing, with
>>> several new contributors recently added.
>>> 
>>> == Inexperience with Open Source ==
>>> 
>>> The initial committers have varying degrees of experience with open
>> source
>>> projects. Many from the community are familiar with open source.
>>> 
>>> == Homogeneous Developers ==
>>> 
>>> The initial set of developers does include many from Google. However, the
>>> project has accepted many patches from independent individuals, and some
>>> have already gained committership. Several companies have expressed
>> interest
>>> and forty individuals participated in the Wave Summit.
>>> 
>>> == Reliance on Salaried Developers ==
>>> 
>>> Following Google's change of focus for Wave in August, some of Wave's
>> Google
>>> developers have chosen to continue working on Wave, but it is imperative
>>> that we continue to grow the community larger in the coming months.
>>> 
>>> == Relationships with Other Apache Products ==
>>> 
>>> We currently use the following libraries from Apache
>>> * Commons CLI
>>> * Commons Codec
>>> * Commons HttpClient
>>> * Commons Logging
>>> * Velocity
>>> * Ant
>>> 
>>> We've also contributed the Wave Gadget implementation into the Apache
>>> Shindig project.
>>> 
>>> = Documentation =
>>> 
>>> Entry point for documentation of all the specs and designs.
>>> http://waveprotocol.org/
>>> 
>>> Wave Robots API
>>> http://code.google.com/apis/wave/extensions/robots/
>>> 
>>> Wave Gadgets API
>>> http://code.google.com/apis/wave/extensions/gadgets/guide.html
>>> 
>>> = Initial Source =
>>> 
>>> The initial source will come from
>>> http://code.google.com/p/wave-protocol/source/browse/. This consists of
>> the
>>> Java code necessary for the client and server. These are already open
>> source
>>> repositories licensed under the Apache Public License.
>>> 
>>> = Source and Intellectual Property Submission Plan =
>>> 
>>> Beginning with the initial unveiling, Google published a liberal patent
>>> license:
>>> 
>>> Subject to the terms and conditions of this License, Google and its
>>> affiliates hereby grant to you a perpetual, worldwide, non-exclusive,
>>> no-charge, royalty-free, irrevocable (except as stated in this License)
>>> patent license for patents necessarily infringed by implementation of
>> this
>>> specification. If you institute patent litigation against any entity
>>> (including a cross-claim or counterclaim in a lawsuit) alleging that the
>>> implementation of the specification constitutes direct or contributory
>>> patent infringement, then any patent licenses for the specification
>> granted
>>> to you under this License shall terminate as of the date such litigation
>> is
>>> filed.
>>> 
>>> http://www.waveprotocol.org/patent-license
>>> 
>>> == Trademarks ==
>>> 
>>> Google retains all rights to the trademarks "GOOGLE WAVE" and the wave
>>> design logo, neither of which will be used in the Apache Wave project.
>>> 
>>> = External Dependencies =
>>> 
>>> In addition to the previously mentioned Apache dependencies, the initial
>>> code relies on the following libraries that have Apache compatible
>> licenses:
>>> 
>>> antlr, aopalliance, asm, bouncycastle, cglib, dom4j, emma, gson, guava,
>>> guice, gwt, gxp, hamcrest, jackson, jdom, jetty, jline, jmock, joda_time,
>>> jsr305, junit, libidn, mockito, mongo-driver, oauth, protobuf,
>>> protobuf-format-java, protostuff, stringtemplate, websocket, whack, xpp3
>>> 
>>> = Cryptography =
>>> 
>>> We use standard crypto library methods available in java.security.*. Wave
>>> federation plans to uses encryption for sending deltas to remote Wave
>>> servers.
>>> 
>>> = Required Resources =
>>> 
>>> ==  Mailing lists ==
>>> 
>>> * wave-dev
>>> * wave-commits
>>> * wave-private
>>> 
>>> It is possible that if the project does grown to include many sub project
>>> that we would split the mailing list up by sub project.  Again we have
>>> flexibility.
>>> 
>>> 
>>> == Subversion Directory ==
>>> 
>>> https://svn.apache.org/repos/asf/incubator/wave
>>> 
>>> == Issue Tracking ==
>>> 
>>> Please help us setup a JIRA instance for both issue tracking and code
>>> review.
>>> 
>>> == Other Resources ==
>>> 
>>> * a wiki (for the sites pages) (
>>> http://incubator.apache.org/guides/sites.html or a wiki
>>> http://wiki.apache.org/incubator/)
>>> * code review on reviews.apache.org
>>> * a server to run a dogfood instance
>>> * continuous build bot
>>> 
>>> = Initial Committers =
>>> 
>>> * Alex North (Google)
>>> * Anthony Watkins (SESI)
>>> * Christian Ohler (Google)
>>> * Dan Danilatos (Google)
>>> * Dan Peterson (Google) / dpeter...@apache.org
>>> * David Hearnden (Google)
>>> * David Wang (Google)
>>> * Ian Roughley (Novell) / rough...@apache.org
>>> * James Purser
>>> * Joseph Gentle
>>> * Lennard de Rijk
>>> * Michael MacFadden (Solute)
>>> * Soren Lassen (Google)
>>> * Tad Glines
>>> * Torben Weis (University Duisburg-Essen)
>>> 
>>> = Sponsors =
>>> 
>>> == Champion ==
>>> 
>>> * Paul Lindner
>>> 
>>> == Nominated Mentors ==
>>> 
>>> * Santiago Gala
>>> * Upayavira
>>> * Andrus Adamchik
>>> * Vincent Siveton
>>> * Ben Laurie
>>> 
>>> == Sponsoring Entity ==
>>> 
>>> The Apache Incubator.
>>> 
>> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [RESULTS][VOTE] Wave accepted into the ASF incubator

[Michael MacFadden]

All,

I have volunteered to start the infrastructure set up in the absence of some of 
the Googlers on vacation as Soren mentions.  Hopefully over the next few days 
we'll get some clarity on the actual logistics of becoming a podling in the 
incubator.

I think we will likely start a new thread to figure that out.  I would guess 
that one of the first things we would like to do is to get the mailing lists 
set up so that we can further discuss the organization of the project on a wave 
list.

I am sure the Apache mentors can weigh in here to help us get started.

~Michael


On Dec 3, 2010, at 6:08 PM, Soren Lassen wrote:

> Michael MacFadden has written some ideas here:
> 
> http://www.waveprotocol.org/wave-in-a-box/apache-incubator-roadmap
> 
> FYI, several of us on the Google Wave team are away on vacations in
> parts of the December-January time period, so anything that depends on
> us may move a bit slow for the next month or so.
> 
> Soren
> 
> On Sat, Dec 4, 2010 at 12:55 PM, Matt Richards  wrote:
>> Now that the Vote has been completed.
>> What are the next steps?
>> 
>> On Fri, Dec 3, 2010 at 7:50 PM, Tad Glines  wrote:
>>> 
>>> 2010/12/3 Dan Peterson 
>>>> 
>>>> The 18 binding votes:
>>>> Andrus Adamchik, Ant Elder, Bernd Fondermann, Bertrand Delacretaz, Chris
>>>> A. Mattmann, Christian Grobmeier, Davanum Srinivas, Dave Johnson, Doug
>>>> Cutting, Emmanuel Lecharny, Jim Jagielski, Kevan Miller, Luciano Resende,
>>>> Mark Struberg, Michael McCandless, Ralph Goers, Tim Williams, and Upayavira
>>>> The 8 non-IMPC members who are ASF members:
>>>> Ate Douma, Brett Porter, Leif Hedstrom, Marcel Offermans, Niklas
>>>> Gustavsson, Richard Hall, Santiago Gala, and Vincent Siveton
>>> 
>>> Wow! Did we set some sort of record? I didn't realize that so many ASF
>>> people had voted.
>>> -Tad
>>> 
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "Wave Protocol" group.
>>> To post to this group, send email to wave-proto...@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> wave-protocol+unsubscr...@googlegroups.com.
>>> For more options, visit this group at
>>> http://groups.google.com/group/wave-protocol?hl=en.
>> 
>> 
>> 
>> --
>> --Matt
>> 
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Wave Protocol" group.
>> To post to this group, send email to wave-proto...@googlegroups.com.
>> To unsubscribe from this group, send email to
>> wave-protocol+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/wave-protocol?hl=en.
>> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Wave Incubator Next Steps

[Michael MacFadden]

Wave Mentors,

What are the logistics of boostrapping the Wave Podling?  I assume most of the 
initial committers on the wave project do not have Apache Accounts already.  I 
assume over the next several days we will start that process.  Is there a good 
document that describes the boostraping process, or should we just work with 
you (the mentors), to determine our path?  Thanks for your help.

Sincere Regards,

Michael MacFadden
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Wave Incubator Next Steps

[Michael MacFadden]

Tad,

Thanks.  We had reviewed that page, I suppose what I was looking for was some 
clarity on who would be taking the lead on that and when we should expect to 
start certain activities.

~Michael

On Dec 4, 2010, at 8:22 AM, Tad Glines wrote:

> According to this (
> http://incubator.apache.org/incubation/Incubation_Policy.html#Setting+Up+a+New+Podling),
> once our mentors are added to the IPMC (assuming they where not already
> members), one or more of them will initiate:
> 
>   - the reporting schedule;
>   - the project
> status<http://incubator.apache.org/incubation/Incubation_Policy.html#Ongoing+Activities>
>page;
>   - the mailing lists;
>   - the repository space;
> 
> Also, committers will not be issued accounts until their CLA (either ICLA or
> CCLA) has been received and recorded. Here's the new committers guide:
> http://www.apache.org/dev/new-committers-guide.html.
> 
> -Tad
> 
> On Sat, Dec 4, 2010 at 7:07 AM, Michael MacFadden <
> michael.macfad...@gmail.com> wrote:
> 
>> Wave Mentors,
>> 
>> What are the logistics of boostrapping the Wave Podling?  I assume most of
>> the initial committers on the wave project do not have Apache Accounts
>> already.  I assume over the next several days we will start that process.
>> Is there a good document that describes the boostraping process, or should
>> we just work with you (the mentors), to determine our path?  Thanks for your
>> help.
>> 
>> Sincere Regards,
>> 
>> Michael MacFadden
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Wave Incubator Next Steps

[Michael MacFadden]

Should those of us on the contributor list, just go ahead and get these 
submitted sooner rather than later?

On Dec 4, 2010, at 9:13 AM, Tad Glines wrote:

> On Sat, Dec 4, 2010 at 8:39 AM, Leif Hedstrom  wrote:
> 
>> On 12/04/2010 09:22 AM, Tad Glines wrote:
>> 
>>> 
>>> Also, committers will not be issued accounts until their CLA (either ICLA
>>> or
>>> CCLA) has been received and recorded. Here's the new committers guide:
>>> http://www.apache.org/dev/new-committers-guide.html.
>>> 
>>> 
>> 
>> I'm fairly certain all committers needs to fill out the ICLA, no?
> 
> 
> Yes, I see. Reading this  further I
> see that all have to sign an ICLA, but for some their employer will need to
> submit a CCLA.
> 
> -Tad


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Wave Incubator Next Steps

[Michael MacFadden]

Ralph,

If I understand correctly, an individual could submit an ICLA first and then 
later submit the CCLA if the employer or situation requires it.  Meaning that 
previously submitting an ICLA would not be in conflict with a subsequent CCLA.  
If that is the case I would recommend all of the initial committees for Wave 
get those in as soon as possible. Thanks. 

Regards,
Michael


On Dec 4, 2010, at 10:43 AM, Ralph Goers  wrote:

> 
> On Dec 4, 2010, at 9:13 AM, Tad Glines wrote:
> 
>> On Sat, Dec 4, 2010 at 8:39 AM, Leif Hedstrom  wrote:
>> 
>>> On 12/04/2010 09:22 AM, Tad Glines wrote:
>>> 
 
 Also, committers will not be issued accounts until their CLA (either ICLA
 or
 CCLA) has been received and recorded. Here's the new committers guide:
 http://www.apache.org/dev/new-committers-guide.html.
 
 
>>> 
>>> I'm fairly certain all committers needs to fill out the ICLA, no?
>> 
>> 
>> Yes, I see. Reading this  further I
>> see that all have to sign an ICLA, but for some their employer will need to
>> submit a CCLA.
> 
> It is usually the case that some will want their employer to submit a CCLA 
> rather than need to.  The ICLA is the way an individual states that they have 
> the right to commit the software they contribute.  If during the course of 
> their employment they are called upon to enhance or fix bugs in an Apache 
> project the ICLA is sufficient for them to do that provided they have 
> permission to do so from their employer.  The CCLA protects the individual in 
> that case by explicitly stating the listed individuals have that right. The 
> CCLA is also one way a company can donate software directly to the ASF.  
> There are quite a few companies that don't want to submit a CCLA but will 
> allow their employees to contribute. In those cases it is up to the 
> individual to make sure they are protected should management changes occur, 
> etc.
> 
> Ralph
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Wave Incubator Next Steps

[Michael MacFadden]

All,

Obviously getting the accounts created for the wave committers could take a 
little extra time given the holidays.  Just wondering if we have heard any 
conformation that the process has started, or on the other hand if we have 
missed something procedurally?  Thanks.

Michael

On Dec 23, 2010, at 1:14 AM, Andrus Adamchik wrote:

> I can't see why not forwarding it to Incubator PMC would hold root@ from 
> creating the accounts (I mean, if it is such a big deal, root@ can always 
> forward this message themselves and/or contact me to do it). Anyways, I just 
> forwarded the original request.
> 
> BTW, the original request was sent to root on 12.16, which was "only" a week 
> ago :)
> 
> Andrus
> 
> 
> On Dec 23, 2010, at 1:41 AM, David Crossley wrote:
> 
>> I wondered why the Wave initial committer accounts were not
>> yet set up. The wave-dev list indicates that it seems to be stalled.
>> (Please come to general@ and ask if ever there is a holdup.)
>> 
>> Yes Infra does do it in batches.
>> 
>> However, one reason might be that the request for
>> accounts might not have been done properly.
>> The relevant PMC needs to be Cc too. I don't
>> see any on the Incubator PMC private.
>> 
>> That is because the ASF needs to be a good corporation,
>> follow its procedures and notify the responsible committee.
>> 
>> Hope that helps.
>> 
>> -David
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: ManifoldCF - jars should not be stored in SVN

[Michael MacFadden]

There are additional benefits to dependency management systems like Maven or 
Ivy as well.  Beyond avoiding checking in jar files, you can reference a 
dependency once and not have to proliferate references if you have multi module 
builds (with multiple build files).  Also, if your project gets separated into 
multiple modules, then the build system can actually mange internal 
dependancies.

Of course checking Jars in to SVN is usually simpler in the short term.

~Michael

On Jan 9, 2011, at 4:55 PM, dsh wrote:

> s/way/idea/
> 
> On Mon, Jan 10, 2011 at 1:54 AM, dsh  wrote:
>> Hi,
>> 
>> I'd suggest to consider dependency management systems such as Apache
>> Maven or Apache Ivy as an advantage in the long run. They allow to
>> precisely document your dependencies and both support an offline mode.
>> Additionally both of course provide a very reliable way to define
>> exactly what version of what jars are required and ensure everyone has
>> the same ones.
>> 
>> So don't put the way aside to migrate to a dependency management
>> system as soon as possible.
>> 
>> Cheers
>> Daniel
>> 
>> On Mon, Jan 10, 2011 at 1:46 AM, Alex North  wrote:
>>> The Wave project also has jars in its repository (on its way to Apache SVN).
>>> That seems to be the most reliable way to define exactly what version of
>>> what jars are required and ensure everyone has the same ones.
>>> 
>>> On 10 January 2011 11:16, Grant Ingersoll  wrote:
>>> 
 This seems a bit over the top.  I prefer them in SVN so I can get them all
 at once, which is especially nice when one is working offline.
 
 On Jan 9, 2011, at 5:53 PM, sebb wrote:
 
> I've just noticed that there are lots of jars stored in SVN under
> 
> 
 http://svn.apache.org/repos/asf/incubator/lcf/branches/release-0.1-branch
> 
> AIUI, SVN should not be used for storing library jars.
> 
> ==
> 
> The way other projects manage this is to define the jar dependencies
> in a build file, and get the build process to download the jars.
> 
> If using Maven, this is trivial, as declared dependencies are
> automatically downloaded.
> 
> It's not that difficult when using Ant either - see for example the
> Tomcat or JMeter projects.
> 
> There is also an Ant Maven task:
> http://maven.apache.org/ant-tasks/examples/dependencies.html
> 
> and Apache Ivy
> http://ant.apache.org/ivy/
> 
> though I've not used either of those.
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 
 
 
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
 
>>> 
>> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [Wave] editing incubator documents

[Michael MacFadden]

David,

Thanks for the heads up.  I have been trying to follow said process, however it 
seems like the wave committers have not yet been given that ability to commit 
changes to the incubator SVN.  I have some pending changes to the wave project 
page I have been waiting to check in.

~Michael

On Feb 3, 2011, at 10:02 PM, David Crossley wrote:

> When publishing some Incubator docs (doing 'svn up' on the server)
> i see that someone has made some hard-coded changes to the
> generated html doc for the Wave status page.
> 
> You need to follow this process to make the changes in
> the SVN source files instead, then re-generate, etc.
> http://incubator.apache.org/guides/website.html
> 
> (That is the system until the Incubator switches over
> to use the new CMS.)
> 
> -David
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [Wave] editing incubator documents

[Michael MacFadden]

We have access to the wave SVN, but it seems like we don't have access to the 
incubator SVN.  According to this document:

http://incubator.apache.org/guides/mentor.html#Set+Up+Repository

We should have access to the incubator web site SVN.

I can't actually view the authorization template file it mentions to see if 
that was done, but it appears that it may not have been done.  Either that, or 
there is something specifically wrong with my account.

~Michael

On Feb 4, 2011, at 7:43 AM, Andrus Adamchik wrote:

> Per Feb 2 message from Upayavira on wave-dev 
> (1296637259.12852.1418516...@webmail.messagingengine.com), SVN auth grants 
> are setup for all Wave committers. Not sure if the permissions are extended 
> to the Incubator site?
> 
> Andrus
> 
> On Feb 4, 2011, at 10:31 AM, Michael MacFadden wrote:
> 
>> David,
>> 
>> Thanks for the heads up.  I have been trying to follow said process, however 
>> it seems like the wave committers have not yet been given that ability to 
>> commit changes to the incubator SVN.  I have some pending changes to the 
>> wave project page I have been waiting to check in.
>> 
>> ~Michael
>> 
>> On Feb 3, 2011, at 10:02 PM, David Crossley wrote:
>> 
>>> When publishing some Incubator docs (doing 'svn up' on the server)
>>> i see that someone has made some hard-coded changes to the
>>> generated html doc for the Wave status page.
>>> 
>>> You need to follow this process to make the changes in
>>> the SVN source files instead, then re-generate, etc.
>>> http://incubator.apache.org/guides/website.html
>>> 
>>> (That is the system until the Incubator switches over
>>> to use the new CMS.)
>>> 
>>> -David
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

Re: [Wave] editing incubator documents

[Michael MacFadden]

I'll get that to you today. Thanks. 

Michael

On Feb 4, 2011, at 12:18 PM, "Upayavira"  wrote:

> Sorry, I should have looked at this. I'll need to dig more, because you
> *are* in the incubator group - I saw it when checking your CLAs were
> present. So there's something else going on.
> 
> Can you confirm what URL you are using, and what error you get?
> 
> Upayavira
> 
> On Fri, 04 Feb 2011 07:54 -0800, "Michael MacFadden"
>  wrote:
>> We have access to the wave SVN, but it seems like we don't have access to
>> the incubator SVN.  According to this document:
>> 
>> http://incubator.apache.org/guides/mentor.html#Set+Up+Repository
>> 
>> We should have access to the incubator web site SVN.
>> 
>> I can't actually view the authorization template file it mentions to see
>> if that was done, but it appears that it may not have been done.  Either
>> that, or there is something specifically wrong with my account.
>> 
>> ~Michael
>> 
>> On Feb 4, 2011, at 7:43 AM, Andrus Adamchik wrote:
>> 
>>> Per Feb 2 message from Upayavira on wave-dev 
>>> (1296637259.12852.1418516...@webmail.messagingengine.com), SVN auth grants 
>>> are setup for all Wave committers. Not sure if the permissions are extended 
>>> to the Incubator site?
>>> 
>>> Andrus
>>> 
>>> On Feb 4, 2011, at 10:31 AM, Michael MacFadden wrote:
>>> 
>>>> David,
>>>> 
>>>> Thanks for the heads up.  I have been trying to follow said process, 
>>>> however it seems like the wave committers have not yet been given that 
>>>> ability to commit changes to the incubator SVN.  I have some pending 
>>>> changes to the wave project page I have been waiting to check in.
>>>> 
>>>> ~Michael
>>>> 
>>>> On Feb 3, 2011, at 10:02 PM, David Crossley wrote:
>>>> 
>>>>> When publishing some Incubator docs (doing 'svn up' on the server)
>>>>> i see that someone has made some hard-coded changes to the
>>>>> generated html doc for the Wave status page.
>>>>> 
>>>>> You need to follow this process to make the changes in
>>>>> the SVN source files instead, then re-generate, etc.
>>>>> http://incubator.apache.org/guides/website.html
>>>>> 
>>>>> (That is the system until the Incubator switches over
>>>>> to use the new CMS.)
>>>>> 
>>>>> -David
>>>>> 
>>>>> 
>>>>> -
>>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>>> 
>>>> 
>>>> 
>>>> -
>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>> 
>>>> 
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>> 
>> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [Wave] editing incubator documents

[Michael MacFadden]

The repo I hit was:

https://svn.apache.org/repos/asf/incubator/public/trunk


Here is my check in attempt and the error:


michael incubator$ svn commit -m "Updated the wave project page to include the 
SVN url."
Authentication realm: <https://svn.apache.org:443> ASF Committers
Password for 'michael': 
Sendingsite-author/projects/wave.xml
svn: Commit failed (details follow):
svn: Server sent unexpected return value (403 Forbidden) in response to 
CHECKOUT request for 
'/repos/asf/!svn/ver/1066457/incubator/public/trunk/site-author/projects/wave.xml'
michael incubator$ 


Is this the info you need?


On Feb 4, 2011, at 12:18 PM, Upayavira wrote:

> Sorry, I should have looked at this. I'll need to dig more, because you
> *are* in the incubator group - I saw it when checking your CLAs were
> present. So there's something else going on.
> 
> Can you confirm what URL you are using, and what error you get?
> 
> Upayavira
> 
> On Fri, 04 Feb 2011 07:54 -0800, "Michael MacFadden"
>  wrote:
>> We have access to the wave SVN, but it seems like we don't have access to
>> the incubator SVN.  According to this document:
>> 
>> http://incubator.apache.org/guides/mentor.html#Set+Up+Repository
>> 
>> We should have access to the incubator web site SVN.
>> 
>> I can't actually view the authorization template file it mentions to see
>> if that was done, but it appears that it may not have been done.  Either
>> that, or there is something specifically wrong with my account.
>> 
>> ~Michael
>> 
>> On Feb 4, 2011, at 7:43 AM, Andrus Adamchik wrote:
>> 
>>> Per Feb 2 message from Upayavira on wave-dev 
>>> (1296637259.12852.1418516...@webmail.messagingengine.com), SVN auth grants 
>>> are setup for all Wave committers. Not sure if the permissions are extended 
>>> to the Incubator site?
>>> 
>>> Andrus
>>> 
>>> On Feb 4, 2011, at 10:31 AM, Michael MacFadden wrote:
>>> 
>>>> David,
>>>> 
>>>> Thanks for the heads up.  I have been trying to follow said process, 
>>>> however it seems like the wave committers have not yet been given that 
>>>> ability to commit changes to the incubator SVN.  I have some pending 
>>>> changes to the wave project page I have been waiting to check in.
>>>> 
>>>> ~Michael
>>>> 
>>>> On Feb 3, 2011, at 10:02 PM, David Crossley wrote:
>>>> 
>>>>> When publishing some Incubator docs (doing 'svn up' on the server)
>>>>> i see that someone has made some hard-coded changes to the
>>>>> generated html doc for the Wave status page.
>>>>> 
>>>>> You need to follow this process to make the changes in
>>>>> the SVN source files instead, then re-generate, etc.
>>>>> http://incubator.apache.org/guides/website.html
>>>>> 
>>>>> (That is the system until the Incubator switches over
>>>>> to use the new CMS.)
>>>>> 
>>>>> -David
>>>>> 
>>>>> 
>>>>> -
>>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>>> 
>>>> 
>>>> 
>>>> -
>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>> 
>>>> 
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>> 
>> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [Wave] editing incubator documents

[Michael MacFadden]

That did it... was able to check in.  Thanks David!

~Michael

On Feb 4, 2011, at 3:56 PM, David Crossley wrote:

> Upayavira wrote:
>> Sorry, I should have looked at this. I'll need to dig more, because you
>> *are* in the incubator group - I saw it when checking your CLAs were
>> present. So there's something else going on.
> 
> I found it. In the svn asf-authorization-template
> the wave entry was missing one part of its config:
> http://incubator.apache.org/guides/mentor.html#Set+Up+Repository
> it was missing the third entry.
> 
> Not sure how long its takes for an automatic update
> to propagate. Any done in r784788
> 
> Go for it Michael.
> 
> -David
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] starting the CMS migration process

[Michael MacFadden]

Joe,

As a newbie on the CMS, I would say I don't have any large concerns Wave has 
migrated over without to much trouble.  I think the system works pretty well.  
I like the CMS Bookmarklet, and I really like the staging build and the whole 
process in general.

I would like to see the UI for the CMS mature over time.  It is very 
functional, but the directory navigation, file actions, and editor could use 
some UI polishing as the tool matures (a little UX design and DHTML wouldn't 
hurt).  Are there any plans to do this, or is the CMS pretty much just going to 
be as is from now on?  I wouldn't mind helping out with the actual CMS system 
itself if there was an opportunity to do so.


~Michael


On Apr 3, 2011, at 9:26 AM, Joe Schaefer wrote:

> As my self-imposed deadline has passed, I'd like to pick this
> up again and am looking for volunteers interested in assisting
> with the migration.
> 
> If there are lingering doubts about the switchover, let's address
> those asap.  If the majority of the IPMC prefers to remain with
> Anakia and just switch to svnpubsub that is an acceptable outcome
> infra-wise.  Just not what I'd prefer ;-).
> 
> 
> 
> 
> - Original Message 
>> From: Joe Schaefer 
>> To: general@incubator.apache.org
>> Sent: Tue, January 11, 2011 10:16:41 AM
>> Subject: [DISCUSS] starting the CMS migration process
>> 
>> As mentioned at http://www.apache.org/dev/cms.html the
>> Infrastructure Team would like  the IPMC to consider migrating
>> to the CMS over the coming weeks.  We  will be completely
>> phasing out support for Confluence backed sites this  year,
>> and would like to encourage all Apache projects still relying
>> on  Anakia (such as the Incubator) to migrate as well.  This
>> undoubtedly  will impact current and new podlings.
>> 
>> More information on the CMS is  available at the following links:
>> 
>> http://blogs.apache.org/infra/entry/the_asf_cms
>> http://wiki.apache.org/general/ApacheCms2010
>> http://www.apache.org/dev/infra-site.html
>> http://www.apache.org/dev/cmsref.html
>> 
>> 
>> 
>> 
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [PROPOSAL] Accept Wave for incubation

[Michael MacFadden]

I agree, there are other wave implementations popping up, some of which include 
"wave" in the name and some don't.  "Lightwave" for example is one such 
project.  I think that Apache Wave and the Wave in a Box product should be fine.

Also, as Dan points out "Google Wave" product is going to cease to exist in the 
near future.  The wave.google.com service / application will be shut down  
sometime after the end of the year.  At this point Google's intent (if I 
understand it correctly) is that the open source community take up wave 
technology where they left off.  This should cut down on any confusion an 
complications during the transition.

Regards,
Michael


On Nov 23, 2010, at 6:11 PM, James Purser wrote:

> While Google owns the Google Wave trademark, they don't own the very generic
> "Wave".
> 
> Apache Wave will be a separate thing and unaffected by any trademark that
> Google owns.
> 
> James Purser
> 
> On Wed, Nov 24, 2010 at 1:06 PM, Greg Stein  wrote:
> 
>> On Tue, Nov 23, 2010 at 20:47, Ralph Goers 
>> wrote:
>>> ...
>>> OK - Have they explicitly OK'd Apache Wave?  While Apache Wave would
>> certainly be unique to Apache, if Google intends to keep using Google Wave
>> (and Wave as a shorthand) this would get very confusing.
>> 
>> Don't you think that by proposing Wave to the Incubator that Google
>> has OK'd this?
>> 
>> Come on... back on off the paranoia :-P
>> 
>> Cheers,
>> -g
>> 
>> p.s not to mention that "Apache Wave" would be our trademark and
>> nobody can do or say anything about that.
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [PROPOSAL] Accept Wave for incubation

[Michael MacFadden]

Ralph,

Your due diligence is appropriate and appreciated.  Thanks.

~Michael


On Nov 23, 2010, at 8:20 PM, Ralph Goers wrote:

> Thanks. That answers my only concern. I think this would be a great addition.
> 
> Sent from my iPhone
> 
> On Nov 23, 2010, at 7:56 PM, Soren Lassen  wrote:
> 
>> I work for Google and I speak on the behalf of the Google Wave team. I
>> can assure you that Google supports the Apache Wave proposal. We
>> always wanted to transfer ownership of the open source code to the
>> developer community and, with the discontinuation of development of
>> Google Wave as a standalone product, we accelerated our efforts to
>> spin this out in order to bring certainty to the developer community.
>> Apache Wave should stand on its own without concern for Google's
>> product strategies or priorities.
>> 
>> Nonetheless, please note that Google is looking at ways to continue
>> and extend wave technology in other Google products, specifically ways
>> for users to access waves through Google Docs. But Google only retains
>> the rights to the trademark "GOOGLE WAVE" and the wave design logo.
>> Hopefully, Google will become one of many happy customers of Apache
>> Wave.
>> 
>> Soren
>> 
>> On Wed, Nov 24, 2010 at 2:45 PM, Ralph Goers  
>> wrote:
>>> 
>>> On Nov 23, 2010, at 6:06 PM, Greg Stein wrote:
>>> 
 On Tue, Nov 23, 2010 at 20:47, Ralph Goers  
 wrote:
> ...
> OK - Have they explicitly OK'd Apache Wave?  While Apache Wave would 
> certainly be unique to Apache, if Google intends to keep using Google 
> Wave (and Wave as a shorthand) this would get very confusing.
 
 Don't you think that by proposing Wave to the Incubator that Google
 has OK'd this?
>>> 
>>> I don't work for Google and don't know the people proposing this so no, I 
>>> have no idea whether Google has OK'd this.  This is no different than 
>>> someone taking an Apache project out of the Attic and starting it somewhere 
>>> else using the same name without Apache on the front. IIRC we don't allow 
>>> that.  I don't think this is paranoia but just approaching this from the 
>>> same set of rules that we use for our own projects.
>>> 
>>> Ralph
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>> 
>>> 
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org