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

[Greg Stein]

Yeup. Infra transfers repositories all the time. Just file an INFRA ticket
specifying which repositories are to be transferred, and their new names.
There are a couple approaches to perform the transfer, and that can be
worked out in the ticket.

Cheers,
Greg Stein
Infrastructure Administrator, ASF


On Fri, May 10, 2019 at 2:41 PM Brian Devins-Suresh 
wrote:

> 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: Podling PPMC members and mentors not signed up to private lists

[Greg Stein]

On Fri, May 10, 2019 at 2:36 AM Justin Mclean 
wrote:
>...

> No one should be subscribed to the private list other than mentors, PPMC
> members and ASF members (who can subscribe to any private  list).
>

Strictly speaking, a (P)PMC may have invited guests subscribed to their
private@ list. This is quite unusual, but has some precedent. As you note:
all subscriptions to private@ should be reviewed/moderated.

Cheers,
-g

Re: Podling PPMC members and mentors not signed up to private lists

[sebb]

On Fri, 10 May 2019 at 08:48, Kenneth Knowles  wrote:
>
> *From: *Justin Mclean 
> *Date: *Fri, May 10, 2019 at 12:36 AM
> *To: * 
>
> No one should be subscribed to the private list other than mentors, PPMC
> > members and ASF members (who can subscribe to any private  list).
> >
>
> Ah, my analysis does not include ASF members who are neither PPMC nor
> mentors.

Such subscribers will be shown by Whimsy if the user has sufficient karma.

It's difficult to extrapolate from the numbers.
This is because Whimsy does not check if a person is subscribed twice
(this is not unknown).
Also there may be a variable number of archivers.

> Kenn
>
>
> >
> > The subscriptions are moderated by them PPMC so it is possible to
> > accidentally add someone who isn’t a mentor/PPMC member.
> >
> > Thanks,
> > Justin
> > -
> > 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: Podling PPMC members and mentors not signed up to private lists

[sebb]

On Fri, 10 May 2019 at 08:05, Huxing Zhang  wrote:
>
> Hi,
>
> > - Dubbo - Four PPMC members not signed up [10]
>
> Three of the inactive PPMC have indicated to step down after the graduation.
> For the remaining one, it is a known issue on the private@dubbo list.
> The PPMC member has subscribed to private with apache mail address, I
> am not sure why it is shown as not subscribed. I will continue to
> investigate it.

As a mentor, you should be able to check the subscriber list, see:

https://whimsy.apache.org/committers/moderationhelper
- list current subscribers

> --
> Best Regards！
> Huxing
>
> -
> 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: 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: How to move code and docs from GitHub to GitHub

[Dave Fisher]

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: How to move code and docs from GitHub to GitHub

[Jan Piotrowski]

To be honest, the first thing I would is to ask GitHub support if they
might be able help - just take the repo and move everything over to an
existing empty repo.

Best,
Jan

Am Fr., 10. Mai 2019 um 21:09 Uhr schrieb leerho :
>
> 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

How to move code and docs from GitHub to GitHub

[leerho]

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

[ANNOUNCE] Apache Zipkin (Incubating) version 2.13.0 Released

[Raja Sundaram Ganesan]

TheApache Zipkin(incubating) team is pleased to announce that
the Zipkin 2.13.0 has been released.

Apache Zipkin (incubating) is a distributed tracing system. It helps
gather timing data needed to troubleshoot latency problems in
microservice architectures. It manages both the collection and lookup
of this data. Zipkin’s design is based on the Google Dapper paper.

This source includes a dependency-free library and a spring-boot
server. Storage options include in-memory, JDBC (MySQL), Cassandra,
and Elasticsearch.

The latest release can be downloaded from maven central and docker hub

http://central.maven.org/maven2/org/apache/zipkin/zipkin-server/2.13.0/

https://hub.docker.com/r/openzipkin/zipkin

Release notes can be accessed in the below link

https://github.com/apache/incubator-zipkin/releases/tag/v2.13.0

Thanks,

The Apache Zipkin (Incubating) Team


-

To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org

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

Re: Missing Mentors

[Matt Sicker]

Provided OpenWhisk has another podling report before graduation. Otherwise,
I’ll have missed out on sign offs entirely by joining too late. 😅

On Thu, May 9, 2019 at 23:36, Justin Mclean 
wrote:

