Re: Invite to the github project for Wave...

[Adam John]

Had to rename the project due to naming rights.

The preferred one to join might be:
https://github.com/P2Pvalue/swellrt

Adam John
(914) 623-8433

On Oct 15, 2016 2:52 PM, "Bradley D. Thornton"  wrote:

> Hello,
>
> I received an invite to ApacheWave at github but upon trying to accept the
> invite it appears to be a broken link that results in a 404 error.
>
> Does anyone have the correct URL or could someone send me another invite?
>
> Thanks!
>
>
>
> ---
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
>
>

Re: Retirement

[Bradley D. Thornton]

This is the link below that I cannot seem to locate.

On 8/30/2016 11:25 PM, Adam John wrote:

Created a GitHub organization, added each of the available repos:
https://github.com/ApacheWave

I think I invited everyone on this thread - however there are many others
on the list.
All are welcome.

Loss of Apache incubator status is significant as it means also
organizational loss, tools lost, and would effectively put a nail in the
coffin for the project.

WebCMS, Jira, Jenkins, and Travis are all valuable tools, and part of
Incubator status.

Quality code review (thanks, vega and wisebaldone etc) and an established
process for the inclusion of new contributions by people familiar with
existing approaches and the work in progress... all of this is significant.

The people on this list - and even the list itself - both a service and an
organization that would be a significant loss in any transition...

I think the safety of the incubator is important, for these reasons and
more; and there needs to be improved communication, planning and
coordination... here again, just my opinion.

AJ

Adam John
(914) 623-8433
Google+  | LinkedIn 

On Tue, Aug 30, 2016 at 4:01 PM, Upayavira  wrote:


The best future for Wave at Apache would, I think be to start an
entirely new project at GitHub, and implement a Wave system that people
can actually understand. Once that gains traction, come back to the
Incubator and ask to resurrect Apache Wave with that new codebase.

The current codebase seems to be simply too complex for people to be
able to pick up. The idea stands as a good one, but the code is just too
complex.

Upayavira

On Tue, 30 Aug 2016, at 09:58 PM, Taylor Fahlman wrote:

I've been a reader of this list for a while. I am another one of the
people
who would love to contribute, but literally have no idea where to start.
I
really think that if the code was divided a bit more it'd be easier to
contribute, because I want to see this project keep going. It really does
have a lot of potential in the current climate of silo-ed communication
systems. An easy docker image would really help too.

On Tue, Aug 30, 2016 at 12:54 PM Thomas Wrobel 
wrote:


While the code will always be there in some form, is there any real
hope outside of Apache though? will it not just fizzle out?
Apache provides somewhat needed pressure, structure and to some extent
even prestige.

While retirement is understandable necessity for things without
progress, its nevertheless sad for a project with such potential.  Is
it possible to put a call out for developers? a last warning? a
advert? something beyond this list?
I have no idea what form it would take though. I am so ignorant with
big projects, both socially and structurally. Theres tools out there
supposed to help motivate and organised (www.teamily.com) dont know
how effectively they are though.

It just all seems such a waste for wave to die, its death marking a
little lost hope for the open web to recover some ground from the
closed hubs that dominate today.

--
http://lostagain.nl <-- our company site.
http://fanficmaker.com <-- our, really,really, bad story generator.


On 30 August 2016 at 21:41, Upayavira  wrote:

Michael,

As I said earlier in this thread, retirement means the closure of an
"apache" community. The code is already open source. So long as the
trademark and the Apache License V2 on the code are respected, as

now,

anyone is free to do what they like with the code.

Thus, if someone (or someones) wanted to move it to Github, that'd be
fine. I'm sure Apache wouldn't object to them using the name "Wave"

in

some form.

Upayavira

On Tue, 30 Aug 2016, at 08:54 PM, Michael MacFadden wrote:

Yuri,

Being a mostly silent participant at this point.  I would tend to

agree

with you.  I think however, we should provide a “what next”

option.  So

for example, people might be more willing to retire the project if

they

knew for example we could move to github and still allow people to
contribute and develop if they see fit.

~Michael

On 8/30/16, 11:52 AM, "Yuri Z"  wrote:

 After some thought I hate to agree, that at current levels of
 participation
 the only rational choice is to decide to retire as we are just
 wasting
 Apache Foundation resources without any real hope of graduating.
 Moreover, there were a few active projects based on Apache Wave

that

 felt
 little motivation to contribute back actively. I think this is
 because they
 found little need in Apache Foundation resources, while

contributing

 back
 required certain effort to comply with Apache rules.

 I think we should hold a retirement vote and either recruit
 sufficient
 number of supporters willing and able actively participate
 immediately, or
 retire.

 On Tue, Aug 30, 2016 at 9:13 PM Jonathan Leong <

Invite to the github project for Wave...

[Bradley D. Thornton]

Hello,

I received an invite to ApacheWave at github but upon trying to accept 
the invite it appears to be a broken link that results in a 404 error.


Does anyone have the correct URL or could someone send me another invite?

Thanks!



---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus