Re: Input Needed: Software for the Public Good Stories

[Roy Lenferink]

Hi Whitney,

The form can be accessed now. Thanks for fixing!

Roy

Op do 30 nov 2023 om 21:38 schreef Whitney True 

> Hi Roy,
>
> Thanks for flagging this error. It should be resolved now, but please let
> us know if you still cannot access.
>
> Best,
> Whitney
>
> On Wed, Nov 29, 2023 at 1:06 PM Roy Lenferink 
> wrote:
>
> > Op di 28 nov 2023 om 19:59 schreef Whitney True :
> >
> > > Hello ASF Community,
> > >
> > > The ASF M team is hoping to showcase how the ASF Community has helped
> > > provide software for the public good in celebration of the ASF's 25th
> > > anniversary. We hope you will be willing to share a story for the ASF
> > blog
> > > and social media channels. Please fill out this short form.
> > > <
> > >
> >
> https://docs.google.com/forms/d/e/1FAIpQLSehwdP7CBvX5BrYrRMJnx5tfo9-dDmitSaQKZYfy7qiJjXH7Q/viewform
> > > >
> > >
> > >
> > I am getting a "Form restricted - This form can only be viewed by users
> in
> > the organisation of the owner" (translated from Dutch)
> > Do we need to do anything special to fill it in?
> >
> >
> > > Here is a reminder of the types of stories we are looking for:
> > >
> > >- Case studies that showcase how your project’s technology is being
> > > used;
> > >- Details surrounding an important forthcoming project milestone; or
> > >- Any other ways your project embodies the ASF mission and way?
> Please
> > >use this form anytime you have an exciting milestone to share.
> > >
> > >
> > > *And please note you can submit more than once!*
> > > Many thanks for your time and input,
> > > Whitney
> > > On Behalf of the ASF M team
> > >
> > > On Tue, Nov 7, 2023 at 9:30 AM Whitney True 
> > wrote:
> > >
> > > > Hello ASF Community,
> > > >
> > > > As the ASF nears its 25th anniversary, we want to showcase how the
> ASF
> > > > community has helped realize the Foundation's mission of providing
> > > software
> > > > for the public good.
> > > >
> > > > The ASF Marketing & Publicity (M) team will be showcasing major
> > > > milestones and public good stories across the ASF’s blog and social
> > media
> > > > channels. We hope you'll be willing to share a story by filling out
> > this
> > > > short form <https://forms.gle/fxKc85jagFH3tERbA>.
> > > >
> > > > What are we looking for?
> > > >
> > > >- Case studies that showcase how your project’s technology is
> being
> > > >used;
> > > >- Details surrounding an important forthcoming project milestone;
> or
> > > >- Any other ways your project embodies the ASF mission and way?
> > Please
> > > >use this form anytime you have an exciting milestone to share.
> > > >
> > > > ***Please note you can submit more than once!** *
> > > >
> > > > Many thanks for your time and input,
> > > > Whitney
> > > > On Behalf of the ASF M team
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> >
>

Re: Input Needed: Software for the Public Good Stories

[Roy Lenferink]

Op di 28 nov 2023 om 19:59 schreef Whitney True :

> Hello ASF Community,
>
> The ASF M team is hoping to showcase how the ASF Community has helped
> provide software for the public good in celebration of the ASF's 25th
> anniversary. We hope you will be willing to share a story for the ASF blog
> and social media channels. Please fill out this short form.
> <
> https://docs.google.com/forms/d/e/1FAIpQLSehwdP7CBvX5BrYrRMJnx5tfo9-dDmitSaQKZYfy7qiJjXH7Q/viewform
> >
>
>
I am getting a "Form restricted - This form can only be viewed by users in
the organisation of the owner" (translated from Dutch)
Do we need to do anything special to fill it in?


> Here is a reminder of the types of stories we are looking for:
>
>- Case studies that showcase how your project’s technology is being
> used;
>- Details surrounding an important forthcoming project milestone; or
>- Any other ways your project embodies the ASF mission and way? Please
>use this form anytime you have an exciting milestone to share.
>
>
> *And please note you can submit more than once!*
> Many thanks for your time and input,
> Whitney
> On Behalf of the ASF M team
>
> On Tue, Nov 7, 2023 at 9:30 AM Whitney True  wrote:
>
> > Hello ASF Community,
> >
> > As the ASF nears its 25th anniversary, we want to showcase how the ASF
> > community has helped realize the Foundation's mission of providing
> software
> > for the public good.
> >
> > The ASF Marketing & Publicity (M) team will be showcasing major
> > milestones and public good stories across the ASF’s blog and social media
> > channels. We hope you'll be willing to share a story by filling out this
> > short form .
> >
> > What are we looking for?
> >
> >- Case studies that showcase how your project’s technology is being
> >used;
> >- Details surrounding an important forthcoming project milestone; or
> >- Any other ways your project embodies the ASF mission and way? Please
> >use this form anytime you have an exciting milestone to share.
> >
> > ***Please note you can submit more than once!** *
> >
> > Many thanks for your time and input,
> > Whitney
> > On Behalf of the ASF M team
> >
> >
> >
> >
> >
> >
>

Re: Nearby ASF people, or volunteers page?

[Roy Lenferink]

Op ma 27 nov 2023 om 12:34 schreef Roman Shaposhnik 

> On Mon, Nov 27, 2023 at 1:03 PM Bertrand Delacretaz
>  wrote:
> >
> > Hi,
> >
> > We have a "nearby ASF people" app at [1], meant to help people find
> > mentors or ASF speakers, that's not really maintained and contains a
> > lot of stale data.
> >
> > I think we could just use a website page to provide that information,
> > and I've created a prototype at [2], example output at [3]. It's just
> > an additional "mentors and speakers" page for our website, with a
> > simple way for people to add their information in a Markdown page.
> >
> > What do people think, can we replace the people app with such a simple
> page?
>
> This would work for me, but I'd really love to have a map
> visualisation view as well
> (this should't be too hard, right? ;-))


The map is definitely something I like as well.

Maybe we can even use the Baremaps polling for that?

https://baremaps.apache.org/map/


>
> Thanks,
> Roman.
>
> > Unless people step up to actually maintain [1], I think [2] would at
> > least allow us to publish some up to date information. We can always
> > revive [1] later if volunteers show up.
> >
> > -Bertrand
> >
> > [1] https://community.zones.apache.org/map.html
> > [2] https://github.com/apache/comdev-site/pull/146
> > [3]
> https://community-volunteers.staged.apache.org/contributors/asf-volunteers.html
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: [website] how to add an “edit in GitHub” link?

[Roy Lenferink]

Op ma 27 nov 2023 om 20:26 schreef sebb 

> On Mon, 27 Nov 2023 at 14:20, Bertrand Delacretaz
>  wrote:
> >
> > Hi,
> >
> > I'd like to add an "edit in GitHub" link to the pages of
> > https://community.apache.org/ , like we have in Sling [1].
>
> Personally, I would rather the link was to the page source in the comdev
> repo.
> Otherwise one is forced to clone the repo before one can see how easy
> the change is likely to be.


You mean something like the following?

https://celix.apache.org/contributing/releasing.html

The source for how Celix handles that can be found here:

https://github.com/apache/celix-site/blob/master/layouts/_default/baseof.html#L50



>
> > But I don't know how to do it with Hugo - before I dig too deep, does
> > someone have an example?
>
> Looks like the following can be used in the baseof.html template file
> as the URL target of a link:
>
> https://github.com/apache/comdev-site/blob/main/source/{{ .Page.File }}
>
> This can be nested in the conditional:
>
> {{ if .IsPage }}   {{ end }}
>
> > For some pages like [2] which are generated instead of being backed by
> > a Markdown file, we'd need to either link to the repository home, or
> > add no link.
> >
> > -Bertrand
> >
> > [1] https://sling.apache.org/documentation/development.html (at the
> > bottom, "this page can be edited...")
> > [2] https://community.apache.org/tags.html
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: [ASF M & Conferences] Community Over Code logo for project sites

[Roy Lenferink]

Op wo 16 aug 2023 om 07:19 schreef Daniel Gruno :

> On 2023-08-15 22:37, sebb wrote:
> > On Tue, 15 Aug 2023 at 18:55, Brian Proffitt  wrote:
> >>
> >> All:
> >>
> >> ASF’s flagship event, Community Over Code, is happening October 7-10
> >> in Halifax, Nova Scotia (formerly called ApacheCon).
> >>
> >> I would like to ask all projects to add the logo and event URL to your
> >> project website to help the ASF promote the event - and thank you to
> >> projects who have already done this! Or, if you'd like, promote the
> >> event with the logos on your project's social media channels.
> >>
> >> Logos:
> >> https://apache.org/foundation/press/kit/#eventlogo
> >>
> >> Event URL:
> >> https://communityovercode.org/
> >>
> >> Thank you!
> >> BKP
> >
> > There is already a standard way to do this, as is done by:
> >
> > https://jmeter.apache.org/
> > https://commons.apache.org/
> > https://hc.apache.org/
> >
> > and probably others that use Maven to build their sites.
> >
> > They include a link to the event page:
> > https://www.apache.org/events/current-event.html
> > with an image such as
> > https://www.apache.org/events/current-event-125x125.png
>
> There is even a newer way, https://www.apachecon.com/event-images/ which
> most project sites use by now, and which already features the community
> over code logo as the current event.
>

Whimsy has a check for ^https?://.*apache.org/events/current-event which
checks
against the 'current-event' image/link:
https://whimsy.apache.org/site/check/events