> Hi,
>
> > I am twice on the report of I am one of the 13.  I can't figure out how
> to
> > read this report very well.
>
> You’re fine, the 13 people I extracted from this I’ve not listed anywhere
> public. They probably know who they are and hopefully decide what best for
> their podlings if they are not being active.
>
> I think the biggest take away is last time we look at this I think there
> was 70 odd mentors flagged as potentially missing. This is a huge
> improvement aver last time, and possibly shows that mentors are being more
> engaged and active.
>
> The report has some limitations:
> - It’s parsed from the incubator reports so it can only go off what text
> is in that.
> - Som times it’s not 100% correct
> - The podlings are listed form oldest to newest left to right.
> - Orange mean you missed a sign-off, blue you signed off the report.
> - It includes podlings that have graduated
> - It includes people who are no longer mentors.
>
> Having dates of sign-offs would probably help and  would separating
> current podlings from graduated one and indicating where some one is no
> longer a mentor,
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
> --
Matt Sicker 

Re: Podling PPMC members and mentors not signed up to private lists

[Kenneth Knowles]

*From: *Justin Mclean 
*Date: *Fri, May 10, 2019 at 12:36 AM
*To: * 

No one should be subscribed to the private list other than mentors, PPMC
> members and ASF members (who can subscribe to any private  list).
>

Ah, my analysis does not include ASF members who are neither PPMC nor
mentors.

Kenn


>
> The subscriptions are moderated by them PPMC so it is possible to
> accidentally add someone who isn’t a mentor/PPMC member.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Podling PPMC members and mentors not signed up to private lists

[Justin Mclean]

Hi,

> I have questions:
> - whimsy's UI does not (*) for mentors not on private@, right? if so, can
> we tell if mentors are on it?

Yes it will mark mentors with a * who are not subscribed.

> - how were people able to subscribe to private@ when they are not mentors
> or ppmc?

No one should be subscribed to the private list other than mentors, PPMC 
members and ASF members (who can subscribe to any private  list).

The subscriptions are moderated by them PPMC so it is possible to accidentally 
add someone who isn’t a mentor/PPMC member.

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

Re: Podling PPMC members and mentors not signed up to private lists

[justin]

Hi,

> As I said all the mentors are subscribed, blur there's are 6 PPMC members who 
> are not subscribed and one person should shouldn’t be subscribed which the 
> PPMC was asked to remove previously.


It may be possible they have signed up with an email address that is not in 
their Apache profile to the podling private list? But the numbers seems a 
little high and how did people know they were PPMC members when they signed up 
with a unknown email address?

Thanks,
Justin

Re: Podling PPMC members and mentors not signed up to private lists

[Kenneth Knowles]

(minus dev@tuweni and plus dev@datasketches)

Thanks for compiling this. If it was manual, that is heroic.

Writing with my datasketches mentor hat on:

 - 3 mentors
 - 7 non-mentor PPMC

So there's 10

 - whimsy indicates private@ has 8 subscribers which implies 2 not
subscribed
 - whimsy indicates 5 PPMC marked with (*) are not subscribed

Seems like there's some internal issue here. I have questions:

 - whimsy's UI does not (*) for mentors not on private@, right? if so, can
we tell if mentors are on it?
 - how were people able to subscribe to private@ when they are not mentors
or ppmc?

Kenn

*From: *Pierre Smits 
*Date: *Thu, May 9, 2019 at 11:30 PM
*To: * 

