(Dev)

(Cmd)-recover_keyboad

Re: Suspicious file /dev/shm/ShM.c5fa4b64H8dd08c52

My mistake, thanks for the tip! Okay, great, glad to hear it's expected behavior. Best, Dan On Sun, Mar 10, 2024 at 7:35 PM Daniel Gruno wrote: > On 3/10/24 21:02, Dan Liebner wrote: > > This file `/dev/shm/ShM.c5fa4b64H8dd08c52` seems to be created by apache2 > > according

Re: Suspicious file /dev/shm/ShM.c5fa4b64H8dd08c52

On 3/10/24 21:02, Dan Liebner wrote: This file `/dev/shm/ShM.c5fa4b64H8dd08c52` seems to be created by apache2 according to my audit log. It goes away when apache2 is stopped. It originally showed up in a rkhunter scan. I can't find any information about it online except for similar report

Suspicious file /dev/shm/ShM.c5fa4b64H8dd08c52

This file `/dev/shm/ShM.c5fa4b64H8dd08c52` seems to be created by apache2 according to my audit log. It goes away when apache2 is stopped. It originally showed up in a rkhunter scan. I can't find any information about it online except for similar reports. Is this likely a legitimate file cr

Re: dev Digest 17 Mar 2023 17:32:48 -0000 Issue 2294

On Fri, 2023-03-17 at 19:14 +, Donavon Gamblin wrote: > > o unsubscribe, e-mail: dev-digest-unsubscr...@community.apache.org > > i need unsubscribed asap The instructions are in the email that you sent: > To unsubscribe, e-mail: dev-digest-unsubscr...@community.apache.org &

Re: dev Digest 17 Mar 2023 17:32:48 -0000 Issue 2294

o unsubscribe, e-mail: dev-digest-unsubscr...@community.apache.org i need unsubscribed asap From: dev-digest-h...@community.apache.org Sent: Friday, March 17, 2023 11:32 AM To: dev@community.apache.org Subject: dev Digest 17 Mar 2023 17:32:48 - Issue 2294

[jira] [Commented] (COMDEV-293) scandist does not detect releases renamed from dist/dev