(also part of the site-scan overview: https://whimsy.apache.org/site/ )

It seems that 104 projects link to the 'current-event' image/link.

I remember that the current-event image previously was also used for the
Apache Roadshows, so not only ApacheCon.

Having a look at the project list (I used the Whimsy list): of the first 10
projects
6 use the current-event image/link, 1 also has the Community over code
image (Accumulo)
and 1 contains a direct link to apachecon.com without an image (AGE).

Checking the community.a.o website, even there the current-event image/link
is used.

So to me it seems that not a lot of websites use apachecon.com/event-images/
and it
would be simpler to update the current-event images.


> >
> > The idea behind this was to avoid having to change loads of websites
> > before and after every event.
> > Instead, the event organisers can change the page content (or add a
> > redirect) and the various sized images accordingly.
> >
> > By the way, the SVG and PNG versions of the logo look very different -
> > is that intentional?
> >
> >> Brian Proffitt
> >> VP, Marketing & Publicity
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> >> For additional commands, e-mail: dev-h...@community.apache.org
> >>
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: [website] Jenkins job Community Development/events-site/main#82 failed

[Roy Lenferink]

Here the required fix:
https://github.com/apache/comdev-events-site/commit/b2e068e54b7e5bab3a159f1cfd39d65469bb834a

This was done for comdev-site, but not for comdev-events-site:
https://github.com/apache/comdev-site/commit/271e09ae3d4f092b5a6810cdbe40774d64b729fc

A new build is already scheduled but waiting on the next available executor
(in Jenkins); we'll know
in ~15 minutes whether things are working again.

Op do 25 mei 2023 om 20:54 schreef Mark Thomas :

> Anyone familiar with the website build process and can look at this?
>
> We could do with getting the updates deployed.
>
> Mark
>
>
> On 25/05/2023 18:40, Jenkins wrote:
> > There is a build failure in Community Development/events-site/main.
> >
> > Build:
> https://ci-builds.apache.org/job/Community%20Development/job/events-site/job/main/82/
> >
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: Community related menu at main ASF site

[Roy Lenferink]

Op zo 14 mei 2023 om 13:23 schreef sebb :

> On Sun, 14 May 2023 at 02:03, Rich Bowen  wrote:
> >
> > Sure. I can see the value of such a redirect. What I don't see is the
> value
> > of menu nav link to that content , expressly calling it out, and then
> > saying "never mind, we don't have that." Seems misleading.
>
> The point is, there used to be such a page.
> If we decide to stop providing that information, I think it is polite
> to tell people that the specific page no longer exists.
>

I just added a redirect from /mentoringprogramme.html to /mentoring/
See
https://github.com/apache/comdev-site/commit/0e545c51e9dac344a9e71a3df52dfd41498d99b2

This at least doesn't return a 404 to our users.


> Also we should not expect other sites to adjust their links if we
> change our pages, even if we happen to have access to update the other
> site's pages.
>
> We have to assume that some people will use the original URL; we
> should not tell them to "go away" with a 404.
>
> > But, sure, I
> > won't get in the way of folks doing that if that's what you thinks
> > makes sense.
>
> I didn't break the links.
>
> > On Fri, May 12, 2023, 19:12 sebb  wrote:
> >
> > > On Fri, 12 May 2023 at 22:23, Rich Bowen  wrote:
> > > >
> > > > Linking to a mentoring program that doesn't exist doesn't seem like a
> > > > service to anyone.
> > >
> > > The redirect can go to a page that explains that the mentoring program
> > > has been closed, and suggest some alternatives.
> > >
> > > For example, https://community.apache.org/mentoring/
> > >
> > >
> > > >
> > > > On Thu, May 11, 2023, 01:35 sebb  wrote:
> > > >
> > > > > On Thu, 11 May 2023 at 04:03, Rich Bowen 
> wrote:
> > > > > >
> > > > > > On Wed, May 10, 2023, 05:59 sebb  wrote:
> > > > > >
> > > > > > > On Wed, 10 May 2023 at 11:23, Maxim Solodovnik <
> > > solomax...@gmail.com>
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > On Wed, 10 May 2023 at 17:09, sebb  wrote:
> > > > > > > > >
> > > > > > > > > Thanks for the detail.
> > > > > > > > > If that was previously a valid URL, then I think the proper
> > > fix is
> > > > > to
> > > > > > > > > add a redirect to the comdev site.
> > > > > > > >
> > > > > > > > I'm afraid the original page was deleted:
> > > > > > > >
> > > > > > >
> > > > >
> > >
> https://github.com/apache/comdev-site/commit/9172c73871f20f8af5bc02dbb5066a93345c0761
> > > > > > >
> > > > > > > Very useful, thanks.
> > > > > > >
> > > > > > > In which case it would be good to try and add redirects for
> all the
> > > > > > > pages deleted in that commit.
> > > > > > > Starting with the one we know is still being used ...
> > > > > > >
> > > > > >
> > > > > > I'd rather remove that menu link and/or point it to the site
> front
> > > page.
> > > > > > I'll do that tomorrow.
> > > > >
> > > > > No, please don’t.
> > > > >
> > > > > There may be other instances of the same link, and some may be in
> > > > > sites over which the ASF has no control.
> > > > >
> > > > > I believe site owners have a duty to maintain URLs where possible.
> > > > >
> > > > >
> -
> > > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > > > For additional commands, e-mail: dev-h...@community.apache.org
> > > > >
> > > > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > For additional commands, e-mail: dev-h...@community.apache.org
> > >
> > >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: [website] Jenkins job Community Development/site/main#41 failed

[Roy Lenferink]

It seems to only fail on the 'websites2' node. Other builds that are scheduled 
on e.g. 'websites1'
or 'jenkins-websites-ec2-or' don't seem to have that problem.

Having had a quick look at the build output, it fails to write to the 
/tmp/hugo_cache directory.
Maybe the permissions of that directory between websites2 and the other nodes 
are different?
It seems other people have the same problem: 
https://github.com/gohugoio/hugo/issues/7391

After reading that I noticed that there is a --cacheDir argument which can be 
used to specify
another cache directory:

--cacheDir stringfilesystem path to cache directory. Defaults: 
$TMPDIR/hugo_cache/

Maybe we need to start using this option (mktemp -d at the start, cleanup in 
post), because I can
only assume if there are two concurrent builds on the same node that this will 
result in some
problems.

On 2023/04/30 10:45:58 sebb wrote:
> Not quite sure why this failed to create the directory. Perhaps there
> was a concurrent run?
> Anyway, I re-ran the job and it worked
> 
> On Sun, 30 Apr 2023 at 11:44, Jenkins  wrote:
> >
> > There is a build failure in Community Development/site/main.
> >
> > Build: 
> > https://ci-builds.apache.org/job/Community%20Development/job/site/job/main/41/
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
> 
> 

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

[website] comdev blogs import from roller

[Roy Lenferink]

Recently INFRA announced the decommissioning of roller, which means that 
projects were
asked to copy the content from the existing blogs.a.o to their own 
.a.o/blog/ location if
a project wants to retain their blog content.

I just moved and refactored the blog content for the comdev blogs into our 
website and
opened a pull request for review [1].

A preview is available here: 
https://community-import-blogs.staged.apache.org/blog/

I think this is not really doable to review on content-level, but feel free to 
have a look using the
generated preview.

[1] https://github.com/apache/comdev-site/pull/111

Roy

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

Re: [website] FYI, tag-based navigation added to community.a.o

[Roy Lenferink]

I just had a look and I definitely like this addition.

Thanks for adding this!

Roy

Op do 27 apr 2023 om 11:24 schreef Bertrand Delacretaz <
bdelacre...@apache.org>:

> Hi,
>
> I meant to activate this in a preview branch first, but that didn't
> work as Hugo generates absolute URLs for the tag navigation.
>
> So I have committed my tag-based navigation changes to our website,
> you can start at https://community.apache.org/tags.html to see how it
> looks.
>
> Feedback is welcome, and if this broke anything it's easy to revert!
>
> I have added an initial set of tags to some pages [1], feel free to
> add more, trying to reuse existing tags as much as possible.
>
> I'm a big fan of tag-based navigation, as menu-based usually only fits
> a single mental model, with tags it's much easier to discover related
> content.
>
> -Bertrand
>
> [1]
> https://github.com/apache/comdev-site/commit/3bb0a6382cda77f31d211e82eac5270f73d58906
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: Broken link in GSoC article on news.a.o

[Roy Lenferink]

Op wo 29 mrt 2023 om 16:57 schreef sebb :

> On Wed, 29 Mar 2023 at 15:42, Roy Lenferink  wrote:
> >
> > I just noticed a broken link in the following blog post:
> >
> https://news.apache.org/foundation/entry/asf-to-mentor-gsoc-contributors-in-2023
> >
> > The link "Students: read this!" refers to
> >
> > https://community.apache.org/gsoc.html#students-read-this
> >
> > instead of
> >
> > https://community.apache.org/gsoc/#students-read-this
> >
> > This probably has to do with refactoring the GSoC sections.
>
> I think it is more likely due to the __index.md renames.
>
>
In this case it was the re-ordering of the gsoc content.


> > Does anyone know who wrote that blog post and how to correct the broken
> > link?
>
> There should be no need to correct the blog post.
>
> Indeed unless that link never worked, I don't think that is the
> correct way to fix a broken link, as it will only fix that instance of
> the link.
> There may be many others.
>
> It should be possible to redirect to the updated page using .htaccess
> (I'll try and fix that shortly).
>

I just learned about the existence of Hugo aliases [1] and that seems
to work for me locally. See [2] on how this applies to the refactored
GSoC content.

Do we have a preference on .htaccess (single file with all redirects)
vs Hugo aliases (old urls close to the new files) ?

[1] https://gohugo.io/content-management/urls/#aliases
[2] https://github.com/apache/comdev-site/pull/98


>
> Sebb
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Broken link in GSoC article on news.a.o

[Roy Lenferink]

I just noticed a broken link in the following blog post:
https://news.apache.org/foundation/entry/asf-to-mentor-gsoc-contributors-in-2023

The link "Students: read this!" refers to

https://community.apache.org/gsoc.html#students-read-this

instead of

https://community.apache.org/gsoc/#students-read-this

This probably has to do with refactoring the GSoC sections.

Does anyone know who wrote that blog post and how to correct the broken
link?

Re: comdev-website: why are files named __index.md rather than _index.md?

[Roy Lenferink]

Thanks for asking this and pointing out the empty pages Sebb!

The __index.md was a suggested workaround on the Hugo forums (can't find
an exact reference).

This workaround was needed because the community.apache.org website used a
combination of different URLs, e.g.:

/about/
/committers/
/committers/voting.html
/newcommitter.html
/newbiefaq.html

By default having the example file structure below, Hugo will generate
a directory for every file, e.g.:

source/about/_index.md => target/content/about/index.html
source/about/some-page.md => target/content/about/some-page/index.html
source/some-page.md => target/content/some-page/index.html

Because comdev uses a combination of different URLs and I didn't
want to break existing URLs, we use an option called uglyURLs [1].

This allows for e.g.:

source/about.md => target/content/about.html
source/some-page.md => target/content/some-page.html

To still allow a top level file (e.g. /about/index.html) I created the
__index.md files (double underscore), because this was suggested as
a workaround for above /some-page.html and /some-page/ URLs.

I just noticed that Hugo supports the 'url' part in Markdown files now [2],
which IIRC wasn't an option with the Hugo release we were using before
(or I missed the existence of that option). This seems to better fit for
what we want and also won't generate the empty pages listed by Sebb.

I have gone ahead and updated the __index.md to the Hugo advertised
_index.md [3] and use the 'url' option [4]

I hope this explains it a bit, if additional details are needed let me know
and
I'll try my best to write them down :-)

[1]
https://github.com/apache/comdev-site/blob/ae48404766416af1bbd0d72d3cdc8f323d5d293e/hugo.toml#L9
[2] https://gohugo.io/content-management/urls/
[3] https://gohugo.io/content-management/organization/#index-pages-_indexmd
[4]
https://github.com/apache/comdev-site/commit/ae48404766416af1bbd0d72d3cdc8f323d5d293e

Op di 28 mrt 2023 om 01:01 schreef sebb :

> Just noticed that there are quite a few redundant files in the generated
> site:
>
> https://community.apache.org/about.html
> https://community.apache.org/calendars.html
> https://community.apache.org/committers.html
> https://community.apache.org/contributors.html
> https://community.apache.org/gsoc.html
> https://community.apache.org/mentoring.html
> https://community.apache.org/newcomers.html
> https://community.apache.org/newsletter.html
> https://community.apache.org/speakers.html
>
> i.e. all the top-level html files apart from
> https://community.apache.org/index.html
>
> These spurious entries correspond with the __index.md files
>
> There are also a few pages which are not linked into the site
> navigation, e.g. the pages under history
>
> Also one or two broken breadcrumbs, e.g.
> 'Apache way' on the page
> https://community.apache.org/apache-way/apache-project-maturity-model.html
>
>
> On Mon, 27 Mar 2023 at 15:33,  wrote:
> >
> > On Sun, 2023-03-26 at 16:12 +0100, sebb wrote:
> > > Most of the index files are named __index.md, except for one which is
> > > _index.md.
> > >
> > > Why is this?
> > >
> > > Do they serve a different purpose?
> >
> > Yeah, I wondered this, too, but just stick with the convention. I'd
> > like to understand this. Roy, can you give some insight here please?
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
>

Re: GSoC messaging?

[Roy Lenferink]

Something I have been wondering for a couple of weeks now: does it make
sense to
keep the current name 'mentors@community' for the GSoC mentors mailing list
?

Maybe it is possible to rename the mentors@community mailing list to
something
like gsoc-mentors@community to prevent confusion that we have an active
mentors program.

And maybe also introduce a new list, e.g. gsoc@community for all GSoC stuff
(the JIRA notifications can also be send there). I feel like all the GSoC
notifications are a bit
much for the dev@community list.

Op di 21 mrt 2023 om 14:27 schreef :

> On Tue, 2023-03-21 at 10:28 +0700, Maxim Solodovnik wrote:
> > Done:
> >
> https://github.com/apache/comdev-site/commit/4d4fb12609f3b3ef62e398acac4282798ddafcc0
> > Sorry for delay :)
> >
> > New JIRA GSOC project was created (Thanks to sebb)
> > So I'll try to update all docs, move current JIRAs and notify
> > mentors@
> > list as my next steps :))
>
> This is fantastic. Thanks.
>
> --Rich
>
>
> >
> >
> > On Thu, 16 Mar 2023 at 23:55,  wrote:
> > >
> > > On Thu, 2023-03-16 at 23:24 +0700, Maxim Solodovnik wrote:
> > > > Hello Rich,
> > > >
> > > > we are using mentors@community.a.o ML for communications
> > > >
> > > > I'll try to keep https://community.apache.org/gsoc.html page in
> > > > up-to-date state :)
> > > >
> > > > I'll move all GSoC related pages (there should be 3-5 of them) to
> > > > subfolder (will try to do it before Monday)
> > > >
> > > > And will update this thread :)
> > >
> > > Thank you. That's awesome.
> > >
> > > There's a lot of ambiguity, on the website, between GSoC and
> > > Mentoring,
> > > and getting the GSoC stuff into a subdir would greatly help with
> > > that.
> > >
> > > --Rich
> > >
> > > ---
> > > --
> > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > For additional commands, e-mail: dev-h...@community.apache.org
> > >
> >
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: Master branch in web site https://github.com/apache/comdev-site

[Roy Lenferink]

Op di 31 aug. 2021 om 21:10 schreef Craig Russell 

> I think now would be a good time to consider changing the main branch name
> from "master" to "main".


+1


>
> WDYT?
> Craig
>
> Craig L Russell
> c...@apache.org
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: comdev-site updates

[Roy Lenferink]

Hi Craig (and others),

One of the outstanding questions I had is still an outstanding question.
See [1].
I am known with the term ‘mailing lists’ around multiple projects, so was
not sure if we should mass update to ‘email lists’.

Any opinions here ?

Since this change is part of multiple pull requests it makes sense to first
resolve it at one place without having to repeat the same in multiple
places.

Roy

[1]
https://github.com/apache/comdev-site/pull/55#discussion_r575787550

Op zo 13 jun. 2021 om 01:36 schreef Craig Russell 

> Hi,
>
> I see that there are a few PRs for the comdev-site that have not been
> processed.
>
> I'm not a PMC member, nor a committer, but I'm happy to help if given the
> commit bit for the git repository.
>
> Regards,
> Craig
>
> Craig L Russell
> c...@apache.org
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: FOAF sync towards "Nearby Apache People"

[Roy Lenferink]

Op vr 16 apr. 2021 om 22:23 schreef Roy Lenferink :

>
>
> Op vr 16 apr. 2021 om 19:43 schreef Nick Burch 
>
>> On Fri, 16 Apr 2021, Richard Zowalla wrote:
>> > is the sync for https://community.zones.apache.org/map.html offline?
>> > I added a FOAF file to SVN a few days ago (according to [1]) but the
>> > content seems to be static. In addition, it seems, that the google map
>> > requires verification.
>
>
>>
>> I think that service has effectively died due to a lack of interest.
>> There
>> had been talk of providing an easier way to maintain and share the info
>> than editing DOAP + FOAF files (which seems to be too high a barrier to
>> gain widespread participation), but volunteer energy ran out before
>> anything was ever developed...
>>
>> If you are interested in the service, the ASF infra team would love
>> someone to help get the code onto a new box, properly defined and
>> automated,
>
>
> Some time ago infra requested for the VM to be moved to an updated box /
> puppet6.
> This is something I started with and the initial setup for automating
> things is available here (committers private):
> https://github.com/apache/infrastructure-p6/tree/env/comdev_nearby
>
> I’ll inform this list once the migration is done.
>

The migration is done and the service has been running for the last couple
of weeks.
It also performs nightly updates again for new data and the whole
configuration is also
properly automated now.

If someone wants to improve things from where we are right now,
improvements are welcome.

One thing that is not working properly at the moment is the Google Maps
usage. Since Google Maps
requires a token - and we don't have a valid one configured right now - it
is showing that we are running
a "For development purposes only" instance.

Any advice here is welcome.


>
> before it finally dies! The code and docs are at
>> https://svn.apache.org/repos/asf/comdev/nearby_people .
>>
>> Equally if you have ideas on better ways to let people list and de-list
>> themselves, to present the data etc, new volunteers are needed! :)
>
>
> Volunteers are welcome indeed :)
>
>
>> Nick
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>> For additional commands, e-mail: dev-h...@community.apache.org
>>
>>

Re: FOAF sync towards "Nearby Apache People"

[Roy Lenferink]

Op vr 16 apr. 2021 om 19:43 schreef Nick Burch 

> On Fri, 16 Apr 2021, Richard Zowalla wrote:
> > is the sync for https://community.zones.apache.org/map.html offline?
> > I added a FOAF file to SVN a few days ago (according to [1]) but the
> > content seems to be static. In addition, it seems, that the google map
> > requires verification.


>
> I think that service has effectively died due to a lack of interest. There
> had been talk of providing an easier way to maintain and share the info
> than editing DOAP + FOAF files (which seems to be too high a barrier to
> gain widespread participation), but volunteer energy ran out before
> anything was ever developed...
>
> If you are interested in the service, the ASF infra team would love
> someone to help get the code onto a new box, properly defined and
> automated,


Some time ago infra requested for the VM to be moved to an updated box /
puppet6.
This is something I started with and the initial setup for automating
things is available here (committers private):
https://github.com/apache/infrastructure-p6/tree/env/comdev_nearby

I’ll inform this list once the migration is done.

before it finally dies! The code and docs are at
> https://svn.apache.org/repos/asf/comdev/nearby_people .
>
> Equally if you have ideas on better ways to let people list and de-list
> themselves, to present the data etc, new volunteers are needed! :)


