You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@annotator.apache.org by Randall Leeds <ra...@apache.org> on 2019/10/10 20:28:43 UTC
Fwd: [NOTICE] Introducing .asf.yaml for enhanced automation of git
repository services
Is this useful for us for Annotator?
On Wed, Sep 4, 2019 at 8:32 PM Daniel Gruno <hu...@apache.org> wrote:
> Hello, fellow Apache committers and enthusiasts!
>
> Today, the Apache Infrastructure Team is launching new self-serve
> features to help augment the productivity of Apache projects through a
> series of simple configurations for enabling automation of various
> service offerings.
>
> We call this new initiative '.asf.yaml', and as the name implies, it
> consists of a new file that projects can add to their git repositories
> to control various aspects that were previously done through JIRA
> tickets and manual operations by the Infrastructure staff.
>
> For detailed information about these features and how to enable them,
> please visit our documentation page at: https://s.apache.org/asfyaml
>
> At launch time, .asf.yaml has three features enabled that projects can
> make use of: web site staging, web site publishing, and github meta-data
> settings:
>
> web site staging:
> Much like with the Apache CMS system, projects using git can now get
> their web sites staged for previews at a specific (HTTPS-enabled)
> staging domain. Staging supports multi-tenancy, which allows for
> multiple staging web sites from different site repository branches.
> For more information on multi-tenancy, see the canonical documentation
> linked above.
>
> web site publishing:
> Projects can now automatically set up publishing for their own main
> web site ($project.apache.org) and change at will, without the need to
> wait for assistance from the Infrastructure team. New podlings and
> projects can also get web sites bootstrapped and ready immediately.
>
> github meta-data settings:
> Projects can now, via .asf.yaml, specify their repositories' meta-data
> on github, such as the description, homepage URL, and which topics to
> add to a repository's front page.
>
> In the coming months, we will extend this feature with many new,
> exciting features such as automated buildbot integration for web site
> generation (think CMS but via git) and enhanced JIRA integration
> automation.
>
> We hope projects will appreciate and make use of these new features. If
> you or your project have any questions, please feel free to reach out to
> us at: users@infra.apache.org - but please read through the
> documentation first :)
>
> With regards, and on behalf of the Apache Infrastructure Team,
> Daniel.
>
Re: [NOTICE] Introducing .asf.yaml for enhanced automation of git
repository services
Posted by Randall Leeds <ra...@apache.org>.
Thanks, Benjamin!
On Wed, Nov 6, 2019 at 2:04 PM Benjamin Young <by...@bigbluehat.com> wrote:
> Definitely! :)
>
> I've added an initial one just tweaking our GitHub metadata:
>
> https://github.com/apache/incubator-annotator/commit/7ff79c1a345169c85d15b4ae46761875e185e453
>
> We should be able to use this with the website repo to (re)setup GitHub
> Pages there too--though I'm not keen to disrupt things there (i.e. it ain't
> broke ;) ).
>
> Feel free to tweak those labels, etc.
>
> Cheers!
> Benjamin
>
>
> --
>
> http://bigbluehat.com/
>
> http://linkedin.com/in/benjaminyoung
>
> ________________________________
> From: Randall Leeds <ra...@apache.org>
> Sent: Thursday, October 10, 2019 4:28 PM
> To: dev@annotator.incubator.apache.org <dev@annotator.incubator.apache.org
> >
> Subject: Fwd: [NOTICE] Introducing .asf.yaml for enhanced automation of
> git repository services
>
> Is this useful for us for Annotator?
>
> On Wed, Sep 4, 2019 at 8:32 PM Daniel Gruno <hu...@apache.org> wrote:
>
> > Hello, fellow Apache committers and enthusiasts!
> >
> > Today, the Apache Infrastructure Team is launching new self-serve
> > features to help augment the productivity of Apache projects through a
> > series of simple configurations for enabling automation of various
> > service offerings.
> >
> > We call this new initiative '.asf.yaml', and as the name implies, it
> > consists of a new file that projects can add to their git repositories
> > to control various aspects that were previously done through JIRA
> > tickets and manual operations by the Infrastructure staff.
> >
> > For detailed information about these features and how to enable them,
> > please visit our documentation page at: https://s.apache.org/asfyaml
> >
> > At launch time, .asf.yaml has three features enabled that projects can
> > make use of: web site staging, web site publishing, and github meta-data
> > settings:
> >
> > web site staging:
> > Much like with the Apache CMS system, projects using git can now get
> > their web sites staged for previews at a specific (HTTPS-enabled)
> > staging domain. Staging supports multi-tenancy, which allows for
> > multiple staging web sites from different site repository branches.
> > For more information on multi-tenancy, see the canonical documentation
> > linked above.
> >
> > web site publishing:
> > Projects can now automatically set up publishing for their own main
> > web site ($project.apache.org) and change at will, without the need
> to
> > wait for assistance from the Infrastructure team. New podlings and
> > projects can also get web sites bootstrapped and ready immediately.
> >
> > github meta-data settings:
> > Projects can now, via .asf.yaml, specify their repositories' meta-data
> > on github, such as the description, homepage URL, and which topics to
> > add to a repository's front page.
> >
> > In the coming months, we will extend this feature with many new,
> > exciting features such as automated buildbot integration for web site
> > generation (think CMS but via git) and enhanced JIRA integration
> > automation.
> >
> > We hope projects will appreciate and make use of these new features. If
> > you or your project have any questions, please feel free to reach out to
> > us at: users@infra.apache.org - but please read through the
> > documentation first :)
> >
> > With regards, and on behalf of the Apache Infrastructure Team,
> > Daniel.
> >
>
Re: [NOTICE] Introducing .asf.yaml for enhanced automation of git
repository services
Posted by Benjamin Young <by...@bigbluehat.com>.
Definitely! :)
I've added an initial one just tweaking our GitHub metadata:
https://github.com/apache/incubator-annotator/commit/7ff79c1a345169c85d15b4ae46761875e185e453
We should be able to use this with the website repo to (re)setup GitHub Pages there too--though I'm not keen to disrupt things there (i.e. it ain't broke ;) ).
Feel free to tweak those labels, etc.
Cheers!
Benjamin
--
http://bigbluehat.com/
http://linkedin.com/in/benjaminyoung
________________________________
From: Randall Leeds <ra...@apache.org>
Sent: Thursday, October 10, 2019 4:28 PM
To: dev@annotator.incubator.apache.org <de...@annotator.incubator.apache.org>
Subject: Fwd: [NOTICE] Introducing .asf.yaml for enhanced automation of git repository services
Is this useful for us for Annotator?
On Wed, Sep 4, 2019 at 8:32 PM Daniel Gruno <hu...@apache.org> wrote:
> Hello, fellow Apache committers and enthusiasts!
>
> Today, the Apache Infrastructure Team is launching new self-serve
> features to help augment the productivity of Apache projects through a
> series of simple configurations for enabling automation of various
> service offerings.
>
> We call this new initiative '.asf.yaml', and as the name implies, it
> consists of a new file that projects can add to their git repositories
> to control various aspects that were previously done through JIRA
> tickets and manual operations by the Infrastructure staff.
>
> For detailed information about these features and how to enable them,
> please visit our documentation page at: https://s.apache.org/asfyaml
>
> At launch time, .asf.yaml has three features enabled that projects can
> make use of: web site staging, web site publishing, and github meta-data
> settings:
>
> web site staging:
> Much like with the Apache CMS system, projects using git can now get
> their web sites staged for previews at a specific (HTTPS-enabled)
> staging domain. Staging supports multi-tenancy, which allows for
> multiple staging web sites from different site repository branches.
> For more information on multi-tenancy, see the canonical documentation
> linked above.
>
> web site publishing:
> Projects can now automatically set up publishing for their own main
> web site ($project.apache.org) and change at will, without the need to
> wait for assistance from the Infrastructure team. New podlings and
> projects can also get web sites bootstrapped and ready immediately.
>
> github meta-data settings:
> Projects can now, via .asf.yaml, specify their repositories' meta-data
> on github, such as the description, homepage URL, and which topics to
> add to a repository's front page.
>
> In the coming months, we will extend this feature with many new,
> exciting features such as automated buildbot integration for web site
> generation (think CMS but via git) and enhanced JIRA integration
> automation.
>
> We hope projects will appreciate and make use of these new features. If
> you or your project have any questions, please feel free to reach out to
> us at: users@infra.apache.org - but please read through the
> documentation first :)
>
> With regards, and on behalf of the Apache Infrastructure Team,
> Daniel.
>