You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@community.apache.org by Rich Bowen <rb...@rcbowen.com> on 2019/05/20 18:43:36 UTC
ComDev website, pelican
Long, long ago I opened this:
https://issues.apache.org/jira/browse/INFRA-15387
It has recently been woken up again.
I'm looking for someone to take the reins on this, since I do not really
have time to do it any time before September.
Any volunteers?
--
Rich Bowen - rbowen@rcbowen.com
http://rcbowen.com/
@rbowen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: ComDev website, pelican
Posted by sebb <se...@gmail.com>.
On Wed, 5 Jun 2019 at 16:32, Andrew Musselman
<an...@gmail.com> wrote:
>
> Oh my bad, I thought this project's name was "community."
The name in committee-info.txt is "Community Development"
The mailing lists are @community.apache.org
The website is http://community.apache.org
However the LDAP project name is comdev, and the SVN resources use
/comdev and /pmc/comdev
I don't know why there is this discrepancy.
> We're set with "comdev-site.git" unless there are any other suggestions.
>
> On Wed, Jun 5, 2019 at 8:28 AM Andrew Musselman <an...@gmail.com>
> wrote:
>
> > That's not clear to me; that self-serve page's instructions say "Here you
> > can request a new git repository. To request the main repository,
> > $project.git, simply leave the 'Repository Name' field blank. The PMC
> > selection will fill in the $project field."
> >
> > If a PMC member for the "community" project selects the PMC "community",
> > and puts "site" in the Repository Name field, "community-site.git" should
> > be generated. Sebb, would you mind trying that, to see if we need INFRA
> > help?
> >
> > On Wed, Jun 5, 2019 at 5:40 AM sebb <se...@gmail.com> wrote:
> >
> >> On Tue, 4 Jun 2019 at 18:25, Andrew Musselman
> >> <an...@gmail.com> wrote:
> >> >
> >> > Need a PMC member to set them up:
> >> > https://gitbox.apache.org/setup/newrepo.html
> >>
> >> Unfortunately its not possible with the current self-serve app; repos
> >> are forced to have comdev as a prefix.
> >>
> >> INFRA will have to set up the repos.
> >>
> >> I wonder whether it would be better to wait before creating a code repo.
> >> It might make more sense to have one repo per code area, e.g.
> >> community-app1, community-app2 etc.
> >> That would require knowing what code will be created.
> >>
> >> > For context, here's the JIRA:
> >> > https://issues.apache.org/jira/browse/INFRA-15387
> >> >
> >> > On Tue, Jun 4, 2019 at 10:15 AM Andrew Musselman <
> >> andrew.musselman@gmail.com>
> >> > wrote:
> >> >
> >> > > Sounds good to me; I'll get those two repos set up; will have push
> >> rights
> >> > > granted to all community committers.
> >> > >
> >> > > Thanks for the feedback!
> >> > >
> >> > > On Tue, Jun 4, 2019 at 3:55 AM Shane Curcuru <as...@shanecurcuru.org>
> >> wrote:
> >> > >
> >> > >> Bertrand Delacretaz wrote on 2019-6-4 5:02AM EDT:
> >> > >> > On Tue, Jun 4, 2019 at 9:53 AM sebb <se...@gmail.com> wrote:
> >> > >> >> "While there is not an official standard per-se, most projects use
> >> > >> >> $project-site.git to host their site generation code...
> >> > >> >
> >> > >> > +1
> >> > >> >
> >> > >> > considering that we have https://svn.apache.org/repos/asf/comdev/
> >> for
> >> > >> > existing code I think the (Git) website repository should be named
> >> > >> > comdev-site or community-site.
> >> > >>
> >> > >> +1 for community-site. "comdev" is merely an abbreviation we made up
> >> > >> for the formal "Community Development" project, which has no meaning
> >> > >> outside this group. "Community" on the other hand, is what we do -
> >> and
> >> > >> it's the domain name of our website.
> >> > >>
> >> > >> +1 for community-site.git (website) and community.git (all the
> >> various
> >> > >> code bits) is my suggestion.
> >> > >>
> >> > >> Thanks for working on this!
> >> > >>
> >> > >> --
> >> > >>
> >> > >> - Shane
> >> > >> Community Development Project Management Committee Member 8-)
> >> > >> The Apache Software Foundation
> >> > >>
> >> > >> ---------------------------------------------------------------------
> >> > >> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> >> > >> For additional commands, e-mail: dev-help@community.apache.org
> >> > >>
> >> > >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> >> For additional commands, e-mail: dev-help@community.apache.org
> >>
> >>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: ComDev website, pelican
Posted by Andrew Musselman <an...@gmail.com>.
Oh my bad, I thought this project's name was "community."
We're set with "comdev-site.git" unless there are any other suggestions.
On Wed, Jun 5, 2019 at 8:28 AM Andrew Musselman <an...@gmail.com>
wrote:
> That's not clear to me; that self-serve page's instructions say "Here you
> can request a new git repository. To request the main repository,
> $project.git, simply leave the 'Repository Name' field blank. The PMC
> selection will fill in the $project field."
>
> If a PMC member for the "community" project selects the PMC "community",
> and puts "site" in the Repository Name field, "community-site.git" should
> be generated. Sebb, would you mind trying that, to see if we need INFRA
> help?
>
> On Wed, Jun 5, 2019 at 5:40 AM sebb <se...@gmail.com> wrote:
>
>> On Tue, 4 Jun 2019 at 18:25, Andrew Musselman
>> <an...@gmail.com> wrote:
>> >
>> > Need a PMC member to set them up:
>> > https://gitbox.apache.org/setup/newrepo.html
>>
>> Unfortunately its not possible with the current self-serve app; repos
>> are forced to have comdev as a prefix.
>>
>> INFRA will have to set up the repos.
>>
>> I wonder whether it would be better to wait before creating a code repo.
>> It might make more sense to have one repo per code area, e.g.
>> community-app1, community-app2 etc.
>> That would require knowing what code will be created.
>>
>> > For context, here's the JIRA:
>> > https://issues.apache.org/jira/browse/INFRA-15387
>> >
>> > On Tue, Jun 4, 2019 at 10:15 AM Andrew Musselman <
>> andrew.musselman@gmail.com>
>> > wrote:
>> >
>> > > Sounds good to me; I'll get those two repos set up; will have push
>> rights
>> > > granted to all community committers.
>> > >
>> > > Thanks for the feedback!
>> > >
>> > > On Tue, Jun 4, 2019 at 3:55 AM Shane Curcuru <as...@shanecurcuru.org>
>> wrote:
>> > >
>> > >> Bertrand Delacretaz wrote on 2019-6-4 5:02AM EDT:
>> > >> > On Tue, Jun 4, 2019 at 9:53 AM sebb <se...@gmail.com> wrote:
>> > >> >> "While there is not an official standard per-se, most projects use
>> > >> >> $project-site.git to host their site generation code...
>> > >> >
>> > >> > +1
>> > >> >
>> > >> > considering that we have https://svn.apache.org/repos/asf/comdev/
>> for
>> > >> > existing code I think the (Git) website repository should be named
>> > >> > comdev-site or community-site.
>> > >>
>> > >> +1 for community-site. "comdev" is merely an abbreviation we made up
>> > >> for the formal "Community Development" project, which has no meaning
>> > >> outside this group. "Community" on the other hand, is what we do -
>> and
>> > >> it's the domain name of our website.
>> > >>
>> > >> +1 for community-site.git (website) and community.git (all the
>> various
>> > >> code bits) is my suggestion.
>> > >>
>> > >> Thanks for working on this!
>> > >>
>> > >> --
>> > >>
>> > >> - Shane
>> > >> Community Development Project Management Committee Member 8-)
>> > >> The Apache Software Foundation
>> > >>
>> > >> ---------------------------------------------------------------------
>> > >> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>> > >> For additional commands, e-mail: dev-help@community.apache.org
>> > >>
>> > >>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>> For additional commands, e-mail: dev-help@community.apache.org
>>
>>
Re: ComDev website, pelican
Posted by Andrew Musselman <an...@gmail.com>.
That's not clear to me; that self-serve page's instructions say "Here you
can request a new git repository. To request the main repository,
$project.git, simply leave the 'Repository Name' field blank. The PMC
selection will fill in the $project field."
If a PMC member for the "community" project selects the PMC "community",
and puts "site" in the Repository Name field, "community-site.git" should
be generated. Sebb, would you mind trying that, to see if we need INFRA
help?
On Wed, Jun 5, 2019 at 5:40 AM sebb <se...@gmail.com> wrote:
> On Tue, 4 Jun 2019 at 18:25, Andrew Musselman
> <an...@gmail.com> wrote:
> >
> > Need a PMC member to set them up:
> > https://gitbox.apache.org/setup/newrepo.html
>
> Unfortunately its not possible with the current self-serve app; repos
> are forced to have comdev as a prefix.
>
> INFRA will have to set up the repos.
>
> I wonder whether it would be better to wait before creating a code repo.
> It might make more sense to have one repo per code area, e.g.
> community-app1, community-app2 etc.
> That would require knowing what code will be created.
>
> > For context, here's the JIRA:
> > https://issues.apache.org/jira/browse/INFRA-15387
> >
> > On Tue, Jun 4, 2019 at 10:15 AM Andrew Musselman <
> andrew.musselman@gmail.com>
> > wrote:
> >
> > > Sounds good to me; I'll get those two repos set up; will have push
> rights
> > > granted to all community committers.
> > >
> > > Thanks for the feedback!
> > >
> > > On Tue, Jun 4, 2019 at 3:55 AM Shane Curcuru <as...@shanecurcuru.org>
> wrote:
> > >
> > >> Bertrand Delacretaz wrote on 2019-6-4 5:02AM EDT:
> > >> > On Tue, Jun 4, 2019 at 9:53 AM sebb <se...@gmail.com> wrote:
> > >> >> "While there is not an official standard per-se, most projects use
> > >> >> $project-site.git to host their site generation code...
> > >> >
> > >> > +1
> > >> >
> > >> > considering that we have https://svn.apache.org/repos/asf/comdev/
> for
> > >> > existing code I think the (Git) website repository should be named
> > >> > comdev-site or community-site.
> > >>
> > >> +1 for community-site. "comdev" is merely an abbreviation we made up
> > >> for the formal "Community Development" project, which has no meaning
> > >> outside this group. "Community" on the other hand, is what we do -
> and
> > >> it's the domain name of our website.
> > >>
> > >> +1 for community-site.git (website) and community.git (all the various
> > >> code bits) is my suggestion.
> > >>
> > >> Thanks for working on this!
> > >>
> > >> --
> > >>
> > >> - Shane
> > >> Community Development Project Management Committee Member 8-)
> > >> The Apache Software Foundation
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > >> For additional commands, e-mail: dev-help@community.apache.org
> > >>
> > >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
>
Re: ComDev website, pelican
Posted by sebb <se...@gmail.com>.
On Tue, 4 Jun 2019 at 18:25, Andrew Musselman
<an...@gmail.com> wrote:
>
> Need a PMC member to set them up:
> https://gitbox.apache.org/setup/newrepo.html
Unfortunately its not possible with the current self-serve app; repos
are forced to have comdev as a prefix.
INFRA will have to set up the repos.
I wonder whether it would be better to wait before creating a code repo.
It might make more sense to have one repo per code area, e.g.
community-app1, community-app2 etc.
That would require knowing what code will be created.
> For context, here's the JIRA:
> https://issues.apache.org/jira/browse/INFRA-15387
>
> On Tue, Jun 4, 2019 at 10:15 AM Andrew Musselman <an...@gmail.com>
> wrote:
>
> > Sounds good to me; I'll get those two repos set up; will have push rights
> > granted to all community committers.
> >
> > Thanks for the feedback!
> >
> > On Tue, Jun 4, 2019 at 3:55 AM Shane Curcuru <as...@shanecurcuru.org> wrote:
> >
> >> Bertrand Delacretaz wrote on 2019-6-4 5:02AM EDT:
> >> > On Tue, Jun 4, 2019 at 9:53 AM sebb <se...@gmail.com> wrote:
> >> >> "While there is not an official standard per-se, most projects use
> >> >> $project-site.git to host their site generation code...
> >> >
> >> > +1
> >> >
> >> > considering that we have https://svn.apache.org/repos/asf/comdev/ for
> >> > existing code I think the (Git) website repository should be named
> >> > comdev-site or community-site.
> >>
> >> +1 for community-site. "comdev" is merely an abbreviation we made up
> >> for the formal "Community Development" project, which has no meaning
> >> outside this group. "Community" on the other hand, is what we do - and
> >> it's the domain name of our website.
> >>
> >> +1 for community-site.git (website) and community.git (all the various
> >> code bits) is my suggestion.
> >>
> >> Thanks for working on this!
> >>
> >> --
> >>
> >> - Shane
> >> Community Development Project Management Committee Member 8-)
> >> The Apache Software Foundation
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> >> For additional commands, e-mail: dev-help@community.apache.org
> >>
> >>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: ComDev website, pelican
Posted by Andrew Musselman <an...@gmail.com>.
Need a PMC member to set them up:
https://gitbox.apache.org/setup/newrepo.html
For context, here's the JIRA:
https://issues.apache.org/jira/browse/INFRA-15387
On Tue, Jun 4, 2019 at 10:15 AM Andrew Musselman <an...@gmail.com>
wrote:
> Sounds good to me; I'll get those two repos set up; will have push rights
> granted to all community committers.
>
> Thanks for the feedback!
>
> On Tue, Jun 4, 2019 at 3:55 AM Shane Curcuru <as...@shanecurcuru.org> wrote:
>
>> Bertrand Delacretaz wrote on 2019-6-4 5:02AM EDT:
>> > On Tue, Jun 4, 2019 at 9:53 AM sebb <se...@gmail.com> wrote:
>> >> "While there is not an official standard per-se, most projects use
>> >> $project-site.git to host their site generation code...
>> >
>> > +1
>> >
>> > considering that we have https://svn.apache.org/repos/asf/comdev/ for
>> > existing code I think the (Git) website repository should be named
>> > comdev-site or community-site.
>>
>> +1 for community-site. "comdev" is merely an abbreviation we made up
>> for the formal "Community Development" project, which has no meaning
>> outside this group. "Community" on the other hand, is what we do - and
>> it's the domain name of our website.
>>
>> +1 for community-site.git (website) and community.git (all the various
>> code bits) is my suggestion.
>>
>> Thanks for working on this!
>>
>> --
>>
>> - Shane
>> Community Development Project Management Committee Member 8-)
>> The Apache Software Foundation
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>> For additional commands, e-mail: dev-help@community.apache.org
>>
>>
Re: ComDev website, pelican
Posted by Andrew Musselman <an...@gmail.com>.
Sounds good to me; I'll get those two repos set up; will have push rights
granted to all community committers.
Thanks for the feedback!
On Tue, Jun 4, 2019 at 3:55 AM Shane Curcuru <as...@shanecurcuru.org> wrote:
> Bertrand Delacretaz wrote on 2019-6-4 5:02AM EDT:
> > On Tue, Jun 4, 2019 at 9:53 AM sebb <se...@gmail.com> wrote:
> >> "While there is not an official standard per-se, most projects use
> >> $project-site.git to host their site generation code...
> >
> > +1
> >
> > considering that we have https://svn.apache.org/repos/asf/comdev/ for
> > existing code I think the (Git) website repository should be named
> > comdev-site or community-site.
>
> +1 for community-site. "comdev" is merely an abbreviation we made up
> for the formal "Community Development" project, which has no meaning
> outside this group. "Community" on the other hand, is what we do - and
> it's the domain name of our website.
>
> +1 for community-site.git (website) and community.git (all the various
> code bits) is my suggestion.
>
> Thanks for working on this!
>
> --
>
> - Shane
> Community Development Project Management Committee Member 8-)
> The Apache Software Foundation
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
>
Re: ComDev website, pelican
Posted by Shane Curcuru <as...@shanecurcuru.org>.
Bertrand Delacretaz wrote on 2019-6-4 5:02AM EDT:
> On Tue, Jun 4, 2019 at 9:53 AM sebb <se...@gmail.com> wrote:
>> "While there is not an official standard per-se, most projects use
>> $project-site.git to host their site generation code...
>
> +1
>
> considering that we have https://svn.apache.org/repos/asf/comdev/ for
> existing code I think the (Git) website repository should be named
> comdev-site or community-site.
+1 for community-site. "comdev" is merely an abbreviation we made up
for the formal "Community Development" project, which has no meaning
outside this group. "Community" on the other hand, is what we do - and
it's the domain name of our website.
+1 for community-site.git (website) and community.git (all the various
code bits) is my suggestion.
Thanks for working on this!
--
- Shane
Community Development Project Management Committee Member 8-)
The Apache Software Foundation
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: ComDev website, pelican
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Tue, Jun 4, 2019 at 9:53 AM sebb <se...@gmail.com> wrote:
> "While there is not an official standard per-se, most projects use
> $project-site.git to host their site generation code...
+1
considering that we have https://svn.apache.org/repos/asf/comdev/ for
existing code I think the (Git) website repository should be named
comdev-site or community-site.
-Bertrand
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: ComDev website, pelican
Posted by sebb <se...@gmail.com>.
On Tue, 4 Jun 2019 at 03:30, Andrew Musselman
<an...@gmail.com> wrote:
>
> Just picking this back up; reminder if anyone's able to pitch in to convert
> files over to markdown I'll appreciate the help.
>
> Beyond that, is there a reason to make a new "comdev-wwwsite" repo instead
> of just setting one up for "community"? Looks like
> http://github.com/apache/community is not being used, would be a nice way
> to surface the code for people to pitch in.
See INFRA-18549
"While there is not an official standard per-se, most projects use
$project-site.git to host their site generation code, and commit the
rendered code to an asf-site branch within that repo, which is then
used by Infra's pubsub system to display the content ..."
> Let me know, if there are no objections I'll request a repo and start
> getting things set up.
>
> On Mon, May 20, 2019 at 12:34 PM Andrew Musselman <
> andrew.musselman@gmail.com> wrote:
>
> > Feel free to assign that ticket to me (akm@a.o).
> >
> > Any volunteers to convert either the HTML files or CMS raw markup files to
> > markdown, please get in touch.
> >
> > There will be some redesign (mostly accepting theme defaults and layout
> > limitations of markdown) necessary unless we want to invest in a perfect
> > reproduction; we can log differences in this JIRA ticket and decide how to
> > handle as we go.
> >
> > On Mon, May 20, 2019 at 12:20 PM Rich Bowen <rb...@rcbowen.com> wrote:
> >
> >>
> >>
> >> On 5/20/19 3:08 PM, Andrew Musselman wrote:
> >> > Assuming the goal is a straight lift and shift from CMS to pelican, I
> >> could
> >> > commit to starting a skeleton and setting up a workflow for other
> >> > volunteers to convert existing content to markdown files.
> >> >
> >> > Not this month, but during June if that works.
> >> >
> >>
> >> Works for me. Sooner than I'd get to it.
> >>
> >> --Rich
> >>
> >>
> >> > On Mon, May 20, 2019 at 11:43 AM Rich Bowen <rb...@rcbowen.com> wrote:
> >> >
> >> >> Long, long ago I opened this:
> >> >> https://issues.apache.org/jira/browse/INFRA-15387
> >> >>
> >> >> It has recently been woken up again.
> >> >>
> >> >> I'm looking for someone to take the reins on this, since I do not
> >> really
> >> >> have time to do it any time before September.
> >> >>
> >> >> Any volunteers?
> >> >>
> >> >> --
> >> >> Rich Bowen - rbowen@rcbowen.com
> >> >> http://rcbowen.com/
> >> >> @rbowen
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> >> >> For additional commands, e-mail: dev-help@community.apache.org
> >> >>
> >> >>
> >> >
> >>
> >> --
> >> Rich Bowen - rbowen@rcbowen.com
> >> http://rcbowen.com/
> >> @rbowen
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> >> For additional commands, e-mail: dev-help@community.apache.org
> >>
> >>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: ComDev website, pelican
Posted by Andrew Musselman <an...@gmail.com>.
Just picking this back up; reminder if anyone's able to pitch in to convert
files over to markdown I'll appreciate the help.
Beyond that, is there a reason to make a new "comdev-wwwsite" repo instead
of just setting one up for "community"? Looks like
http://github.com/apache/community is not being used, would be a nice way
to surface the code for people to pitch in.
Let me know, if there are no objections I'll request a repo and start
getting things set up.
On Mon, May 20, 2019 at 12:34 PM Andrew Musselman <
andrew.musselman@gmail.com> wrote:
> Feel free to assign that ticket to me (akm@a.o).
>
> Any volunteers to convert either the HTML files or CMS raw markup files to
> markdown, please get in touch.
>
> There will be some redesign (mostly accepting theme defaults and layout
> limitations of markdown) necessary unless we want to invest in a perfect
> reproduction; we can log differences in this JIRA ticket and decide how to
> handle as we go.
>
> On Mon, May 20, 2019 at 12:20 PM Rich Bowen <rb...@rcbowen.com> wrote:
>
>>
>>
>> On 5/20/19 3:08 PM, Andrew Musselman wrote:
>> > Assuming the goal is a straight lift and shift from CMS to pelican, I
>> could
>> > commit to starting a skeleton and setting up a workflow for other
>> > volunteers to convert existing content to markdown files.
>> >
>> > Not this month, but during June if that works.
>> >
>>
>> Works for me. Sooner than I'd get to it.
>>
>> --Rich
>>
>>
>> > On Mon, May 20, 2019 at 11:43 AM Rich Bowen <rb...@rcbowen.com> wrote:
>> >
>> >> Long, long ago I opened this:
>> >> https://issues.apache.org/jira/browse/INFRA-15387
>> >>
>> >> It has recently been woken up again.
>> >>
>> >> I'm looking for someone to take the reins on this, since I do not
>> really
>> >> have time to do it any time before September.
>> >>
>> >> Any volunteers?
>> >>
>> >> --
>> >> Rich Bowen - rbowen@rcbowen.com
>> >> http://rcbowen.com/
>> >> @rbowen
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>> >> For additional commands, e-mail: dev-help@community.apache.org
>> >>
>> >>
>> >
>>
>> --
>> Rich Bowen - rbowen@rcbowen.com
>> http://rcbowen.com/
>> @rbowen
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>> For additional commands, e-mail: dev-help@community.apache.org
>>
>>
Re: ComDev website, pelican
Posted by Andrew Musselman <an...@gmail.com>.
Feel free to assign that ticket to me (akm@a.o).
Any volunteers to convert either the HTML files or CMS raw markup files to
markdown, please get in touch.
There will be some redesign (mostly accepting theme defaults and layout
limitations of markdown) necessary unless we want to invest in a perfect
reproduction; we can log differences in this JIRA ticket and decide how to
handle as we go.
On Mon, May 20, 2019 at 12:20 PM Rich Bowen <rb...@rcbowen.com> wrote:
>
>
> On 5/20/19 3:08 PM, Andrew Musselman wrote:
> > Assuming the goal is a straight lift and shift from CMS to pelican, I
> could
> > commit to starting a skeleton and setting up a workflow for other
> > volunteers to convert existing content to markdown files.
> >
> > Not this month, but during June if that works.
> >
>
> Works for me. Sooner than I'd get to it.
>
> --Rich
>
>
> > On Mon, May 20, 2019 at 11:43 AM Rich Bowen <rb...@rcbowen.com> wrote:
> >
> >> Long, long ago I opened this:
> >> https://issues.apache.org/jira/browse/INFRA-15387
> >>
> >> It has recently been woken up again.
> >>
> >> I'm looking for someone to take the reins on this, since I do not really
> >> have time to do it any time before September.
> >>
> >> Any volunteers?
> >>
> >> --
> >> Rich Bowen - rbowen@rcbowen.com
> >> http://rcbowen.com/
> >> @rbowen
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> >> For additional commands, e-mail: dev-help@community.apache.org
> >>
> >>
> >
>
> --
> Rich Bowen - rbowen@rcbowen.com
> http://rcbowen.com/
> @rbowen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
>
Re: ComDev website, pelican
Posted by Rich Bowen <rb...@rcbowen.com>.
On 5/20/19 3:08 PM, Andrew Musselman wrote:
> Assuming the goal is a straight lift and shift from CMS to pelican, I could
> commit to starting a skeleton and setting up a workflow for other
> volunteers to convert existing content to markdown files.
>
> Not this month, but during June if that works.
>
Works for me. Sooner than I'd get to it.
--Rich
> On Mon, May 20, 2019 at 11:43 AM Rich Bowen <rb...@rcbowen.com> wrote:
>
>> Long, long ago I opened this:
>> https://issues.apache.org/jira/browse/INFRA-15387
>>
>> It has recently been woken up again.
>>
>> I'm looking for someone to take the reins on this, since I do not really
>> have time to do it any time before September.
>>
>> Any volunteers?
>>
>> --
>> Rich Bowen - rbowen@rcbowen.com
>> http://rcbowen.com/
>> @rbowen
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>> For additional commands, e-mail: dev-help@community.apache.org
>>
>>
>
--
Rich Bowen - rbowen@rcbowen.com
http://rcbowen.com/
@rbowen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: ComDev website, pelican
Posted by Andrew Musselman <an...@gmail.com>.
Assuming the goal is a straight lift and shift from CMS to pelican, I could
commit to starting a skeleton and setting up a workflow for other
volunteers to convert existing content to markdown files.
Not this month, but during June if that works.
On Mon, May 20, 2019 at 11:43 AM Rich Bowen <rb...@rcbowen.com> wrote:
> Long, long ago I opened this:
> https://issues.apache.org/jira/browse/INFRA-15387
>
> It has recently been woken up again.
>
> I'm looking for someone to take the reins on this, since I do not really
> have time to do it any time before September.
>
> Any volunteers?
>
> --
> Rich Bowen - rbowen@rcbowen.com
> http://rcbowen.com/
> @rbowen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
>