Re: How to move code and docs from GitHub to GitHub

[Brian Devins-Suresh]

Echoing what Dave said, we have had Infra transfer the repos
in instead of just pushing a new version so that we could keep
all issues, release notes, etc

-Brian

On Fri, May 10, 2019 at 3:31 PM Dave Fisher  wrote:

> Hi -
>
> I would discuss this with Apache Infra. Either:
>
> join https://the-asf.slack.com - #asfinfra, or
> subscribe to us...@infra.apache.org and send an email.
>
> Regards,
> Dave
>
> > On May 10, 2019, at 12:08 PM, leerho  wrote:
> >
> > I am in the process of trying to move code from our current GitHub
> > repositories to the newly assigned Apache incubator GitHub
> repositories.  I
> > could use some advice on the best way to do this.
> >
> > So far, I have used the command
> >
> > $ > git push --all --tags --repo=g...@github.com:
> apache/incubator-.git
> >
> > This pushes code and tags from my laptop *clone* of our current repo to
> the
> > apache repo.  But it does not transfer important *release documentation*,
> > which is a feature of the GitHub repo website.
> >
> > Is there a way to effectively copy everything (code, tags, documentation,
> > etc) directly from our current origin GitHub repo to the Apache repo?
> > Without having to use my laptop clone in the middle? AND without wiping
> out
> > the current origin GitHub repo?
> >
> > Otherwise, I am having to manually copy and paste all the associated
> > release documentation!
> >
> > Any help would be appreciated!
> >
> > Thanks
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Hello World / CRUNCH Framework

[Brian Devins-Suresh]

Hi Julian,

This seems like a cool project. I'd like to point out one thing with your
name, there is already an Apache Crunch project: https://crunch.apache.org

On a couple collaborative notes, as a (incubating) Zipkin developer I could
see some use for your project in our community. We've had trouble building
reusable analytics components so if your framework would help facilitate
that then we might be able to get community buy-in for adopting.

My other collaboration point is it would be cool if it could be used with
the newly incubating IoTDB once that has all of its source available.

- Brian

On Fri, Dec 14, 2018 at 5:59 AM Julian Feinauer <
j.feina...@pragmaticminds.de> wrote:

> Hi Chris,
>
> yes, you got it right.
> We do not care about "how does this message get from this processing node
> to that".
> We "transpile" the higher level input into a DAG which can then run on
> basically every streaming engine (I agree, we do NOT need yet another one),
> in that sense it is a bit like Apache Beam.
> Thus, I do not see it as a contender to Edgent but more as a
> complementary, because edgents focus is more the engine and Cloud
> Communication and CRUNCHs focus is more of "what exactly does the pipeline
> do".
>
> Julian
>
> Am 14.12.18, 11:54 schrieb "Christofer Dutz" :
>
> Hi Julian,
>
> For me it always felt like crunch can't directly be compared to the
> other "streaming engines" as I see it as a bundle of a streaming engine and
> a higher level framework for doing typical industry operations on top of
> that.
>
> I think the higher level library should actually be able to run on top
> of any of the other streaming engines we have. Does such a split make
> sense, or did I get something wrong? Perhaps it would make sense to
> evaluate Edgents stream processing and eventually merge in improvements. I
> don't see a need multiple edge stream frameworks especially if we have to
> revive the existing one.
>
> I think an engine for higher level functions on top of a streaming
> engine of choice would be a great addition, because adding such logic to
> only one of the existing seems to be a waste.
>
> Chris
>
> Outlook for Android herunterladen
>
> 
> From: Julian Feinauer 
> Sent: Friday, December 14, 2018 11:11:40 AM
> To: general@incubator.apache.org
> Subject: Hello World / CRUNCH Framework
>
> Hi all,
>
> I just joined the incubator ML and wanted to present myself and
> possibly also start a discussion about a software project we developed in
> the past.
> But first things first. My name is Julian Feinauer and I come from
> Germany where I run two “start-up” companies where we work a lot on the
> “industrial IoT” topics, data science and processing of “larger amounts of
> data”. We love open source and so we love the ASF. Most notably, I closely
> follow the Apache Calcite project and hopefully find some time soon to
> contribute a bit more than in the last monts. Futhermore, I am engaged in
> the (incubating) PLC4X project as (P)PMC and in the  (incubating) Edgent
> project where I try to “revive” the community as new (P)PMC together with
> Christopher Dutz.
>
> Now to the real topic. Over the last 3 years I started to develop a
> “Framework/Library” (currently a set of jars) to facilitate processing of
> timeseries data. The focus is mostly on processing of data from test
> stands, e.g., automotive tests, driving profiles and so on. Furthermore, in
> the recent year we added a lot of functionality for processing of
> “industrial data”. This means that we want to make it easy to analyze
> things like “how long did the machine spend in this state”, “when are the
> following set of bits set” or “nofity when the following conditions is true
> for the first time”.
> It is a bit technical and I don’t want to go too deep into it, but
> generally speaking we try to introduce the “right” semantics to answer the
> typical questions when analyzing machine or test data. This project is
> called “CRUNCH” and we are in the process of making it open source (will be
> moved to a public github repo in this year) under the Apache 2.0 License.
>
> As there can be seen a close relationship to other (incubating or TLP)
> projects we are thinking about if this project could fit into the
> incubator. Some examples for Apache projects that we see as “related” are
> Apache Flink (which we can use as the Streaming Engine to process the
> stream), (incubating) Edgent which we also can support as Streaming Engine
> and where we try to find a suitable project goal and community currently as
> some of the (P)PMC members retired or went inactive. Finally, CRUNCH has a
> very natural fit with PLC4X because it can directly process the data
> gathered form PLCs (and in fact we are already using it in some of our
> projects that way). I had several discussions with some of the (P)PMCs of
> PLC4X, namely