You are viewing a plain text version of this content. The canonical link for it is here.
Posted to diversity@apache.org by Naomi Slater <no...@tumbolia.org> on 2019/05/29 10:43:23 UTC
[PROPOSAL] send automated emails to dev@diversity
(copying diversity@apache.org for the time being because I expect it will
take a few days for everyone to move over to dev@diversity.apache.org)
now that we have dev@ set up, I would like to propose that we start sending
automated emails to the list
this is fairly standard practice at the ASF (although not ubiquitous) and
makes dev@ the hub of activity for our collective oversight
specifically, at the moment:
- automated emails from our JIRA project
- automated emails from our wiki
I am not too familiar with how Pelican works (the system that will power
our website at diversity.apache.org) but if there are changeset emails or
such like, I propose we send copies to dev@
I also propose that any Git projects we might end up using send copies of
automated emails to dev@
anything else I'm missing?
Re: [PROPOSAL] send automated emails to dev@diversity
Posted by Aizhamal Nurmamat kyzy <ai...@google.com.INVALID>.
+1
On Wed, May 29, 2019 at 3:16 PM Joan Touzet <wo...@apache.org> wrote:
> Also +1 for Git, and if it's like the project in which we're involved,
> an asf-site branch can def. be used to autopublish a website.
>
> -Joan
>
> On 2019-05-29 8:43, Myrle Krantz wrote:
> > On Wed, May 29, 2019 at 1:46 PM Naomi Slater <no...@tumbolia.org> wrote:
> >
> >> Git imo. so we can work on GitHub (assuming this is in fact possible for
> >> the website)
> >>
> >
> > +1 Git. I use svn when I have to, but I'm not super comfortable with it
> > yet.
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: diversity-unsubscribe@apache.org
> For additional commands, e-mail: diversity-help@apache.org
>
>
Re: Fwd: [PROPOSAL] send automated emails to dev@diversity
Posted by Joan Touzet <wo...@apache.org>.
Hi Trevor,
On 2019-05-29 6:55 p.m., Trevor Grant wrote:
> If the repo is only website code, then you can do it with git pages.
ASF Infra has special code that extends beyond the functionality of
GitHub Pages. We'll work with them to have the site published.
I was referring to this code when I talked about using the special
"asf-site" branch.
You can see this here:
https://github.com/apache/couchdb-www
> However, back to original proposal of "email us changes",
>
> I might recommend another mailing list like commits@d.a.o for the automated
> stuff (which I also think is sometimes a standard practice) bc depending
> how many commits you're getting, that can get real spammy real fast.
I agree, though hopefully it's not changing that often...and we're still
a small group. Let's deal with splitting the lists when the volume
becomes too high.
-Joan
---------------------------------------------------------------------
To unsubscribe, e-mail: diversity-unsubscribe@apache.org
For additional commands, e-mail: diversity-help@apache.org
Re: Fwd: [PROPOSAL] send automated emails to dev@diversity
Posted by Joan Touzet <wo...@apache.org>.
Hi Trevor,
On 2019-05-29 6:55 p.m., Trevor Grant wrote:
> If the repo is only website code, then you can do it with git pages.
ASF Infra has special code that extends beyond the functionality of
GitHub Pages. We'll work with them to have the site published.
I was referring to this code when I talked about using the special
"asf-site" branch.
You can see this here:
https://github.com/apache/couchdb-www
> However, back to original proposal of "email us changes",
>
> I might recommend another mailing list like commits@d.a.o for the automated
> stuff (which I also think is sometimes a standard practice) bc depending
> how many commits you're getting, that can get real spammy real fast.
I agree, though hopefully it's not changing that often...and we're still
a small group. Let's deal with splitting the lists when the volume
becomes too high.
-Joan
Fwd: [PROPOSAL] send automated emails to dev@diversity
Posted by Trevor Grant <tr...@gmail.com>.
lulz, I wasn't subscribed to dev@ (I also didn't reply-to, but even if i
had it wouldn't have worked).
see below
---------- Forwarded message ---------
From: Trevor Grant <tr...@gmail.com>
Date: Wed, May 29, 2019 at 5:53 PM
Subject: Re: [PROPOSAL] send automated emails to dev@diversity
To: <di...@apache.org>
Hey all,
Long time lurker, first time talker:
I actually set this up for the Mahout project.
If the repo is only website code, then you can do it with git pages.
If the website is just one directory, then you just set it up to do execute
a build script in travis CI which builds the site then copies the HTML
files to where they go. Happy to help if needed.
However, back to original proposal of "email us changes",
I might recommend another mailing list like commits@d.a.o for the automated
stuff (which I also think is sometimes a standard practice) bc depending
how many commits you're getting, that can get real spammy real fast.
just my .02
On Wed, May 29, 2019 at 5:16 PM Joan Touzet <wo...@apache.org> wrote:
> Also +1 for Git, and if it's like the project in which we're involved,
> an asf-site branch can def. be used to autopublish a website.
>
> -Joan
>
> On 2019-05-29 8:43, Myrle Krantz wrote:
> > On Wed, May 29, 2019 at 1:46 PM Naomi Slater <no...@tumbolia.org> wrote:
> >
> >> Git imo. so we can work on GitHub (assuming this is in fact possible for
> >> the website)
> >>
> >
> > +1 Git. I use svn when I have to, but I'm not super comfortable with it
> > yet.
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: diversity-unsubscribe@apache.org
> For additional commands, e-mail: diversity-help@apache.org
>
>
Fwd: [PROPOSAL] send automated emails to dev@diversity
Posted by Trevor Grant <tr...@gmail.com>.
lulz, I wasn't subscribed to dev@ (I also didn't reply-to, but even if i
had it wouldn't have worked).
see below
---------- Forwarded message ---------
From: Trevor Grant <tr...@gmail.com>
Date: Wed, May 29, 2019 at 5:53 PM
Subject: Re: [PROPOSAL] send automated emails to dev@diversity
To: <di...@apache.org>
Hey all,
Long time lurker, first time talker:
I actually set this up for the Mahout project.
If the repo is only website code, then you can do it with git pages.
If the website is just one directory, then you just set it up to do execute
a build script in travis CI which builds the site then copies the HTML
files to where they go. Happy to help if needed.
However, back to original proposal of "email us changes",
I might recommend another mailing list like commits@d.a.o for the automated
stuff (which I also think is sometimes a standard practice) bc depending
how many commits you're getting, that can get real spammy real fast.
just my .02
On Wed, May 29, 2019 at 5:16 PM Joan Touzet <wo...@apache.org> wrote:
> Also +1 for Git, and if it's like the project in which we're involved,
> an asf-site branch can def. be used to autopublish a website.
>
> -Joan
>
> On 2019-05-29 8:43, Myrle Krantz wrote:
> > On Wed, May 29, 2019 at 1:46 PM Naomi Slater <no...@tumbolia.org> wrote:
> >
> >> Git imo. so we can work on GitHub (assuming this is in fact possible for
> >> the website)
> >>
> >
> > +1 Git. I use svn when I have to, but I'm not super comfortable with it
> > yet.
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: diversity-unsubscribe@apache.org
> For additional commands, e-mail: diversity-help@apache.org
>
>
Re: [PROPOSAL] send automated emails to dev@diversity
Posted by Trevor Grant <tr...@gmail.com>.
Hey all,
Long time lurker, first time talker:
I actually set this up for the Mahout project.
If the repo is only website code, then you can do it with git pages.
If the website is just one directory, then you just set it up to do execute
a build script in travis CI which builds the site then copies the HTML
files to where they go. Happy to help if needed.
However, back to original proposal of "email us changes",
I might recommend another mailing list like commits@d.a.o for the automated
stuff (which I also think is sometimes a standard practice) bc depending
how many commits you're getting, that can get real spammy real fast.
just my .02
On Wed, May 29, 2019 at 5:16 PM Joan Touzet <wo...@apache.org> wrote:
> Also +1 for Git, and if it's like the project in which we're involved,
> an asf-site branch can def. be used to autopublish a website.
>
> -Joan
>
> On 2019-05-29 8:43, Myrle Krantz wrote:
> > On Wed, May 29, 2019 at 1:46 PM Naomi Slater <no...@tumbolia.org> wrote:
> >
> >> Git imo. so we can work on GitHub (assuming this is in fact possible for
> >> the website)
> >>
> >
> > +1 Git. I use svn when I have to, but I'm not super comfortable with it
> > yet.
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: diversity-unsubscribe@apache.org
> For additional commands, e-mail: diversity-help@apache.org
>
>
Re: [PROPOSAL] send automated emails to dev@diversity
Posted by Joan Touzet <wo...@apache.org>.
Also +1 for Git, and if it's like the project in which we're involved,
an asf-site branch can def. be used to autopublish a website.
-Joan
On 2019-05-29 8:43, Myrle Krantz wrote:
> On Wed, May 29, 2019 at 1:46 PM Naomi Slater <no...@tumbolia.org> wrote:
>
>> Git imo. so we can work on GitHub (assuming this is in fact possible for
>> the website)
>>
>
> +1 Git. I use svn when I have to, but I'm not super comfortable with it
> yet.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: diversity-unsubscribe@apache.org
For additional commands, e-mail: diversity-help@apache.org
Re: [PROPOSAL] send automated emails to dev@diversity
Posted by Myrle Krantz <my...@apache.org>.
On Wed, May 29, 2019 at 1:46 PM Naomi Slater <no...@tumbolia.org> wrote:
> Git imo. so we can work on GitHub (assuming this is in fact possible for
> the website)
>
+1 Git. I use svn when I have to, but I'm not super comfortable with it
yet.
Re: [PROPOSAL] send automated emails to dev@diversity
Posted by Myrle Krantz <my...@apache.org>.
On Wed, May 29, 2019 at 1:46 PM Naomi Slater <no...@tumbolia.org> wrote:
> Git imo. so we can work on GitHub (assuming this is in fact possible for
> the website)
>
+1 Git. I use svn when I have to, but I'm not super comfortable with it
yet.
Re: [PROPOSAL] send automated emails to dev@diversity
Posted by Naomi Slater <no...@tumbolia.org>.
On Wed, 29 May 2019 at 13:44, Shane Curcuru <as...@shanecurcuru.org> wrote:
>
> Pelican is just the templating/build system. The files will still be in
> a traditional SVN or git repository. Question: which do we want to use?
>
Git imo. so we can work on GitHub (assuming this is in fact possible for
the website)
Re: [PROPOSAL] send automated emails to dev@diversity
Posted by Naomi Slater <no...@tumbolia.org>.
On Wed, 29 May 2019 at 13:44, Shane Curcuru <as...@shanecurcuru.org> wrote:
>
> Pelican is just the templating/build system. The files will still be in
> a traditional SVN or git repository. Question: which do we want to use?
>
Git imo. so we can work on GitHub (assuming this is in fact possible for
the website)
Re: [PROPOSAL] send automated emails to dev@diversity
Posted by Shane Curcuru <as...@shanecurcuru.org>.
Naomi Slater wrote on 2019-5-29 6:43AM EDT:
> (copying diversity@apache.org for the time being because I expect it will
> take a few days for everyone to move over to dev@diversity.apache.org)
(Replying to corrected list name as you noted)
>
> now that we have dev@ set up, I would like to propose that we start sending
> automated emails to the list
ProTip: Apache committers can self-subscribe to lists via Whimsy:
https://whimsy.apache.org/committers/subscribe (requires login)
> this is fairly standard practice at the ASF (although not ubiquitous) and
> makes dev@ the hub of activity for our collective oversight
>
> specifically, at the moment:
>
> - automated emails from our JIRA project
> - automated emails from our wiki
+1, good idea.
> I am not too familiar with how Pelican works (the system that will power
> our website at diversity.apache.org) but if there are changeset emails or
> such like, I propose we send copies to dev@
Pelican is just the templating/build system. The files will still be in
a traditional SVN or git repository. Question: which do we want to use?
> I also propose that any Git projects we might end up using send copies of
> automated emails to dev@
>
> anything else I'm missing?
>
--
- Shane
Director & Member
The Apache Software Foundation
---------------------------------------------------------------------
To unsubscribe, e-mail: diversity-unsubscribe@apache.org
For additional commands, e-mail: diversity-help@apache.org
Re: [PROPOSAL] send automated emails to dev@diversity
Posted by Naomi Slater <no...@tumbolia.org>.
adding dev@diversity.apache.org properly this time. I made a typo in my
first email CC line. please reply to this email with further replies so
that the new list gets copies (and so you don't get "email address doesn't
exist" messages)
On Wed, 29 May 2019 at 13:03, Awasum Yannick <aw...@apache.org> wrote:
> +1
>
> On Wed, May 29, 2019 at 12:02 PM Myrle Krantz <my...@apache.org> wrote:
>
> > +1
> >
> > On Wed, May 29, 2019 at 12:53 PM Naomi Slater <no...@tumbolia.org> wrote:
> >
> > > (copying diversity@apache.org for the time being because I expect it
> > will
> > > take a few days for everyone to move over to dev@diversity.apache.org)
> > >
> > > now that we have dev@ set up, I would like to propose that we start
> > > sending
> > > automated emails to the list
> > >
> > > this is fairly standard practice at the ASF (although not ubiquitous)
> and
> > > makes dev@ the hub of activity for our collective oversight
> > >
> > > specifically, at the moment:
> > >
> > > - automated emails from our JIRA project
> > > - automated emails from our wiki
> > >
> > > I am not too familiar with how Pelican works (the system that will
> power
> > > our website at diversity.apache.org) but if there are changeset emails
> > or
> > > such like, I propose we send copies to dev@
> > >
> > > I also propose that any Git projects we might end up using send copies
> of
> > > automated emails to dev@
> > >
> > > anything else I'm missing?
> > >
> >
>
Re: [PROPOSAL] send automated emails to dev@diversity
Posted by Naomi Slater <no...@tumbolia.org>.
adding dev@diversity.apache.org properly this time. I made a typo in my
first email CC line. please reply to this email with further replies so
that the new list gets copies (and so you don't get "email address doesn't
exist" messages)
On Wed, 29 May 2019 at 13:03, Awasum Yannick <aw...@apache.org> wrote:
> +1
>
> On Wed, May 29, 2019 at 12:02 PM Myrle Krantz <my...@apache.org> wrote:
>
> > +1
> >
> > On Wed, May 29, 2019 at 12:53 PM Naomi Slater <no...@tumbolia.org> wrote:
> >
> > > (copying diversity@apache.org for the time being because I expect it
> > will
> > > take a few days for everyone to move over to dev@diversity.apache.org)
> > >
> > > now that we have dev@ set up, I would like to propose that we start
> > > sending
> > > automated emails to the list
> > >
> > > this is fairly standard practice at the ASF (although not ubiquitous)
> and
> > > makes dev@ the hub of activity for our collective oversight
> > >
> > > specifically, at the moment:
> > >
> > > - automated emails from our JIRA project
> > > - automated emails from our wiki
> > >
> > > I am not too familiar with how Pelican works (the system that will
> power
> > > our website at diversity.apache.org) but if there are changeset emails
> > or
> > > such like, I propose we send copies to dev@
> > >
> > > I also propose that any Git projects we might end up using send copies
> of
> > > automated emails to dev@
> > >
> > > anything else I'm missing?
> > >
> >
>
Re: [PROPOSAL] send automated emails to dev@diversity
Posted by Awasum Yannick <aw...@apache.org>.
+1
On Wed, May 29, 2019 at 12:02 PM Myrle Krantz <my...@apache.org> wrote:
> +1
>
> On Wed, May 29, 2019 at 12:53 PM Naomi Slater <no...@tumbolia.org> wrote:
>
> > (copying diversity@apache.org for the time being because I expect it
> will
> > take a few days for everyone to move over to dev@diversity.apache.org)
> >
> > now that we have dev@ set up, I would like to propose that we start
> > sending
> > automated emails to the list
> >
> > this is fairly standard practice at the ASF (although not ubiquitous) and
> > makes dev@ the hub of activity for our collective oversight
> >
> > specifically, at the moment:
> >
> > - automated emails from our JIRA project
> > - automated emails from our wiki
> >
> > I am not too familiar with how Pelican works (the system that will power
> > our website at diversity.apache.org) but if there are changeset emails
> or
> > such like, I propose we send copies to dev@
> >
> > I also propose that any Git projects we might end up using send copies of
> > automated emails to dev@
> >
> > anything else I'm missing?
> >
>
Re: [PROPOSAL] send automated emails to dev@diversity
Posted by Myrle Krantz <my...@apache.org>.
+1
On Wed, May 29, 2019 at 12:53 PM Naomi Slater <no...@tumbolia.org> wrote:
> (copying diversity@apache.org for the time being because I expect it will
> take a few days for everyone to move over to dev@diversity.apache.org)
>
> now that we have dev@ set up, I would like to propose that we start
> sending
> automated emails to the list
>
> this is fairly standard practice at the ASF (although not ubiquitous) and
> makes dev@ the hub of activity for our collective oversight
>
> specifically, at the moment:
>
> - automated emails from our JIRA project
> - automated emails from our wiki
>
> I am not too familiar with how Pelican works (the system that will power
> our website at diversity.apache.org) but if there are changeset emails or
> such like, I propose we send copies to dev@
>
> I also propose that any Git projects we might end up using send copies of
> automated emails to dev@
>
> anything else I'm missing?
>
Re: [PROPOSAL] send automated emails to dev@diversity
Posted by Shane Curcuru <as...@shanecurcuru.org>.
Naomi Slater wrote on 2019-5-29 6:43AM EDT:
> (copying diversity@apache.org for the time being because I expect it will
> take a few days for everyone to move over to dev@diversity.apache.org)
(Replying to corrected list name as you noted)
>
> now that we have dev@ set up, I would like to propose that we start sending
> automated emails to the list
ProTip: Apache committers can self-subscribe to lists via Whimsy:
https://whimsy.apache.org/committers/subscribe (requires login)
> this is fairly standard practice at the ASF (although not ubiquitous) and
> makes dev@ the hub of activity for our collective oversight
>
> specifically, at the moment:
>
> - automated emails from our JIRA project
> - automated emails from our wiki
+1, good idea.
> I am not too familiar with how Pelican works (the system that will power
> our website at diversity.apache.org) but if there are changeset emails or
> such like, I propose we send copies to dev@
Pelican is just the templating/build system. The files will still be in
a traditional SVN or git repository. Question: which do we want to use?
> I also propose that any Git projects we might end up using send copies of
> automated emails to dev@
>
> anything else I'm missing?
>
--
- Shane
Director & Member
The Apache Software Foundation