Volunteers are welcome indeed :)


> Nick
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

What to do with community-vm?

[Roy Lenferink]

Hi fellow comdev-ers,

An e-mail long overdue;

Some time ago I worked with Drew from infra on migrating projects-vm2
(16.04) to projects-vm3 (20.04) and having it managed by puppet6. This is
already done and running successfully.
The question was also asked whether community-vm.apache.org could be
migrated [2]
This VM is managed by ComDev and is hosting the 'Nearby Apache People'
service [1]

Having a look through the httpd logs of community.zones.a.o it looks like
people are still visiting / using this service.

What do we want to do with the Nearby Apache People service? I could
migrate it and host it on e.g. projects-vm3 (instead of a separate VM).
Do we still want to continue Nearby Apache People and if so, are we allowed
to do so from a privacy point of view?

- Roy

[1] https://community.zones.apache.org/
[2] https://issues.apache.org/jira/browse/INFRA-20349

Re: Internal server error when visiting chi.py

[Roy Lenferink]

Hi Mike,

Thanks for reporting. I've just fixed the issue and it is now working again.

Roy

Op wo 9 sep. 2020 om 00:55 schreef Mike Jumper :

> Hello all,
>
> Visiting https://reporter.apache.org/chi.py (and logging in as "mjumper"),
> the server reports HTTP 500 and states the following:
>
> "Internal Server Error
>
> The server encountered an internal error or misconfiguration and was unable
> to complete your request.
>
> Please contact the server administrator at dev@community.apache.org to
> inform them of the time this error occurred, and the actions you performed
> just before this error.
>
> More information about this error may be available in the server error
> log."
>
> The time of the most recent error that I encountered was today (2020-09-08)
> at 22:52:52 UTC.
>
> - Mike
>

[jira] [Closed] (COMDEV-375) repositories.json data source not updated since 2016

[Roy Lenferink (Jira)]

 [ 
https://issues.apache.org/jira/browse/COMDEV-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Roy Lenferink closed COMDEV-375.

  Assignee: Roy Lenferink  (was: Herve Boutemy)
Resolution: Fixed

> repositories.json data source not updated since 2016
> 
>
> Key: COMDEV-375
> URL: https://issues.apache.org/jira/browse/COMDEV-375
> Project: Community Development
>  Issue Type: Bug
>Reporter: Sebb
>Assignee: Roy Lenferink
>Priority: Major
>
> The file 
> https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk/site/json/foundation/repositories.json
>  has not been updated since 2016.
> I cannot find any details of how the file was created.
> Either the file needs to be maintained regularly, or it should be dropped.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Commented] (COMDEV-375) repositories.json data source not updated since 2016

[Roy Lenferink (Jira)]

[ 
https://issues.apache.org/jira/browse/COMDEV-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17184649#comment-17184649
 ] 

Roy Lenferink commented on COMDEV-375:
--

[https://github.com/apache/infrastructure-p6/commit/2f65371b21bb934a7a3d6ca40092650bf1c60453]
 ensures a cronjob is generating an actual repositories.json again.

since nobody knew how the file was generated i created the following python 
script to fetch the svn top locations for projects and merge it with the gitbox 
repositories.json: 
https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk/scripts/cronjobs/generaterepos.py

> repositories.json data source not updated since 2016
> 
>
> Key: COMDEV-375
> URL: https://issues.apache.org/jira/browse/COMDEV-375
> Project: Community Development
>  Issue Type: Bug
>Reporter: Sebb
>Assignee: Herve Boutemy
>Priority: Major
>
> The file 
> https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk/site/json/foundation/repositories.json
>  has not been updated since 2016.
> I cannot find any details of how the file was created.
> Either the file needs to be maintained regularly, or it should be dropped.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Commented] (COMDEV-381) gunicorn failing on projects-vm3

[Roy Lenferink (Jira)]

[ 
https://issues.apache.org/jira/browse/COMDEV-381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17184642#comment-17184642
 ] 

Roy Lenferink commented on COMDEV-381:
--

due to daniel's fix gunicorn now runs again

 

> gunicorn failing on projects-vm3
> 
>
> Key: COMDEV-381
> URL: https://issues.apache.org/jira/browse/COMDEV-381
> Project: Community Development
>  Issue Type: Bug
>Reporter: Sebb
>Priority: Major
>
> Since the move to vm3, gunicorn has not been running properly.
> I have fixed the restarting error, which was due to gunicorn not being on the 
> path for the cron job.
> Gunicorn now starts, but fails almost immediately with:
> urllib.error.URLError: 
> This is invoked from:
> File "/var/www/reporter.apache.org/scripts/pdata.py", line 92, in 
>    charters = loadJson(DESCRIPTIONS)
> File "/var/www/reporter.apache.org/scripts/pdata.py", line 84, in loadJson
>    resp = uc.get(url, name=None, encoding='utf-8', errors=None)
> However I have been unable to determine why the request is failing.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Closed] (COMDEV-381) gunicorn failing on projects-vm3

[Roy Lenferink (Jira)]

 [ 
https://issues.apache.org/jira/browse/COMDEV-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Roy Lenferink closed COMDEV-381.

Resolution: Fixed

> gunicorn failing on projects-vm3
> 
>
> Key: COMDEV-381
> URL: https://issues.apache.org/jira/browse/COMDEV-381
> Project: Community Development
>  Issue Type: Bug
>Reporter: Sebb
>Priority: Major
>
> Since the move to vm3, gunicorn has not been running properly.
> I have fixed the restarting error, which was due to gunicorn not being on the 
> path for the cron job.
> Gunicorn now starts, but fails almost immediately with:
> urllib.error.URLError: 
> This is invoked from:
> File "/var/www/reporter.apache.org/scripts/pdata.py", line 92, in 
>    charters = loadJson(DESCRIPTIONS)
> File "/var/www/reporter.apache.org/scripts/pdata.py", line 84, in loadJson
>    resp = uc.get(url, name=None, encoding='utf-8', errors=None)
> However I have been unable to determine why the request is failing.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Re: Volunteers for Apache Local Community Website

[Roy Lenferink]

Op vr 21 aug. 2020 om 17:06 schreef Bertrand Delacretaz <
bdelacre...@apache.org>

> Hi,
>
> On Fri, Aug 21, 2020 at 3:55 PM Brian Demers 
> wrote:
> > ...How/where is pub-sub configured for the deploy branch `asf-site`? Is
> it
> > just an infra request, or is there a self service option?..
>
> As per
> https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features#git.asf.yamlfeatures-Staticwebsitecontentgeneration
> this is now self-service, by adding a .asf.yaml file to the website
> repository. I haven't used that variant myself yet.


However for community.a.o (and this will be needed for local.a.o as well)
there is an exception because the subdomain (community) doesn’t match the
PMC name (comdev) which is something the .asf.yaml not supports.

The config for community.a.o is here:

https://github.com/apache/infrastructure-puppet/blob/9c1365140c409689f66fc480046bd7652d554e9e/modules/gitwcsub/files/config/gitwcsub.cfg#L59



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

Re: The Events website

[Roy Lenferink]

Hey all,

I just played around a bit with the events website and wanted to feel how
easy it would be to migrate the site, got lost in time a bit and finished
it already :)
I stored the content in a personal repository for now for others to review
[1]. Hugo is used (same as with community.a.o). Design and urls remain the
same.

What I propose:
- Request a new git repo named 'comdev-events-site'
- Push the new content (history is included)
- Create a Jenkins job to automatically generate the website when new
changes are committed to the default branch.

If there are no objections within the next few days I'll continue with
above steps.

Roy

[1] https://github.com/rlenferink/comdev-events-site/tree/cms-migration

Op di 4 aug. 2020 om 20:55 schreef Andrew Wetmore :

> Several projects are using Hugo, and I expect more to take it up.
>
> a
>
> <
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> >
> Virus-free.
> www.avast.com
> <
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> >
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> On Tue, Aug 4, 2020 at 3:41 PM Roy Lenferink 
> wrote:
>
> > We could use the same setup as with community.a.o : a git repo containing
> > website sources (Hugo could be an option to be uniform with our websites)
> > with a Jenkins job generating the actual content and pushing it to the
> > asf-site branch.
> >
> > Roy
> >
> > Op di 4 aug. 2020 om 20:21 schreef Andrew Wetmore 
> >
> > > I don't have figures to hand on what project is using what. Infra is
> > using
> > > Pelican, and it seems to be working well.
> > >
> > > a
> > >
> > > <
> > >
> >
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> > > >
> > > Virus-free.
> > > www.avast.com
> > > <
> > >
> >
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> > > >
> > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> > >
> > > On Tue, Aug 4, 2020 at 2:49 PM Rich Bowen  wrote:
> > >
> > > > I will try to get this done this week.
> > > >
> > > > I have no opinions on which site-builder I want to use. From where I
> > > > sit, there are no practical differences. What are the majority of our
> > > > sites going with? (Assuming that the tools are listed in order of
> > > > preference, I guess I'll pick Pelican.)
> > > >
> > > > On 8/4/20 1:30 PM, Andrew Wetmore wrote:
> > > > > Hi:
> > > > >
> > > > > The site is like a well-rigged ship that just sails on and on
> without
> > > its
> > > > > crew having to lift a finger...until the CMS falls over.
> > > > >
> > > > > Two first steps you can take concurrently: 1) open a Jira ticket
> for
> > > > INFRA
> > > > > with component "CMS" indicating a willingness to migrate. 2) Decide
> > > which
> > > > > site-builder you want to use. The links I provided outline some
> > options
> > > > in
> > > > > that area.
> > > > >
> > > > > Andrew
> > > > >
> > > > > <
> > > >
> > >
> >
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> > > > >
> > > > > Virus-free.
> > > > > www.avast.com
> > > > > <
> > > >
> > >
> >
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> > > > >
> > > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> > > > >
> > > > > On Tue, Aug 4, 2020 at 1:38 PM Rich Bowen 
> > wrote:
> > > > >
> > > > >> The events site is "mine", in the sense that it's under VP
> > > Conferences,
> > > > >> mostly. It is currently managed under the CMS, but I don't love
> the
> > > CMS
> > > > >> and am ready to migrate.
> > > > >>
> > > > >> It looks like Shane and I are the only people to have touched the
> > > > >> content in almost 2 years. And there have been almost no changes
> > this
> > > > >> year - mostly I manage the content in Google Calendar.
> > > > >>
&g

Re: The Events website

[Roy Lenferink]

We could use the same setup as with community.a.o : a git repo containing
website sources (Hugo could be an option to be uniform with our websites)
with a Jenkins job generating the actual content and pushing it to the
asf-site branch.

Roy

Op di 4 aug. 2020 om 20:21 schreef Andrew Wetmore 

> I don't have figures to hand on what project is using what. Infra is using
> Pelican, and it seems to be working well.
>
> a
>
> <
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> >
> Virus-free.
> www.avast.com
> <
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> >
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> On Tue, Aug 4, 2020 at 2:49 PM Rich Bowen  wrote:
>
> > I will try to get this done this week.
> >
> > I have no opinions on which site-builder I want to use. From where I
> > sit, there are no practical differences. What are the majority of our
> > sites going with? (Assuming that the tools are listed in order of
> > preference, I guess I'll pick Pelican.)
> >
> > On 8/4/20 1:30 PM, Andrew Wetmore wrote:
> > > Hi:
> > >
> > > The site is like a well-rigged ship that just sails on and on without
> its
> > > crew having to lift a finger...until the CMS falls over.
> > >
> > > Two first steps you can take concurrently: 1) open a Jira ticket for
> > INFRA
> > > with component "CMS" indicating a willingness to migrate. 2) Decide
> which
> > > site-builder you want to use. The links I provided outline some options
> > in
> > > that area.
> > >
> > > Andrew
> > >
> > > <
> >
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> > >
> > > Virus-free.
> > > www.avast.com
> > > <
> >
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> > >
> > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> > >
> > > On Tue, Aug 4, 2020 at 1:38 PM Rich Bowen  wrote:
> > >
> > >> The events site is "mine", in the sense that it's under VP
> Conferences,
> > >> mostly. It is currently managed under the CMS, but I don't love the
> CMS
> > >> and am ready to migrate.
> > >>
> > >> It looks like Shane and I are the only people to have touched the
> > >> content in almost 2 years. And there have been almost no changes this
> > >> year - mostly I manage the content in Google Calendar.
> > >>
> > >> So ... what's next steps?
> > >>
> > >> On 8/4/20 9:59 AM, Andrew Wetmore wrote:
> > >>> Hi:
> > >>>
> > >>> I am part of the Infrastructure team, and am writing to ask whether
> > >> comdev
> > >>> is still using the Apache CMS for the Events website. As you know,
> the
> > >> CMS
> > >>> is reaching end-of-life, and we need projects to move their websites
> > >> onto a
> > >>> different option within the next few weeks.
> > >>>
> > >>> There are several alternatives available, including those listed on
> > this
> > >>> page [1] on managing project websites. Infra is assembling a Wiki
> page
> > >> [2]
> > >>> on migrating a website from the CMS, and is looking forward to
> helping
> > >>> projects with this transition.
> > >>>
> > >>> Please let me know whether the events site is still on the Apache CMS
> > >> and,
> > >>> if so, who will be the point-of-contact with Infra for the migration.
> > >>>
> > >>> Thank you!
> > >>>
> > >>>
> > >>>
> > >>>
> > >>> [1] https://infra.apache.org/project-site.html
> > >>>
> > >>> [2]
> > >>>
> > >>
> >
> https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS
> > >>>
> > >>>
> > >>
> > >> --
> > >> Rich Bowen - rbo...@rcbowen.com
> > >> @rbowen
> > >>
> > >> -
> > >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > >> For additional commands, e-mail: dev-h...@community.apache.org
> > >>
> > >>
> > >
> >
> > --
> > Rich Bowen - rbo...@rcbowen.com
> > @rbowen
> >
>
>
> --
> Andrew Wetmore
> Technical Writer-Editor
> Infra
> *Apache Software Foundation*
> andr...@apache.org
>
> <
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> >
> Virus-free.
> www.avast.com
> <
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> >
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>

Re: ASF Slack for community?

[Roy Lenferink]

Also keep in mind that Slack uses a Fair Billing Policy [1]. You won't be
billed for inactive members (inactive being if a member didn't use its
Slack account in over 14 days).
Having a certain number of users join during/after a conference they
probably all have useful input for the Beam community (code, documentation,
presentation or as a potential Beam user).
In the first couple of weeks after the conference most of that input will
probably be collected (the yay factor for new projects). And if not they
will probably go inactive and you won't be billed for them.

