On Wed, 5 Jun 2019 at 16:32, Andrew Musselman
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
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
wrote:
> That's not clear to me; that self-serve page's instructions say "Here you
> can request a new git
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
On Tue, 4 Jun 2019 at 18:25, Andrew Musselman
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
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
wrote:
> Sounds good to me; I'll get those two repos set up; will have push rights
>
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 wrote:
> Bertrand Delacretaz wrote on 2019-6-4 5:02AM EDT:
> > On Tue, Jun 4, 2019 at 9:53 AM sebb wrote:
> >>
Bertrand Delacretaz wrote on 2019-6-4 5:02AM EDT:
> On Tue, Jun 4, 2019 at 9:53 AM sebb 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
On Tue, Jun 4, 2019 at 9:53 AM sebb 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
On Tue, 4 Jun 2019 at 03:30, Andrew Musselman
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
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
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
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.
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
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 - rbo...@rcbowen.com
14 matches
Mail list logo