form would it take in the pubsub-generated commit? The regex in `scandist.py` catches the release string as shown below: {{#!/usr/bin/env python3 import re path = "release/spark/spark-2.2.2" RELEASE_MATCH = r"^release/([^/]+)/" match = re.match(RELEASE_MATCH, path) print(matc

[jira] [Commented] (COMDEV-293) scandist does not detect releases renamed from dist/dev

all releases. > scandist does not detect releases renamed from dist/dev > --- > > Key: COMDEV-293 > URL: https://issues.apache.org/jira/browse/COMDEV-293 > Project: Community Develo

[jira] [Commented] (COMDEV-293) scandist does not detect releases renamed from dist/dev

here people needing it, etc.? I see it's looking for this pattern `RELEASE_MATCH = r"^release/([^/]+)/" # match any name followed by /`. Not immediately clear why it's not catching the path in `A /release/spark/spark-2.2.2 (from /dev/spark/v2.2.2-rc2-bin:27901)` > scandi

Fwd: confirm subscribe to dev@community.apache.org

-- Forwarded message - From: Date: Thu, Jun 16, 2022 at 10:15 PM Subject: http://www.apache.org/foundation/private-archives. <http://www.apache.org/foundation/public-archives.html>aspx= dev@community.apache.org To: Hi! This is the ezmlm program. I'm manag

Welcome to Apache ShardingSphere first DEV meetup

Hello community, Hope you all do well! Good news here! We plan to hold the first ShardingSphere Dev meetup on 13th Nov in Beijing and ONLINE! (You know, due to the coronavirus, it's likely the offline meetup will be canceled.) This is our first community meetup. We truly pay a l

Re: Subscribe dev@community.apache.org

Thank you very much, Andrew. Sent it again to dev-subscr...@community.apache.org. Best, Mark On 2021/09/16 12:37:36, Andrew Wetmore wrote: > I think the address you use is "dev-subscr...@community.apache.org" > > > Andrew > > On Thu, Sep 16, 2021

Re: Subscribe dev@community.apache.org

I think the address you use is "dev-subscr...@community.apache.org" Andrew On Thu, Sep 16, 2021 at 8:26 AM Mark Shan wrote: > Subscribe dev@community.apache.org > > -- > Mark Shan > -- Andrew Wetmore Technical Writer-Editor Infra *Apache Software Foundation* andr...@apache.org

****** CONFIRMED Follow-up & Thank you....We'll Be Happy to Subscribe to This August Organization & Our Best Wishes, too...**** Re: Subscribe dev@community.apache.org

the actions of men the best interpreters of their thoughts." - John Locke On 9/16/21, Mark Shan wrote: > Subscribe dev@community.apache.org > > -- > Mark Shan > -- Regards / Met vriendelijke groet Pw McKenna Carey, III #1137 432 Randall Rd.

Subscribe dev@community.apache.org

Subscribe dev@community.apache.org -- Mark Shan

dev-sc.1631789928.idabhbbbdkcgjjjlpjbh-xiaoyu=apache....@community.apache.org

dev-sc.1631789928.idabhbbbdkcgjjjlpjbh-xiaoyu= apache@community.apache.org

Re: [QUESTION] how to subscribe mail-list dev@community.apache.org?

zhenxu94 > > Begin forwarded message: > > *From: *Tomasz Urbaszek > *Subject: **Re: [QUESTION] how to subscribe mail-list > dev@community.apache.org ?* > *Date: *November 18, 2020 at 1:12:33 AM GMT+8 > *To: *dev > *Reply-To: *dev@community.apache.org > > If you want t

Fwd: [QUESTION] how to subscribe mail-list dev@community.apache.org?

Since he can’t subscribe to the ML so I guess it’s highly possible he can’t see this email, forwarding to him directly. — Zhenxu Ke (柯振旭) GitHub @kezhenxu94 > Begin forwarded message: > > From: Tomasz Urbaszek > Subject: Re: [QUESTION] how to subscribe m

Re: [QUESTION] how to subscribe mail-list dev@community.apache.org?

If you want to subscribe to dev@community.apache.org you need to send an email to dev-subscr...@community.apache.org as per this guide: https://www.apache.org/foundation/mailinglists.html https://www.apache.org/foundation/mailinglists.html#foundation-community Cheers, Tomek On Tue, Nov 17, 2020

[QUESTION] how to subscribe mail-list dev@community.apache.org?

Hi: I do not find the way. :( -- *MembPhis* My GitHub: https://github.com/membphis Apache APISIX: https://github.com/apache/apisix

Re: Dev model questions (Was Re: ASF Slack for community?)

has a healthy community with a functioning PMC to make its decisions. If you want to understand ASF better, I suggest picking a few projects that interest you and, for each PROJECT_NAME, subscribing to dev@PROJECT_NAME.apache.org. There you will see the project in action. 2. What release

Dev model questions (Was Re: ASF Slack for community?)

is to Linux) * https://sifted.eu/articles/element-germany-deal/ -- news about big government deployments of Matrix ----- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.ap

Re: Re: subscribe dev community

Yup,It's so great! DolphinScheduler(Incubator) PPMC Gang Li 李岗 lgcareer2...@outlook.com<mailto:lgcareer2...@outlook.com> From: Juan Pan Date: 2020-02-28 16:05 To: dev@community.apache.org CC: dev; lgcareer2...@outlook.com Subject: Re: subscribe dev community Detailed and so ki

Re: subscribe dev community

the mail mistakenly to the dev list, if this was intentional then for subscribing the mailing list, please send a mail to dev-subscr...@community.apache.org After this, you will receive a 'confirm subscribe' mail, simply send an empty reply to that as well. :) Best regards,

Re: subscribe dev community

Hello Gang Li, Welcome to the Apache Community Development! It seems you have sent the mail mistakenly to the dev list, if this was intentional then for subscribing the mailing list, please send a mail to dev-subscr...@community.apache.org After this, you will receive a 'confirm subscribe&

subscribe dev community

DolphinScheduler(Incubator) PPMC Gang Li 李岗 lgcareer2...@outlook.com

[jira] [Created] (DI-8) Point JIRA updates to dev@d.a.o

Andrew Musselman created DI-8: - Summary: Point JIRA updates to dev@d.a.o Key: DI-8 URL: https://issues.apache.org/jira/browse/DI-8 Project: Diversity and Inclusion Issue Type: Task

Re: Discussions in pull requests vs. dev list (was: The Apache Way and good developers...)

:02 PM Christopher wrote: > >>> ...it would be a mistake if ASF were to try to impose a more spammy > >>> workflow to dev@ onto every PMC, as a requirement... > >> > >> FWIW I didn't suggest imposing anything like that - my only concern is &g

Re: Discussions in pull requests vs. dev list (was: The Apache Way and good developers...)

> On Nov 5, 2018, at 8:35 AM, Christopher wrote: > > On Mon, Nov 5, 2018 at 3:49 AM Bertrand Delacretaz > wrote: >> >> Hi, >> >> On Fri, Nov 2, 2018 at 7:02 PM Christopher wrote: >>> ...it would be a mistake if ASF were to try to impose a mo

Re: Discussions in pull requests vs. dev list (was: The Apache Way and good developers...)

On Mon, Nov 5, 2018 at 3:49 AM Bertrand Delacretaz wrote: > > Hi, > > On Fri, Nov 2, 2018 at 7:02 PM Christopher wrote: > >...it would be a mistake if ASF were to try to impose a more spammy > > workflow to dev@ onto every PMC, as a requirement... > > FWIW I didn&#x

Re: Discussions in pull requests vs. dev list (was: The Apache Way and good developers...)

Hi, On Fri, Nov 2, 2018 at 7:02 PM Christopher wrote: >...it would be a mistake if ASF were to try to impose a more spammy > workflow to dev@ onto every PMC, as a requirement... FWIW I didn't suggest imposing anything like that - my only concern is that it should be possible to

Re: Discussions in pull requests vs. dev list (was: The Apache Way and good developers...)

This comes up a lot on Beam too. We have a practice where if a PR is a big change, or if discussion veers into into design details rather than just code, we expect our committers to say "let's move this to the dev list". We also try to encourage everyone to announce on dev@ not just

Re: Discussions in pull requests vs. dev list (was: The Apache Way and good developers...)

In Accumulo and Fluo, we route to notifications@ also. If these went to dev@, it would be too spammy, and I suspect even fewer people would participate on important dev@ threads than they do now. Letting it go to notifications@, people can subscribe to all activity there, if they wish... or they

Re: Discussions in pull requests vs. dev list (was: The Apache Way and good developers...)

We also use them successfully on CouchDB and I don't see the problem here. We do route these notifications to notifications@, not dev@. My email client properly threads multiple comments on the same PR. Another option is to use the GitHub "watch" functionality on a repository, wh

Re: Discussions in pull requests vs. dev list (was: The Apache Way and good developers...)

mail client to find 50 new emails and all of these are related to a single PR and each mail being a single comment. This is extremely annoying Chris Outlook for Android<https://aka.ms/ghei36> herunterladen From: Dave Fisher Sent: Friday, November 2, 2018 4:59:43 PM To: dev@community.apache.

Re: Discussions in pull requests vs. dev list (was: The Apache Way and good developers...)

most of the action happens on > GitHub (*) it can be hard or impossible to follow the action by just > subscribing to the project's dev list. > > I don't think there's anything wrong with discussions happening in > pull requests (PRs), that's the natural way of w

Discussions in pull requests vs. dev list (was: The Apache Way and good developers...)

ot;off-list" between the submitter and the other devs... I agree with that - in a project where most of the action happens on GitHub (*) it can be hard or impossible to follow the action by just subscribing to the project's dev list. I don't think there's anything wrong with discussi

Re: [Mifos-users] Dev vs User Mailing Lists

ng the fact that people will talk real time anyway - so why >> not make that a venue that you at least have some control/visibility over? >> In fact, my doctoral research was on how semi-synchronous communications >> support distance work and learning better than fully asynchronous

Re: Dev vs User Mailing Lists

us discussions will happen anyway and that's good. OTOH I think we have a number of podlings, and maybe projects, for which the dev list seems to be just an annoyance, things happen on Slack anyway so who cares? I'm pushing it a bit here but just a bit. I think there's a balance t

Re: Dev vs User Mailing Lists

nyway - so why > not make that a venue that you at least have some control/visibility over? > In fact, my doctoral research was on how semi-synchronous communications > support distance work and learning better than fully asynchronous ones.... > > -Joan > > - Original Message

Re: Dev vs User Mailing Lists

search was on how semi-synchronous communications support distance work and learning better than fully asynchronous ones -Joan - Original Message - From: "Bertrand Delacretaz" To: "dev" Cc: d...@fineract.apache.org, "Myrle Krantz" , mifos-devel

Re: Dev vs User Mailing Lists

Thanks for sharing that Bertrand - it was a good read - and easy for you to share because it was discussed publicly on a mailing list :) On that thread as well there was also a lot of support for a discourse-based forum too which can be a nice happy medium offering the advantages of a mailing lis

Re: Dev vs User Mailing Lists

org%3E -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org

Re: Dev vs User Mailing Lists

; correct way to achieve are through resources, Get Outlook for Android<https://aka.ms/ghei36> From: r...@gardler.org Sent: Tuesday, October 16, 2018 12:45:58 PM To: dev@community.apache.org; 'Dev'; 'Myrle Krantz' Cc: 'M

RE: Dev vs User Mailing Lists

le Sent: Monday, October 15, 2018 10:33 AM To: Dev ; Myrle Krantz Cc: Mifos software development ; mifos-users ; u...@fineract.apache.org; dev@community.apache.org Subject: Re: Dev vs User Mailing Lists Circling back to the original topic of discussion on this thread, given the volume on

Re: Dev vs User Mailing Lists

a mailing list seems an effective way to achieve our desired aim. If and when, volume grows too much or the dev list becomes unfocused or too chatty, we can set up the separate user list again. I will let discussion play out a bit more here and then start a separate thread with the proposal and

Re: Dev vs User Mailing Lists

Javier, Thanks for the suggestion about a WhatsApp group - I agree that a user-friendly more real-time chat tool is a nice complement to mailing lists but by no means a replacement. I agree with all the feedback shared by Mark and Myrle and don't really think WhatsApp might be the most ideal tool

Re: Dev vs User Mailing Lists

Thanks all for your comments, there are strong arguments against Whatsapp, and it seems that the biggest one is that cannot be stored on ASF servers (for now?). Hipchat is good, but Whatsapp is ubiquitous and for many of us, number 1 messaging and communication tool. We just need to lower the ent

Re: Dev vs User Mailing Lists

/browse/PYTHON-532 is a fantastic example of how to handle "difficult" bug reports) -Bertrand ----- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org