So I agree with Austin here, does the cost of adding the users outweigh the
addition of potential new contributors.

Also, if the cost of Slack is becoming too much for the ASF (don't know if
we have a sponsored instance?), how about e.g. Mattermost [2][3] as a
self-hosted alternative (or only for conferences) ? Just throwing some
ideas out there..

- Roy

[1] https://slack.com/intl/en-nl/help/articles/218915077-Fair-Billing-Policy
[2] https://github.com/mattermost/mattermost-server
[3] https://mattermost.com/

Op ma 27 jul. 2020 om 18:31 schreef Austin Bennett <
whatwouldausti...@gmail.com>:

> Hi All,
>
> My intent would be to use this ASF Resource for communication of potential
> newcomers to the Beam community (and with the hope that they become
> involved with the foundation overall), looking to state that clearly.
>
> Cost is a reasonable argument -- but I need to question whether the
> financial costs outweigh the potential benefits, and therefore looking to
> make explicit the purpose of the Slack Community, if this is something we
> are going to be told not to do.
>
>
> As a thought exercise/perspective; please bear with the following -->
>
> * I have been in the ASF Slack long before I was a committer on the
> project.
> * There is lots of activity in the ASF Slack Beam channels from
> non-committers (and a way to identify future committers, based on positive
> interactions with the community).
> * I lead workshops (in most cases personal free/volunteer time) on getting
> involved with contributing to OpenSource/ASF/Beam, and I certainly point
> all attendees to the training to ASF Slack channel (as well as mailing
> lists) -- should I not be doing that?
>
> One potentially useful, but not great analogy would be traditional funnels
> and conversion rates -- would like to build a funnel and community for Beam
> (and serving ASF more generally), people that are interested/curious, some
> of which will convert to maintaining activity -> learning more -> chatting
> with others -> contributing docs/use-case/bugs/code -> becoming committers
> -> etc...  In that light, you can see how there are benefits for this to be
> the start of an interaction and journey for people to get involved with the
> foundation?  That is at least my goal/motivation.
>
> How do we distinguish users in this case (say anyone I point to the Slack
> channels as a way to start following a community and getting involved in
> discussions), from a broader conference attendee (in the cases, such
> workshops are often at conferences)?  Why would we exclude people/purpose?
>
> Do my aims make sense?  Is growing the ASF community in this manner not
> supported by the infrastructure?  If Slack is not a useful common tool that
> we can point anyone to, should we be using it?  Or, at least can someone
> provide clear bounds on what is OK and not OK to be doing with it?
>
> Proposal: we use this slack channel for the BeamSummit, and learn how it
> goes.
> If concerned about persisting user accounts, perhaps can we configure an
> alternate link (if given permissions, I am willing) and we can track the
> signups through that link [ s.apache.org/
> temp-slack-invite ] - and
> auto-expire/delete their account after 30 days (or some interval) without
> some additional requirements to keep them as users.  It seems the fear is
> around accounts getting created that are not used and costing money.  I
> suspect (a) there are alot of inactive accounts, and (b) that we should be
> supporting the growing community in the same place.
>
> Thanks for bearing with this long message.
> Austin
>
> On Tue, Jul 21, 2020 at 12:15 PM Chris Thistlethwaite 
> wrote:
>
>> Infra discussed this at our last team meeting. Currently the way Slack
>> invites work via s.apache.org/slack-invite sends out an invite to become
>> a full member of the-asf.slack.com. You can read a bit more about this
>> at https://infra.apache.org/slack.html. The issue with that is members
>> (Slack Members NOT ASF Members) then cost money for the ASF, which will
>> be hard to track and forecast if every project starts using the-asf
>> workspace as a conference meet-up area. There's not an official way to
>> invite someone as a Single Channel Guest to Slack without their email
>> address. There's no URL they can visit to get an invite. There are
>> products out there that use a deprecated Slack 

Re: formatting on one of the community.a.o pages

[Roy Lenferink]

Thanks for pointing out Andrew.
This is fixed & live now.

Roy

Op ma 13 jul. 2020 om 14:39 schreef Andrew Wetmore :

> Hi:
>
> I was looking at the page about crowdfunding disclaimers [1]. It seems
> there is a formatting issue near the bottom of the page, where there should
> be a link:
>
> The [explanation in their about section])
> https://opencollective.com/friends-of-groovy#about= makes it clear that
> ...
>
> Looks like there is a ")" where there should be a "(" and a "=" where there
> should be a ")". In any case, it does not display as a link.
>
> [1] https://community.apache.org/committers/funding-disclaimer.html
>
>
> HTH
>
> --
> Andrew Wetmore
> Technical Writer-Editor
> Infra
> *Apache Software Foundation*
> andr...@apache.org
>

Re: [ANNOUNCE] Welcome Roy Lenferink as a New PMC Member

[Roy Lenferink]

Thanks Akash :)

Op ma 11 mei 2020 om 13:08 schreef akash jain :

> Congratulations Roy Lenferink!
>
> Thanks and Regards
> --
> Akash Jain
>
> On Tue, May 5, 2020 at 8:47 PM Sharan Foga  wrote:
>
> > Hi Everyone
> >
> > The Community Development PMC has invited Roy Lenferink to become a new
> > member of the PMC and we are happy to announce that he has accepted.
> >
> > Roy has been helping out and doing a lot of work behind the scenes on our
> > website http://community.apache.org/. We have also been very impressed
> > with his general positive and can do attitude which is what Comdev is all
> > about!.
> >
> > We are sure that Roy will be a great addition to the PMC.
> >
> > Please join me in welcoming Roy and congratulating him on his new role.
> >
> > Thanks
> > Sharan
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
> >
>

Re: [ANNOUNCE] Welcome Roy Lenferink as a New PMC Member

[Roy Lenferink]

Thanks all for the warm welcome! Happy to be on-board :)

Roy

Op wo 6 mei 2020 om 14:13 schreef Pranay Pandey :

> Congratulations Roy!
>
> Best regards,
> Pranay Pandey
> https://ofbiz.apache.org/
>
>
> On Tue, May 5, 2020 at 8:47 PM Sharan Foga  wrote:
>
> > Hi Everyone
> >
> > The Community Development PMC has invited Roy Lenferink to become a new
> > member of the PMC and we are happy to announce that he has accepted.
> >
> > Roy has been helping out and doing a lot of work behind the scenes on our
> > website http://community.apache.org/. We have also been very impressed
> > with his general positive and can do attitude which is what Comdev is all
> > about!.
> >
> > We are sure that Roy will be a great addition to the PMC.
> >
> > Please join me in welcoming Roy and congratulating him on his new role.
> >
> > Thanks
> > Sharan
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
> >
>

RE: FYI, community.a.o site with Hugo/Git (mostly) works

[Roy Lenferink]

Thanks for verifying the taken steps Bertrand :)
The community.a.o entry has been removed from cms.a.o as well now.

Another thing I noticed on this topic is the comdev-wwwsite [1] repository. It 
seems it was once 
requested as playground for converting the site to Pelican.Is this repository 
still needed otherwise we 
might as well delete it (to prevent possible confusions like this [2]).

[1] https://github.com/apache/comdev-wwwsite
[2] 
https://issues.apache.org/jira/browse/INFRA-20009?focusedCommentId=17065576=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17065576

On 2020/04/03 10:41:31, Bertrand Delacretaz  wrote: 
> Hi,
> 
> Thank you very much Roy for this work (details below),  I just tested
> the new website build and it looks good to me!
> 
> I added a link to https://github.com/apache/comdev-site to the footer
> of http://community.apache.org/
> 
> The README of https://github.com/apache/comdev-site has all the
> information and links on how to edit and publish the website, so from
> now on that URL is the only thing one needs to know to update the
> website.
> 
> The only thing that didn't work for me is the automatic trigger of the
> Jenkins build after pushing my changes to
> https://github.com/apache/comdev-site - not sure why but manually
> triggering the build job worked.
> 
> Thanks again Roy for your great work!
> 
> -Bertrand
> 
> On Tue, Mar 31, 2020 at 6:07 PM Roy Lenferink  wrote:
> >
> > I agree the PR [1] is ready to be merged (no conflicts anymore and minor 
> > differences are resolved as
> > well now). Also, merging the pull requests doesn't automatically switch 
> > over serving of community.a.o
> > from svn to git. It will only be served from git after [2] is merged.
> >
> > So what I'd suggest:
> > - merge [1],
> > - create a Jenkins job which updates the asf-site branch after changes to 
> > the 'master' branch are
> > made (I'll do this)
> > - then merge [2] and start serving community.a.o from git :)
> >
> > [1] https://github.com/apache/comdev-site/pull/5
> > [2] https://github.com/apache/infrastructure-puppet/pull/1753 ...
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
> 
> 

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

Re: [RESULT][VOTE] Move community.a.o site from CMS/SVN to Hugo/Git

[Roy Lenferink]

I agree the PR [1] is ready to be merged (no conflicts anymore and minor 
differences are resolved as
well now). Also, merging the pull requests doesn't automatically switch over 
serving of community.a.o
from svn to git. It will only be served from git after [2] is merged.

So what I'd suggest: 
- merge [1],
- create a Jenkins job which updates the asf-site branch after changes to the 
'master' branch are 
made (I'll do this)
- then merge [2] and start serving community.a.o from git :)

[1] https://github.com/apache/comdev-site/pull/5
[2] https://github.com/apache/infrastructure-puppet/pull/1753

On 2020/03/31 13:42:53, Rich Bowen  wrote: 
> So ... bringing it back to the list.
> 
> We chatted about this on Slack briefly, and we are still in the forklift 
> process. There's a MASSIVE PR here - 
> https://github.com/apache/comdev-site/pull/5
> 
> I have recommended we just merge it, and then deal with the fallout of 
> the handful of things that will probably break. But that's just one 
> opinion. (FWIW, Shane agreed with me.)
> 
> But, the summary is, this is happening, and life gets in the way. So I 
> just need to be patient.
> 
> HOWEVER, if you want to help test, the git repo is as above, and Hugo 
> (our new site framework) lives here: 
> https://github.com/gohugoio/hugo/releases/tag/v0.63.2.
> 
> --Rich
> 
> On 3/31/20 9:13 AM, Rich Bowen wrote:
> > Can you update us as to where this is?
> > 
> > Specifically, I'm trying to make an edit to the site, and it turns out I 
> > don't know how. Can you please update 
> > https://community.apache.org/about/#about-this-website and 
> > https://community.apache.org/newbiefaq.html#websitecms with the info 
> > necessary for me to make edits?
> > 
> > Thanks!
> > 
> > --Rich
> > 
> > On 3/10/20 2:27 PM, Roy Lenferink wrote:
> >> Hi,
> >>
> >> The community has voted on moving over the current 
> >> community.apache.org website from the
> >> CMS/SVN to be Git/Hugo based [1]
> >>
> >> The vote passed with the following results:
> >> +1 Rich Bowen (binding)
> >> +1 Sebb (binding)
> >>
> >> +1 Austin Bennett (non-binding)
> >> +1 Aizhamal Nurmamat kyzy (non-binding)
> >> +1 Willem Ning Jiang (non-binding)
> >> +1 Kamil Breguła (non-binding)
> >> +1 Liang Zhang (non-binding)
> >> +1 Jarek Potiuk (non-binding)
> >> +1 Aditya Sharma (non-binding)
> >> +1 Tomasz Urbaszek (non-binding)
> >> +1 Manish Sharma (non-binding)
> >> +1 Xin Wang (non-binding)
> >> +1 Ming Wen (non-binding)
> >> +1 Roy Lenferink (non-binding)
> >>
> >> +1 Christopher Tubbs (non-binding) to switching to a git-based website
> >> +0 Christopher Tubbs (non-binding) to switching to Hugo
> >>
> >> +1 Luciano Resende (binding) for moving to git
> >> -0 Luciano Resende (binding) for hugo
> >>
> >> I'll start to get things moving.
> >>
> >> Regards,
> >> Roy
> >>
> >> [1] 
> >> https://lists.apache.org/thread.html/rd5f62582ac2feb0d707cde413cc9288d681cb17b9f37ef71f349e078%40%3Cdev.community.apache.org%3E
> >>  
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> >> For additional commands, e-mail: dev-h...@community.apache.org
> >>
> > 
> 
> -- 
> Rich Bowen - rbo...@rcbowen.com
> http://rcbowen.com/
> @rbowen
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
> 
> 

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

[RESULT][VOTE] Move community.a.o site from CMS/SVN to Hugo/Git

[Roy Lenferink]

Hi,

The community has voted on moving over the current community.apache.org website 
from the
CMS/SVN to be Git/Hugo based [1]

The vote passed with the following results:
+1 Rich Bowen (binding)
+1 Sebb (binding)

+1 Austin Bennett (non-binding)
+1 Aizhamal Nurmamat kyzy (non-binding)
+1 Willem Ning Jiang (non-binding)
+1 Kamil Breguła (non-binding)
+1 Liang Zhang (non-binding)
+1 Jarek Potiuk (non-binding)
+1 Aditya Sharma (non-binding)
+1 Tomasz Urbaszek (non-binding)
+1 Manish Sharma (non-binding)
+1 Xin Wang (non-binding)
+1 Ming Wen (non-binding)
+1 Roy Lenferink (non-binding)

+1 Christopher Tubbs (non-binding) to switching to a git-based website
+0 Christopher Tubbs (non-binding) to switching to Hugo

+1 Luciano Resende (binding) for moving to git
-0 Luciano Resende (binding) for hugo

I'll start to get things moving.

Regards,
Roy

[1] 
https://lists.apache.org/thread.html/rd5f62582ac2feb0d707cde413cc9288d681cb17b9f37ef71f349e078%40%3Cdev.community.apache.org%3E

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

Re: [VOTE] Move community.a.o site from CMS/SVN to Hugo/Git

[Roy Lenferink]

Adding my +1 as well

