On Tue, 4 Jun 2019 at 18:25, Andrew Musselman
<andrew.mussel...@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.mussel...@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 <a...@shanecurcuru.org> wrote:
> >
> >> Bertrand Delacretaz wrote on 2019-6-4 5:02AM EDT:
> >> > On Tue, Jun 4, 2019 at 9:53 AM sebb <seb...@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-unsubscr...@community.apache.org
> >> For additional commands, e-mail: dev-h...@community.apache.org
> >>
> >>

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

Reply via email to