Re: Dev vs User Mailing Lists

On Sun, Oct 14, 2018 at 3:47 PM Shawn Heisey wrote: > ...I suspect that it's a little > bit odd within Apache for a dev list to be larger than a user list... It depends on the "shape" of your community. The rationale for recommending that (most) Apache podlings initially g

Re: Dev vs User Mailing Lists

On 10/10/2018 9:59 AM, Ed Cable wrote: Reading over the escalation guide and the advice it gave on directing appropriate issues/matters to the respective mailing lists, it got me thinking about our Fineract Dev and Fineract User lists. We are always trying to be inclusive especially around

Re: Dev vs User Mailing Lists

t for that and > > the community to grow. > > > > We are changing an entire industry as a community because the community > > outperforms the individuals. > > > > Let's keep rocking!! > > Javier > > > > El mié., 10 oct. 2018 a las 13:00, Ed Cabl

Re: Dev vs User Mailing Lists

l mié., 10 oct. 2018 a las 13:00, Ed Cable () escribió: > >> Reading over the escalation guide and the advice it gave on directing >> appropriate issues/matters to the respective mailing lists, it got me >> thinking about our Fineract Dev and Fineract User lists. >> >&g

Re: Dev vs User Mailing Lists

ms the individuals. Let's keep rocking!! Javier El mié., 10 oct. 2018 a las 13:00, Ed Cable () escribió: > Reading over the escalation guide and the advice it gave on directing > appropriate issues/matters to the respective mailing lists, it got me > thinking about our Fineract D

