Re: project dependencies - important

[P. Taylor Goetz]

Note that any code/content not previously donated by DT (i.e. covered by an 
SGA) would have to go through the IP clearance process [1] [2].

-Taylor

[1] https://incubator.apache.org/guides/ip_clearance.html 

[2] http://incubator.apache.org/ip-clearance/ 




> On May 3, 2018, at 12:45 PM, Thomas Weise  wrote:
> 
> Pramod,
> 
> There are several Apex related blogs on the DT web site that are referenced
> from http://apex.apache.org/docs.html (there are probably a few more, but
> that should be easy to identify).
> 
> Would it be possible to export that subset (for example by saving as full
> page html) and check them into another github with ASL license? This way
> they would remain available to users and we could continue to reference
> them.
> 
> Thanks
> 
> 
> On Thu, May 3, 2018 at 6:27 AM, Pramod Immaneni 
> wrote:
> 
>> There may be copyright issues to deal with in case of a move.
>> 
>> Thanks
>> 
>> On Wed, May 2, 2018 at 10:22 PM, Vlad Rozov  wrote:
>> 
>>> For netlet we can either move it to apex-core (it will require package
>>> name change and major version update) or keep it in public github
>>> repository. Other libraries are available on maven central and I see that
>>> you already open a PR (+1).
>>> 
>>> Thank you,
>>> 
>>> Vlad
>>> 
>>> 
>>> On 5/2/18 19:38, Thomas Weise wrote:
>>> 
 That one is not needed and I think we can nuke the zmq operator also.
 
 R has an example, so we might want to find a way to keep that alive.
 
 
 On Wed, May 2, 2018 at 7:33 PM, Pramod Immaneni >> 
 wrote:
 
 I see a kafka 0.7.1. Not sure if it is still being used.
> 
> Thanks
> 
> On Wed, May 2, 2018 at 7:05 PM, Thomas Weise  wrote:
> 
> Hi Pramod,
>> 
>> Thanks for the headsup.
>> 
>> Do you have the list of malhar dependencies that live in the DT
>> server?
>> 
>> I remember R and zmq, anything else?
>> 
>> Thanks,
>> Thomas
>> 
>> 
>> On Wed, May 2, 2018 at 6:53 PM, Pramod Immaneni <
>> pra...@datatorrent.com
>>> 
>> wrote:
>> 
>> Hello Community,
>>> 
>>> As you may know, DataTorrent was the original developer and initial
>>> contributor of Apex. There are a couple of dependencies the project
>>> 
>> still
> 
>> has on DataTorrent.
>>> 
>>> One of them is the project netlet, hosted in DataTorrent github, that
>>> provides a networking library for data transfer. Second, malhar
>> depends
>>> on thirdparty maven artifacts hosted on DataTorrent maven server.
>> Going
>>> forward, DataTorrent will no longer be hosting these resources.
>>> 
>>> The netlet repository has been transferred to
>>> https://github.com/dtpublic/netlet which is a general account
>>> 
>> unrelated
> 
>> to
>> 
>>> DataTorrent org. This project can also be brought into apex if we
>> think
>>> that would be best for the library and the apex project.
>>> 
>>> There are a small number of custom maven artifacts under
>>> https://www.datatorrent.com/maven/content/repositories/thirdparty/.
>> A
>>> 
>> new
>> 
>>> home needs to be found for these or malhar changed to not depend on
>>> 
>> these.
>> 
>>> The maven server will be shutdown tomorrow. One idea for the
>> immediate
>>> 
>> need
>> 
>>> is to temporarily store these under apex-site.
>>> 
>>> Thanks
>>> 
>>> 
>>> 
>> 



signature.asc
Description: Message signed with OpenPGP

Re: [DISCUSS] Time for attic?

[P. Taylor Goetz]

IMHO, the bare minimum for “survivability” as an ASF project is 3 Active PMC 
members  (to make project decisions) and enough of an active community to make 
releases when necessary (e.g. Respond to CVEs, etc.).

Given the responses to this thread, I believe the project has the former. The 
question becomes is there enough of a community left for the latter?

Also, life after Apache is possible. The most important consideration, is that 
to do so would require renaming/rebranding, since the ASF owns the Apex 
trademark.