Hi Justin,
>
> (cross-posting to dev@tuweni ML)
>
> It seems your information about the Tuweni project is incorrect. For its
> first report I did a diversity check on each of the project's mailing
> lists, and it proves that each of those has a healthy number of mentors
> subscribed. The more important MLs, being dev@, user@ and private@ have
> resp. 4, 5, and 6 mentors signed up. See [1]
>
>
> [1]
>
> https://lists.apache.org/thread.html/fd3e232392bb21c219ced89d5b09c3c93bb9d516dea7992adec550b6@%3Cdev.tuweni.apache.org%3E
>
> Best regards,
>
> Pierre Smits
>
> *Apache Trafodion , Vice President*
> *Apache Directory , PMC Member*
> Apache Incubator , committer
> *Apache OFBiz , contributor (without privileges)
> since 2008*
> Apache Steve , committer
>
>
> On Fri, May 10, 2019 at 6:33 AM Justin Mclean 
> wrote:
>
> > Hi,
> >
> > A number of podlings mentors and PPMC members are not signed up to their
> > podling private lists.
> >
> > If you are a mentor of a project listed below can you please remind your
> > PPMC members to sign up to the private list and ensure that yourself or
> > other mentors are signed up to your podlings private list.
> >
> > Important emails get sent to the podlings private email lists and as a
> > PPMC member you really need to be signed up to it so you don’t miss
> them. I
> > know there may be reasons for this not happening, as some people only use
> > lists.apache.org and there may be people who were on an initial PPMC
> that
> > didn’t get involved or your podling may just be starting out.
> >
> > If your project is approaching graduation I’d especially suggest you try
> > and fix this.
> >
> > The number of missing signups here may indicate that there’s an issue
> e.g.
> > It may be that mentors are not active or not all PPMC members are
> actively
> > involved or it could be just an on-boarding issue of new PPMC members for
> > the podling or an initial steppe step that was skipped. Whatever it is it
> > wold be good to see more mentors and PPMC members signed up.
> > - Amaterasu - One mentor not signed up to private list and no PPMC member
> > signed up [1]
> > - Annotator  - Two mentors not signed up  and one PPMC member not signed
> > up [2]
> > - Datasketches - Five PPMC members not signed up [6]
> > - Flagon - Two mentors not signed up and three PPMC members not signed up
> > [13]
> > - Hivemall - Two mentors not signed up [15]
> > - Iceberg - One mentor not signed dup and all PPMC not signed up [17]
> > - MXNet - Thirteen PPMC members not signed up. [22]
> > - Nemo - Seven PPMC members not signed up. [24]
> > - Openwisk - Six PPMC members not signed up [26]
> > - Piont - One mentor not signed up and ten PPMC members not signed up.
> [28]
> > - Ratis - One mentor and five PPMC members not signed up. [30]
> > - Soma - Two mentors not signed up. [33]
> > - SDAP - Two mentors not signed up and eight PPMC members not signed up,
> > [34]
> > - Spot - Thirteen PPMC members not signed up. [37]
> > - Taverna - Two mentors and five PPMC members not signed up. [40]
> > - Training - Five PPMC members not signed up. [43]
> > - Tuweni - Six PPMC members not signed up. [44]
> >
> > These are less concerning, but it would be nice to see all mentors signed
> > up:
> > - BatchEE - One mentor not signed up and four PPMC members not signed up
> > [3]
> > - Crail - Three PPMC not signed up [4]
> > - Dories - One mentor not signed up and one PMC member not signed up. [8]
> > - Druid - Four PPMC members not signed up [9]
> > - Dubbo - Four PPMC members not signed up [10]
> > - ECharts - Four PPMC members not signed up [11]
> > - Goblin - One mentor not signed up and two PPMC members not signed up.
> > [14]
> > - Hudi - One mentor not signed up and one PPMC mentor not signed dup.
> [16]
> > - Livy - One mentor not signed up and one PPMC member not signed dup.
> [19]
> > - Omid - One mentor not signed up. [25]
> > - Superset - One mentor and one PPMc member not signed up. [38]
> > - Tamaya - One mentor and two PPMC members not signed up. [39]
> > - Tephra - One mentor and one PPMC member not signed up. [41]
> > - Shardingsphere - One mentor not signed up. [35]
> > - Singa - One mentor and one PP

Re: Podling PPMC members and mentors not signed up to private lists

[Huxing Zhang]

Hi,

> - Dubbo - Four PPMC members not signed up [10]

Three of the inactive PPMC have indicated to step down after the graduation.
For the remaining one, it is a known issue on the private@dubbo list.
The PPMC member has subscribed to private with apache mail address, I
am not sure why it is shown as not subscribed. I will continue to
investigate it.

-- 
Best Regards！
Huxing

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

Re: Podling PPMC members and mentors not signed up to private lists

[Justin Mclean]

Hi,

> It seems your information about the Tuweni project is incorrect.

How exactly?

As I said all the mentors are subscribed, blur there's are 6 PPMC members who 
are not subscribed and one person should shouldn’t be subscribed which the PPMC 
was asked to remove previously.

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