Re: Dev vs User Mailing Lists

www.google.com Xavier.Galindo1972 On Oct 11, 2018 04:53, "Bertrand Delacretaz" wrote: Hi, On Wed, Oct 10, 2018 at 6:00 PM Ed Cable wrote: > ...One possible option is just to consolidate the lists into dev but I don't > think that is good long-term because as communi

Re: Dev vs User Mailing Lists

Hi, On Wed, Oct 10, 2018 at 6:00 PM Ed Cable wrote: > ...One possible option is just to consolidate the lists into dev but I don't > think that is good long-term because as community grows we will have > distinct technical vs. functional/design conversations happening... Until tha

Re: Dev vs User Mailing Lists

sts, it got me > thinking about our Fineract Dev and Fineract User lists. > > We are always trying to be inclusive especially around awarding merit or > committership in valuing non-technical contributions to the project. In > that same spirit, I worry we sometimes might be leaving o

Dev vs User Mailing Lists

Reading over the escalation guide and the advice it gave on directing appropriate issues/matters to the respective mailing lists, it got me thinking about our Fineract Dev and Fineract User lists. We are always trying to be inclusive especially around awarding merit or committership in valuing

[jira] [Created] (COMDEV-293) scandist does not detect releases renamed from dist/dev

Sebb created COMDEV-293: --- Summary: scandist does not detect releases renamed from dist/dev Key: COMDEV-293 URL: https://issues.apache.org/jira/browse/COMDEV-293 Project: Community Development Issue