On 2020/03/07 03:37:07, Ming Wen  wrote: 
> +1 (non-binding)
> 
> Xin Wang 于2020年3月7日 周六上午11:22写道：
> 
> > +1 (non-binding)
> >
> > - Xin
> >
> > Manish Sharma  于2020年3月6日周五 下午11:52写道：
> >
> > > +1
> > >
> > > On Fri, 6 Mar 2020 at 20:49, Tomasz Urbaszek 
> > wrote:
> > >
> > > > +1 (no-binding)
> > > >
> > > > T.
> > > >
> > > >
> > > > On Fri, Mar 6, 2020 at 4:06 PM Aditya Sharma 
> > > > wrote:
> > > > >
> > > > > +1 (no-binding)
> > > > >
> > > > > Thanks and Regards,
> > > > > Aditya Sharma
> > > > >
> > > > > On Fri, 6 Mar 2020 at 19:53, Jarek Potiuk  wrote:
> > > > > >
> > > > > > +1 (non-binding). Hugo is great! Git even more so.
> > > > > >
> > > > > > On Fri, Mar 6, 2020 at 10:37 AM Liang Zhang  > >
> > > > wrote:
> > > > > >
> > > > > > > +1 (no-binding)
> > > > > > > I developed ShardingSphere website using Hugo, I like it.
> > > > > > >
> > > > > > > On 2020/02/22 11:11:15, Roy Lenferink 
> > > wrote:
> > > > > > > > Hi all,
> > > > > > > >
> > > > > > > > After this week's proposal [1] I'd like to start a formal vote
> > on
> > > > moving
> > > > > > > over community.a.o from the
> > > > > > > > current Apache CMS/SVN to Hugo/Git.
> > > > > > > >
> > > > > > > > Involved steps:
> > > > > > > > - Create a comdev-site gitbox repository which will be synced
> > > with
> > > > the
> > > > > > > current comdev-site repo on
> > > > > > > > GitHub.
> > > > > > > > - Rename 'trunk' to 'master' and set 'master' as default branch
> > > > (git
> > > > > > > repo)
> > > > > > > > - Create a Jenkins job which generates the actual site to the
> > > > 'asf-site'
> > > > > > > branch
> > > > > > > > - Move serving of community.a.o from svn to git
> > > > > > > > - Remove 'community' from the CMS
> > > > > > > > - Add a MOVED_TO_GIT file to the svn repo making clear the the
> > > > directory
> > > > > > > contents have moved
> > > > > > > > to git.
> > > > > > > >
> > > > > > > > Please vote:
> > > > > > > > [ ] +1 for moving over from the CMS/svn to Hugo/git.
> > > > > > > > [ ] -1 for not moving over, in this case please explain why
> > > > > > > >
> > > > > > > > Best,
> > > > > > > > Roy
> > > > > > > >
> > > > > > > > [1]
> > > > > > >
> > > >
> > >
> > https://lists.apache.org/thread.html/r338baf731f509c6ae833600469c2b247cafe02022c1687a705a66012%40%3Cdev.community.apache.org%3E
> > > > > > > >
> > > > > > > >
> > > > -
> > > > > > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > > > > > > For additional commands, e-mail: dev-h...@community.apache.org
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > -
> > > > > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > > > > > For additional commands, e-mail: dev-h...@community.apache.org
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > --
> > > > > > +48 660 796 129
> > > > >
> > > > > -
> > > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > > > For additional commands, e-mail: dev-h...@community.apache.org
> > > > >
> > > >
> > > > -
> > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > > For additional commands, e-mail: dev-h...@community.apache.org
> > > >
> > > >
> > >
> >
> >
> > --
> > Thanks,
> > Xin
> >
> -- 
> Thanks,
> Ming Wen, Apache APISIX
> Twitter: _WenMing
> 

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

[VOTE] Move community.a.o site from CMS/SVN to Hugo/Git

[Roy Lenferink]

Hi all,

After this week's proposal [1] I'd like to start a formal vote on moving over 
community.a.o from the
current Apache CMS/SVN to Hugo/Git.

Involved steps:
- Create a comdev-site gitbox repository which will be synced with the current 
comdev-site repo on
GitHub.
- Rename 'trunk' to 'master' and set 'master' as default branch (git repo)
- Create a Jenkins job which generates the actual site to the 'asf-site' branch
- Move serving of community.a.o from svn to git
- Remove 'community' from the CMS
- Add a MOVED_TO_GIT file to the svn repo making clear the the directory 
contents have moved
to git.

Please vote:
[ ] +1 for moving over from the CMS/svn to Hugo/git.
[ ] -1 for not moving over, in this case please explain why

Best,
Roy

[1] 
https://lists.apache.org/thread.html/r338baf731f509c6ae833600469c2b247cafe02022c1687a705a66012%40%3Cdev.community.apache.org%3E

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

Re: Move community.a.o site from CMS/SVN to Hugo/Git

[Roy Lenferink]

Thanks Bertrand!

At Celix we are using Hugo as well, which indeed works pretty well :)
https://github.com/apache/celix-site

On 2020/02/19 09:49:50, Bertrand Delacretaz  wrote: 
> On Tue, Feb 18, 2020 at 8:09 PM Roy Lenferink  wrote:
> > ...An example (for demo purposes only) of Hugo its output is available here:
> > http://comdev-site.roylenferink.nl/
> 
> Nice, thank you very much for working on this, I think it's long overdue!
> 
> Us being geeks, it'll be hard to agree on tools, IMHO whoever does the
> work decides, within the agreed upon constraints.
> 
> So unless there are concrete benefits to using Pelican (or Jekyll
> which is also mentioned at https://s.apache.org/asfyaml) I think what
> you suggest works, being based on Markdown, well-known, with a
> convenient templating mechanism and already used by other projects
> (like https://github.com/apache/airflow-site).
> 
> -Bertrand
> 

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

Re: Move community.a.o site from CMS/SVN to Hugo/Git

[Roy Lenferink]

Hi Daniel / Rich,

To be honest, I completely forgot the .asf.yaml was able to do such things, my 
bad.

Currently the .asf.yaml supports both Jekyll and Pelican. My previous 
experience with Jekyll is that
it is really slow at incrementally generating content when file changes are 
made (running on the 
Ubuntu bash shell on Windows). Also it requires ruby, rubygems, etc. to be 
installed.

After your message I tried Pelican as well [1], I have to say, it is fairly 
easy to install (note: I already
had pip installed). However, one big disadvantage would be that Pelican its 
output is a bit of a mess.
Pelican is storing all its generated content in a single folder (e.g. 
/output/pages), which kinda
breaks every link from an external website to community.a.o, e.g. the
http://community.apache.org/newcommitter.html link will be broken as well. IMO 
we need to try to 
minimize impact when moving over. Of course we can work with RewriteRules and 
adding a 'Slug' to 
pages but that just adds extra maintenance.

With Hugo I was able to keep all current URLs working. Generating the comdev 
site is done in ~226
ms. Hugo contains incremental builds as well (useful for development), which it 
serves from memory 
instead of writing the generated files to disk (compared to Pelican). 
Installing Hugo is just as easy
as downloading the specified release, extracting the tarball and you're good to 
go ;)

GitHub statistics:
Jekyll: 39.7k stars / 8.7k forks / 893 contributors [2]
Hugo: 41.7k stars / 4.7k forks / 606 contributors [3]
Pelican: 9.4k stars / 1.6k forks / 347 contributors [4]

@ Daniel, maybe I can help Infra to possibly support Hugo builds as well ? :)

[1] https://github.com/rlenferink/comdev-site/tree/feature/conversion-to-pelican
[2] https://github.com/jekyll/jekyll
[3] https://github.com/gohugoio/hugo/
[4] https://github.com/getpelican/pelican

On 2020/02/18 19:47:30, Daniel Gruno  wrote: 
> There are pelican auto-builds and auto-publishing via .asf.yaml files 
> already, as well as custom build steps being introduced on builbot 2.
> 
> see https://s.apache.org/asfyaml for starters...
> 
> On 18/02/2020 13.45, Rich Bowen wrote:
> > I would like to hear more about Hugo, since it's not one that I've heard 
> > of before.
> > 
> > There are a zillion different content frameworks out there, and I have 
> > no preference for any of them except that the underlying file format is 
> > standard-ish. Markdown, or something similar that can be easily 
> > converted to the next framework-du-jour when Hugo is no longer the 
> > latest hotness.
> > 
> > I would also strenuously encourage you to include Infra in any such 
> > discussion, before we forge our own new path, while Infra is already 
> > looking at a CMS replacement.
> > 

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

Re: Move community.a.o site from CMS/SVN to Hugo/Git

[Roy Lenferink]

Forgot to mention:

An example (for demo purposes only) of Hugo its output is available here:
http://comdev-site.roylenferink.nl/

On 2020/02/18 19:07:09, Roy Lenferink  wrote: 
> Hi fellow comdev-ers,
> 
> The e-mail from a few days ago asking to change the year from 2018 -> 2020 
> triggered me and I
> thought how this could be improved. Also, an 'Edit this page' button will 
> already help people to 
> contribute changes to the current website.
> 
> One way of doing this could be to start using a static website as Hugo. Hugo 
> is a single static binary
> being able to generate static websites. More or less similar to what the 
> Apache CMS is doing, except
> it is being used in a quite diverse set of communities (Kubernetes being one 
> of them). Content written 
> for the site will remain in markdown.
> 
> This afternoon I had half an hour to spare and tried to convert community.a.o 
> from the current CMS
> style to the style useful for Hugo. This worked out pretty well and not that 
> much changes were 
> needed.
> 
> I have just created a pull request to the comdev-site repo on GitHub so 
> people are able to review
> the work I did [1].
> 
> What I propose when people are okay with this move:
> - Request a comdev-site gitbox repository synced with the comdev-site repo on 
> GitHub.
> - Change 'trunk' to 'master' as that matches a bit more with the git style of 
> working
> - Merge the PR I created [1]
> - Create a Jenkins job to have the site automatically generated whenever new 
> commits happen.
> - Move over serving community.a.o from svn to git.
> 
> I'd like to hear your opinions on this ;)
> 
> Best,
> Roy
> 
> [1] https://github.com/apache/comdev-site/pull/5
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
> 
> 

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

Move community.a.o site from CMS/SVN to Hugo/Git

[Roy Lenferink]

Hi fellow comdev-ers,

The e-mail from a few days ago asking to change the year from 2018 -> 2020 
triggered me and I
thought how this could be improved. Also, an 'Edit this page' button will 
already help people to 
contribute changes to the current website.

One way of doing this could be to start using a static website as Hugo. Hugo is 
a single static binary
being able to generate static websites. More or less similar to what the Apache 
CMS is doing, except
it is being used in a quite diverse set of communities (Kubernetes being one of 
them). Content written 
for the site will remain in markdown.

This afternoon I had half an hour to spare and tried to convert community.a.o 
from the current CMS
style to the style useful for Hugo. This worked out pretty well and not that 
much changes were 
needed.

I have just created a pull request to the comdev-site repo on GitHub so people 
are able to review
the work I did [1].

What I propose when people are okay with this move:
- Request a comdev-site gitbox repository synced with the comdev-site repo on 
GitHub.
- Change 'trunk' to 'master' as that matches a bit more with the git style of 
working
- Merge the PR I created [1]
- Create a Jenkins job to have the site automatically generated whenever new 
commits happen.
- Move over serving community.a.o from svn to git.

I'd like to hear your opinions on this ;)

Best,
Roy

[1] https://github.com/apache/comdev-site/pull/5

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

Re: Update information on community.apache.org

[Roy Lenferink]

Following the WEBSITE-HOWTO [1] I just updated the year from 2018 to 2020.
However, a comdev-er still needs to publish the site [2] as I was unable to.
"svnmucc: E175013: Access to
'/repos/infra/!svn/txr/1056611-mpm7/websites/production/community/content'
forbidden"

[1] https://github.com/apache/comdev-site/blob/trunk/WEBSITE-HOWTO.txt
[2] https://cms.apache.org/community/publish?diff=1

Roy

Op zo 16 feb. 2020 om 00:51 schreef Austin Bennett <
whatwouldausti...@gmail.com>:

> Looks like would change the file
> https://github.com/apache/comdev-site/blob/trunk/templates/standard.html
>
> Still didn't read as to exactly the process for updating and getting the
> site built, so I didn't put in a PR (to modify master and/or trunc).
>
>
>
> On Sat, Feb 15, 2020 at 11:03 AM Tomasz Urbaszek 
> wrote:
>
> > Hi all,
> >
> > I've just spotted that footer on community page
> > https://community.apache.org has "Copyright© 2018". I think this
> > should be updated to avoid "this page is dead" feeling. Who should I
> > contact to request the update?
> >
> > Best,
> > Tomek Urbaszek
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
> >
>

Re: Shared service for Websites?

[Roy Lenferink]

Recently Celix migrated from the Apache CMS to hosting the website through
the gitpubsub system as well.
For Celix we're using Hugo meaning our content is written in markdown.

If you want to have a look please do here: http://celix.apache.org/
The source exists here: https://github.com/apache/celix-site

Roy

Op wo 18 sep. 2019 om 16:33 schreef Owen O'Malley :

> Since all of the Apache projects have their websites checked in, find one
> you like and copy the style and start from there. That is how Calcite
> 's page ended up looking at lot like ORC
> 's.
> ..Owen
>
>
> On Wed, Sep 18, 2019 at 6:16 AM Christofer Dutz  >
> wrote:
>
> > Hi all,
> >
> > I just wanted to ask if there is any “shared service” or nice person that
> > could help the PLC4X Website.
> > It’s sort of looked the same since I initiated the project and I think
> > it’s not quite in a state that will make people get interested in what
> > we’re doing.
> > As I really suck greatly at web-design, I just wanted to ask if there is
> > any shared service or someone willing to help us with improving it.
> >
> > Would be happy for some positive feedback,
> > Chris
> >
>

Re: Diversity / Inclusion

[Roy Lenferink]

Hi Austin,

Since a month we have got a training podling as well. The goal of this
training
project is to gather and provide as much training material as possible.
This can vary from project specific material but I can understand that
'How-to
ASF' material is present as well. A website hasn't been created yet,
but the mailing list is quite active already, so if you need any material
you may ask over there as well.

- Roy

Op zo 31 mrt. 2019 om 08:49 schreef Ross Gardler :

