Re: [Proposal] ASF Fediverse/ActivityPub instance

I like my j...@apache.org email to ! 😊 From: Owen O'Malley Date: Monday, December 5, 2022 at 7:25 PM To: dev@community.apache.org Subject: Re: [Proposal] ASF Fediverse/ActivityPub instance I disagree. I think having an individual identity at Apache is important. Just beca

Re: Keeping PMC communications public when possible -- is an obvious-looking address responsible?

At the CNCF, I’ve noticed that almost all decisions are made in hangouts and in GitHub issues, and proposals. It definitely is a model that can work. Not saying we should copy them, but just noting that there’s more then one way to skin a cat, and there aren’t any right answers here. > On Dec

Re: Keeping PMC communications public when possible -- is an obvious-looking address responsible?

Agree / propose: remove all private communication. Other foundations are becoming more open then us, and the overhead of managing the process is in and of itself a cost we can’t afford in a fast moving world. > On Dec 6, 2018, at 8:02 AM, Bertrand Delacretaz > wrote: > > Hi, > >> On Thu, Dec

Re: Great example of the benefit of a low barrier to entry

+1000, lowering entry barriers is overlooked . Nothing more annoying then taking time out of your day to contribute an idea to an open source project and then having to get the third degree in a review process. Github makes this easy with its PR editing and suggesting stuff. I wonder if we rea

Re: slack

A great offset to the **true danger** which is "Real time closed door communication" is "Real time open communication.". This gives the open source engineer a defensible reason to be transparent tell "we can easily have this discussion in the community" > On Aug 10, 2015, at 12:43 PM, Ma

Re: slack

Good point benson, and I definetely agree with the values *but* I don't think i agree w/ the conclusion. 1) We have to trust PMCs to foster a healthy and transparent roadmap. Exclusive cliques and backchannels should not ever exist in a healthy ASF project, period. 2) Restricting a projects

Re: slack

the asf uses slack and hip hat and atlassian already so the open source debate is moot, right? People will use the best tools for the job and so that should be the focus. I'm neutral on slack vs irc, but I think if growing the ASF is important slack will be of major benefit. > On Aug 8, 2015

Re: GitHub Pages

n a fork, before doing a PR against the gh-pages branch. If > > ASF ever did provide automated rendering, this is one reason I'd want > > it to be gh-pages compatible (because users who don't/can't have the > > build tools locally, can still make helpful contributions). > > > > > > -- > Niclas Hedhman, Software Developer > http://zest.apache.org - New Energy for Java > -- jay vyas

Re: GitHub Pages

Yeah, same question... Svn pushing or CMS still required? According to the snippet below the svn part is no longer needed? But maybe I'm misinterpreting ...? > On Aug 3, 2015, at 11:22 AM, Stian Soiland-Reyes wrote: > > This looks good. > > So do I understand any of the commiters editing

Re: GitHub Pages

t; >>> > > > >>> > > > >>> I'm not sure I understand how Jekyll affects that. Are we concerned > > >>> that GitHub will not render the site's source accurately? And, if so, > > >>> wouldn't that concern extend to non-Jekyll static sources also? > > >>> > > >>> > > >>> > There have been objections in this thread about using github.io > > >>> > based sites even with site name masquerading. > > >>> > > > >>> > > > >>> Does anybody wish to summarize those? I think it would be helpful. > > >>> > > >>> > > >>> > Sent from my iPhone > > >>> > > > >>> > > On Mar 6, 2015, at 14:36, Christopher > wrote: > > >>> > > > > >>> > > Regarding some of the other comments about jekyll... it's not > true > > >>> > > that > > >>> > you > > >>> > > need jekyll. You can publish plain HTML or Markdown also. > > >>> > > > >>> > > > -- jay vyas

Re: Lightning talks

are you > willing to be the Lightning Talks MC? (Wednesday evening, after Andy > Terrel's keynote.) > >>> > >>> -- > >>> Rich Bowen - rbo...@rcbowen.com - @rbowen > >>> http://apachecon.com/ - @apachecon > >> > > -- jay vyas

Re: GitHub Pages

yup ! GH-pages just finds the branch. if its there it displays it. its a totally decoupled publishing tool. ​using gh-pages as a convention could allow automation of th SVN tooling as well, so its really a great, cross platform convention that wont force coupling to github.

Re: GitHub Pages

atible mechanism to render these branches in our > infrastructure as an alternative to CMS. That seems like more work for > INFRA, though. > > > -- > Christopher L Tubbs II > http://gravatar.com/ctubbsii > > On Wed, Mar 4, 2015 at 6:23 PM, Jay Vyas > wrote: > &

Re: GitHub Pages

I like the idea. Anything to avoid requiring svn to update project sites. But... Iirc I started a similar thread before and was told that forwarding Apache.org to github static site was against the rules ?Maybe I misinterpreted ... > On Mar 4, 2015, at 4:06 PM, Christopher wrote: > > All, >

Groovy: Great news ! Willing to help.

mming language that is a project in the ASF ? If so, thats really great news ! -- jay vyas

Re: [IDEA] ASF "Certifications"

inal Message- > From: Rich Bowen [mailto:rbo...@rcbowen.com] > Sent: Friday, February 20, 2015 12:55 PM > To: dev@community.apache.org > Subject: Re: [IDEA] ASF "Certifications" > > > > On 02/20/2015 12:26 PM, jay vyas wrote: > > Hi apache. Just had

[IDEA] ASF "Certifications"

e the back flow of collaboration from companies as well. I think alot of other projects (for example, even the Apache HTTP server, Derby, CTakes, and so on). -- jay vyas

Mailing lists, sites, ...

Hi Apache . Every so often we get the question come up: does Apache infra allow/support . The answer is sometimes "not yet" and related to the fact that there are 100s of projects that require uniformity at Apache, and it would be chaos of every new project was allowed a new infrastructure

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

fra to do it that we can copy? On Thu, Jan 8, 2015 at 9:31 AM, David Nalley wrote: > 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? > > > >

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

ty. With the projects on > folks plates right now, the contractors at least, won't have time to > begin looking at this for at least 18 months. Volunteers could of > course tackle this if wanted. > > --David > -- jay vyas

Re: WELCOME to dev@community.apache.org

> Daniel. > > On 2015-01-07 21:06, jay vyas wrote: > >> Hi apache ! >> >> 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 sta

Re: WELCOME to dev@community.apache.org

GC5tWd > KASw== > MIME-Version: 1.0 > X-Received: by 10.194.88.131 with SMTP id bg3mr9420545wjb.99.1420660578606; > Wed, 07 Jan 2015 11:56:18 -0800 (PST) > Received: by 10.27.144.214 with HTTP; Wed, 7 Jan 2015 11:56:18 -0800 (PST) > In-Reply-To: <1420660420.2944.