Fwd: confirm subscrbe to dev@community.apache.org

-- Forwarded message - From: Date: Sat, May 5, 2018, 5:12 AM Subject: confirm subscribe to dev@community.apache.org To: <27bw...@gmail.com> Hi! This is the ezmlm program. I'm managing the dev@community.apache.org mailing list. I'm working for my owner, who can b

[jira] [Updated] (COMDEV-280) OpenWhisk GSOC: Dev Experience: IDE Debugging (VSCode, IntelliJ)

[ https://issues.apache.org/jira/browse/COMDEV-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated COMDEV-280: Component/s: GSoC/Mentoring ideas > OpenWhisk GSOC: Dev Experience: IDE Debugging (VSCode, Intel

[jira] [Commented] (COMDEV-280) OpenWhisk GSOC: Dev Experience: IDE Debugging (VSCode, IntelliJ)

aduate in the computer science and engineering, University of Moratuwa. How do I start to work on this project? I would love to work with your foundation and as Openwhisk is a new topic for me and I need a good starting point. > OpenWhisk GSOC: Dev Experience: IDE Debugging (VSCo

[jira] [Updated] (COMDEV-280) OpenWhisk GSOC: Dev Experience: IDE Debugging (VSCode, IntelliJ)

[ https://issues.apache.org/jira/browse/COMDEV-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Santana updated COMDEV-280: -- Issue Type: Brainstorming (was: Project) > OpenWhisk GSOC: Dev Experience: IDE Debugg

[jira] [Created] (COMDEV-280) OpenWhisk GSOC: Dev Experience: IDE Debugging (VSCode, IntelliJ)

Carlos Santana created COMDEV-280: - Summary: OpenWhisk GSOC: Dev Experience: IDE Debugging (VSCode, IntelliJ) Key: COMDEV-280 URL: https://issues.apache.org/jira/browse/COMDEV-280 Project: Community

Re: IBM's first Index dev conf in San Francisco

you all think? I can probably reach out to Todd Moore if this suggestion makes sense. That said, if anyone here (like Sam for example) have a more direct line of sight into IBM's dev-rel organization -- that may help as well. Thanks, Roman. Thanks for this notice. More exposure for the ASF at gener

IBM's first Index dev conf in San Francisco

his suggestion makes sense. That said, if anyone here (like Sam for example) have a more direct line of sight into IBM's dev-rel organization -- that may help as well. Thanks, Roman. - To unsubscribe, e-mail: dev-unsubscr...

dev-uc.1497794773.iffkkbnnflcdmiddmbip-siriso=protonmail....@community.apache.org

Sent with [ProtonMail](https://protonmail.com) Secure Email. Original Message Subject: confirm unsubscribe from dev@community.apache.org Local Time: June 18, 2017 4:06 PM UTC Time: June 18, 2017 2:06 PM From: dev-h...@community.apache.org To: sir...@protonmail.com Hi! This is

Re: confirm subscribe to dev@community.apache.org

On Mon, Mar 27, 2017, at 03:31 PM, dev-h...@community.apache.org wrote: > Hi! This is the ezmlm program. I'm managing the > dev@community.apache.org mailing list. > > I'm working for my owner, who can be reached > at dev-ow...@community.apache.org. > > To confirm

Re: confirm unsubscribe from dev@community.apache.org

Unsubscribe On 28-Sep-2016 5:44 AM, "Igor Galić" wrote: > > > ​​-- > Igor Galić > > Tel: +43 (0) 664 886 22 883 > Mail: i.ga...@brainsware.org > URL: https://brainsware.org/ > GPG: 8716 7A9F 989B ABD5 100F 4008 F266 55D6 2998 1641 >

Re: confirm unsubscribe from dev@community.apache.org

​​-- Igor Galić Tel: +43 (0) 664 886 22 883 Mail: i.ga...@brainsware.org URL: https://brainsware.org/ GPG: 8716 7A9F 989B ABD5 100F 4008 F266 55D6 2998 1641 On Wed, 28 Sep 2016, at 02:14, dev-h...@community.apache.org wrote: > Hi! This is the ezmlm program. I'm managing t

Re: confirm subscribe to dev@community.apache.org

hi On 3 June 2016 at 15:55, wrote: > Hi! This is the ezmlm program. I'm managing the > dev@community.apache.org mailing list. > > I'm working for my owner, who can be reached > at dev-ow...@community.apache.org. > > To confirm that you would like > >pra

Re: confirm subscribe to dev@community.apache.org

ys On Jun 3, 2016 8:32 PM, "prakriti pandey" wrote: > On 3 June 2016 at 15:55, wrote: > > > Hi! This is the ezmlm program. I'm managing the > > dev@community.apache.org mailing list. > > > > I'm working for my owner, who can be reached > &g

Re: confirm subscribe to dev@community.apache.org

On 3 June 2016 at 15:55, wrote: > Hi! This is the ezmlm program. I'm managing the > dev@community.apache.org mailing list. > > I'm working for my owner, who can be reached > at dev-ow...@community.apache.org. > > To confirm that you would like > >prakrit

Re: dev Digest 5 Dec 2015 14:15:39 -0000 Issue 789

:) Thank you all Apache OpenOffice. Grand. Absolutely grand. On Sat, Dec 5, 2015 at 6:15 AM, wrote: > > >

Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)

On 09.01.2015 15:43, Branko Čibej wrote: > On 09.01.2015 14:04, Ulrich Stärk wrote: >> If I'm not mistaken, SVN does the same (combine and compress all changes >> prior to sending it over >> the wire). > Not entirely; it sends deltas and will compress new files IF the server > has mod_deflate conf

Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)

On 09.01.2015 14:04, Ulrich Stärk wrote: > If I'm not mistaken, SVN does the same (combine and compress all changes > prior to sending it over > the wire). Not entirely; it sends deltas and will compress new files IF the server has mod_deflate configured (but they usually don't because there was

Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)