> Justin Mclean has done some work on Apache Way teaching modules (added to
> To line as I'm not sure if he is on the ComDev list)
>
> 
> From: Austin Bennett 
> Sent: Saturday, March 30, 2019 7:19 PM
> To: dev@community.apache.org
> Subject: Diversity / Inclusion
>
> Hi Apache Community,
>
> This is related to recent discussions, but I'm looking for practical
> suggestions for a concrete initiative, so not jumping in on those threads.
>
> Working with the administration at a local community college - looking at
> methods for training some English as a second language - and immigrant (to
> the USA) - students to learn things coding/computing.  Computer Science is
> an 'impacted' major, meaning students are not even able to gain access to
> those classes, so there is motivation to figure out how to expand those
> capabilities.
>
> This has me exploring putting things together to train these students.
> Outside of the technical skills, I am imagining teaching them about (and
> encourage living by) the Apache Way, and thoughts around encouraging this
> mentality from the outset ("meritocracy" as a quite loaded word, for
> example).  It seems such awareness would be beneficial to people as they
> are learning (and anyone); In addition this might serve as a pipeline for
> the future for people that would contribute positively to Apache.
>
> Anything else I should be looking at outside of the website:
>
> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcommunity.apache.orgdata=02%7C01%7C%7C1e0ef8bd54174f76f88508d6b57f51c3%7C84df9e7fe9f640afb435%7C1%7C0%7C636895955760405352sdata=IEJzzDEsxGCaeFHpfr%2BpGizvwxvClhZWuB%2BudCoyW0s%3Dreserved=0
> ?
>
> Thanks,
> Austin
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: Proposed process for recognizing *Non-Technical* Contributions

[Roy Lenferink]

Op ma 21 jan. 2019 om 20:25 schreef Joan Touzet :

> "Mark Thomas"  wrote:
> > On 21/01/2019 17:59, Roy Lenferink wrote:
> > > CNCF is using a bot on their GitHub repositories which adds a label
> > > to
> > > every pull request whether the contributor has a cla on file
> > > [1][2].
> > > More info on this here [3]
> > > The cla label is checked before the PR can be merged.
> > >
> > > As we're moving to a broader GitHub integration maybe it is an idea
> > > to use
> > > a technology like this as well.
> >
> > That would make CLAs mandatory and I disagree very strongly with any
> > move in that direction.
>
> Absolutely agree with Mark here.
>

That indeed is a huge disadvantage as well. It isn't that I'm all for
requiring CLAs,
as it will block simple bug fixes as well, but at least I think it would be
good to
maybe enhance the process, e.g. a bot adding a "cla:no" or "cla:yes" label
doesn't harm anyone, and if a contributor is submitting a PR with a
sufficient
amount of changes it makes it easier for the committer to verify whether
the
contributor has a CLA filed.

But that's just my opinion. It's not a problem at all if anyone thinks
differently.
I'm just trying to figure out what would be best ;)


>
> The way we see it, when we receive a PR on an Apache repo from a random
> contributor that is merged by a committer, it is the committer who is
> responsible for the code, and the committer who has already signed
> the CLA.
>

IMO this is not completely true. I think it indeed is the responsibility of
the committer
to check whether a contributor needs to file an ICLA, but it still is the
contributor who actually committed the change and it's the contributor's
name
and e-mail that will be listed as author for the commit. The ASF committer
just
simply merged the commit back to the repo (knowing he has to check licenses
for used technology etc..).

But again, please correct me if I'm wrong.


>
> This is no different from when we used to receive .patch files by
> mailing list or JIRA. They arrived plenty of times from people
> who didn't have signed CLAs or commit bits. It was the committer's
> responsibility to review and accept the code, and it was their
> liability if something went wrong. This extends to any version
> controlled asset.
>
> Wikis are weird - we've dropped use of ours for most things, since
> there was misleading, confusing, and outdated content in ours, chiefly
> because there was no Review-Then-Commit model. GitHub PRs are RTC,
> not CTR, so the safeguard is built in. I can see the desire for a
> CLA to be signed when there is only a CTR process available.
>
> Communities that require CLAs to be signed before code can even be
> proposed for merging in a pull request, emailed patch or simlar
> definitely show a lower rate of participation than those who don't
> in my experience.
>
> -Joan
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: Proposed process for recognizing *Non-Technical* Contributions

[Roy Lenferink]

I think it is an excellent idea to suggest submitting an ICLA to
contributors when they submit a contribution.
CNCF is using a bot on their GitHub repositories which adds a label to
every pull request whether the contributor has a cla on file [1][2].
More info on this here [3]
The cla label is checked before the PR can be merged.

As we're moving to a broader GitHub integration maybe it is an idea to use
a technology like this as well.
I can foresee a small problem with this, as AFAIK all CLAs are still
processed manually, but correct me if I'm wrong.

What do you think?

[1] http://home.apache.org/~rlenferink/img/cncf-cla-message.png
[2] http://home.apache.org/~rlenferink/img/cncf-cla-reporting.png (last
job: cla/linuxfoundation)
[3]
https://github.com/kubernetes/community/blob/master/CLA.md#the-contributor-license-agreement

- Roy

Op ma 21 jan. 2019 om 07:02 schreef Craig Russell :

>
>
> > On Jan 20, 2019, at 9:52 PM, Craig Russell  wrote:
> >
> > Hi Sharan,
> >
> >> On Jan 13, 2019, at 5:59 AM, Sharan Foga  sha...@apache.org>> wrote:
> >>
> >> Hi Craig
> >>
> >> One thing that we have done in OFBiz is that when a contributor
> requests access to our wiki, we ask them to complete an ICLA before the
> access request is processed. This has helped to capture people who for
> example want to create documentation.
> >
> > This is a terrific idea. I think we should add something to the PMC
> pages about recognizing contributions and asking contributors to file ICLAs.
>
> Thinking about this some more, we might even recommend that the PMC
> actively monitor contributions from non-committers, not just those who
> request access to the wiki; and suggest that they should submit an ICLA.
>
> Craig
> >
> > In addition to the community building and the recognition, filing an
> ICLA has subsequent benefits to the project and the future committer. Just
> as soon as the PMC decides to invite the contributor to become a committer,
> they can finish the process without any delays.
> >
> > I'll propose some updates to the PMC community pages to reflect this.
> >
> > Craig
> >>
> >> We have setup a page with some basic explanations of what an ICLA is
> and why we are asking them to sign one.
> >>
> >> https://s.apache.org/NrGP 
> >>
> >> As well as setting them up with wiki access, we flag them in our Jira
> as part of a contributor group where they can then actually start assigning
> tasks (including the non technical ones) to themselves.
> >>
> >> Perhaps this could be one of the potential suggestions that we could
> include for projects.
> >>
> >> Thanks
> >> Sharan
> >>
> >> On 2019/01/10 15:52:19, Craig Russell  apache@gmail.com>> wrote:
> >>> Hi Sally,
> >>>
>  On Jan 10, 2019, at 12:53 AM, Sally Khudairi  s...@apache.org>> wrote:
> 
> >>> Great writeup and I can wholeheartedly agree with everything except
> this:
> >>>
>  3) All project/committee participants are encouraged to sign an ASF
> ICLA in order to have their contributions recognized.
> >>>
> >>> With my Secretary hat on: It is really a lot of work to process
> non-CLA contributors. So I'd change this to:
> >>>
> >>> 3) All project/committee participants are required to sign an ASF ICLA
> in order to have their contributions recognized.
> >>>
> >>> Normally this will have been done in step 2 but your writeup seems to
> imply that filing an ICLA is optional. My recommendation: not optional.
> >>>
> >>> Regards,
> >>>
> >>> Craig
> >>>
> >>> Craig L Russell
> >>> Secretary, Apache Software Foundation
> >>> c...@apache.org  > http://db.apache.org/jdo  <
> http://db.apache.org/jdo >
> >>>
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org  dev-unsubscr...@community.apache.org>
> >> For additional commands, e-mail: dev-h...@community.apache.org  dev-h...@community.apache.org>
> > Craig L Russell
> > Secretary, Apache Software Foundation
> > c...@apache.org  http://db.apache.org/jdo <
> http://db.apache.org/jdo>
> Craig L Russell
> Secretary, Apache Software Foundation
> c...@apache.org  http://db.apache.org/jdo <
> http://db.apache.org/jdo>
>

Re: Web-tool for moderation

[Roy Lenferink]

I didn't even think about integrating it to ponymail. That indeed would be
even a better solution. And maybe that will expand the ponymail community
as well.

- Roy

Op zo 30 dec. 2018 om 17:59 schreef Christofer Dutz <
christofer.d...@c-ware.de>:

> And such a tool could also made to handle spam and such.
> When moderating some of the lists, I do notice that as soon as I get spam
> on one list, usually within a few seconds I get more mails with the exact
> same input.
> For all I usually "reject" (Don't know if this is even needed).
>
> I think wouldn't ponymail be a good tool for things like this?
>
> Chris
>
>
>
> Am 30.12.18, 17:41 schrieb "Roy Lenferink" :
>
> About Chris his question for a web-tool for moderating mailing-lists:
>
> > PS: Do we have a web-tool for moderation? Right now all moderators
> get
> the same email and I can't see if someone else already accepted or
> rejected
> a message ... would be great if there was some "moderation inbox" with
> accept and reject buttons to quickly moderate all lists someone is
> listed
> as moderator for.
>
> I don't know if such a tool already exists but I am fairly interested
> in
> helping out if we want to create something. It shouldn't be too hard,
> but
> IMHO it will be really useful as currently moderation can be time
> consuming. I am currently moderating some mailing-lists as well and I
> found
> out that all the moderators are constantly replying to the same set of
> emails. A web-tool offering the ability to accept or reject mails (and
> maybe add a comment which other moderators can view as well) can be
> quite a
> solution. Would it be an idea to send this as an incubation proposal
> (just
> as Ponymail)?
>
> What's everyone else's opinion about this? Is there any interest in
> such a
> web-tool?
>
> - Roy
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: Introducing lists based on the overall project categories?

[Roy Lenferink]

Sounds good. Using the self-service platform it indeed is fairly easy to
request the mailing list(s) ;)

Roy

Op zo 30 dec. 2018 om 18:01 schreef Christofer Dutz <
christofer.d...@c-ware.de>:

> I think creating them wouldn't be a huge overhead ...
>
> and then we could simply notify the dev-lists of the projects tagged with
> a given category about the new list.
> This way anyone could signup.
>
> Chris
>
> Am 30.12.18, 17:38 schrieb "Roy Lenferink" :
>
> Are we starting with iot@ or are we creating other lists as well, e.g.
> streaming@ (Flink, Spark, Storm, Heron .) and big-data@ (Hadoop,
> Metron
> ) and so on.
> And were do we document the existence of these lists or do we leave it
> to
> the projects if they want to point to the iot@a.o (as an example)
> mailing
> list?
>
> - Roy
>
> Op zo 30 dec. 2018 om 14:56 schreef Christofer Dutz <
> christofer.d...@c-ware.de>:
>
> > So how would we create such a list?
> >
> > Chris
> >
> > Am 17.12.18, 09:44 schrieb "Christofer Dutz" <
> christofer.d...@c-ware.de>:
> >
> > Well I'd be happy to help moderating this. What's "one more
> list" in
> > the moderation inbox?
> >
> > Do we have to vote on setting up the "i...@apache.org" list ...
> if yes
> > ... do we do it here? Or could someone just create it.
> >
> >
> > Chris
> >
> > PS: Do we have a web-tool for moderation? Right now all
> moderators get
> > the same email and I can't see if someone else already accepted or
> rejected
> > a message ... would be great if there was some "moderation inbox"
> with
> > accept and reject buttons to quickly moderate all lists someone is
> listed
> > as moderator for.
> >
> >
> > Am 16.12.18, 14:53 schrieb "Rich Bowen" :
> >
> > +1 to the concept, and there's precedent with the geospatial
> list.
> >
> > Bertrand mentions the tech@ list but I don't think anybody
> knows
> > that it's
> > there or what it is for. Lists with topic names seem to have
> better
> > discoverability.
> >
> > Note also that they attract more spam so ensure that you
> have some
> > willing
> > moderators.
> >
> > I think an iot@ list is a great way to attract new
> participants
> > who aren't
> > already aware of the various projects and what they do.
> >
> > On Thu, Dec 13, 2018, 03:34 Christofer Dutz <
> > christofer.d...@c-ware.de
> > wrote:
> >
> > > Hi all,
> > >
> > > at the moment I’m involved in 3 Apache project in the IoT
> area.
> > A lot of
> > > the work I have been doing is to help make all of these
> work
> > together.
> > > PLC4X – NiFi Integration
> > > PLC4X – Apache Kafka Connect
> > > PLC4X – Camel Integration
> > > PLC4X – Edgent Integration
> > > Edgent - … integration
> > >
> > > However sometimes I could for example need some help by
> NiFi
> > Guys to check
> > > my NiFi integration, have Kafka Connect gurus provide
> > suggestions on how to
> > > improve our connector, …
> > >
> > > There’s a lot happening here and signing up and keeping up
> to
> > date for all
> > > the dev-lists of all the projects around here would leave
> no
> > time to
> > > actually work on things.
> > >
> > > So my idea is: As we have a list of general categories for
> our
> > projects,
> > > how about creating general “@apache.org” mailinglists for
> each
> > of these
> > > categories for the purpose of coordinating such efforts.
> > >
> > > What do you think?
> > >
> > >
> > > Chris
> > >
> >
> >
> >
> >
>  -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
> >
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
> >
>
>
>

Web-tool for moderation

[Roy Lenferink]

About Chris his question for a web-tool for moderating mailing-lists:

> PS: Do we have a web-tool for moderation? Right now all moderators get
the same email and I can't see if someone else already accepted or rejected
a message ... would be great if there was some "moderation inbox" with
accept and reject buttons to quickly moderate all lists someone is listed
as moderator for.

I don't know if such a tool already exists but I am fairly interested in
helping out if we want to create something. It shouldn't be too hard, but
IMHO it will be really useful as currently moderation can be time
consuming. I am currently moderating some mailing-lists as well and I found
out that all the moderators are constantly replying to the same set of
emails. A web-tool offering the ability to accept or reject mails (and
maybe add a comment which other moderators can view as well) can be quite a
solution. Would it be an idea to send this as an incubation proposal (just
as Ponymail)?

What's everyone else's opinion about this? Is there any interest in such a
web-tool?

- Roy

Re: Introducing lists based on the overall project categories?

[Roy Lenferink]

Are we starting with iot@ or are we creating other lists as well, e.g.
streaming@ (Flink, Spark, Storm, Heron .) and big-data@ (Hadoop, Metron
) and so on.
And were do we document the existence of these lists or do we leave it to
the projects if they want to point to the iot@a.o (as an example) mailing
list?

- Roy

Op zo 30 dec. 2018 om 14:56 schreef Christofer Dutz <
christofer.d...@c-ware.de>:

