RedYetiDev commented on PR #12:
URL:
https://github.com/apache/comdev-events-site/pull/12#issuecomment-2048283988
Sounds good!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific commen
RedYetiDev closed pull request #12: New Design for events.apache.org
URL: https://github.com/apache/comdev-events-site/pull/12
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment
bdelacretaz commented on PR #12:
URL:
https://github.com/apache/comdev-events-site/pull/12#issuecomment-2046838024
#13 looks focused on style + nav changes which is good, in terms of being "a
single thing". Best might be to close this PR and create another one with the
suggested content ch
RedYetiDev commented on PR #12:
URL:
https://github.com/apache/comdev-events-site/pull/12#issuecomment-2034882850
Hey, @bdelacretaz, would you like me to close this and open more similar to
#13, or close #13 in favor this (#12)?
--
This is an automated message from the Apache Git Service
> On Apr 1, 2024, at 8:16 AM, RedYetiDev (via GitHub) wrote:
>
>
> RedYetiDev commented on PR #12:
> URL:
> https://github.com/apache/comdev-events-site/pull/12#issuecomment-2029669946
>
> Okay! Do you want me to split up this PR, or keep that in note for the
> future?
>
> Thank you!
RedYetiDev commented on PR #12:
URL:
https://github.com/apache/comdev-events-site/pull/12#issuecomment-2029669946
Okay! Do you want me to split up this PR, or keep that in note for the
future?
Thank you!
--
This is an automated message from the Apache Git Service.
To respond to th
bdelacretaz commented on PR #12:
URL:
https://github.com/apache/comdev-events-site/pull/12#issuecomment-2029602689
This changes many things indeed, in general we prefer having "atomic" PRs
which change one thing only and can be reviewed in isolation. I suggest
creating separate PRs at leas
On Sat, Mar 30, 2024, 17:08 RedYetiDev (via GitHub) wrote:
>
> RedYetiDev opened a new pull request, #12:
> URL: https://github.com/apache/comdev-events-site/pull/12
>
> In <https://events.apache.org/about/commcode/volunteer.html>, the
> following item was listed:
RedYetiDev opened a new pull request, #12:
URL: https://github.com/apache/comdev-events-site/pull/12
In <https://events.apache.org/about/commcode/volunteer.html>, the following
item was listed: 'Keep this events.apache.org [website source code
updated](https://svn.apache.or
rbowen merged PR #120:
URL: https://github.com/apache/comdev-site/pull/120
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@community.apa
bdelacretaz commented on PR #120:
URL: https://github.com/apache/comdev-site/pull/120#issuecomment-1548546036
+1 to dropping /calendars and merging this
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to
rbowen opened a new pull request, #120:
URL: https://github.com/apache/comdev-site/pull/120
Move calendar reference to https://events.apache.org/ which is the canonical
source of ASF events. Also removes references to long-defunct resources, in
case someone gets to the old resource somehow
ot job [1] to publish the page which runs about 30
> > mins after the normal mdtext update time.
> >
> > [1]
> > https://issues.apache.org/jira/browse/INFRA-16882?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel&focusedCommentId=16577605#comment-16
> [1]
> https://issues.apache.org/jira/browse/INFRA-16882?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel&focusedCommentId=16577605#comment-16577605
>
>> Unfortunately, since events.apache.org is hardly ever published, the
>> changes to the meetup page
ra/browse/INFRA-16882?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel&focusedCommentId=16577605#comment-16577605
> Unfortunately, since events.apache.org is hardly ever published, the
> changes to the meetup page never go live either.
>
> This has been on my list for a very long time, and I'd
those changes go live, too.
Unfortunately, since events.apache.org is hardly ever published, the
changes to the meetup page never go live either.
This has been on my list for a very long time, and I'd be delighted for
someone else to figure out a completely automatic solution to this.
--Rich
would expect the site to be updated after a new commit is
>> pushed
>> (which then triggers a
>> new build), but the events.a.o website is still listing old meetups [1]
>> while the meetups are updated every day [2].
>> I noticed [3] is listing the most recent meetups th
ld), but the events.a.o website is still listing old meetups [1]
> while the meetups are updated every day [2].
> I noticed [3] is listing the most recent meetups though.
>
> [1]: http://events.apache.org/event/meetups.html
> [2]: https://svn.apache.org/viewvc/concom/site/?vie
ed [3] is listing the most recent meetups though.
[1]: http://events.apache.org/event/meetups.html
[2]: https://svn.apache.org/viewvc/concom/site/?view=log
[3]: https://apache.org/events/meetups.html
Roy
On 04/12/2018 03:01 AM, Isabel Drost-Fromm wrote:
On 10/04/18 14:57, Kevin A. McGrail wrote:
I think we are closer.
- events.apache.org (community event calendar that will also include
entries for Apache official events linked to apachecon_
- apachecon.com (apachecon, roadshows and official
Isabel Drost-Fromm wrote on 4/12/18 3:01 AM:
> On 10/04/18 14:57, Kevin A. McGrail wrote:
>> I think we are closer.
>>
>> - events.apache.org (community event calendar that will also include
>> entries for Apache official events linked to apachecon_
>> - apache
tire the http://events.apache.org/ calendar, which IMO
doesn't bring more value above such a shared set of calendars.
-Bertrand
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional comma
On 09/04/18 11:12, Daniel Gruno wrote:
On 04/09/2018 11:09 AM, Bertrand Delacretaz wrote:
There needs to be some consolidation, definitely.
+1 to consolidation, removal of stale content, making it dead-easy for
people to make changes to these sites (and making it easy to figure out
how they a
On 10/04/18 14:57, Kevin A. McGrail wrote:
I think we are closer.
- events.apache.org (community event calendar that will also include
entries for Apache official events linked to apachecon_
- apachecon.com (apachecon, roadshows and official Apache events)
I believe we need a better
I think we are closer.
- events.apache.org (community event calendar that will also include
entries for Apache official events linked to apachecon_
- apachecon.com (apachecon, roadshows and official Apache events)
--
Kevin A. McGrail
Asst. Treasurer & VP Fundraising, Apache Software Founda
some
projects, and foo.apache.org for a developer-facing side.
So, two places:
- events.apache.org (the developer/community side of it)
- apachecon.com (apachecon, roadshow?, the "customer" facing side)
With regards,
Daniel
--
Kevin A. McGrail
Asst. Treasurer & VP Fundraising, Apache
om/in/kmcgrail - 703.798.0171
On Tue, Apr 10, 2018 at 6:37 AM, Rich Bowen wrote:
> On Mon, Apr 9, 2018, 11:32 Kevin A. McGrail wrote:
>
> > Hi Daniel,
> >
> > I am -1 to maintain multiple places for Apache Events. I think
> > events.apache.org, www.apache.org/founda
On Mon, Apr 9, 2018, 11:32 Kevin A. McGrail wrote:
> Hi Daniel,
>
> I am -1 to maintain multiple places for Apache Events. I think
> events.apache.org, www.apache.org/foundation/events, etc. should all
> redirect to apachecon.com and all energies and efforts should be spent o
amAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171
On Mon, Apr 9, 2018 at 11:38 AM, Daniel Gruno wrote:
> On 04/09/2018 05:32 PM, Kevin A. McGrail wrote:
>
>> Hi Daniel,
>>
>> I am -1 to maintain multiple places for Apache Events. I think
>> events.apa
On 04/09/2018 05:32 PM, Kevin A. McGrail wrote:
Hi Daniel,
I am -1 to maintain multiple places for Apache Events. I think
events.apache.org, www.apache.org/foundation/events, etc. should all
redirect to apachecon.com and all energies and efforts should be spent on
maintaining that site as the
Hi Daniel,
I am -1 to maintain multiple places for Apache Events. I think
events.apache.org, www.apache.org/foundation/events, etc. should all
redirect to apachecon.com and all energies and efforts should be spent on
maintaining that site as the source of truth.
To my knowledge all the other
le idea" or are you suggesting changes to
where the roadshow website lives? Throwing a -1 into it seems a bit much.
I'd likely point www.a.o/events to events.apache.org and point that to
apachecon.com.
--
Kevin A. McGrail
Asst. Treasurer & VP Fundraising, Apache Software Fou
Sorry, but I'm a -1. I view the roadshows as mini ApacheCons. I'm also
trying to build sponsors who look at the whole year of events rather than
just AC. Especially where AC EU is in fact a roadshow.
I'd likely point www.a.o/events to events.apache.org and point that t
Daniel Gruno wrote on 4/9/18 5:12 AM:
> On 04/09/2018 11:09 AM, Bertrand Delacretaz wrote:
...snip...
> There needs to be some consolidation, definitely.
> We currently use:
> - apachecon.com
> - events.apache.org
> - www.a.o/events/
Forgot some (my recommendations)
http
, VP Events
owning it sounds great to me.
But if you have enough on your plate already I'd say let's kill it -
better not have it than having stale or very incomplete information.
There needs to be some consolidation, definitely.
We currently use:
- apachecon.com
- events.apache.org
On 9 April 2018 at 10:09, Bertrand Delacretaz wrote:
> Hi Rich,
>
> On Tue, Apr 3, 2018 at 4:00 PM, Rich Bowen wrote:
>> Three answers:
>> 1) Yes, ComDev owns it. ..
>
> I think formally this is the case...
>
>> b) I, with my VP Events hat, own it...
>
> ..but if no one in comdev is interested in
Hi Rich,
On Tue, Apr 3, 2018 at 4:00 PM, Rich Bowen wrote:
> Three answers:
> 1) Yes, ComDev owns it. ..
I think formally this is the case...
> b) I, with my VP Events hat, own it...
..but if no one in comdev is interested in maintaining it, VP Events
owning it sounds great to me.
But if you
Rich Bowen wrote on 4/3/18 10:00 AM:
> On 04/01/2018 09:09 AM, sebb wrote:
>> As the subject says: which group is responsible for the content of
>> events.apache.org?
I made it point to current events, and included a "see source" link,
once I figured out where
ys: which group is responsible for the content of
>> events.apache.org?
>>
>> Is it ComDev?
>>
>
> Three answers:
>
> 1) Yes, ComDev owns it.
>
> b) I, with my VP Events hat, own it.
>
> #) Nobody owns it. It is a pit of despair, sadness, and bitrot, and
On 04/01/2018 09:09 AM, sebb wrote:
As the subject says: which group is responsible for the content of
events.apache.org?
Is it ComDev?
Three answers:
1) Yes, ComDev owns it.
b) I, with my VP Events hat, own it.
#) Nobody owns it. It is a pit of despair, sadness, and bitrot, and
needs
As the subject says: which group is responsible for the content of
events.apache.org?
Is it ComDev?
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
41 matches
Mail list logo