t;>> I would like to express demand from the Flink project. svn is a pain to >>> use >>> (since we host javadocs and our documentation on our website, the upload >>> usually runs for 6+ hours. Probably because its so many files). >>> >> How is that

Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)

On 08.01.2015 19:01, jan i wrote: > On 8 January 2015 at 18:51, Branko Čibej wrote: > >> In cases like this I'd strongly recommend that you ask Infra to set up a >> small VM for you to build and host the Javadocs on, and link to that >> from your web site (or proxy it; the VM itself doesn't have t

Re: GitHub pages for git based Apache projects (Was: Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org))

On Thu, Jan 8, 2015 at 3:29 AM, Bertrand Delacretaz wrote: > Hi, > > On Thu, Jan 8, 2015 at 10:14 AM, Ted Dunning > wrote: > > ...Apache Drill has been doing something like this for some time. They > use > > Jekyll from Github to render markdown as HTML and then commit the HTML to > > SVN to th

Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)

On 8 January 2015 at 18:51, Branko Čibej wrote: > On 08.01.2015 17:12, Robert Metzger wrote: > > Hi Brane, > > See answer inline: > > > > On Thu, Jan 8, 2015 at 4:29 PM, Branko Čibej wrote: > > > >> On 08.01.2015 09:55, Robert Metzger wrote: > >>> Hi, > >>> > If there is sufficient demand,

Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)