> So how would we create such a list?
>
> Chris
>
> Am 17.12.18, 09:44 schrieb "Christofer Dutz" :
>
> Well I'd be happy to help moderating this. What's "one more list" in
> the moderation inbox?
>
> Do we have to vote on setting up the "i...@apache.org" list ... if yes
> ... do we do it here? Or could someone just create it.
>
>
> Chris
>
> PS: Do we have a web-tool for moderation? Right now all moderators get
> the same email and I can't see if someone else already accepted or rejected
> a message ... would be great if there was some "moderation inbox" with
> accept and reject buttons to quickly moderate all lists someone is listed
> as moderator for.
>
>
> Am 16.12.18, 14:53 schrieb "Rich Bowen" :
>
> +1 to the concept, and there's precedent with the geospatial list.
>
> Bertrand mentions the tech@ list but I don't think anybody knows
> that it's
> there or what it is for. Lists with topic names seem to have better
> discoverability.
>
> Note also that they attract more spam so ensure that you have some
> willing
> moderators.
>
> I think an iot@ list is a great way to attract new participants
> who aren't
> already aware of the various projects and what they do.
>
> On Thu, Dec 13, 2018, 03:34 Christofer Dutz <
> christofer.d...@c-ware.de
> wrote:
>
> > Hi all,
> >
> > at the moment I’m involved in 3 Apache project in the IoT area.
> A lot of
> > the work I have been doing is to help make all of these work
> together.
> > PLC4X – NiFi Integration
> > PLC4X – Apache Kafka Connect
> > PLC4X – Camel Integration
> > PLC4X – Edgent Integration
> > Edgent - … integration
> >
> > However sometimes I could for example need some help by NiFi
> Guys to check
> > my NiFi integration, have Kafka Connect gurus provide
> suggestions on how to
> > improve our connector, …
> >
> > There’s a lot happening here and signing up and keeping up to
> date for all
> > the dev-lists of all the projects around here would leave no
> time to
> > actually work on things.
> >
> > So my idea is: As we have a list of general categories for our
> projects,
> > how about creating general “@apache.org” mailinglists for each
> of these
> > categories for the purpose of coordinating such efforts.
> >
> > What do you think?
> >
> >
> > Chris
> >
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: Upcoming event "ad" needed

[Roy Lenferink]

I've just taken the liberty to update these event images.

The images are committed and staged already. I couldn't publish the site
because of (Comdev PMC?) restrictions, so if someone else would want to
publish them that would be great ;)

This is what I've created:
http://www.staging.apache.org/events/current-event-125x125.jpg
http://www.staging.apache.org/events/current-event-234x60.jpg

If you want to have the dates changed to the 13th, just let me now as it
only takes a few minutes to change them.

Roy

Op wo 5 dec. 2018 om 18:53 schreef Rich Bowen :

>
>
> On 12/4/18 5:25 PM, Christopher wrote:
> > The dates on the graphic differ from the events website.
>
> Yes, they do. The 13th isn't really a conference day.
>
> Patches welcome. I will not get to this today.
>
> --Rich
>
>
> > On Tue, Dec 4, 2018 at 4:03 PM Rich Bowen  wrote:
> >>
> >> On 11/12/18 7:47 AM, Rich Bowen wrote:
> >>> We still need someone to create the ad images for the upcoming Apache
> >>> Roadshow. Project sites are still displaying the ad for Apachecon
> >>> Montreal. If anybody has the skill and time to do this, it would be
> >>> great if we could get that done this week.
> >>
> >> FWIW, I've updated these images. They don't look great, but at least
> >> they're correct now.
> >>
> >> Volunteers who know their way around image creation still welcome to
> >> make them look better.
> >>
> >> http://apache.org/events/README.txt
> >>
> >> --Rich
> >>
> >>
> >> --
> >> Rich Bowen - rbo...@rcbowen.com
> >> http://rcbowen.com/
> >> @rbowen
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> >> For additional commands, e-mail: dev-h...@community.apache.org
> >>
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
>
> --
> Rich Bowen - rbo...@rcbowen.com
> http://rcbowen.com/
> @rbowen
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Events.apache.org

[Roy Lenferink]

Hi folks,

I've got a question. How is events.a.o website updated?
Normally I 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 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

Re: Upcoming event "ad" needed

[Roy Lenferink]

Hi Rich,

I quickly tried to create the 2 images, as the upcoming roadshow is in less
than 3 weeks already.
Keep in mind I'm a software developer, not a graphical designer :)

http://home.apache.org/~rlenferink/img/apache-roadshow-2018-125x125.jpg
http://home.apache.org/~rlenferink/img/apache-roadshow-2018-234x60.jpg

Is this good enough or are you looking for something else?

Roy

Op ma 12 nov. 2018 om 19:05 schreef Rich Bowen :

> The required sizes are documented here -
> http://apache.org/events/README.txt
>
> I am getting on a plane and can offer more details later if needed
>
> On Mon, Nov 12, 2018, 12:31 Griselda Cuevas  wrote:
>
> > Hi Rich,
> >
> > Are you looking for a graphic design? If you give more specifics like
> type,
> > image size, content, etc. I might be able to help.
> >
> > G
> >
> >
> >
> >
> > On Mon, 12 Nov 2018 at 04:47, Rich Bowen  wrote:
> >
> > > We still need someone to create the ad images for the upcoming Apache
> > > Roadshow. Project sites are still displaying the ad for Apachecon
> > Montreal.
> > > If anybody has the skill and time to do this, it would be great if we
> > could
> > > get that done this week.
> > >
> >
>

Re: Apache Logo finder

[Roy Lenferink]

Perfect! I noticed you fixed the problem and everything is working fine
again ;)

Op zo 9 sep. 2018 om 14:49 schreef Daniel Gruno :

> Whoops! Looks like an update was missed, thanks for figuring that out! :)
>
> I can give you access to the machine, but only in an unofficial capacity
> right now - we're waiting for puppet 5 support at Apache (which is
> required for this VM) so we can set up LDAP auth for comdev folks.
>
> On 09/09/2018 02:32 PM, Roy Lenferink wrote:
> > Hi Daniel and other mailing list subscribers,
> >
> > I don't know how to check it myself therefore this question. Checking the
> > Apache logo finder [1] every 'Original' link is returning undef.svg.
> > This probably is because [2] is not having the 'opath' variable (included
> > in revision [3]).
> > Does anyone know if the latest compile.py is being executed or can
> someone
> > provide me with the information on how to check it myself?
> >
> > Roy
> >
> > [1] http://www.apache.org/logos/
> > [2] http://www.apache.org/logos/res/logos.json
> > [3]
> >
> https://svn.apache.org/viewvc/comdev/project-logos/tools/compile.py?r1=1839225=1839312
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Apache Logo finder

[Roy Lenferink]

Hi Daniel and other mailing list subscribers,

I don't know how to check it myself therefore this question. Checking the
Apache logo finder [1] every 'Original' link is returning undef.svg.
This probably is because [2] is not having the 'opath' variable (included
in revision [3]).
Does anyone know if the latest compile.py is being executed or can someone
provide me with the information on how to check it myself?

Roy

[1] http://www.apache.org/logos/
[2] http://www.apache.org/logos/res/logos.json
[3]
https://svn.apache.org/viewvc/comdev/project-logos/tools/compile.py?r1=1839225=1839312

Re: svn commit: r1839354 - /comdev/project-logos/site/js/logofinder.js

[Roy Lenferink]

On 2018/08/27 18:29:57, Daniel Gruno  wrote: 
> On 08/27/2018 08:28 PM, Roy Lenferink wrote:
> > 
> > 
> > On 2018/08/27 17:37:56, Daniel Gruno  wrote:
> >> On 08/27/2018 07:35 PM, rlenfer...@apache.org wrote:
> >>> Author: rlenferink
> >>> Date: Mon Aug 27 17:35:28 2018
> >>> New Revision: 1839354
> >>>
> >>> URL: http://svn.apache.org/viewvc?rev=1839354=rev
> >>> Log:
> >>> Resolved problem of showing wrong image icons for originals when the 
> >>> project name contains the extension (e.g. 'ai' in 'Pony Mail')
> >>
> >> Nice catch!
> >> I'm always nervous about using too "new" ecma standards ;-) but what the
> >> heck, I was using 'let' anyway!
> >>
> >> With regards,
> >> Daniel
> >>
> > 
> > Thanks, I checked [1] and Array#includes has more or less been around for 
> > 20 versions on Firefox/Chrome/Opera & Edge and because of the 'let' I 
> > thought, why not use it ;)
> > 
> > Side question:
> > Does the site update itself / does it pull in the latest changes from svn 
> > every hour? Or is that still an action you need to do manually?
> 
> It updates every hour and pulls in changes. I sometimes pull the stuff 
> manually when I update things.

Aha, thanks for answering, I was thinking it didn't update after committing, 
but I just noticed it has been propagated to the live version. Perfect ;)

Roy

> 
> > 
> > Regards,
> > Roy
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
> 
> 

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

Re: svn commit: r1839354 - /comdev/project-logos/site/js/logofinder.js

[Roy Lenferink]

On 2018/08/27 17:37:56, Daniel Gruno  wrote: 
> On 08/27/2018 07:35 PM, rlenfer...@apache.org wrote:
> > Author: rlenferink
> > Date: Mon Aug 27 17:35:28 2018
> > New Revision: 1839354
> > 
> > URL: http://svn.apache.org/viewvc?rev=1839354=rev
> > Log:
> > Resolved problem of showing wrong image icons for originals when the 
> > project name contains the extension (e.g. 'ai' in 'Pony Mail')
> 
> Nice catch!
> I'm always nervous about using too "new" ecma standards ;-) but what the 
> heck, I was using 'let' anyway!
> 
> With regards,
> Daniel
> 

Thanks, I checked [1] and Array#includes has more or less been around for 20 
versions on Firefox/Chrome/Opera & Edge and because of the 'let' I thought, why 
not use it ;)

Side question:
Does the site update itself / does it pull in the latest changes from svn every 
hour? Or is that still an action you need to do manually?

Regards,
Roy

[1] 
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/includes#Browser_compatibility