-Taylor

> On Jan 9, 2019, at 5:01 PM, Vlad Rozov  wrote:
> 
> Hi Sanjay, long time, no see.
> 
> This is my attempt to mobilize the community and see if we can revive some 
> activity on the project. Note that the same discussion happened among PMCs 
> members 2 month ago and there were promises to contribute back to the project 
> with no new PRs being open. Should you follow the e-mail thread thoroughly, 
> you would see that the move to the attic was questioned by the Apache board, 
> so it was not me who initiated the move. I simply made community aware that 
> Apex is the subject of the move if it continues the way it was for the last 
> 6-8 months. With the current activity and no commitment to make new 
> contributions Apex does belong to the attic.
> 
> Thank you,
> 
> Vlad 
> 
>> On Jan 9, 2019, at 12:27, Sanjay Pujare  wrote:
>> 
>> Hi Vlad
>> 
>> I have been watching this debate from the sidelines and just decided to
>> jump in.
>> 
>> As an Apex PMC member you said "... I am responsible for maintaining the
>> correct state of the project...". But let's face it, you don't actually
>> have to do it just like you didn't have to make contributions, make
>> proposals or do all sorts of other things for keeping the project alive and
>> vibrant. Without doing absolutely anything, PMC members will continue to
>> remain PMC members which applies to you as well.
>> 
>> So at this stage, you may do nothing, you may start mobilizing for making
>> contributions, you may stop being a member of PMC or you may start this
>> drive to move the project to the attic. May I know why you chose the last
>> option instead of one of the others? It will be good to know your answer
>> before discussing the details of people staying away or being discouraged.
>> 
>> Sanjay
>> 
>> 
>> 
>>> On Wed, Jan 9, 2019 at 10:50 AM Vlad Rozov  wrote:
>>> 
>>> Amol,
>>> 
>>> Without details who decided to stay away and why it is not very
>>> constructive and does not tell me whether I should continue or not. Again,
>>> I’d like to see what policies needs to be changed that will bring more
>>> contributions and won’t affect quality of the code. If you have a concrete
>>> proposal, please post it here, so the community can decide whether to
>>> accept them or not.
>>> 
>>> It is always the case that a contributor decides what to contribute. The
>>> goal of the e-mail thread is to see if there are few contributors who plan
>>> to contribute in the new future and what do they plan to contribute.
>>> 
>>> Thank you,
>>> 
>>> Vlad
>>> 
 On Jan 9, 2019, at 10:18, amol kekre  wrote:
 
 Vlad,
 Would you want to continue to be involved in the project, even if this
 involvement is itself causing community folks to stay away? If the issue
>>> is
 cultural, things will not improve. Doing the same thing again and
>>> expecting
 different result will not work. Why not change the policies that
>>> enforces a
 different culture, and then wait 6 months to see if things change. With
 regards to listing features, that needs to be something that the
 contributors should decide.
 
 Amol
 
 
> On Wed, Jan 9, 2019 at 9:22 AM Vlad Rozov  wrote:
> 
> Remember that to vote -1 it is necessary to provide justification, so
>>> I’d
> like to see the justifications and the plan from those who do not want
>>> to
> move Apex to the attic. I am also not very happy that my past efforts
>>> will
> be placed in the attic, but let’s face the reality. It is not that I
>>> don’t
> want to be involved in the project, but as the PMC I am responsible for
> maintaining the correct state of the project and with the current level
>>> of
> contributions, IMO, it belongs the the attic.
> 
> Thank you,
> 
> Vlad
> 
>> On Jan 9, 2019, at 09:02, Pramod Immaneni 
> wrote:
>> 
>> What would be the purpose of such a vote? From the discussions it is
> quite
>> apparent that there is a significant, possibly majority view that
>>> project
>> shouldn’t go to attic. The same could be reported to the board, can’t
>>> it?
>> Like I also said if you or others don’t like where the project is at
>>> and
>> feel it is a dead end, you don’t have to continue to be involved with
>>> the
>> project and that’s your prerogative. Let others who want to continue,
> take
>> it forward, why try to force your will on to everyone.