On 08.01.2015 17:12, Robert Metzger wrote: > Hi Brane, > See answer inline: > > On Thu, Jan 8, 2015 at 4:29 PM, Branko Čibej wrote: > >> On 08.01.2015 09:55, Robert Metzger wrote: >>> Hi, >>> If there is sufficient demand, however, that could change - the code >> that >>> would make this poss

Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)

On Thu, Jan 8, 2015 at 11:24 AM, Roman Shaposhnik wrote: > On Wed, Jan 7, 2015 at 12:42 PM, Daniel Gruno > wrote: > > The main reason we do not support git in this workflow is that git does > not > > enable single-file checkouts, and that we haven't properly tested > gitwcsub > > (a git version

Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)

On Wed, Jan 7, 2015 at 12:42 PM, Daniel Gruno wrote: > The main reason we do not support git in this workflow is that git does not > enable single-file checkouts, and that we haven't properly tested gitwcsub > (a git version of svnwcsub which is the frontend for svnpubsub) for web > sites yet. If

Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)

Hi Brane, See answer inline: On Thu, Jan 8, 2015 at 4:29 PM, Branko Čibej wrote: > On 08.01.2015 09:55, Robert Metzger wrote: > > Hi, > > > >> If there is sufficient demand, however, that could change - the code > that > > would make this possible does exist. > > > > I would like to express dema

Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)

Thanks for the feedback ! How about, then this solution : A cron job which copies all files from site/ in xyz apache project, into /content, every day, and does a svn commit. 1) We can try this for one of our projects (maybe i can propose it bigtop) ... and if it works Maybe even donate/broaden i

Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)

On Thu, Jan 8, 2015 at 10:24 AM, jay vyas wrote: > IS the ASF okay with simply doing a one time commit to SVN, of a single > HTML page which forwards to gh-pages? > I am pretty sure there is a brand requirement that the project's web site is at $foo.a.o - http://www.apache.org/foundation/marks/pm

Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)

On Thu, Jan 8, 2015 at 4:24 PM, jay vyas wrote: > ...IS the ASF okay with simply doing a one time commit to SVN, of a single > HTML page which forwards to gh-pages?.. You mean redirect to github which has the actual content? That's not ok IMO, like our source code our websites have to be hosted

Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)