> > 
> > Modified:
> >  comdev/project-logos/site/js/logofinder.js
> > 
> > Modified: comdev/project-logos/site/js/logofinder.js
> > URL: 
> > http://svn.apache.org/viewvc/comdev/project-logos/site/js/logofinder.js?rev=1839354=1839353=1839354=diff
> > ==
> > --- comdev/project-logos/site/js/logofinder.js (original)
> > +++ comdev/project-logos/site/js/logofinder.js Mon Aug 27 17:35:28 2018
> > @@ -111,8 +111,9 @@ function make_div(key, project) {
> >   // original:
> >   let img =imgs[0];
> >   img.opath = img.opath || 'undef.svg';
> > -let ma = img.opath.match(/(eps|svg|ai|pdf)/);
> > -let oext = ma ? ma[1] : 'svg';
> > +let allowedExtensions = ['eps', 'svg', 'ai', 'pdf'];
> > +let imgExt = img.opath.split('.').pop();
> > +let oext = allowedExtensions.includes(imgExt) ? imgExt : 'svg';
> >   let arr = [
> >   new HTML('img', {src:'images/%s.png'.format(oext), style: 
> > {maxWidth: '24px', maxHeight: '24px'}}),
> >   new HTML('br'),
> > 
> > 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
> 
> 

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

Re: Help with task: Ensure all Apache TLPs have Wikipedia pages

[Roy Lenferink]

Hi Mehmet,

Thanks for offering your help.

Some time ago we updated the wikipedia page containing a list of active
projects [1]
Best is to start with the projects mentioned in this list which don't have
a wikipedia
page and create one following the instructions on the following page: [2]

Feel free to contact me, or this mailing list, if you have any questions at
all

Regards,
Roy

[1] https://en.wikipedia.org/wiki/List_of_Apache_Software_
Foundation_projects
[2] https://helpwanted.apache.org/task.html?0b349bee

2018-07-17 10:35 GMT+02:00 Mehmet Ali Özbay :

> I would like to help out with the task listed at
> https://helpwanted.apache.org/task.html?0b349bee
>

Re: Help with task: Ensure all Apache TLPs have Wikipedia pages

[Roy Lenferink]

Hi Ida,

Thanks for your interest.
A couple of weeks ago we updated the list of our projects on Wikipedia.
This list can be found here [1]
You can start creating pages for the projects that don't have a wikipedia
page (they will show up in red). The helpwanted task also gives a good
description about how to get started [2]

Please contact me, or this mailing list, if you have any questions at all

Roy

[1]
https://en.wikipedia.org/wiki/List_of_Apache_Software_Foundation_projects
[2] https://helpwanted.apache.org/task.html?0b349bee

2018-06-05 6:38 GMT+01:00 Ida Duarte :

> I would like to help out with the task listed at
> https://helpwanted.apache.org/task.html?0b349bee
>

Re: Volunteer for Task #0b349bee: Ensure all Apache TLPs have Wikipedia pages

[Roy Lenferink]

Hi Kelvin,

Thanks for your interest.
A couple of weeks ago we updated the list of our projects on Wikipedia.
This list can be found here [1]
You can start creating pages for the projects that don't have a wikipedia
page (they will show up in red).
The helpwanted task also gives a good description about how to get started
[2]

Please contact me, or this mailing list, if you have any questions at all

Roy

[1]
https://en.wikipedia.org/wiki/List_of_Apache_Software_Foundation_projects
[2] https://helpwanted.apache.org/task.html?0b349bee

2018-05-31 4:02 GMT+01:00 Kelvin Quee 魏有豪 :

> Hello there.
>
> Thank you for the good work at Mozilla.
>
> I am interested to help out in the following task -
>
>Task #0b349bee: Ensure all Apache TLPs have Wikipedia pages
>
> Please let me know what I can do. My profile can be found here -
>
>http://kelvin.quee.org
>
> Sincerely,
>
> --
> Kelvin Quee  魏有豪
> +65 9177 3635
>
>

Re: Apache TLP help

[Roy Lenferink]

On 2018/05/07 15:29:44, sebb <seb...@gmail.com> wrote: 
> On 7 May 2018 at 15:29, Roy Lenferink <lenferink...@gmail.com> wrote:
> > Hi Wayne,
> >
> > Thanks for your interest!
> >
> > What I would recommend to start with is to get a project from
> > https://projects.apache.org/projects.html and check if a Wikipedia
> > page exists for this project.
> >
> > If no such page exists, create one with a brief description, the
> > project's logo, language etc.
> >
> > I myself did this for the project I am involved with, Apache Celix [1]
> >
> > Use this as an example and start creating Wikipedia pages for
> > the projects listed on projects.apache.org
> > Note that I had to mention the source of the brief description
> > and that the website was licensed under the Apache License v2
> > as well. Otherwise the possibility exists that the article will be
> > flagged for deletion.
> >
> > The task aims to check the Wikipedia pages for all projects and
> > this can be time-consuming. Just start with one project, create a
> > Wikipedia page, and have fun contributing back to the community.
> >
> > Please contact me, or this mailing list, if you have any
> > questions at all.
> >
> > @Comdev PMC
> > It is probably a good idea to track the status of this task somewhere.
> > Is anyone having an idea for this, or is the cwiki the best place for this?
> 
> I wonder if one could add a Wikipedia page that lists all the Apache projects?

Coming back to this question. Such a page already existed but was last updated 
somewhere in 2015. Altough it took me some time, I just completed updating this 
list, and the Wikipedia page can be found here [1].

This way, when someone wants to start/continue with this task we can simply 
point them to the list of projects on Wikipedia.

[1] https://en.wikipedia.org/wiki/List_of_Apache_Software_Foundation_projects

> 
> > Roy
> >
> > [1] https://en.wikipedia.org/wiki/Apache_Celix
> >
> > 2018-05-06 23:53 GMT+01:00 Wayne Williams <wwill...@fiu.edu>:
> >
> >> I wanted to help out with the apache TLP wikipedia pages. Is there anything
> >> specific that I would need to know?
> >>
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
> 
> 

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

Re: Apache TLP help

[Roy Lenferink]

Hi Wayne,

Thanks for your interest!

What I would recommend to start with is to get a project from
https://projects.apache.org/projects.html and check if a Wikipedia
page exists for this project.

If no such page exists, create one with a brief description, the
project's logo, language etc.

I myself did this for the project I am involved with, Apache Celix [1]

Use this as an example and start creating Wikipedia pages for
the projects listed on projects.apache.org
Note that I had to mention the source of the brief description
and that the website was licensed under the Apache License v2
as well. Otherwise the possibility exists that the article will be
flagged for deletion.

The task aims to check the Wikipedia pages for all projects and
this can be time-consuming. Just start with one project, create a
Wikipedia page, and have fun contributing back to the community.

Please contact me, or this mailing list, if you have any
questions at all.

@Comdev PMC
It is probably a good idea to track the status of this task somewhere.
Is anyone having an idea for this, or is the cwiki the best place for this?

Roy

[1] https://en.wikipedia.org/wiki/Apache_Celix

2018-05-06 23:53 GMT+01:00 Wayne Williams :

> I wanted to help out with the apache TLP wikipedia pages. Is there anything
> specific that I would need to know?
>

Re: Help with task: How do I edit the site?

[Roy Lenferink]

Hi Glenn,

Thanks for your interest!

What I would recommend to start with is to get a project from
https://projects.apache.org/projects.html
For each project listed there, you'll find all details and the link to
its website.

Once you've found a project site that needs to be improved, you'll
have to get involved with the project's community to see how
changes can be applied to the site. All Apache projects use mailing lists
for
communication and you'll find all the project lists here:
lists.apache.org
Send an email to the project's mailing list asking for pointers on how
to edit the site, and consider subscribing to the list to be up to
date with the feedback and replies. You'll find a convenience
"subscribe" button at the bottom of each project's mailing list page.

The task aims to check all project sites and this can be
time-consuming. Just start with one project, dive into its site, and
have fun contributing back to the community.

Please contact me, or this mailing list, if you have any
questions at all.

To subscribe to this list, send an email to
dev-subscr...@community.apache.org and that will let you see responses
that go to the list, instead of to you directly.

Roy


Op wo 11 apr. 2018 om 02:21 schreef scndgln...@gmail.com <
scndgln...@gmail.com>

> I would like to help out with the task listed at
> https://helpwanted.apache.org/task.html?60e13b6eThanks Glenn Allan moore
> Sent from Yahoo Mail on Android

Re: Help with task: How do I edit the site?

[Roy Lenferink]

Hi Lori,

Thanks for your interest!

What I would recommend to start with is to get a project from
https://projects.apache.org/projects.html
For each project listed there, you'll find all details and the link to
its website.

Once you've found a project site that needs to be improved, you'll
have to get involved with the project's community to see how
changes can be applied to the site. All Apache projects use mailing lists
for
communication and you'll find all the project lists here:
lists.apache.org
Send an email to the project's mailing list asking for pointers on how
to edit the site, and consider subscribing to the list to be up to
date with the feedback and replies. You'll find a convenience
"subscribe" button at the bottom of each project's mailing list page.

The task aims to check all project sites and this can be
time-consuming. Just start with one project, dive into its site, and
have fun contributing back to the community.

Please contact me, or this mailing list, if you have any
questions at all.

To subscribe to this list, send an email to
dev-subscribe@community.apache.organd that will let you see responses
that go to the list, instead of to you directly.

Roy


Op di 10 apr. 2018 om 23:59 schreef Lori Worthington 

> I would like to help out with the task listed at
> https://helpwanted.apache.org/task.html?60e13b6e
> Please send me information
>

Re: About Help in Community

[Roy Lenferink]

Hi Mohit,

What I would recommend is that you take a look at
https://projects.apache.org/projects.html
This page is listing all Apache projects. It is probably the best that you
filter on a category
and/or specific programming language to find a project that you like to get
started with.
After you found yourself a project which you like to contribute to, you
will need to get in
touch with the project's community. You can do so by subscribing to the
project's mailing
list and asking them if there is a roadmap available to see which new
features they want to
implement. You can also start contributing to the project by submitting
small patches
to resolve any bugs. Issues for the project can be found on the GitHub
issues page or
in one of the issue trackers: https://issues.apache.org/

Please contact me, or this mailing list, if you have any questions at all.

To subscribe to this list, send an email to
dev-subscr...@community.apache.org and that will let you see responses
that go to the list, instead of to you directly.

Roy

2018-04-07 9:04 GMT+01:00 mohit patni :

> I am high school student I am expert in HTML , CSS ,C++ and Java.
> Please suggest any projects for me.
>
>
>
>  Sent with Mailtrack
>  il-inbox/ndnaehgpjlnokgebbaldlmgkapkpjkkb?utm_source=gmail
> tm_medium=signature_campaign=signaturevirality>
>

Re: Help with task: How do I edit the site?

[Roy Lenferink]

 Hi,

Thanks for your interest!

What I would recommend to start with is to get a project from
https://projects.apache.org/projects.html
For each project listed there, you'll find all details and the link to
its website.

Once you've found a project site that needs to be improved, you'll
have to get involved with the project's community to see how
changes can be applied to the site. All Apache projects use mailing lists
for
communication and you'll find all the project lists here:
lists.apache.org
Send an email to the project's mailing list asking for pointers on how
to edit the site, and consider subscribing to the list to be up to
date with the feedback and replies. You'll find a convenience
"subscribe" button at the bottom of each project's mailing list page.

The task aims to check all project sites and this can be
time-consuming. Just start with one project, dive into its site, and
have fun contributing back to the community.

Please contact me, or this mailing list, if you have any
questions at all.

To subscribe to this list, send an email to
dev-subscr...@community.apache.org and that will let you see responses
that go to the list, instead of to you directly.

Roy


2018-04-07 13:27 GMT+01:00 วรรณิษา อ่อนหวาน :

> I would like to help out with the task listed at
> https://helpwanted.apache.org/task.html?60e13b6e
>

Re: Help with task: How do I edit the site?

[Roy Lenferink]

Hi,

Thanks for your interest!

What I would recommend to start with is to get a project from
https://projects.apache.org/projects.html
For each project listed there, you'll find all details and the link to
its website.

Once you've found a project site that needs to be improved, you'll
have to get involved with the project's community to see how
changes can be applied to the site. All Apache projects use mailing lists
for
communication and you'll find all the project lists here:
lists.apache.org
Send an email to the project's mailing list asking for pointers on how
to edit the site, and consider subscribing to the list to be up to
date with the feedback and replies. You'll find a convenience
"subscribe" button at the bottom of each project's mailing list page.

The task aims to check all project sites and this can be
time-consuming. Just start with one project, dive into its site, and
have fun contributing back to the community.

Please contact me, or this mailing list, if you have any
questions at all.

To subscribe to this list, send an email to
dev-subscr...@community.apache.org and that will let you see responses
that go to the list, instead of to you directly.

Roy


2018-04-07 1:12 GMT+01:00 سعېد ـآلنـآهسې :

> I would like to help out with the task listed at
> https://helpwanted.apache.org/task.html?60e13b6e
>

Re: Help with task: Ensure all Apache TLPs have Wikipedia pages

[Roy Lenferink]

 Hi Elied,

Thanks for your interest!

What I would recommend to start with is to get a project from
https://projects.apache.org/projects.html and check if a Wikipedia
page exists for this project.

If no such page exists, create one with a brief description, the
project's logo, language etc.

I myself did this for the project I am involved with, Apache Celix.
The Wikipedia page can be found here:
https://en.wikipedia.org/wiki/Apache_Celix

Use this as an example and start creating Wikipedia pages for
the projects listed on projects.apache.org
Note that I had to mention the source of the brief description
and that the website was licensed under the Apache License v2
as well. Otherwise the possibility exists that the article will be
deleted.

The task aims to check the Wikipedia pages for all projects and
this can be time-consuming. Just start with one project, create a
Wikipedia page, and have fun contributing back to the community.

Please contact me, or this mailing list, if you have any
questions at all.

To subscribe to this list, send an email to
dev-subscr...@community.apache.org and that will let you see responses
that go to the list, instead of to you directly.

Roy

2018-04-05 4:24 GMT+01:00 Elied Peña Hernández <
cricr1...@gmail.com>:

> I would like to help out with the task listed at
> https://helpwanted.apache.org/task.html?0b349bee
>

Re: Help with task: How do I edit the site?

[Roy Lenferink]

Hi Truong,

Thanks for your interest!

What I would recommend to start with is to get a project from
https://projects.apache.org/projects.html
For each project listed there, you'll find all details and the link to
its website.

Once you've found a project site that needs to be improved, you'll
have to get involved with the project's community to see how
changes can be applied to the site. All Apache projects use mailing lists
for
communication and you'll find all the project lists here:
lists.apache.org
Send an email to the project's mailing list asking for pointers on how
to edit the site, and consider subscribing to the list to be up to
date with the feedback and replies. You'll find a convenience
"subscribe" button at the bottom of each project's mailing list page.

The task aims to check all project sites and this can be
time-consuming. Just start with one project, dive into its site, and
have fun contributing back to the community.

Please contact me, or this mailing list, if you have any
questions at all.

To subscribe to this list, send an email to
dev-subscr...@community.apache.org and that will let you see responses
that go to the list, instead of to you directly.

Roy

2018-04-05 6:34 GMT+01:00 Truong Nhung :

> I would like to help out with the task listed at
> https://helpwanted.apache.org/task.html?60e13b6e
>

Re: Help with task: Ensure all Apache TLPs have Wikipedia pages

[Roy Lenferink]

Hi Mark,

Thank you for your response and sorting this out. At first the page was
nominated for deletion again, even with your answer and pointing to the
License. After some time she changed her mind because she took an actual
look on the website.

For everyone else working on this task, Wikipedia works in the way when you
are using a sentence from the project its websites, you have to
specifically mention the website is licensed under the Apache License as
well.
For an example, see "External links" on [1] : "*Prose in this article was
copied from this source, which is released under an Apache License, Version
2.0.*"

Thanks Mark!

Roy

[1] https://en.wikipedia.org/wiki/Apache_Celix


2018-03-22 9:33 GMT+00:00 Mark Thomas <ma...@apache.org>:

> Roy,
>
> I spoken with the editor concerned [1] and it should be possible for you
> to recreate the Apache Celix page and any other pages that that editor
> removed.
>
> For future reference in case it helps you or others:
>
> The content of all of our web sites is licensed under the Apache
> License, version 2 unless explicitly stated otherwise. I can't think of
> any examples of alternative licencing off the top of my head but there
> might be a few instances somewhere.
>
> The ALv2 permits re-use (see sections 2 and 4 in particular).
>
> While section 6 of the ALv2 may appear to prevent the use of logos, it
> does not prevent nominative use [2] and our policy explicitly calls out
> using the logo in an article to refer to the project as being OK [3].
>
> HTH,
>
> Mark
>
> [1] https://en.wikipedia.org/wiki/User_talk:RHaworth
> [2] http://www.apache.org/foundation/marks/#principles
> [3] http://www.apache.org/foundation/marks/#guidelines
>
>
> On 20/03/18 20:32, Roy Lenferink wrote:
> > Hi,
> >
> > I also started with this task. What should one do to keep the pages to
> > exist?
> >
> > * https://en.wikipedia.org/wiki/Apache_Celix
> > * https://commons.wikimedia.org/wiki/File:Apache_Celix.png
> > * https://en.wikipedia.org/wiki/Apache_Zeppelin
> > * https://commons.wikimedia.org/wiki/File:Apache_Zeppelin.png
> >
> > And this is going on for all the pages.
> >
> > The response: Looking at the license, material created using the software
> > is released under license. But the license does not appear to extend to
> > their webpages, logos, and so on. Asking for pages to be created is not
> the
> > same thing as releasing copyright material under a compatible license.
> >
> > Even when using the main project sentence which explains the project
> which
> > is stored in the official README in the GitHub repository mirror a
> > complaint is filed:
> > https://en.wikipedia.org/wiki/Talk:Apache_Zeppelin
> >
> > What is probably the best way to resolve this, as the information put on
> > Wikipedia should match the Apache TLP its website.
> >
> > Roy
> >
> > 2018-03-15 18:40 GMT+00:00 Rich Bowen <rbo...@rcbowen.com>:
> >
> >> What I would recommend as a starting point is to go to the Apache
> Software
> >> Foundation wikipedia page, and stub in links to all of the projects that
> >> are listed at projects.apache.org
> >>
> >>
> >> On 03/15/2018 05:29 AM, THE THE wrote:
> >>
> >>> I would like to help out with the task listed at
> >>> https://helpwanted.apache.org/task.html?0b349bee
> >>>
> >>>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> >> For additional commands, e-mail: dev-h...@community.apache.org
> >>
> >>
> >
>
>

Re: Help with task: Ensure all Apache TLPs have Wikipedia pages

[Roy Lenferink]

Hi,

I also started with this task. What should one do to keep the pages to
exist?

* https://en.wikipedia.org/wiki/Apache_Celix
* https://commons.wikimedia.org/wiki/File:Apache_Celix.png
* https://en.wikipedia.org/wiki/Apache_Zeppelin
* https://commons.wikimedia.org/wiki/File:Apache_Zeppelin.png

And this is going on for all the pages.

The response: Looking at the license, material created using the software
is released under license. But the license does not appear to extend to
their webpages, logos, and so on. Asking for pages to be created is not the
same thing as releasing copyright material under a compatible license.

Even when using the main project sentence which explains the project which
is stored in the official README in the GitHub repository mirror a
complaint is filed:
https://en.wikipedia.org/wiki/Talk:Apache_Zeppelin

What is probably the best way to resolve this, as the information put on
Wikipedia should match the Apache TLP its website.

Roy

2018-03-15 18:40 GMT+00:00 Rich Bowen :

> What I would recommend as a starting point is to go to the Apache Software
> Foundation wikipedia page, and stub in links to all of the projects that
> are listed at projects.apache.org
>
>
> On 03/15/2018 05:29 AM, THE THE wrote:
>
>> I would like to help out with the task listed at
>> https://helpwanted.apache.org/task.html?0b349bee
>>
>>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>