You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openaz.apache.org by David Ash <gr...@gmail.com> on 2016/04/20 18:19:04 UTC
Moving forward
I think first priority is getting the new team promoted to committers, and
probably set as initial-commiters so we can utilize the private email list
in the future. But that can be done by the PMC I think.
First up for the devs is the website in my opinion, because that will help
us organize better. I think we should go with the Apache CMS solution
because that will get us up and running quickly, and free us up to do other
tasks. If anyone disagrees about priority or direction, please chime in.
Information for setting up a podling website is at:
http://incubator.apache.org/guides/sites.html
Regarding podling websites, this guide says:
Regardless of which tool you use, the web site should be maintained in the
> svn repository, and include the site generation tool as a binary file. This
> simplifies the process of site generation and enables changes to the site
> to be made by any committer. The generated site should also be checked into
> svn. This allows the generated site to be relocated to any part of the
> Apache site after incubation is complete.
Since the site is independent of the code, it should exist high in the svn
> repository, e.g. parallel to the trunk of the source tree.
Previously we were going to make a github repo for the website, commit
there, and then merge that into the apache repo. Has a github repo been
created yet? If so, what is the URL? If not, please respond quickly so we
can make one.
Once we have committers, we can commit it - or an existing committer can
commit it if they can do so quickly.
Also, until we have a website, there's some important URLs for the project
that I guess we should just post here for now. Here's what I know, please
add anything I'm missing.
*General*
Incubator page: http://incubator.apache.org/projects/openaz.html
Website: http://openaz.incubator.apache.org/
Project management:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20OPENAZ%20ORDER%20BY%20status%20DESC
*Source code*
Official Repo:
https://git-wip-us.apache.org/repos/asf?p=incubator-openaz.git
Github Repo: https://github.com/apache/incubator-openaz
*Website*
Official Repo: (same as source code, branching at top level?)
Github Repo: ???
*Other ASF / Useful Links:*
http://www.apache.org/dev/new-committers-guide.html
http://incubator.apache.org/guides/sites.html
http://www.apache.org/dev/cms.html
Any other thoughts for moving forward? Let's keep the conversation rolling!
David
Re: Moving forward
Posted by David Ash <gr...@gmail.com>.
*Mailing list subscription addresses:*
Everyone should subscribe to the dev list and commits list by sending an
> email to the following:
>
> dev-subscribe at openaz.incubator.apache.org
> users-subscribe at openaz.incubator.apache.org
> commits-subscribe at openaz.incubator.apache.org
>
> The folks on the initial committers list should also subscribe to the
> private list by sending an email to:
> private-subscribe at openaz.incubator.apache.org
On Wed, Apr 20, 2016 at 10:19 AM, David Ash <gr...@gmail.com> wrote:
> I think first priority is getting the new team promoted to committers, and
> probably set as initial-commiters so we can utilize the private email list
> in the future. But that can be done by the PMC I think.
>
> First up for the devs is the website in my opinion, because that will help
> us organize better. I think we should go with the Apache CMS solution
> because that will get us up and running quickly, and free us up to do other
> tasks. If anyone disagrees about priority or direction, please chime in.
>
> Information for setting up a podling website is at:
> http://incubator.apache.org/guides/sites.html
>
> Regarding podling websites, this guide says:
>
> Regardless of which tool you use, the web site should be maintained in the
>> svn repository, and include the site generation tool as a binary file. This
>> simplifies the process of site generation and enables changes to the site
>> to be made by any committer. The generated site should also be checked into
>> svn. This allows the generated site to be relocated to any part of the
>> Apache site after incubation is complete.
>
> Since the site is independent of the code, it should exist high in the svn
>> repository, e.g. parallel to the trunk of the source tree.
>
>
> Previously we were going to make a github repo for the website, commit
> there, and then merge that into the apache repo. Has a github repo been
> created yet? If so, what is the URL? If not, please respond quickly so we
> can make one.
>
> Once we have committers, we can commit it - or an existing committer can
> commit it if they can do so quickly.
>
> Also, until we have a website, there's some important URLs for the project
> that I guess we should just post here for now. Here's what I know, please
> add anything I'm missing.
>
> *General*
> Incubator page: http://incubator.apache.org/projects/openaz.html
> Website: http://openaz.incubator.apache.org/
> Project management:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20OPENAZ%20ORDER%20BY%20status%20DESC
>
> *Source code*
> Official Repo:
> https://git-wip-us.apache.org/repos/asf?p=incubator-openaz.git
> Github Repo: https://github.com/apache/incubator-openaz
>
> *Website*
> Official Repo: (same as source code, branching at top level?)
> Github Repo: ???
>
> *Other ASF / Useful Links:*
> http://www.apache.org/dev/new-committers-guide.html
> http://incubator.apache.org/guides/sites.html
> http://www.apache.org/dev/cms.html
>
>
> Any other thoughts for moving forward? Let's keep the conversation
> rolling!
>
> David
>
Re: Moving forward
Posted by Yanik Grignon <yg...@salesforce.com>.
David,
Dug this out of the Feburary 2016 archive of the dev mailing list...
https://mail-archives.apache.org/mod_mbox/incubator-openaz-dev/201602.mbox/browser
Thanks!
Yanik Grignon
Sharing Team
On Wed, Apr 20, 2016 at 2:13 PM, David Ash <gr...@gmail.com> wrote:
> I know that url, but thanks for replying. :-)
>
> I'm actually looking for the url for the website's repo on github, that pam
> created for putting up the blank page. Or were you saying that page
> contained a link to it?
> On Apr 20, 2016 1:04 PM, "Yanik Grignon" <yg...@salesforce.com> wrote:
>
> > http://openaz.incubator.apache.org/
> >
> >
> > Thanks!
> >
> > Yanik Grignon
> > Sharing Team
> >
> > On Wed, Apr 20, 2016 at 1:49 PM, David Ash <gr...@gmail.com> wrote:
> >
> > > That's great info! What's the website URL?
> > >
> > > On Wed, Apr 20, 2016 at 12:41 PM, Yanik Grignon <
> ygrignon@salesforce.com
> > >
> > > wrote:
> > >
> > > > Pam made an initial commit into the website repo. It's basically an
> > empty
> > > > HTML file. Got the web site "working" in that it no longer generates
> an
> > > > error when you go there.
> > > >
> > > >
> > > > Thanks!
> > > >
> > > > Yanik Grignon
> > > > Sharing Team
> > > >
> > > > On Wed, Apr 20, 2016 at 11:19 AM, David Ash <gr...@gmail.com>
> > > wrote:
> > > >
> > > > > I think first priority is getting the new team promoted to
> > committers,
> > > > and
> > > > > probably set as initial-commiters so we can utilize the private
> email
> > > > list
> > > > > in the future. But that can be done by the PMC I think.
> > > > >
> > > > > First up for the devs is the website in my opinion, because that
> will
> > > > help
> > > > > us organize better. I think we should go with the Apache CMS
> > solution
> > > > > because that will get us up and running quickly, and free us up to
> do
> > > > other
> > > > > tasks. If anyone disagrees about priority or direction, please
> chime
> > > in.
> > > > >
> > > > > Information for setting up a podling website is at:
> > > > > http://incubator.apache.org/guides/sites.html
> > > > >
> > > > > Regarding podling websites, this guide says:
> > > > >
> > > > > Regardless of which tool you use, the web site should be maintained
> > in
> > > > the
> > > > > > svn repository, and include the site generation tool as a binary
> > > file.
> > > > > This
> > > > > > simplifies the process of site generation and enables changes to
> > the
> > > > site
> > > > > > to be made by any committer. The generated site should also be
> > > checked
> > > > > into
> > > > > > svn. This allows the generated site to be relocated to any part
> of
> > > the
> > > > > > Apache site after incubation is complete.
> > > > >
> > > > > Since the site is independent of the code, it should exist high in
> > the
> > > > svn
> > > > > > repository, e.g. parallel to the trunk of the source tree.
> > > > >
> > > > >
> > > > > Previously we were going to make a github repo for the website,
> > commit
> > > > > there, and then merge that into the apache repo. Has a github repo
> > > been
> > > > > created yet? If so, what is the URL? If not, please respond
> quickly
> > > so
> > > > we
> > > > > can make one.
> > > > >
> > > > > Once we have committers, we can commit it - or an existing
> committer
> > > can
> > > > > commit it if they can do so quickly.
> > > > >
> > > > > Also, until we have a website, there's some important URLs for the
> > > > project
> > > > > that I guess we should just post here for now. Here's what I know,
> > > > please
> > > > > add anything I'm missing.
> > > > >
> > > > > *General*
> > > > > Incubator page: http://incubator.apache.org/projects/openaz.html
> > > > > Website: http://openaz.incubator.apache.org/
> > > > > Project management:
> > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20OPENAZ%20ORDER%20BY%20status%20DESC
> > > > >
> > > > > *Source code*
> > > > > Official Repo:
> > > > > https://git-wip-us.apache.org/repos/asf?p=incubator-openaz.git
> > > > > Github Repo: https://github.com/apache/incubator-openaz
> > > > >
> > > > > *Website*
> > > > > Official Repo: (same as source code, branching at top level?)
> > > > > Github Repo: ???
> > > > >
> > > > > *Other ASF / Useful Links:*
> > > > > http://www.apache.org/dev/new-committers-guide.html
> > > > > http://incubator.apache.org/guides/sites.html
> > > > > http://www.apache.org/dev/cms.html
> > > > >
> > > > >
> > > > > Any other thoughts for moving forward? Let's keep the conversation
> > > > > rolling!
> > > > >
> > > > > David
> > > > >
> > > >
> > >
> >
>
Re: Moving forward
Posted by David Ash <gr...@gmail.com>.
I know that url, but thanks for replying. :-)
I'm actually looking for the url for the website's repo on github, that pam
created for putting up the blank page. Or were you saying that page
contained a link to it?
On Apr 20, 2016 1:04 PM, "Yanik Grignon" <yg...@salesforce.com> wrote:
> http://openaz.incubator.apache.org/
>
>
> Thanks!
>
> Yanik Grignon
> Sharing Team
>
> On Wed, Apr 20, 2016 at 1:49 PM, David Ash <gr...@gmail.com> wrote:
>
> > That's great info! What's the website URL?
> >
> > On Wed, Apr 20, 2016 at 12:41 PM, Yanik Grignon <ygrignon@salesforce.com
> >
> > wrote:
> >
> > > Pam made an initial commit into the website repo. It's basically an
> empty
> > > HTML file. Got the web site "working" in that it no longer generates an
> > > error when you go there.
> > >
> > >
> > > Thanks!
> > >
> > > Yanik Grignon
> > > Sharing Team
> > >
> > > On Wed, Apr 20, 2016 at 11:19 AM, David Ash <gr...@gmail.com>
> > wrote:
> > >
> > > > I think first priority is getting the new team promoted to
> committers,
> > > and
> > > > probably set as initial-commiters so we can utilize the private email
> > > list
> > > > in the future. But that can be done by the PMC I think.
> > > >
> > > > First up for the devs is the website in my opinion, because that will
> > > help
> > > > us organize better. I think we should go with the Apache CMS
> solution
> > > > because that will get us up and running quickly, and free us up to do
> > > other
> > > > tasks. If anyone disagrees about priority or direction, please chime
> > in.
> > > >
> > > > Information for setting up a podling website is at:
> > > > http://incubator.apache.org/guides/sites.html
> > > >
> > > > Regarding podling websites, this guide says:
> > > >
> > > > Regardless of which tool you use, the web site should be maintained
> in
> > > the
> > > > > svn repository, and include the site generation tool as a binary
> > file.
> > > > This
> > > > > simplifies the process of site generation and enables changes to
> the
> > > site
> > > > > to be made by any committer. The generated site should also be
> > checked
> > > > into
> > > > > svn. This allows the generated site to be relocated to any part of
> > the
> > > > > Apache site after incubation is complete.
> > > >
> > > > Since the site is independent of the code, it should exist high in
> the
> > > svn
> > > > > repository, e.g. parallel to the trunk of the source tree.
> > > >
> > > >
> > > > Previously we were going to make a github repo for the website,
> commit
> > > > there, and then merge that into the apache repo. Has a github repo
> > been
> > > > created yet? If so, what is the URL? If not, please respond quickly
> > so
> > > we
> > > > can make one.
> > > >
> > > > Once we have committers, we can commit it - or an existing committer
> > can
> > > > commit it if they can do so quickly.
> > > >
> > > > Also, until we have a website, there's some important URLs for the
> > > project
> > > > that I guess we should just post here for now. Here's what I know,
> > > please
> > > > add anything I'm missing.
> > > >
> > > > *General*
> > > > Incubator page: http://incubator.apache.org/projects/openaz.html
> > > > Website: http://openaz.incubator.apache.org/
> > > > Project management:
> > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20OPENAZ%20ORDER%20BY%20status%20DESC
> > > >
> > > > *Source code*
> > > > Official Repo:
> > > > https://git-wip-us.apache.org/repos/asf?p=incubator-openaz.git
> > > > Github Repo: https://github.com/apache/incubator-openaz
> > > >
> > > > *Website*
> > > > Official Repo: (same as source code, branching at top level?)
> > > > Github Repo: ???
> > > >
> > > > *Other ASF / Useful Links:*
> > > > http://www.apache.org/dev/new-committers-guide.html
> > > > http://incubator.apache.org/guides/sites.html
> > > > http://www.apache.org/dev/cms.html
> > > >
> > > >
> > > > Any other thoughts for moving forward? Let's keep the conversation
> > > > rolling!
> > > >
> > > > David
> > > >
> > >
> >
>
Re: Moving forward
Posted by Yanik Grignon <yg...@salesforce.com>.
http://openaz.incubator.apache.org/
Thanks!
Yanik Grignon
Sharing Team
On Wed, Apr 20, 2016 at 1:49 PM, David Ash <gr...@gmail.com> wrote:
> That's great info! What's the website URL?
>
> On Wed, Apr 20, 2016 at 12:41 PM, Yanik Grignon <yg...@salesforce.com>
> wrote:
>
> > Pam made an initial commit into the website repo. It's basically an empty
> > HTML file. Got the web site "working" in that it no longer generates an
> > error when you go there.
> >
> >
> > Thanks!
> >
> > Yanik Grignon
> > Sharing Team
> >
> > On Wed, Apr 20, 2016 at 11:19 AM, David Ash <gr...@gmail.com>
> wrote:
> >
> > > I think first priority is getting the new team promoted to committers,
> > and
> > > probably set as initial-commiters so we can utilize the private email
> > list
> > > in the future. But that can be done by the PMC I think.
> > >
> > > First up for the devs is the website in my opinion, because that will
> > help
> > > us organize better. I think we should go with the Apache CMS solution
> > > because that will get us up and running quickly, and free us up to do
> > other
> > > tasks. If anyone disagrees about priority or direction, please chime
> in.
> > >
> > > Information for setting up a podling website is at:
> > > http://incubator.apache.org/guides/sites.html
> > >
> > > Regarding podling websites, this guide says:
> > >
> > > Regardless of which tool you use, the web site should be maintained in
> > the
> > > > svn repository, and include the site generation tool as a binary
> file.
> > > This
> > > > simplifies the process of site generation and enables changes to the
> > site
> > > > to be made by any committer. The generated site should also be
> checked
> > > into
> > > > svn. This allows the generated site to be relocated to any part of
> the
> > > > Apache site after incubation is complete.
> > >
> > > Since the site is independent of the code, it should exist high in the
> > svn
> > > > repository, e.g. parallel to the trunk of the source tree.
> > >
> > >
> > > Previously we were going to make a github repo for the website, commit
> > > there, and then merge that into the apache repo. Has a github repo
> been
> > > created yet? If so, what is the URL? If not, please respond quickly
> so
> > we
> > > can make one.
> > >
> > > Once we have committers, we can commit it - or an existing committer
> can
> > > commit it if they can do so quickly.
> > >
> > > Also, until we have a website, there's some important URLs for the
> > project
> > > that I guess we should just post here for now. Here's what I know,
> > please
> > > add anything I'm missing.
> > >
> > > *General*
> > > Incubator page: http://incubator.apache.org/projects/openaz.html
> > > Website: http://openaz.incubator.apache.org/
> > > Project management:
> > >
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20OPENAZ%20ORDER%20BY%20status%20DESC
> > >
> > > *Source code*
> > > Official Repo:
> > > https://git-wip-us.apache.org/repos/asf?p=incubator-openaz.git
> > > Github Repo: https://github.com/apache/incubator-openaz
> > >
> > > *Website*
> > > Official Repo: (same as source code, branching at top level?)
> > > Github Repo: ???
> > >
> > > *Other ASF / Useful Links:*
> > > http://www.apache.org/dev/new-committers-guide.html
> > > http://incubator.apache.org/guides/sites.html
> > > http://www.apache.org/dev/cms.html
> > >
> > >
> > > Any other thoughts for moving forward? Let's keep the conversation
> > > rolling!
> > >
> > > David
> > >
> >
>
Re: Moving forward
Posted by David Ash <gr...@gmail.com>.
That's great info! What's the website URL?
On Wed, Apr 20, 2016 at 12:41 PM, Yanik Grignon <yg...@salesforce.com>
wrote:
> Pam made an initial commit into the website repo. It's basically an empty
> HTML file. Got the web site "working" in that it no longer generates an
> error when you go there.
>
>
> Thanks!
>
> Yanik Grignon
> Sharing Team
>
> On Wed, Apr 20, 2016 at 11:19 AM, David Ash <gr...@gmail.com> wrote:
>
> > I think first priority is getting the new team promoted to committers,
> and
> > probably set as initial-commiters so we can utilize the private email
> list
> > in the future. But that can be done by the PMC I think.
> >
> > First up for the devs is the website in my opinion, because that will
> help
> > us organize better. I think we should go with the Apache CMS solution
> > because that will get us up and running quickly, and free us up to do
> other
> > tasks. If anyone disagrees about priority or direction, please chime in.
> >
> > Information for setting up a podling website is at:
> > http://incubator.apache.org/guides/sites.html
> >
> > Regarding podling websites, this guide says:
> >
> > Regardless of which tool you use, the web site should be maintained in
> the
> > > svn repository, and include the site generation tool as a binary file.
> > This
> > > simplifies the process of site generation and enables changes to the
> site
> > > to be made by any committer. The generated site should also be checked
> > into
> > > svn. This allows the generated site to be relocated to any part of the
> > > Apache site after incubation is complete.
> >
> > Since the site is independent of the code, it should exist high in the
> svn
> > > repository, e.g. parallel to the trunk of the source tree.
> >
> >
> > Previously we were going to make a github repo for the website, commit
> > there, and then merge that into the apache repo. Has a github repo been
> > created yet? If so, what is the URL? If not, please respond quickly so
> we
> > can make one.
> >
> > Once we have committers, we can commit it - or an existing committer can
> > commit it if they can do so quickly.
> >
> > Also, until we have a website, there's some important URLs for the
> project
> > that I guess we should just post here for now. Here's what I know,
> please
> > add anything I'm missing.
> >
> > *General*
> > Incubator page: http://incubator.apache.org/projects/openaz.html
> > Website: http://openaz.incubator.apache.org/
> > Project management:
> >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20OPENAZ%20ORDER%20BY%20status%20DESC
> >
> > *Source code*
> > Official Repo:
> > https://git-wip-us.apache.org/repos/asf?p=incubator-openaz.git
> > Github Repo: https://github.com/apache/incubator-openaz
> >
> > *Website*
> > Official Repo: (same as source code, branching at top level?)
> > Github Repo: ???
> >
> > *Other ASF / Useful Links:*
> > http://www.apache.org/dev/new-committers-guide.html
> > http://incubator.apache.org/guides/sites.html
> > http://www.apache.org/dev/cms.html
> >
> >
> > Any other thoughts for moving forward? Let's keep the conversation
> > rolling!
> >
> > David
> >
>
Re: Moving forward
Posted by Yanik Grignon <yg...@salesforce.com>.
Pam made an initial commit into the website repo. It's basically an empty
HTML file. Got the web site "working" in that it no longer generates an
error when you go there.
Thanks!
Yanik Grignon
Sharing Team
On Wed, Apr 20, 2016 at 11:19 AM, David Ash <gr...@gmail.com> wrote:
> I think first priority is getting the new team promoted to committers, and
> probably set as initial-commiters so we can utilize the private email list
> in the future. But that can be done by the PMC I think.
>
> First up for the devs is the website in my opinion, because that will help
> us organize better. I think we should go with the Apache CMS solution
> because that will get us up and running quickly, and free us up to do other
> tasks. If anyone disagrees about priority or direction, please chime in.
>
> Information for setting up a podling website is at:
> http://incubator.apache.org/guides/sites.html
>
> Regarding podling websites, this guide says:
>
> Regardless of which tool you use, the web site should be maintained in the
> > svn repository, and include the site generation tool as a binary file.
> This
> > simplifies the process of site generation and enables changes to the site
> > to be made by any committer. The generated site should also be checked
> into
> > svn. This allows the generated site to be relocated to any part of the
> > Apache site after incubation is complete.
>
> Since the site is independent of the code, it should exist high in the svn
> > repository, e.g. parallel to the trunk of the source tree.
>
>
> Previously we were going to make a github repo for the website, commit
> there, and then merge that into the apache repo. Has a github repo been
> created yet? If so, what is the URL? If not, please respond quickly so we
> can make one.
>
> Once we have committers, we can commit it - or an existing committer can
> commit it if they can do so quickly.
>
> Also, until we have a website, there's some important URLs for the project
> that I guess we should just post here for now. Here's what I know, please
> add anything I'm missing.
>
> *General*
> Incubator page: http://incubator.apache.org/projects/openaz.html
> Website: http://openaz.incubator.apache.org/
> Project management:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20OPENAZ%20ORDER%20BY%20status%20DESC
>
> *Source code*
> Official Repo:
> https://git-wip-us.apache.org/repos/asf?p=incubator-openaz.git
> Github Repo: https://github.com/apache/incubator-openaz
>
> *Website*
> Official Repo: (same as source code, branching at top level?)
> Github Repo: ???
>
> *Other ASF / Useful Links:*
> http://www.apache.org/dev/new-committers-guide.html
> http://incubator.apache.org/guides/sites.html
> http://www.apache.org/dev/cms.html
>
>
> Any other thoughts for moving forward? Let's keep the conversation
> rolling!
>
> David
>
Re: Moving forward
Posted by David Ash <gr...@gmail.com>.
Yeah, and there's another pr in there as well, which I'd presume is the PR
that didn't merge correctly?
On Apr 20, 2016 1:07 PM, "Yanik Grignon" <yg...@salesforce.com> wrote:
> Speaking of which, there's still your pull request that has not been
> integrated (PAP code port form AT&T repo).
>
>
> Thanks!
>
> Yanik Grignon
> Sharing Team
>
> On Wed, Apr 20, 2016 at 2:03 PM, David Ash <gr...@gmail.com> wrote:
>
> > That's a good question. Does anyone know the answer to that? Can any
> > committer merge a pull request on github, or how does that happen? We'd
> > like to make sure we can move quickly, so the more people capable of
> doing
> > it the better, particularly regarding the website.
> > On Apr 20, 2016 12:58 PM, "Sam Barrett" <sa...@gmail.com> wrote:
> >
> > > Sounds good. We can start working on the website, and then commit it
> and
> > > submit a pull request once we have the address for the website github
> > repo.
> > > But who merges the pull request on github? Will we be able to do that
> > once
> > > we're committers?
> > >
> > > On Wed, Apr 20, 2016 at 12:50 PM, David Ash <gr...@gmail.com>
> > wrote:
> > >
> > > > I spoke with our new developers, and they just got subscribed to the
> > > > mailing list, so I'm re-sending what I sent earlier. If you already
> > saw
> > > > this, please ignore:
> > > >
> > > >
> > > > I think first priority is getting the new team promoted to
> committers,
> > > and
> > > > > probably set as initial-commiters so we can utilize the private
> email
> > > > list
> > > > > in the future. But that can be done by the PMC I think.
> > > > >
> > > > > First up for the devs is the website in my opinion, because that
> will
> > > > help
> > > > > us organize better. I think we should go with the Apache CMS
> > solution
> > > > > because that will get us up and running quickly, and free us up to
> do
> > > > other
> > > > > tasks. If anyone disagrees about priority or direction, please
> chime
> > > in.
> > > > >
> > > > > Information for setting up a podling website is at:
> > > > > http://incubator.apache.org/guides/sites.html
> > > > >
> > > > > Regarding podling websites, this guide says:
> > > > >
> > > > > Regardless of which tool you use, the web site should be maintained
> > in
> > > > the
> > > > >> svn repository, and include the site generation tool as a binary
> > file.
> > > > This
> > > > >> simplifies the process of site generation and enables changes to
> the
> > > > site
> > > > >> to be made by any committer. The generated site should also be
> > checked
> > > > into
> > > > >> svn. This allows the generated site to be relocated to any part of
> > the
> > > > >> Apache site after incubation is complete.
> > > > >
> > > > > Since the site is independent of the code, it should exist high in
> > the
> > > > svn
> > > > >> repository, e.g. parallel to the trunk of the source tree.
> > > > >
> > > > >
> > > > > Previously we were going to make a github repo for the website,
> > commit
> > > > > there, and then merge that into the apache repo. Has a github repo
> > > been
> > > > > created yet? If so, what is the URL? If not, please respond
> quickly
> > > so
> > > > we
> > > > > can make one.
> > > > >
> > > > > Once we have committers, we can commit it - or an existing
> committer
> > > can
> > > > > commit it if they can do so quickly.
> > > > >
> > > > > Also, until we have a website, there's some important URLs for the
> > > > project
> > > > > that I guess we should just post here for now. Here's what I know,
> > > > please
> > > > > add anything I'm missing.
> > > > >
> > > > > *General*
> > > > > Incubator page: http://incubator.apache.org/projects/openaz.html
> > > > > Website: http://openaz.incubator.apache.org/
> > > > > Project management:
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20OPENAZ%20ORDER%20BY%20status%20DESC
> > > > >
> > > > > *Source code*
> > > > > Official Repo:
> > > > > https://git-wip-us.apache.org/repos/asf?p=incubator-openaz.git
> > > > > Github Repo: https://github.com/apache/incubator-openaz
> > > > >
> > > > > *Website*
> > > > > Official Repo: (same as source code, branching at top level?)
> > > > > Github Repo: ???
> > > > >
> > > > > *Other ASF / Useful Links:*
> > > > > http://www.apache.org/dev/new-committers-guide.html
> > > > > http://incubator.apache.org/guides/sites.html
> > > > > http://www.apache.org/dev/cms.html
> > > > >
> > > >
> > > > *Mailing list subscription addresses:*
> > > >
> > > > Everyone should subscribe to the dev list and commits list by sending
> > an
> > > > > email to the following:
> > > > >
> > > > > dev-subscribe at openaz.incubator.apache.org
> > > > > users-subscribe at openaz.incubator.apache.org
> > > > > commits-subscribe at openaz.incubator.apache.org
> > > > >
> > > > > The folks on the initial committers list should also subscribe to
> the
> > > > > private list by sending an email to:
> > > > > private-subscribe at openaz.incubator.apache.org
> > > >
> > > >
> > > >
> > > > >
> > > > >
> > > > >
> > > > > Any other thoughts for moving forward? Let's keep the conversation
> > > > > rolling!
> > > > >
> > > > > David
> > > > >
> > > >
> > >
> >
>
Re: Moving forward
Posted by Yanik Grignon <yg...@salesforce.com>.
Speaking of which, there's still your pull request that has not been
integrated (PAP code port form AT&T repo).
Thanks!
Yanik Grignon
Sharing Team
On Wed, Apr 20, 2016 at 2:03 PM, David Ash <gr...@gmail.com> wrote:
> That's a good question. Does anyone know the answer to that? Can any
> committer merge a pull request on github, or how does that happen? We'd
> like to make sure we can move quickly, so the more people capable of doing
> it the better, particularly regarding the website.
> On Apr 20, 2016 12:58 PM, "Sam Barrett" <sa...@gmail.com> wrote:
>
> > Sounds good. We can start working on the website, and then commit it and
> > submit a pull request once we have the address for the website github
> repo.
> > But who merges the pull request on github? Will we be able to do that
> once
> > we're committers?
> >
> > On Wed, Apr 20, 2016 at 12:50 PM, David Ash <gr...@gmail.com>
> wrote:
> >
> > > I spoke with our new developers, and they just got subscribed to the
> > > mailing list, so I'm re-sending what I sent earlier. If you already
> saw
> > > this, please ignore:
> > >
> > >
> > > I think first priority is getting the new team promoted to committers,
> > and
> > > > probably set as initial-commiters so we can utilize the private email
> > > list
> > > > in the future. But that can be done by the PMC I think.
> > > >
> > > > First up for the devs is the website in my opinion, because that will
> > > help
> > > > us organize better. I think we should go with the Apache CMS
> solution
> > > > because that will get us up and running quickly, and free us up to do
> > > other
> > > > tasks. If anyone disagrees about priority or direction, please chime
> > in.
> > > >
> > > > Information for setting up a podling website is at:
> > > > http://incubator.apache.org/guides/sites.html
> > > >
> > > > Regarding podling websites, this guide says:
> > > >
> > > > Regardless of which tool you use, the web site should be maintained
> in
> > > the
> > > >> svn repository, and include the site generation tool as a binary
> file.
> > > This
> > > >> simplifies the process of site generation and enables changes to the
> > > site
> > > >> to be made by any committer. The generated site should also be
> checked
> > > into
> > > >> svn. This allows the generated site to be relocated to any part of
> the
> > > >> Apache site after incubation is complete.
> > > >
> > > > Since the site is independent of the code, it should exist high in
> the
> > > svn
> > > >> repository, e.g. parallel to the trunk of the source tree.
> > > >
> > > >
> > > > Previously we were going to make a github repo for the website,
> commit
> > > > there, and then merge that into the apache repo. Has a github repo
> > been
> > > > created yet? If so, what is the URL? If not, please respond quickly
> > so
> > > we
> > > > can make one.
> > > >
> > > > Once we have committers, we can commit it - or an existing committer
> > can
> > > > commit it if they can do so quickly.
> > > >
> > > > Also, until we have a website, there's some important URLs for the
> > > project
> > > > that I guess we should just post here for now. Here's what I know,
> > > please
> > > > add anything I'm missing.
> > > >
> > > > *General*
> > > > Incubator page: http://incubator.apache.org/projects/openaz.html
> > > > Website: http://openaz.incubator.apache.org/
> > > > Project management:
> > > >
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20OPENAZ%20ORDER%20BY%20status%20DESC
> > > >
> > > > *Source code*
> > > > Official Repo:
> > > > https://git-wip-us.apache.org/repos/asf?p=incubator-openaz.git
> > > > Github Repo: https://github.com/apache/incubator-openaz
> > > >
> > > > *Website*
> > > > Official Repo: (same as source code, branching at top level?)
> > > > Github Repo: ???
> > > >
> > > > *Other ASF / Useful Links:*
> > > > http://www.apache.org/dev/new-committers-guide.html
> > > > http://incubator.apache.org/guides/sites.html
> > > > http://www.apache.org/dev/cms.html
> > > >
> > >
> > > *Mailing list subscription addresses:*
> > >
> > > Everyone should subscribe to the dev list and commits list by sending
> an
> > > > email to the following:
> > > >
> > > > dev-subscribe at openaz.incubator.apache.org
> > > > users-subscribe at openaz.incubator.apache.org
> > > > commits-subscribe at openaz.incubator.apache.org
> > > >
> > > > The folks on the initial committers list should also subscribe to the
> > > > private list by sending an email to:
> > > > private-subscribe at openaz.incubator.apache.org
> > >
> > >
> > >
> > > >
> > > >
> > > >
> > > > Any other thoughts for moving forward? Let's keep the conversation
> > > > rolling!
> > > >
> > > > David
> > > >
> > >
> >
>
Re: Moving forward
Posted by David Ash <gr...@gmail.com>.
Nevermind, I'll add the tasks and just assign them.
On Wed, Apr 20, 2016 at 2:54 PM, David Ash <gr...@gmail.com> wrote:
> Alternately, you could just work on the contributor pages and we can add
> the task later. It's really up to anyone what they work on, just
> communicate what you're doing with everyone else.
>
> On Wed, Apr 20, 2016 at 2:30 PM, David Ash <gr...@gmail.com> wrote:
>
>> Oh yeah, and make them tasks rather than features.
>>
>> On Wed, Apr 20, 2016 at 2:29 PM, David Ash <gr...@gmail.com> wrote:
>>
>>> You can see I already created two tasks:
>>>
>>> * Create skeleton of Apache CMS for website
>>> * Create content page: index
>>>
>>> Just keep going and add the other pages as one task each.
>>>
>>> So the next would be "Create content page: what is openaz" or something
>>> close to that. And you just keep going. Skip descriptions for now.
>>>
>>> It would be ideal if you could create a Website Epic, and assign them to
>>> it. But we can do that later, too.
>>>
>>> Once we have tasks in there, we can prioritize and assign them out. My
>>> priorities are first most on the skeleton, and next on the index and any
>>> pages for contributors.
>>>
>>>
>>> On Wed, Apr 20, 2016 at 2:22 PM, David Ash <gr...@gmail.com> wrote:
>>>
>>>> Nevermind, I see that you are. :-)
>>>>
>>>> Previously, I came up with a top-level map that detailed the pages.
>>>>
>>>>
>>>> I. Homepage
>>>>> - What is Apache OpenAZ? (very briefly, marketing material)
>>>>> - Release information
>>>>> - Links
>>>>
>>>>
>>>>
>>>>>
>>>>> II. General information
>>>>> - About (maybe more detailed)
>>>>> - License
>>>>> - FAQ
>>>>
>>>>
>>>>
>>>>>
>>>>> III. Download
>>>>
>>>>
>>>>
>>>>>
>>>>> IV. Documentation
>>>>> - Quick start guide
>>>>> - Detailed documentation
>>>>> - Wiki
>>>>
>>>>
>>>>
>>>>>
>>>>> V. Support
>>>>
>>>>
>>>>
>>>>>
>>>>> VI. Community
>>>>> - Mailing lists
>>>>> - Bug reports
>>>>> - Developer information
>>>>> - Contributors
>>>>> - Sponsors / Sponsorships
>>>>
>>>>
>>>>
>>>> Does anyone have any objections to using this as the sitemap for now?
>>>>
>>>> If not, Farasath, could you create new tasks in Jira for each page?
>>>> We need to break it up so different people can do different things.
>>>>
>>>> Also, we're going to need the repo you found mirrored on github. Do
>>>> you know/have the ability to make that happen, so the github URL would be:
>>>>
>>>> https://github.com/apache/incubator-openaz-site
>>>>
>>>>
>>>>
>>>> On Wed, Apr 20, 2016 at 2:14 PM, David Ash <gr...@gmail.com>
>>>> wrote:
>>>>
>>>>> Awesome! Are you signed up on the Jira?
>>>>>
>>>>> On Wed, Apr 20, 2016 at 2:07 PM, Farasath Ahamed <mefarazath@gmail.com
>>>>> > wrote:
>>>>>
>>>>>> When creating content I would like to give a hand. Let's get started
>>>>>> :)
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>
Re: Moving forward
Posted by David Ash <gr...@gmail.com>.
Alternately, you could just work on the contributor pages and we can add
the task later. It's really up to anyone what they work on, just
communicate what you're doing with everyone else.
On Wed, Apr 20, 2016 at 2:30 PM, David Ash <gr...@gmail.com> wrote:
> Oh yeah, and make them tasks rather than features.
>
> On Wed, Apr 20, 2016 at 2:29 PM, David Ash <gr...@gmail.com> wrote:
>
>> You can see I already created two tasks:
>>
>> * Create skeleton of Apache CMS for website
>> * Create content page: index
>>
>> Just keep going and add the other pages as one task each.
>>
>> So the next would be "Create content page: what is openaz" or something
>> close to that. And you just keep going. Skip descriptions for now.
>>
>> It would be ideal if you could create a Website Epic, and assign them to
>> it. But we can do that later, too.
>>
>> Once we have tasks in there, we can prioritize and assign them out. My
>> priorities are first most on the skeleton, and next on the index and any
>> pages for contributors.
>>
>>
>> On Wed, Apr 20, 2016 at 2:22 PM, David Ash <gr...@gmail.com> wrote:
>>
>>> Nevermind, I see that you are. :-)
>>>
>>> Previously, I came up with a top-level map that detailed the pages.
>>>
>>>
>>> I. Homepage
>>>> - What is Apache OpenAZ? (very briefly, marketing material)
>>>> - Release information
>>>> - Links
>>>
>>>
>>>
>>>>
>>>> II. General information
>>>> - About (maybe more detailed)
>>>> - License
>>>> - FAQ
>>>
>>>
>>>
>>>>
>>>> III. Download
>>>
>>>
>>>
>>>>
>>>> IV. Documentation
>>>> - Quick start guide
>>>> - Detailed documentation
>>>> - Wiki
>>>
>>>
>>>
>>>>
>>>> V. Support
>>>
>>>
>>>
>>>>
>>>> VI. Community
>>>> - Mailing lists
>>>> - Bug reports
>>>> - Developer information
>>>> - Contributors
>>>> - Sponsors / Sponsorships
>>>
>>>
>>>
>>> Does anyone have any objections to using this as the sitemap for now?
>>>
>>> If not, Farasath, could you create new tasks in Jira for each page? We
>>> need to break it up so different people can do different things.
>>>
>>> Also, we're going to need the repo you found mirrored on github. Do you
>>> know/have the ability to make that happen, so the github URL would be:
>>>
>>> https://github.com/apache/incubator-openaz-site
>>>
>>>
>>>
>>> On Wed, Apr 20, 2016 at 2:14 PM, David Ash <gr...@gmail.com> wrote:
>>>
>>>> Awesome! Are you signed up on the Jira?
>>>>
>>>> On Wed, Apr 20, 2016 at 2:07 PM, Farasath Ahamed <me...@gmail.com>
>>>> wrote:
>>>>
>>>>> When creating content I would like to give a hand. Let's get started :)
>>>>>
>>>>
>>>>
>>>
>>
>
Re: Moving forward
Posted by David Ash <gr...@gmail.com>.
Oh yeah, and make them tasks rather than features.
On Wed, Apr 20, 2016 at 2:29 PM, David Ash <gr...@gmail.com> wrote:
> You can see I already created two tasks:
>
> * Create skeleton of Apache CMS for website
> * Create content page: index
>
> Just keep going and add the other pages as one task each.
>
> So the next would be "Create content page: what is openaz" or something
> close to that. And you just keep going. Skip descriptions for now.
>
> It would be ideal if you could create a Website Epic, and assign them to
> it. But we can do that later, too.
>
> Once we have tasks in there, we can prioritize and assign them out. My
> priorities are first most on the skeleton, and next on the index and any
> pages for contributors.
>
>
> On Wed, Apr 20, 2016 at 2:22 PM, David Ash <gr...@gmail.com> wrote:
>
>> Nevermind, I see that you are. :-)
>>
>> Previously, I came up with a top-level map that detailed the pages.
>>
>>
>> I. Homepage
>>> - What is Apache OpenAZ? (very briefly, marketing material)
>>> - Release information
>>> - Links
>>
>>
>>
>>>
>>> II. General information
>>> - About (maybe more detailed)
>>> - License
>>> - FAQ
>>
>>
>>
>>>
>>> III. Download
>>
>>
>>
>>>
>>> IV. Documentation
>>> - Quick start guide
>>> - Detailed documentation
>>> - Wiki
>>
>>
>>
>>>
>>> V. Support
>>
>>
>>
>>>
>>> VI. Community
>>> - Mailing lists
>>> - Bug reports
>>> - Developer information
>>> - Contributors
>>> - Sponsors / Sponsorships
>>
>>
>>
>> Does anyone have any objections to using this as the sitemap for now?
>>
>> If not, Farasath, could you create new tasks in Jira for each page? We
>> need to break it up so different people can do different things.
>>
>> Also, we're going to need the repo you found mirrored on github. Do you
>> know/have the ability to make that happen, so the github URL would be:
>>
>> https://github.com/apache/incubator-openaz-site
>>
>>
>>
>> On Wed, Apr 20, 2016 at 2:14 PM, David Ash <gr...@gmail.com> wrote:
>>
>>> Awesome! Are you signed up on the Jira?
>>>
>>> On Wed, Apr 20, 2016 at 2:07 PM, Farasath Ahamed <me...@gmail.com>
>>> wrote:
>>>
>>>> When creating content I would like to give a hand. Let's get started :)
>>>>
>>>
>>>
>>
>
Re: Moving forward
Posted by David Ash <gr...@gmail.com>.
You can see I already created two tasks:
* Create skeleton of Apache CMS for website
* Create content page: index
Just keep going and add the other pages as one task each.
So the next would be "Create content page: what is openaz" or something
close to that. And you just keep going. Skip descriptions for now.
It would be ideal if you could create a Website Epic, and assign them to
it. But we can do that later, too.
Once we have tasks in there, we can prioritize and assign them out. My
priorities are first most on the skeleton, and next on the index and any
pages for contributors.
On Wed, Apr 20, 2016 at 2:22 PM, David Ash <gr...@gmail.com> wrote:
> Nevermind, I see that you are. :-)
>
> Previously, I came up with a top-level map that detailed the pages.
>
>
> I. Homepage
>> - What is Apache OpenAZ? (very briefly, marketing material)
>> - Release information
>> - Links
>
>
>
>>
>> II. General information
>> - About (maybe more detailed)
>> - License
>> - FAQ
>
>
>
>>
>> III. Download
>
>
>
>>
>> IV. Documentation
>> - Quick start guide
>> - Detailed documentation
>> - Wiki
>
>
>
>>
>> V. Support
>
>
>
>>
>> VI. Community
>> - Mailing lists
>> - Bug reports
>> - Developer information
>> - Contributors
>> - Sponsors / Sponsorships
>
>
>
> Does anyone have any objections to using this as the sitemap for now?
>
> If not, Farasath, could you create new tasks in Jira for each page? We
> need to break it up so different people can do different things.
>
> Also, we're going to need the repo you found mirrored on github. Do you
> know/have the ability to make that happen, so the github URL would be:
>
> https://github.com/apache/incubator-openaz-site
>
>
>
> On Wed, Apr 20, 2016 at 2:14 PM, David Ash <gr...@gmail.com> wrote:
>
>> Awesome! Are you signed up on the Jira?
>>
>> On Wed, Apr 20, 2016 at 2:07 PM, Farasath Ahamed <me...@gmail.com>
>> wrote:
>>
>>> When creating content I would like to give a hand. Let's get started :)
>>>
>>
>>
>
Re: Moving forward
Posted by David Ash <gr...@gmail.com>.
Nevermind, I see that you are. :-)
Previously, I came up with a top-level map that detailed the pages.
I. Homepage
> - What is Apache OpenAZ? (very briefly, marketing material)
> - Release information
> - Links
>
> II. General information
> - About (maybe more detailed)
> - License
> - FAQ
>
> III. Download
>
> IV. Documentation
> - Quick start guide
> - Detailed documentation
> - Wiki
>
> V. Support
>
> VI. Community
> - Mailing lists
> - Bug reports
> - Developer information
> - Contributors
> - Sponsors / Sponsorships
Does anyone have any objections to using this as the sitemap for now?
If not, Farasath, could you create new tasks in Jira for each page? We
need to break it up so different people can do different things.
Also, we're going to need the repo you found mirrored on github. Do you
know/have the ability to make that happen, so the github URL would be:
https://github.com/apache/incubator-openaz-site
On Wed, Apr 20, 2016 at 2:14 PM, David Ash <gr...@gmail.com> wrote:
> Awesome! Are you signed up on the Jira?
>
> On Wed, Apr 20, 2016 at 2:07 PM, Farasath Ahamed <me...@gmail.com>
> wrote:
>
>> When creating content I would like to give a hand. Let's get started :)
>>
>
>
Re: Moving forward
Posted by David Ash <gr...@gmail.com>.
Awesome! Are you signed up on the Jira?
On Wed, Apr 20, 2016 at 2:07 PM, Farasath Ahamed <me...@gmail.com>
wrote:
> When creating content I would like to give a hand. Let's get started :)
>
Re: Moving forward
Posted by David Ash <gr...@gmail.com>.
Awesome! Good job, and thanks!
On Sun, May 22, 2016, 2:14 AM Farasath Ahamed <me...@gmail.com> wrote:
> Hi,
>
> Added some content to the doc and included some links from which we can
> pull content to the website.
>
>
> Thanks
>
> On Sat, May 21, 2016 at 2:20 AM, David Ash <gr...@gmail.com> wrote:
>
>> My bad, Farasath. Good catch. I've opened it to editing by anyone that
>> has a copy of the link.
>>
>> On Thu, May 19, 2016 at 11:14 PM, Farasath Ahamed <me...@gmail.com>
>> wrote:
>>
>>> Hi David,
>>>
>>> It looks like read-only to me. Can you change the permissions please? :)
>>> or share the doc with mefarazath@gmail.com so that I can add content
>>>
>>> Thanks.
>>>
>>> On Thu, May 19, 2016 at 11:14 PM, David Ash <gr...@gmail.com>
>>> wrote:
>>>
>>>> I've started a public Google doc that has the skeleton of the website.
>>>> I figure we can use it to create a rough draft of the content.
>>>>
>>>>
>>>> https://docs.google.com/document/d/1fs2h7e1v7oog7UkZC5x_v1Vyg8TQ1tLzPsJGVMPjzio/edit?usp=sharing
>>>>
>>>>
>>>> Everyone, please feel free to make any constructive additions / edits.
>>>>
>>>>
>>>>
>>>> Thanks!
>>>>
>>>> David Ash
>>>>
>>>>
>>>>
>>>>
>>>> On Wed, Apr 20, 2016 at 2:07 PM, Farasath Ahamed <me...@gmail.com>
>>>> wrote:
>>>>
>>>>> When creating content I would like to give a hand. Let's get started :)
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> *A.Farasath Ahamed*
>>> Undergraduate | Department of Computer Science and
>>> Engineering,University of Moratuwa
>>> Article Writer | MoraSpirit
>>> Mobile: +94 777 603 866
>>> Blog: blog.farazath.com
>>> E-Mail: mefarazath@gmail.com
>>>
>>
>>
>
>
> --
> *A.Farasath Ahamed*
> Undergraduate | Department of Computer Science and Engineering,University
> of Moratuwa
> Article Writer | MoraSpirit
> Mobile: +94 777 603 866
> Blog: blog.farazath.com
> E-Mail: mefarazath@gmail.com
>
Re: Moving forward
Posted by Farasath Ahamed <me...@gmail.com>.
Hi,
Added some content to the doc and included some links from which we can
pull content to the website.
Thanks
On Sat, May 21, 2016 at 2:20 AM, David Ash <gr...@gmail.com> wrote:
> My bad, Farasath. Good catch. I've opened it to editing by anyone that
> has a copy of the link.
>
> On Thu, May 19, 2016 at 11:14 PM, Farasath Ahamed <me...@gmail.com>
> wrote:
>
>> Hi David,
>>
>> It looks like read-only to me. Can you change the permissions please? :)
>> or share the doc with mefarazath@gmail.com so that I can add content
>>
>> Thanks.
>>
>> On Thu, May 19, 2016 at 11:14 PM, David Ash <gr...@gmail.com> wrote:
>>
>>> I've started a public Google doc that has the skeleton of the website.
>>> I figure we can use it to create a rough draft of the content.
>>>
>>>
>>> https://docs.google.com/document/d/1fs2h7e1v7oog7UkZC5x_v1Vyg8TQ1tLzPsJGVMPjzio/edit?usp=sharing
>>>
>>>
>>> Everyone, please feel free to make any constructive additions / edits.
>>>
>>>
>>>
>>> Thanks!
>>>
>>> David Ash
>>>
>>>
>>>
>>>
>>> On Wed, Apr 20, 2016 at 2:07 PM, Farasath Ahamed <me...@gmail.com>
>>> wrote:
>>>
>>>> When creating content I would like to give a hand. Let's get started :)
>>>>
>>>
>>>
>>
>>
>> --
>> *A.Farasath Ahamed*
>> Undergraduate | Department of Computer Science and
>> Engineering,University of Moratuwa
>> Article Writer | MoraSpirit
>> Mobile: +94 777 603 866
>> Blog: blog.farazath.com
>> E-Mail: mefarazath@gmail.com
>>
>
>
--
*A.Farasath Ahamed*
Undergraduate | Department of Computer Science and Engineering,University
of Moratuwa
Article Writer | MoraSpirit
Mobile: +94 777 603 866
Blog: blog.farazath.com
E-Mail: mefarazath@gmail.com
Re: Moving forward
Posted by David Ash <gr...@gmail.com>.
My bad, Farasath. Good catch. I've opened it to editing by anyone that
has a copy of the link.
On Thu, May 19, 2016 at 11:14 PM, Farasath Ahamed <me...@gmail.com>
wrote:
> Hi David,
>
> It looks like read-only to me. Can you change the permissions please? :)
> or share the doc with mefarazath@gmail.com so that I can add content
>
> Thanks.
>
> On Thu, May 19, 2016 at 11:14 PM, David Ash <gr...@gmail.com> wrote:
>
>> I've started a public Google doc that has the skeleton of the website. I
>> figure we can use it to create a rough draft of the content.
>>
>>
>> https://docs.google.com/document/d/1fs2h7e1v7oog7UkZC5x_v1Vyg8TQ1tLzPsJGVMPjzio/edit?usp=sharing
>>
>>
>> Everyone, please feel free to make any constructive additions / edits.
>>
>>
>>
>> Thanks!
>>
>> David Ash
>>
>>
>>
>>
>> On Wed, Apr 20, 2016 at 2:07 PM, Farasath Ahamed <me...@gmail.com>
>> wrote:
>>
>>> When creating content I would like to give a hand. Let's get started :)
>>>
>>
>>
>
>
> --
> *A.Farasath Ahamed*
> Undergraduate | Department of Computer Science and Engineering,University
> of Moratuwa
> Article Writer | MoraSpirit
> Mobile: +94 777 603 866
> Blog: blog.farazath.com
> E-Mail: mefarazath@gmail.com
>
Re: Moving forward
Posted by Farasath Ahamed <me...@gmail.com>.
Hi David,
It looks like read-only to me. Can you change the permissions please? :)
or share the doc with mefarazath@gmail.com so that I can add content
Thanks.
On Thu, May 19, 2016 at 11:14 PM, David Ash <gr...@gmail.com> wrote:
> I've started a public Google doc that has the skeleton of the website. I
> figure we can use it to create a rough draft of the content.
>
>
> https://docs.google.com/document/d/1fs2h7e1v7oog7UkZC5x_v1Vyg8TQ1tLzPsJGVMPjzio/edit?usp=sharing
>
>
> Everyone, please feel free to make any constructive additions / edits.
>
>
>
> Thanks!
>
> David Ash
>
>
>
>
> On Wed, Apr 20, 2016 at 2:07 PM, Farasath Ahamed <me...@gmail.com>
> wrote:
>
>> When creating content I would like to give a hand. Let's get started :)
>>
>
>
--
*A.Farasath Ahamed*
Undergraduate | Department of Computer Science and Engineering,University
of Moratuwa
Article Writer | MoraSpirit
Mobile: +94 777 603 866
Blog: blog.farazath.com
E-Mail: mefarazath@gmail.com
Re: Moving forward
Posted by David Ash <gr...@gmail.com>.
I've started a public Google doc that has the skeleton of the website. I
figure we can use it to create a rough draft of the content.
https://docs.google.com/document/d/1fs2h7e1v7oog7UkZC5x_v1Vyg8TQ1tLzPsJGVMPjzio/edit?usp=sharing
Everyone, please feel free to make any constructive additions / edits.
Thanks!
David Ash
On Wed, Apr 20, 2016 at 2:07 PM, Farasath Ahamed <me...@gmail.com>
wrote:
> When creating content I would like to give a hand. Let's get started :)
>
Re: Moving forward
Posted by Farasath Ahamed <me...@gmail.com>.
When creating content I would like to give a hand. Let's get started :)
Re: Moving forward
Posted by David Ash <gr...@gmail.com>.
Awesome THANKS!! :-D
On Wed, Apr 20, 2016 at 2:02 PM, Farasath Ahamed <me...@gmail.com>
wrote:
> I think this is the site git repo
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-openaz-site.git
> On Apr 21, 2016 1:24 AM, "David Ash" <gr...@gmail.com> wrote:
>
>> Cool, thanks for the info!
>>
>> On Wed, Apr 20, 2016 at 1:53 PM, Farasath Ahamed <me...@gmail.com>
>> wrote:
>>
>> > Anyome with write access to the git repo should be able to merge pull
>> > requests :)
>> >
>> > So any committer should be able to do that
>> > On Apr 21, 2016 12:33 AM, "David Ash" <gr...@gmail.com> wrote:
>> >
>> > > That's a good question. Does anyone know the answer to that? Can any
>> > > committer merge a pull request on github, or how does that happen?
>> We'd
>> > > like to make sure we can move quickly, so the more people capable of
>> > doing
>> > > it the better, particularly regarding the website.
>> > > On Apr 20, 2016 12:58 PM, "Sam Barrett" <sa...@gmail.com>
>> wrote:
>> > >
>> > > > Sounds good. We can start working on the website, and then commit it
>> > and
>> > > > submit a pull request once we have the address for the website
>> github
>> > > repo.
>> > > > But who merges the pull request on github? Will we be able to do
>> that
>> > > once
>> > > > we're committers?
>> > > >
>> > > > On Wed, Apr 20, 2016 at 12:50 PM, David Ash <gr...@gmail.com>
>> > > wrote:
>> > > >
>> > > > > I spoke with our new developers, and they just got subscribed to
>> the
>> > > > > mailing list, so I'm re-sending what I sent earlier. If you
>> already
>> > > saw
>> > > > > this, please ignore:
>> > > > >
>> > > > >
>> > > > > I think first priority is getting the new team promoted to
>> > committers,
>> > > > and
>> > > > > > probably set as initial-commiters so we can utilize the private
>> > email
>> > > > > list
>> > > > > > in the future. But that can be done by the PMC I think.
>> > > > > >
>> > > > > > First up for the devs is the website in my opinion, because that
>> > will
>> > > > > help
>> > > > > > us organize better. I think we should go with the Apache CMS
>> > > solution
>> > > > > > because that will get us up and running quickly, and free us up
>> to
>> > do
>> > > > > other
>> > > > > > tasks. If anyone disagrees about priority or direction, please
>> > chime
>> > > > in.
>> > > > > >
>> > > > > > Information for setting up a podling website is at:
>> > > > > > http://incubator.apache.org/guides/sites.html
>> > > > > >
>> > > > > > Regarding podling websites, this guide says:
>> > > > > >
>> > > > > > Regardless of which tool you use, the web site should be
>> maintained
>> > > in
>> > > > > the
>> > > > > >> svn repository, and include the site generation tool as a
>> binary
>> > > file.
>> > > > > This
>> > > > > >> simplifies the process of site generation and enables changes
>> to
>> > the
>> > > > > site
>> > > > > >> to be made by any committer. The generated site should also be
>> > > checked
>> > > > > into
>> > > > > >> svn. This allows the generated site to be relocated to any
>> part of
>> > > the
>> > > > > >> Apache site after incubation is complete.
>> > > > > >
>> > > > > > Since the site is independent of the code, it should exist high
>> in
>> > > the
>> > > > > svn
>> > > > > >> repository, e.g. parallel to the trunk of the source tree.
>> > > > > >
>> > > > > >
>> > > > > > Previously we were going to make a github repo for the website,
>> > > commit
>> > > > > > there, and then merge that into the apache repo. Has a github
>> repo
>> > > > been
>> > > > > > created yet? If so, what is the URL? If not, please respond
>> > quickly
>> > > > so
>> > > > > we
>> > > > > > can make one.
>> > > > > >
>> > > > > > Once we have committers, we can commit it - or an existing
>> > committer
>> > > > can
>> > > > > > commit it if they can do so quickly.
>> > > > > >
>> > > > > > Also, until we have a website, there's some important URLs for
>> the
>> > > > > project
>> > > > > > that I guess we should just post here for now. Here's what I
>> know,
>> > > > > please
>> > > > > > add anything I'm missing.
>> > > > > >
>> > > > > > *General*
>> > > > > > Incubator page:
>> http://incubator.apache.org/projects/openaz.html
>> > > > > > Website: http://openaz.incubator.apache.org/
>> > > > > > Project management:
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20OPENAZ%20ORDER%20BY%20status%20DESC
>> > > > > >
>> > > > > > *Source code*
>> > > > > > Official Repo:
>> > > > > > https://git-wip-us.apache.org/repos/asf?p=incubator-openaz.git
>> > > > > > Github Repo: https://github.com/apache/incubator-openaz
>> > > > > >
>> > > > > > *Website*
>> > > > > > Official Repo: (same as source code, branching at top level?)
>> > > > > > Github Repo: ???
>> > > > > >
>> > > > > > *Other ASF / Useful Links:*
>> > > > > > http://www.apache.org/dev/new-committers-guide.html
>> > > > > > http://incubator.apache.org/guides/sites.html
>> > > > > > http://www.apache.org/dev/cms.html
>> > > > > >
>> > > > >
>> > > > > *Mailing list subscription addresses:*
>> > > > >
>> > > > > Everyone should subscribe to the dev list and commits list by
>> sending
>> > > an
>> > > > > > email to the following:
>> > > > > >
>> > > > > > dev-subscribe at openaz.incubator.apache.org
>> > > > > > users-subscribe at openaz.incubator.apache.org
>> > > > > > commits-subscribe at openaz.incubator.apache.org
>> > > > > >
>> > > > > > The folks on the initial committers list should also subscribe
>> to
>> > the
>> > > > > > private list by sending an email to:
>> > > > > > private-subscribe at openaz.incubator.apache.org
>> > > > >
>> > > > >
>> > > > >
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > > Any other thoughts for moving forward? Let's keep the
>> conversation
>> > > > > > rolling!
>> > > > > >
>> > > > > > David
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
>
Re: Moving forward
Posted by Farasath Ahamed <me...@gmail.com>.
I think this is the site git repo
https://git-wip-us.apache.org/repos/asf?p=incubator-openaz-site.git
On Apr 21, 2016 1:24 AM, "David Ash" <gr...@gmail.com> wrote:
> Cool, thanks for the info!
>
> On Wed, Apr 20, 2016 at 1:53 PM, Farasath Ahamed <me...@gmail.com>
> wrote:
>
> > Anyome with write access to the git repo should be able to merge pull
> > requests :)
> >
> > So any committer should be able to do that
> > On Apr 21, 2016 12:33 AM, "David Ash" <gr...@gmail.com> wrote:
> >
> > > That's a good question. Does anyone know the answer to that? Can any
> > > committer merge a pull request on github, or how does that happen? We'd
> > > like to make sure we can move quickly, so the more people capable of
> > doing
> > > it the better, particularly regarding the website.
> > > On Apr 20, 2016 12:58 PM, "Sam Barrett" <sa...@gmail.com> wrote:
> > >
> > > > Sounds good. We can start working on the website, and then commit it
> > and
> > > > submit a pull request once we have the address for the website github
> > > repo.
> > > > But who merges the pull request on github? Will we be able to do that
> > > once
> > > > we're committers?
> > > >
> > > > On Wed, Apr 20, 2016 at 12:50 PM, David Ash <gr...@gmail.com>
> > > wrote:
> > > >
> > > > > I spoke with our new developers, and they just got subscribed to
> the
> > > > > mailing list, so I'm re-sending what I sent earlier. If you
> already
> > > saw
> > > > > this, please ignore:
> > > > >
> > > > >
> > > > > I think first priority is getting the new team promoted to
> > committers,
> > > > and
> > > > > > probably set as initial-commiters so we can utilize the private
> > email
> > > > > list
> > > > > > in the future. But that can be done by the PMC I think.
> > > > > >
> > > > > > First up for the devs is the website in my opinion, because that
> > will
> > > > > help
> > > > > > us organize better. I think we should go with the Apache CMS
> > > solution
> > > > > > because that will get us up and running quickly, and free us up
> to
> > do
> > > > > other
> > > > > > tasks. If anyone disagrees about priority or direction, please
> > chime
> > > > in.
> > > > > >
> > > > > > Information for setting up a podling website is at:
> > > > > > http://incubator.apache.org/guides/sites.html
> > > > > >
> > > > > > Regarding podling websites, this guide says:
> > > > > >
> > > > > > Regardless of which tool you use, the web site should be
> maintained
> > > in
> > > > > the
> > > > > >> svn repository, and include the site generation tool as a binary
> > > file.
> > > > > This
> > > > > >> simplifies the process of site generation and enables changes to
> > the
> > > > > site
> > > > > >> to be made by any committer. The generated site should also be
> > > checked
> > > > > into
> > > > > >> svn. This allows the generated site to be relocated to any part
> of
> > > the
> > > > > >> Apache site after incubation is complete.
> > > > > >
> > > > > > Since the site is independent of the code, it should exist high
> in
> > > the
> > > > > svn
> > > > > >> repository, e.g. parallel to the trunk of the source tree.
> > > > > >
> > > > > >
> > > > > > Previously we were going to make a github repo for the website,
> > > commit
> > > > > > there, and then merge that into the apache repo. Has a github
> repo
> > > > been
> > > > > > created yet? If so, what is the URL? If not, please respond
> > quickly
> > > > so
> > > > > we
> > > > > > can make one.
> > > > > >
> > > > > > Once we have committers, we can commit it - or an existing
> > committer
> > > > can
> > > > > > commit it if they can do so quickly.
> > > > > >
> > > > > > Also, until we have a website, there's some important URLs for
> the
> > > > > project
> > > > > > that I guess we should just post here for now. Here's what I
> know,
> > > > > please
> > > > > > add anything I'm missing.
> > > > > >
> > > > > > *General*
> > > > > > Incubator page: http://incubator.apache.org/projects/openaz.html
> > > > > > Website: http://openaz.incubator.apache.org/
> > > > > > Project management:
> > > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20OPENAZ%20ORDER%20BY%20status%20DESC
> > > > > >
> > > > > > *Source code*
> > > > > > Official Repo:
> > > > > > https://git-wip-us.apache.org/repos/asf?p=incubator-openaz.git
> > > > > > Github Repo: https://github.com/apache/incubator-openaz
> > > > > >
> > > > > > *Website*
> > > > > > Official Repo: (same as source code, branching at top level?)
> > > > > > Github Repo: ???
> > > > > >
> > > > > > *Other ASF / Useful Links:*
> > > > > > http://www.apache.org/dev/new-committers-guide.html
> > > > > > http://incubator.apache.org/guides/sites.html
> > > > > > http://www.apache.org/dev/cms.html
> > > > > >
> > > > >
> > > > > *Mailing list subscription addresses:*
> > > > >
> > > > > Everyone should subscribe to the dev list and commits list by
> sending
> > > an
> > > > > > email to the following:
> > > > > >
> > > > > > dev-subscribe at openaz.incubator.apache.org
> > > > > > users-subscribe at openaz.incubator.apache.org
> > > > > > commits-subscribe at openaz.incubator.apache.org
> > > > > >
> > > > > > The folks on the initial committers list should also subscribe to
> > the
> > > > > > private list by sending an email to:
> > > > > > private-subscribe at openaz.incubator.apache.org
> > > > >
> > > > >
> > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > Any other thoughts for moving forward? Let's keep the
> conversation
> > > > > > rolling!
> > > > > >
> > > > > > David
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Moving forward
Posted by David Ash <gr...@gmail.com>.
Cool, thanks for the info!
On Wed, Apr 20, 2016 at 1:53 PM, Farasath Ahamed <me...@gmail.com>
wrote:
> Anyome with write access to the git repo should be able to merge pull
> requests :)
>
> So any committer should be able to do that
> On Apr 21, 2016 12:33 AM, "David Ash" <gr...@gmail.com> wrote:
>
> > That's a good question. Does anyone know the answer to that? Can any
> > committer merge a pull request on github, or how does that happen? We'd
> > like to make sure we can move quickly, so the more people capable of
> doing
> > it the better, particularly regarding the website.
> > On Apr 20, 2016 12:58 PM, "Sam Barrett" <sa...@gmail.com> wrote:
> >
> > > Sounds good. We can start working on the website, and then commit it
> and
> > > submit a pull request once we have the address for the website github
> > repo.
> > > But who merges the pull request on github? Will we be able to do that
> > once
> > > we're committers?
> > >
> > > On Wed, Apr 20, 2016 at 12:50 PM, David Ash <gr...@gmail.com>
> > wrote:
> > >
> > > > I spoke with our new developers, and they just got subscribed to the
> > > > mailing list, so I'm re-sending what I sent earlier. If you already
> > saw
> > > > this, please ignore:
> > > >
> > > >
> > > > I think first priority is getting the new team promoted to
> committers,
> > > and
> > > > > probably set as initial-commiters so we can utilize the private
> email
> > > > list
> > > > > in the future. But that can be done by the PMC I think.
> > > > >
> > > > > First up for the devs is the website in my opinion, because that
> will
> > > > help
> > > > > us organize better. I think we should go with the Apache CMS
> > solution
> > > > > because that will get us up and running quickly, and free us up to
> do
> > > > other
> > > > > tasks. If anyone disagrees about priority or direction, please
> chime
> > > in.
> > > > >
> > > > > Information for setting up a podling website is at:
> > > > > http://incubator.apache.org/guides/sites.html
> > > > >
> > > > > Regarding podling websites, this guide says:
> > > > >
> > > > > Regardless of which tool you use, the web site should be maintained
> > in
> > > > the
> > > > >> svn repository, and include the site generation tool as a binary
> > file.
> > > > This
> > > > >> simplifies the process of site generation and enables changes to
> the
> > > > site
> > > > >> to be made by any committer. The generated site should also be
> > checked
> > > > into
> > > > >> svn. This allows the generated site to be relocated to any part of
> > the
> > > > >> Apache site after incubation is complete.
> > > > >
> > > > > Since the site is independent of the code, it should exist high in
> > the
> > > > svn
> > > > >> repository, e.g. parallel to the trunk of the source tree.
> > > > >
> > > > >
> > > > > Previously we were going to make a github repo for the website,
> > commit
> > > > > there, and then merge that into the apache repo. Has a github repo
> > > been
> > > > > created yet? If so, what is the URL? If not, please respond
> quickly
> > > so
> > > > we
> > > > > can make one.
> > > > >
> > > > > Once we have committers, we can commit it - or an existing
> committer
> > > can
> > > > > commit it if they can do so quickly.
> > > > >
> > > > > Also, until we have a website, there's some important URLs for the
> > > > project
> > > > > that I guess we should just post here for now. Here's what I know,
> > > > please
> > > > > add anything I'm missing.
> > > > >
> > > > > *General*
> > > > > Incubator page: http://incubator.apache.org/projects/openaz.html
> > > > > Website: http://openaz.incubator.apache.org/
> > > > > Project management:
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20OPENAZ%20ORDER%20BY%20status%20DESC
> > > > >
> > > > > *Source code*
> > > > > Official Repo:
> > > > > https://git-wip-us.apache.org/repos/asf?p=incubator-openaz.git
> > > > > Github Repo: https://github.com/apache/incubator-openaz
> > > > >
> > > > > *Website*
> > > > > Official Repo: (same as source code, branching at top level?)
> > > > > Github Repo: ???
> > > > >
> > > > > *Other ASF / Useful Links:*
> > > > > http://www.apache.org/dev/new-committers-guide.html
> > > > > http://incubator.apache.org/guides/sites.html
> > > > > http://www.apache.org/dev/cms.html
> > > > >
> > > >
> > > > *Mailing list subscription addresses:*
> > > >
> > > > Everyone should subscribe to the dev list and commits list by sending
> > an
> > > > > email to the following:
> > > > >
> > > > > dev-subscribe at openaz.incubator.apache.org
> > > > > users-subscribe at openaz.incubator.apache.org
> > > > > commits-subscribe at openaz.incubator.apache.org
> > > > >
> > > > > The folks on the initial committers list should also subscribe to
> the
> > > > > private list by sending an email to:
> > > > > private-subscribe at openaz.incubator.apache.org
> > > >
> > > >
> > > >
> > > > >
> > > > >
> > > > >
> > > > > Any other thoughts for moving forward? Let's keep the conversation
> > > > > rolling!
> > > > >
> > > > > David
> > > > >
> > > >
> > >
> >
>
Re: Moving forward
Posted by Farasath Ahamed <me...@gmail.com>.
Anyome with write access to the git repo should be able to merge pull
requests :)
So any committer should be able to do that
On Apr 21, 2016 12:33 AM, "David Ash" <gr...@gmail.com> wrote:
> That's a good question. Does anyone know the answer to that? Can any
> committer merge a pull request on github, or how does that happen? We'd
> like to make sure we can move quickly, so the more people capable of doing
> it the better, particularly regarding the website.
> On Apr 20, 2016 12:58 PM, "Sam Barrett" <sa...@gmail.com> wrote:
>
> > Sounds good. We can start working on the website, and then commit it and
> > submit a pull request once we have the address for the website github
> repo.
> > But who merges the pull request on github? Will we be able to do that
> once
> > we're committers?
> >
> > On Wed, Apr 20, 2016 at 12:50 PM, David Ash <gr...@gmail.com>
> wrote:
> >
> > > I spoke with our new developers, and they just got subscribed to the
> > > mailing list, so I'm re-sending what I sent earlier. If you already
> saw
> > > this, please ignore:
> > >
> > >
> > > I think first priority is getting the new team promoted to committers,
> > and
> > > > probably set as initial-commiters so we can utilize the private email
> > > list
> > > > in the future. But that can be done by the PMC I think.
> > > >
> > > > First up for the devs is the website in my opinion, because that will
> > > help
> > > > us organize better. I think we should go with the Apache CMS
> solution
> > > > because that will get us up and running quickly, and free us up to do
> > > other
> > > > tasks. If anyone disagrees about priority or direction, please chime
> > in.
> > > >
> > > > Information for setting up a podling website is at:
> > > > http://incubator.apache.org/guides/sites.html
> > > >
> > > > Regarding podling websites, this guide says:
> > > >
> > > > Regardless of which tool you use, the web site should be maintained
> in
> > > the
> > > >> svn repository, and include the site generation tool as a binary
> file.
> > > This
> > > >> simplifies the process of site generation and enables changes to the
> > > site
> > > >> to be made by any committer. The generated site should also be
> checked
> > > into
> > > >> svn. This allows the generated site to be relocated to any part of
> the
> > > >> Apache site after incubation is complete.
> > > >
> > > > Since the site is independent of the code, it should exist high in
> the
> > > svn
> > > >> repository, e.g. parallel to the trunk of the source tree.
> > > >
> > > >
> > > > Previously we were going to make a github repo for the website,
> commit
> > > > there, and then merge that into the apache repo. Has a github repo
> > been
> > > > created yet? If so, what is the URL? If not, please respond quickly
> > so
> > > we
> > > > can make one.
> > > >
> > > > Once we have committers, we can commit it - or an existing committer
> > can
> > > > commit it if they can do so quickly.
> > > >
> > > > Also, until we have a website, there's some important URLs for the
> > > project
> > > > that I guess we should just post here for now. Here's what I know,
> > > please
> > > > add anything I'm missing.
> > > >
> > > > *General*
> > > > Incubator page: http://incubator.apache.org/projects/openaz.html
> > > > Website: http://openaz.incubator.apache.org/
> > > > Project management:
> > > >
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20OPENAZ%20ORDER%20BY%20status%20DESC
> > > >
> > > > *Source code*
> > > > Official Repo:
> > > > https://git-wip-us.apache.org/repos/asf?p=incubator-openaz.git
> > > > Github Repo: https://github.com/apache/incubator-openaz
> > > >
> > > > *Website*
> > > > Official Repo: (same as source code, branching at top level?)
> > > > Github Repo: ???
> > > >
> > > > *Other ASF / Useful Links:*
> > > > http://www.apache.org/dev/new-committers-guide.html
> > > > http://incubator.apache.org/guides/sites.html
> > > > http://www.apache.org/dev/cms.html
> > > >
> > >
> > > *Mailing list subscription addresses:*
> > >
> > > Everyone should subscribe to the dev list and commits list by sending
> an
> > > > email to the following:
> > > >
> > > > dev-subscribe at openaz.incubator.apache.org
> > > > users-subscribe at openaz.incubator.apache.org
> > > > commits-subscribe at openaz.incubator.apache.org
> > > >
> > > > The folks on the initial committers list should also subscribe to the
> > > > private list by sending an email to:
> > > > private-subscribe at openaz.incubator.apache.org
> > >
> > >
> > >
> > > >
> > > >
> > > >
> > > > Any other thoughts for moving forward? Let's keep the conversation
> > > > rolling!
> > > >
> > > > David
> > > >
> > >
> >
>
Re: Moving forward
Posted by David Ash <gr...@gmail.com>.
That's a good question. Does anyone know the answer to that? Can any
committer merge a pull request on github, or how does that happen? We'd
like to make sure we can move quickly, so the more people capable of doing
it the better, particularly regarding the website.
On Apr 20, 2016 12:58 PM, "Sam Barrett" <sa...@gmail.com> wrote:
> Sounds good. We can start working on the website, and then commit it and
> submit a pull request once we have the address for the website github repo.
> But who merges the pull request on github? Will we be able to do that once
> we're committers?
>
> On Wed, Apr 20, 2016 at 12:50 PM, David Ash <gr...@gmail.com> wrote:
>
> > I spoke with our new developers, and they just got subscribed to the
> > mailing list, so I'm re-sending what I sent earlier. If you already saw
> > this, please ignore:
> >
> >
> > I think first priority is getting the new team promoted to committers,
> and
> > > probably set as initial-commiters so we can utilize the private email
> > list
> > > in the future. But that can be done by the PMC I think.
> > >
> > > First up for the devs is the website in my opinion, because that will
> > help
> > > us organize better. I think we should go with the Apache CMS solution
> > > because that will get us up and running quickly, and free us up to do
> > other
> > > tasks. If anyone disagrees about priority or direction, please chime
> in.
> > >
> > > Information for setting up a podling website is at:
> > > http://incubator.apache.org/guides/sites.html
> > >
> > > Regarding podling websites, this guide says:
> > >
> > > Regardless of which tool you use, the web site should be maintained in
> > the
> > >> svn repository, and include the site generation tool as a binary file.
> > This
> > >> simplifies the process of site generation and enables changes to the
> > site
> > >> to be made by any committer. The generated site should also be checked
> > into
> > >> svn. This allows the generated site to be relocated to any part of the
> > >> Apache site after incubation is complete.
> > >
> > > Since the site is independent of the code, it should exist high in the
> > svn
> > >> repository, e.g. parallel to the trunk of the source tree.
> > >
> > >
> > > Previously we were going to make a github repo for the website, commit
> > > there, and then merge that into the apache repo. Has a github repo
> been
> > > created yet? If so, what is the URL? If not, please respond quickly
> so
> > we
> > > can make one.
> > >
> > > Once we have committers, we can commit it - or an existing committer
> can
> > > commit it if they can do so quickly.
> > >
> > > Also, until we have a website, there's some important URLs for the
> > project
> > > that I guess we should just post here for now. Here's what I know,
> > please
> > > add anything I'm missing.
> > >
> > > *General*
> > > Incubator page: http://incubator.apache.org/projects/openaz.html
> > > Website: http://openaz.incubator.apache.org/
> > > Project management:
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20OPENAZ%20ORDER%20BY%20status%20DESC
> > >
> > > *Source code*
> > > Official Repo:
> > > https://git-wip-us.apache.org/repos/asf?p=incubator-openaz.git
> > > Github Repo: https://github.com/apache/incubator-openaz
> > >
> > > *Website*
> > > Official Repo: (same as source code, branching at top level?)
> > > Github Repo: ???
> > >
> > > *Other ASF / Useful Links:*
> > > http://www.apache.org/dev/new-committers-guide.html
> > > http://incubator.apache.org/guides/sites.html
> > > http://www.apache.org/dev/cms.html
> > >
> >
> > *Mailing list subscription addresses:*
> >
> > Everyone should subscribe to the dev list and commits list by sending an
> > > email to the following:
> > >
> > > dev-subscribe at openaz.incubator.apache.org
> > > users-subscribe at openaz.incubator.apache.org
> > > commits-subscribe at openaz.incubator.apache.org
> > >
> > > The folks on the initial committers list should also subscribe to the
> > > private list by sending an email to:
> > > private-subscribe at openaz.incubator.apache.org
> >
> >
> >
> > >
> > >
> > >
> > > Any other thoughts for moving forward? Let's keep the conversation
> > > rolling!
> > >
> > > David
> > >
> >
>
Re: Moving forward
Posted by Sam Barrett <sa...@gmail.com>.
Sounds good. We can start working on the website, and then commit it and
submit a pull request once we have the address for the website github repo.
But who merges the pull request on github? Will we be able to do that once
we're committers?
On Wed, Apr 20, 2016 at 12:50 PM, David Ash <gr...@gmail.com> wrote:
> I spoke with our new developers, and they just got subscribed to the
> mailing list, so I'm re-sending what I sent earlier. If you already saw
> this, please ignore:
>
>
> I think first priority is getting the new team promoted to committers, and
> > probably set as initial-commiters so we can utilize the private email
> list
> > in the future. But that can be done by the PMC I think.
> >
> > First up for the devs is the website in my opinion, because that will
> help
> > us organize better. I think we should go with the Apache CMS solution
> > because that will get us up and running quickly, and free us up to do
> other
> > tasks. If anyone disagrees about priority or direction, please chime in.
> >
> > Information for setting up a podling website is at:
> > http://incubator.apache.org/guides/sites.html
> >
> > Regarding podling websites, this guide says:
> >
> > Regardless of which tool you use, the web site should be maintained in
> the
> >> svn repository, and include the site generation tool as a binary file.
> This
> >> simplifies the process of site generation and enables changes to the
> site
> >> to be made by any committer. The generated site should also be checked
> into
> >> svn. This allows the generated site to be relocated to any part of the
> >> Apache site after incubation is complete.
> >
> > Since the site is independent of the code, it should exist high in the
> svn
> >> repository, e.g. parallel to the trunk of the source tree.
> >
> >
> > Previously we were going to make a github repo for the website, commit
> > there, and then merge that into the apache repo. Has a github repo been
> > created yet? If so, what is the URL? If not, please respond quickly so
> we
> > can make one.
> >
> > Once we have committers, we can commit it - or an existing committer can
> > commit it if they can do so quickly.
> >
> > Also, until we have a website, there's some important URLs for the
> project
> > that I guess we should just post here for now. Here's what I know,
> please
> > add anything I'm missing.
> >
> > *General*
> > Incubator page: http://incubator.apache.org/projects/openaz.html
> > Website: http://openaz.incubator.apache.org/
> > Project management:
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20OPENAZ%20ORDER%20BY%20status%20DESC
> >
> > *Source code*
> > Official Repo:
> > https://git-wip-us.apache.org/repos/asf?p=incubator-openaz.git
> > Github Repo: https://github.com/apache/incubator-openaz
> >
> > *Website*
> > Official Repo: (same as source code, branching at top level?)
> > Github Repo: ???
> >
> > *Other ASF / Useful Links:*
> > http://www.apache.org/dev/new-committers-guide.html
> > http://incubator.apache.org/guides/sites.html
> > http://www.apache.org/dev/cms.html
> >
>
> *Mailing list subscription addresses:*
>
> Everyone should subscribe to the dev list and commits list by sending an
> > email to the following:
> >
> > dev-subscribe at openaz.incubator.apache.org
> > users-subscribe at openaz.incubator.apache.org
> > commits-subscribe at openaz.incubator.apache.org
> >
> > The folks on the initial committers list should also subscribe to the
> > private list by sending an email to:
> > private-subscribe at openaz.incubator.apache.org
>
>
>
> >
> >
> >
> > Any other thoughts for moving forward? Let's keep the conversation
> > rolling!
> >
> > David
> >
>
Re: Moving forward
Posted by David Ash <gr...@gmail.com>.
I spoke with our new developers, and they just got subscribed to the
mailing list, so I'm re-sending what I sent earlier. If you already saw
this, please ignore:
I think first priority is getting the new team promoted to committers, and
> probably set as initial-commiters so we can utilize the private email list
> in the future. But that can be done by the PMC I think.
>
> First up for the devs is the website in my opinion, because that will help
> us organize better. I think we should go with the Apache CMS solution
> because that will get us up and running quickly, and free us up to do other
> tasks. If anyone disagrees about priority or direction, please chime in.
>
> Information for setting up a podling website is at:
> http://incubator.apache.org/guides/sites.html
>
> Regarding podling websites, this guide says:
>
> Regardless of which tool you use, the web site should be maintained in the
>> svn repository, and include the site generation tool as a binary file. This
>> simplifies the process of site generation and enables changes to the site
>> to be made by any committer. The generated site should also be checked into
>> svn. This allows the generated site to be relocated to any part of the
>> Apache site after incubation is complete.
>
> Since the site is independent of the code, it should exist high in the svn
>> repository, e.g. parallel to the trunk of the source tree.
>
>
> Previously we were going to make a github repo for the website, commit
> there, and then merge that into the apache repo. Has a github repo been
> created yet? If so, what is the URL? If not, please respond quickly so we
> can make one.
>
> Once we have committers, we can commit it - or an existing committer can
> commit it if they can do so quickly.
>
> Also, until we have a website, there's some important URLs for the project
> that I guess we should just post here for now. Here's what I know, please
> add anything I'm missing.
>
> *General*
> Incubator page: http://incubator.apache.org/projects/openaz.html
> Website: http://openaz.incubator.apache.org/
> Project management:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20OPENAZ%20ORDER%20BY%20status%20DESC
>
> *Source code*
> Official Repo:
> https://git-wip-us.apache.org/repos/asf?p=incubator-openaz.git
> Github Repo: https://github.com/apache/incubator-openaz
>
> *Website*
> Official Repo: (same as source code, branching at top level?)
> Github Repo: ???
>
> *Other ASF / Useful Links:*
> http://www.apache.org/dev/new-committers-guide.html
> http://incubator.apache.org/guides/sites.html
> http://www.apache.org/dev/cms.html
>
*Mailing list subscription addresses:*
Everyone should subscribe to the dev list and commits list by sending an
> email to the following:
>
> dev-subscribe at openaz.incubator.apache.org
> users-subscribe at openaz.incubator.apache.org
> commits-subscribe at openaz.incubator.apache.org
>
> The folks on the initial committers list should also subscribe to the
> private list by sending an email to:
> private-subscribe at openaz.incubator.apache.org
>
>
>
> Any other thoughts for moving forward? Let's keep the conversation
> rolling!
>
> David
>