On 08.01.2015 09:55, Robert Metzger wrote: > Hi, > >> If there is sufficient demand, however, that could change - the code that > would make this possible does exist. > > I would like to express demand from the Flink project. svn is a pain to use > (since we host javadocs and our documentation on o

Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)

IS the ASF okay with simply doing a one time commit to SVN, of a single HTML page which forwards to gh-pages? On Thu, Jan 8, 2015 at 9:19 AM, David Nalley wrote: > On Thu, Jan 8, 2015 at 3:55 AM, Robert Metzger > wrote: > > Hi, > > > >> If there is sufficient demand, however, that could change

Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)

On Thu, Jan 8, 2015 at 3:55 AM, Robert Metzger wrote: > Hi, > >> If there is sufficient demand, however, that could change - the code that > would make this possible does exist. > > I would like to express demand from the Flink project. svn is a pain to use > (since we host javadocs and our docume

Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)

; use > >> (since we host javadocs and our documentation on our website, the upload > >> usually runs for 6+ hours. Probably because its so many files). > >> > > How is that in any way related to svn? svn or git, if you have that many > > files, it's going

Re: GitHub pages for git based Apache projects (Was: Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org))

Hi, On Thu, Jan 8, 2015 at 10:14 AM, Ted Dunning wrote: > ...Apache Drill has been doing something like this for some time. They use > Jekyll from Github to render markdown as HTML and then commit the HTML to > SVN to that pubsub carries it to the right places... Do you have URLs that show how

Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)

that many > files, it's going to take ages to upload regardless of which repository > system you use. > > If it makes it easier, you might peruse http://www.apache.org/dev/ > cmsref.html#external-build and see if you can't use an external build job > for you site - that

Re: GitHub pages for git based Apache projects (Was: Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org))

projects site, which could then be > >> committed > >> to a gh-pages branch for git based projects. Would anybody be interested > >> in > >> joining such an endeavor? > >> > >> Benedikt > >> > >> 2015-01-07 21:36 GMT+01:00 Ross Gar

Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)

http://www.apache.org/dev/cmsref.html#external-build and see if you can't use an external build job for you site - that way, you just commit the changes to your template/raw docs, and the CMS system builds the javadoc for you. Almost all incoming incubator projects are using git nowadays. Many o

Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)

! >>>> >>>> Whats the simplest way to maintain the xyz.apache.org site? Right now >>>> we >>>> push to SVN, but would be great to use something like the github.io >>>> model, >>>> where the static pages are just hosted directly. >

Re: GitHub pages for git based Apache projects (Was: Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org))

s branch for git based projects. Would anybody be interested >> in >> joining such an endeavor? >> >> Benedikt >> >> 2015-01-07 21:36 GMT+01:00 Ross Gardler (MS OPEN TECH) < >> ross.gard...@microsoft.com>: >> >> The answer to your qu

Re: GitHub pages for git based Apache projects (Was: Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org))

ody be interested in joining such an endeavor? Benedikt 2015-01-07 21:36 GMT+01:00 Ross Gardler (MS OPEN TECH) < ross.gard...@microsoft.com>: The answer to your question is different depending on what xyz is in http://xyz.apache.org Probably the most common answer is http://www.apache.org/dev/c

GitHub pages for git based Apache projects (Was: Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org))

Ross Gardler (MS OPEN TECH) < ross.gard...@microsoft.com>: > The answer to your question is different depending on what xyz is in > http://xyz.apache.org > > Probably the most common answer is http://www.apache.org/dev/cmsref.html > > Microsoft Open Technologies, Inc. > A sub

Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)

s are just hosted directly. On Wed, Jan 7, 2015 at 2:56 PM, wrote: Hi! This is the ezmlm program. I'm managing the dev@community.apache.org mailing list. I'm working for my owner, who can be reached at dev-ow...@community.apache.org. Acknowledgment: I have added the address

  1   2   >