You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@community.apache.org by Jarek Potiuk <ja...@potiuk.com> on 2023/07/06 20:52:02 UTC

Setting up Git Project under comdev for Community Over Code EU

Dear ComDev friends,

I need some help in determining how we should approach developing the
Community Over Code EU website and I believe dev@community.a.o is the right
place to ask for it.

We are getting up to speed with preparation of the Community Over Code EU
2024 in Bratislava (June 3-6) and as a person leading a Tech committee of
the conference, I am looking for a place where we could host our website.

The conclusion of the discussion we had last week was that we want to get a
statically generated website - based on the same tooling and ASF
integration tooling as https://github.com/apache/comdev-site is. We will
eventually make it available at eu.communityovercode.org and (secondary)
goal of that is to make it a nice starting point for future other
communityovercode sites (NA one is currently run via wordpress). Some of
the committee members are particularly keen on transparency and
archiving/inclusivity, so rather than creating a repo outside of ASF (which
is an option) we thought the best will be to get a repo in the "apache"
organisation.

From the JIRA ticket https://issues.apache.org/jira/browse/INFRA-24741 - if
we were to use INFRA supported GitHub repos (under the apache/
organisation) we need a "project" to host it and Rich suggested that
instead of creating a new one we could do it via comdev.

We have some specific requirement re: access to the repository. We are not
a typical PMC where we have committers and PMC members. We are cooperating
with a producer company (Software Guru) and rather than merging their PRs
we would rather (especially at the crucial times before the event) want to
give them direct "push" access and capability of merging PRs.

So my question is:

* has something like that been done before?
* is this possible for comdev projects to have such repos
(apache/comdev-commovercode-eu) with external people access ?
* or maybe we need to add those who need write access to comdev? Is this
possible (how about accessing other comdev projects ?).
* how do we get such a repository (I cannot create a new repo with
self-serve, I guess I would need to become a comdev member?)
* or maybe it's not a good idea for whatever reasons and we should create
some specific initiative (I understand comdev is not a PMC, so having
communityovercodeeu group might not be the worst idea).

Looking forward to getting some clarity on those questions :)

J.

Re: Setting up Git Project under comdev for Community Over Code EU

Posted by sebb <se...@gmail.com>.
You are both in the apachecon auth group, so in theory you should be
able to select apachecon from the drop down.
However, it is not a (P)PMC, and does not have the usual LDAP setup,
so perhaps the auth is not being correctly calculated.

On Mon, 31 Jul 2023 at 18:26, Jarek Potiuk <ja...@potiuk.com> wrote:
>
> back full circle :)
>
> On Mon, Jul 31, 2023 at 7:08 PM <rb...@rcbowen.com> wrote:
> >
> > On Mon, 2023-07-31 at 17:40 +0200, Jarek Potiuk wrote:
> > > Hmm,
> > >
> > > Is it possible to create a repo there then (apachecon-eu - until we
> > > rename the group) - I tried to create one with boxer -
> > > https://gitbox.apache.org/boxer/?action=newrepo but it's greyed-out.
> > >
> > > Or I guess I need more karma for that one?
> >
> >
> > Nope, it's greyed out for me too. I would suggest opening an infra
> > ticket.
> >
> >
> > ---------------------------------------------------------------------
> > 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: Setting up Git Project under comdev for Community Over Code EU

Posted by Jarek Potiuk <ja...@potiuk.com>.
back full circle :)

On Mon, Jul 31, 2023 at 7:08 PM <rb...@rcbowen.com> wrote:
>
> On Mon, 2023-07-31 at 17:40 +0200, Jarek Potiuk wrote:
> > Hmm,
> >
> > Is it possible to create a repo there then (apachecon-eu - until we
> > rename the group) - I tried to create one with boxer -
> > https://gitbox.apache.org/boxer/?action=newrepo but it's greyed-out.
> >
> > Or I guess I need more karma for that one?
>
>
> Nope, it's greyed out for me too. I would suggest opening an infra
> ticket.
>
>
> ---------------------------------------------------------------------
> 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: Setting up Git Project under comdev for Community Over Code EU

Posted by rb...@rcbowen.com.
On Mon, 2023-07-31 at 17:40 +0200, Jarek Potiuk wrote:
> Hmm,
> 
> Is it possible to create a repo there then (apachecon-eu - until we
> rename the group) - I tried to create one with boxer -
> https://gitbox.apache.org/boxer/?action=newrepo but it's greyed-out.
> 
> Or I guess I need more karma for that one?


Nope, it's greyed out for me too. I would suggest opening an infra
ticket.


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


Re: Setting up Git Project under comdev for Community Over Code EU

Posted by Jarek Potiuk <ja...@potiuk.com>.
Hmm,

Is it possible to create a repo there then (apachecon-eu - until we
rename the group) - I tried to create one with boxer -
https://gitbox.apache.org/boxer/?action=newrepo but it's greyed-out.

Or I guess I need more karma for that one?

J.


On Mon, Jul 31, 2023 at 4:18 PM <rb...@rcbowen.com> wrote:
>
> On Mon, 2023-07-31 at 15:51 +0200, Jarek Potiuk wrote:
> > Following up with that after short holidays - how can I (and others
> > from the Community over Code EU) get added to the "apachecon" group
> > so
> > that I can create the repository and have "committer" access to it?
> >
> > Do I need a JIRA ticket or just karma granted by someone ? I can
> > provide a list of ASF members to add there as a good start.
> >
>
>
>
> You are in fact already in that group.
>
> https://whimsy.apache.org/roster/group/apachecon?type=LDAP%20Auth%20Group
>
>
>
> ---------------------------------------------------------------------
> 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: Setting up Git Project under comdev for Community Over Code EU

Posted by rb...@rcbowen.com.
On Mon, 2023-07-31 at 15:51 +0200, Jarek Potiuk wrote:
> Following up with that after short holidays - how can I (and others
> from the Community over Code EU) get added to the "apachecon" group
> so
> that I can create the repository and have "committer" access to it?
> 
> Do I need a JIRA ticket or just karma granted by someone ? I can
> provide a list of ASF members to add there as a good start.
> 



You are in fact already in that group.

https://whimsy.apache.org/roster/group/apachecon?type=LDAP%20Auth%20Group



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


Re: Setting up Git Project under comdev for Community Over Code EU

Posted by Jarek Potiuk <ja...@potiuk.com>.
Following up with that after short holidays - how can I (and others
from the Community over Code EU) get added to the "apachecon" group so
that I can create the repository and have "committer" access to it?

Do I need a JIRA ticket or just karma granted by someone ? I can
provide a list of ASF members to add there as a good start.

On Mon, Jul 10, 2023 at 3:38 PM Jarek Potiuk <ja...@potiuk.com> wrote:
>
> Yep. That would be perfect.
>
> On Mon, Jul 10, 2023 at 3:29 PM Rich Bowen <rb...@rcbowen.com> wrote:
>>
>> We could also put something under the Apachecon ldap group, which I am
>> thinking of renaming to conferences or events. That might be a better match?
>>
>> Shosholoza,
>> Rich
>>
>>
>> On Sun, Jul 9, 2023, 02:28 Jarek Potiuk <ja...@potiuk.com> wrote:
>>
>> > Sure. if we have "apachecon-*" (and possibly renamed). That would be the
>> > best approach.
>> >
>> > No problem with waiting until Rich is back.
>> >
>> > J.
>> >
>> >
>> > On Sun, Jul 9, 2023 at 7:57 AM Willem Jiang <wi...@gmail.com>
>> > wrote:
>> >
>> > > FYI, ApacheCon Asia conference website[1] uses Hugo with a customer
>> > > theme[2].
>> > >
>> > > [1]https://github.com/apache/apachecon-acasia
>> > > [2]
>> > https://github.com/apache/apachecon-acasia/tree/master/themes/apachecon
>> > >
>> > >
>> > > Willem Jiang
>> > >
>> > > Twitter: willemjiang
>> > > Weibo: 姜宁willem
>> > >
>> > > On Sat, Jul 8, 2023 at 7:35 PM Jarek Potiuk <ja...@potiuk.com> wrote:
>> > > >
>> > > > >
>> > > > >
>> > > > > > it might be simpler to manage if we used this PMC instead -
>> > although
>> > > > > > that requires some consensus from this PMC first to own something
>> > > that
>> > > > > > really belongs to conferences.
>> > > > >
>> > > >
>> > > > Yeah. That's what I am really looking for :).  I would also be fine to
>> > > > create
>> > > > a new group ? PMC? for that if ComDev is not the right place. Maybe
>> > there
>> > > > are ways to set up other "entities" for the ASF structure that could
>> > > serve
>> > > > the purpose ? I do not (yet) know all the options - but I believe PMC
>> > is
>> > > not
>> > > > the only option to have a separate "LDAP group".
>> > > >
>> > > > > One note: do you *specifically* want to copy the ComDev site repo?
>> > Or
>> > > > > > do you want to start with the infra-supported (but simpler design)
>> > > >
>> > > >
>> > > > Not really. We can start from scratch, I was referring more to the
>> > > > integrations
>> > > > that we get from INFRA: .asf.yaml, emails sent to specific discussion
>> > > lists
>> > > > we
>> > > > can customize - generally following best practices there.
>> > > >
>> > > >
>> > > > >
>> > > > My experience with both Hugo and Pelican is that Hugo is easier to
>> > > > > customise.
>> > > > >
>> > > >
>> > > > Yes we also prefer Hugo. Airflow Summit Website - prepared entirely by
>> > > the
>> > > > Software
>> > > > Guru team - our producers - is based on Hugo, so that would be our
>> > > > preference as well.
>> > > >
>> > > > https://github.com/softwareguru/airflowsummit-website
>> > > >
>> > > >
>> > > > >
>> > > > > > template repo they recommend for new projects?
>> > > > > >    https://github.com/apache/template-site
>> > > > >
>> > > > > I don't think that is production ready.
>> > > > >
>> > > >
>> > > > We have quite a lot of time before our website will be public (at the
>> > > very
>> > > > least
>> > > > 3-4 months), so we are ok to take it slowly, follow the right process,
>> > > and
>> > > > then
>> > > > even contribute back and make them more ready - if that would be a good
>> > > > start,
>> > > > We are happy to do so. We could eventually also add an "ASF conference
>> > > > template"
>> > > > for others and possibly pave the way to follow the same "process" (but
>> > I
>> > > am
>> > > > usually
>> > > > of the opinion that in order to make something reusable, you have to
>> > make
>> > > > it usable
>> > > > first - so that would likely be a next step and we could "lead by
>> > > > example").
>> > > >
>> > > >
>> > > > > >
>> > > > > > No.  AFAIK any direct write access to /apache repos can only come
>> > > from
>> > > > > > ASF committers who have signed an ICLA.  But that's solvable for a
>> > > > > > special case like this, by having an officer or PMC simply agree to
>> > > > > > invite those outside individuals at Software Guru to be committers
>> > > here.
>> > > > > >   Note also that individuals can be made committers, not companies.
>> > > > >
>> > > > >
>> > > > I believe signing ICLA by those individuals from Software Guru is not a
>> > > > problem at all,
>> > > > and they will be perfectly happy to act in their "individual"
>> > capacity. I
>> > > > know them personally
>> > > > very well and I am sure this is not a problem. And on a personal (about
>> > > > individuals) note -
>> > > > they are so much personally involved with other Apache conferences
>> > > > (Airflow, Beam)
>> > > > and now running the Community Over Code EU, that it would make
>> > absolutely
>> > > > sense to make them committers.
>> > > >
>> > > > I think it's more of a question - if they are made committers in
>> > ComDev,
>> > > > they will have
>> > > > access to the main ASF community site, so possibly having a separate
>> > > > "group"? makes
>> > > > more sense.
>> > > >
>> > > > So I think the main question I have now - is it really possible to have
>> > > it
>> > > > in comdev?
>> > > >
>> > > > Or should we (any leads on how?) create a new "group" to manage it.
>> > > >
>> > > > J.
>> > >
>> > > ---------------------------------------------------------------------
>> > > 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: Setting up Git Project under comdev for Community Over Code EU

Posted by Jarek Potiuk <ja...@potiuk.com>.
Yep. That would be perfect.

On Mon, Jul 10, 2023 at 3:29 PM Rich Bowen <rb...@rcbowen.com> wrote:

> We could also put something under the Apachecon ldap group, which I am
> thinking of renaming to conferences or events. That might be a better
> match?
>
> Shosholoza,
> Rich
>
>
> On Sun, Jul 9, 2023, 02:28 Jarek Potiuk <ja...@potiuk.com> wrote:
>
> > Sure. if we have "apachecon-*" (and possibly renamed). That would be the
> > best approach.
> >
> > No problem with waiting until Rich is back.
> >
> > J.
> >
> >
> > On Sun, Jul 9, 2023 at 7:57 AM Willem Jiang <wi...@gmail.com>
> > wrote:
> >
> > > FYI, ApacheCon Asia conference website[1] uses Hugo with a customer
> > > theme[2].
> > >
> > > [1]https://github.com/apache/apachecon-acasia
> > > [2]
> > https://github.com/apache/apachecon-acasia/tree/master/themes/apachecon
> > >
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > >
> > > On Sat, Jul 8, 2023 at 7:35 PM Jarek Potiuk <ja...@potiuk.com> wrote:
> > > >
> > > > >
> > > > >
> > > > > > it might be simpler to manage if we used this PMC instead -
> > although
> > > > > > that requires some consensus from this PMC first to own something
> > > that
> > > > > > really belongs to conferences.
> > > > >
> > > >
> > > > Yeah. That's what I am really looking for :).  I would also be fine
> to
> > > > create
> > > > a new group ? PMC? for that if ComDev is not the right place. Maybe
> > there
> > > > are ways to set up other "entities" for the ASF structure that could
> > > serve
> > > > the purpose ? I do not (yet) know all the options - but I believe PMC
> > is
> > > not
> > > > the only option to have a separate "LDAP group".
> > > >
> > > > > One note: do you *specifically* want to copy the ComDev site repo?
> > Or
> > > > > > do you want to start with the infra-supported (but simpler
> design)
> > > >
> > > >
> > > > Not really. We can start from scratch, I was referring more to the
> > > > integrations
> > > > that we get from INFRA: .asf.yaml, emails sent to specific discussion
> > > lists
> > > > we
> > > > can customize - generally following best practices there.
> > > >
> > > >
> > > > >
> > > > My experience with both Hugo and Pelican is that Hugo is easier to
> > > > > customise.
> > > > >
> > > >
> > > > Yes we also prefer Hugo. Airflow Summit Website - prepared entirely
> by
> > > the
> > > > Software
> > > > Guru team - our producers - is based on Hugo, so that would be our
> > > > preference as well.
> > > >
> > > > https://github.com/softwareguru/airflowsummit-website
> > > >
> > > >
> > > > >
> > > > > > template repo they recommend for new projects?
> > > > > >    https://github.com/apache/template-site
> > > > >
> > > > > I don't think that is production ready.
> > > > >
> > > >
> > > > We have quite a lot of time before our website will be public (at the
> > > very
> > > > least
> > > > 3-4 months), so we are ok to take it slowly, follow the right
> process,
> > > and
> > > > then
> > > > even contribute back and make them more ready - if that would be a
> good
> > > > start,
> > > > We are happy to do so. We could eventually also add an "ASF
> conference
> > > > template"
> > > > for others and possibly pave the way to follow the same "process"
> (but
> > I
> > > am
> > > > usually
> > > > of the opinion that in order to make something reusable, you have to
> > make
> > > > it usable
> > > > first - so that would likely be a next step and we could "lead by
> > > > example").
> > > >
> > > >
> > > > > >
> > > > > > No.  AFAIK any direct write access to /apache repos can only come
> > > from
> > > > > > ASF committers who have signed an ICLA.  But that's solvable for
> a
> > > > > > special case like this, by having an officer or PMC simply agree
> to
> > > > > > invite those outside individuals at Software Guru to be
> committers
> > > here.
> > > > > >   Note also that individuals can be made committers, not
> companies.
> > > > >
> > > > >
> > > > I believe signing ICLA by those individuals from Software Guru is
> not a
> > > > problem at all,
> > > > and they will be perfectly happy to act in their "individual"
> > capacity. I
> > > > know them personally
> > > > very well and I am sure this is not a problem. And on a personal
> (about
> > > > individuals) note -
> > > > they are so much personally involved with other Apache conferences
> > > > (Airflow, Beam)
> > > > and now running the Community Over Code EU, that it would make
> > absolutely
> > > > sense to make them committers.
> > > >
> > > > I think it's more of a question - if they are made committers in
> > ComDev,
> > > > they will have
> > > > access to the main ASF community site, so possibly having a separate
> > > > "group"? makes
> > > > more sense.
> > > >
> > > > So I think the main question I have now - is it really possible to
> have
> > > it
> > > > in comdev?
> > > >
> > > > Or should we (any leads on how?) create a new "group" to manage it.
> > > >
> > > > J.
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > > For additional commands, e-mail: dev-help@community.apache.org
> > >
> > >
> >
>

Re: Setting up Git Project under comdev for Community Over Code EU

Posted by Rich Bowen <rb...@rcbowen.com>.
We could also put something under the Apachecon ldap group, which I am
thinking of renaming to conferences or events. That might be a better match?

Shosholoza,
Rich


On Sun, Jul 9, 2023, 02:28 Jarek Potiuk <ja...@potiuk.com> wrote:

> Sure. if we have "apachecon-*" (and possibly renamed). That would be the
> best approach.
>
> No problem with waiting until Rich is back.
>
> J.
>
>
> On Sun, Jul 9, 2023 at 7:57 AM Willem Jiang <wi...@gmail.com>
> wrote:
>
> > FYI, ApacheCon Asia conference website[1] uses Hugo with a customer
> > theme[2].
> >
> > [1]https://github.com/apache/apachecon-acasia
> > [2]
> https://github.com/apache/apachecon-acasia/tree/master/themes/apachecon
> >
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Sat, Jul 8, 2023 at 7:35 PM Jarek Potiuk <ja...@potiuk.com> wrote:
> > >
> > > >
> > > >
> > > > > it might be simpler to manage if we used this PMC instead -
> although
> > > > > that requires some consensus from this PMC first to own something
> > that
> > > > > really belongs to conferences.
> > > >
> > >
> > > Yeah. That's what I am really looking for :).  I would also be fine to
> > > create
> > > a new group ? PMC? for that if ComDev is not the right place. Maybe
> there
> > > are ways to set up other "entities" for the ASF structure that could
> > serve
> > > the purpose ? I do not (yet) know all the options - but I believe PMC
> is
> > not
> > > the only option to have a separate "LDAP group".
> > >
> > > > One note: do you *specifically* want to copy the ComDev site repo?
> Or
> > > > > do you want to start with the infra-supported (but simpler design)
> > >
> > >
> > > Not really. We can start from scratch, I was referring more to the
> > > integrations
> > > that we get from INFRA: .asf.yaml, emails sent to specific discussion
> > lists
> > > we
> > > can customize - generally following best practices there.
> > >
> > >
> > > >
> > > My experience with both Hugo and Pelican is that Hugo is easier to
> > > > customise.
> > > >
> > >
> > > Yes we also prefer Hugo. Airflow Summit Website - prepared entirely by
> > the
> > > Software
> > > Guru team - our producers - is based on Hugo, so that would be our
> > > preference as well.
> > >
> > > https://github.com/softwareguru/airflowsummit-website
> > >
> > >
> > > >
> > > > > template repo they recommend for new projects?
> > > > >    https://github.com/apache/template-site
> > > >
> > > > I don't think that is production ready.
> > > >
> > >
> > > We have quite a lot of time before our website will be public (at the
> > very
> > > least
> > > 3-4 months), so we are ok to take it slowly, follow the right process,
> > and
> > > then
> > > even contribute back and make them more ready - if that would be a good
> > > start,
> > > We are happy to do so. We could eventually also add an "ASF conference
> > > template"
> > > for others and possibly pave the way to follow the same "process" (but
> I
> > am
> > > usually
> > > of the opinion that in order to make something reusable, you have to
> make
> > > it usable
> > > first - so that would likely be a next step and we could "lead by
> > > example").
> > >
> > >
> > > > >
> > > > > No.  AFAIK any direct write access to /apache repos can only come
> > from
> > > > > ASF committers who have signed an ICLA.  But that's solvable for a
> > > > > special case like this, by having an officer or PMC simply agree to
> > > > > invite those outside individuals at Software Guru to be committers
> > here.
> > > > >   Note also that individuals can be made committers, not companies.
> > > >
> > > >
> > > I believe signing ICLA by those individuals from Software Guru is not a
> > > problem at all,
> > > and they will be perfectly happy to act in their "individual"
> capacity. I
> > > know them personally
> > > very well and I am sure this is not a problem. And on a personal (about
> > > individuals) note -
> > > they are so much personally involved with other Apache conferences
> > > (Airflow, Beam)
> > > and now running the Community Over Code EU, that it would make
> absolutely
> > > sense to make them committers.
> > >
> > > I think it's more of a question - if they are made committers in
> ComDev,
> > > they will have
> > > access to the main ASF community site, so possibly having a separate
> > > "group"? makes
> > > more sense.
> > >
> > > So I think the main question I have now - is it really possible to have
> > it
> > > in comdev?
> > >
> > > Or should we (any leads on how?) create a new "group" to manage it.
> > >
> > > J.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> > For additional commands, e-mail: dev-help@community.apache.org
> >
> >
>

Re: Setting up Git Project under comdev for Community Over Code EU

Posted by Jarek Potiuk <ja...@potiuk.com>.
Sure. if we have "apachecon-*" (and possibly renamed). That would be the
best approach.

No problem with waiting until Rich is back.

J.


On Sun, Jul 9, 2023 at 7:57 AM Willem Jiang <wi...@gmail.com> wrote:

> FYI, ApacheCon Asia conference website[1] uses Hugo with a customer
> theme[2].
>
> [1]https://github.com/apache/apachecon-acasia
> [2]https://github.com/apache/apachecon-acasia/tree/master/themes/apachecon
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Sat, Jul 8, 2023 at 7:35 PM Jarek Potiuk <ja...@potiuk.com> wrote:
> >
> > >
> > >
> > > > it might be simpler to manage if we used this PMC instead - although
> > > > that requires some consensus from this PMC first to own something
> that
> > > > really belongs to conferences.
> > >
> >
> > Yeah. That's what I am really looking for :).  I would also be fine to
> > create
> > a new group ? PMC? for that if ComDev is not the right place. Maybe there
> > are ways to set up other "entities" for the ASF structure that could
> serve
> > the purpose ? I do not (yet) know all the options - but I believe PMC is
> not
> > the only option to have a separate "LDAP group".
> >
> > > One note: do you *specifically* want to copy the ComDev site repo?  Or
> > > > do you want to start with the infra-supported (but simpler design)
> >
> >
> > Not really. We can start from scratch, I was referring more to the
> > integrations
> > that we get from INFRA: .asf.yaml, emails sent to specific discussion
> lists
> > we
> > can customize - generally following best practices there.
> >
> >
> > >
> > My experience with both Hugo and Pelican is that Hugo is easier to
> > > customise.
> > >
> >
> > Yes we also prefer Hugo. Airflow Summit Website - prepared entirely by
> the
> > Software
> > Guru team - our producers - is based on Hugo, so that would be our
> > preference as well.
> >
> > https://github.com/softwareguru/airflowsummit-website
> >
> >
> > >
> > > > template repo they recommend for new projects?
> > > >    https://github.com/apache/template-site
> > >
> > > I don't think that is production ready.
> > >
> >
> > We have quite a lot of time before our website will be public (at the
> very
> > least
> > 3-4 months), so we are ok to take it slowly, follow the right process,
> and
> > then
> > even contribute back and make them more ready - if that would be a good
> > start,
> > We are happy to do so. We could eventually also add an "ASF conference
> > template"
> > for others and possibly pave the way to follow the same "process" (but I
> am
> > usually
> > of the opinion that in order to make something reusable, you have to make
> > it usable
> > first - so that would likely be a next step and we could "lead by
> > example").
> >
> >
> > > >
> > > > No.  AFAIK any direct write access to /apache repos can only come
> from
> > > > ASF committers who have signed an ICLA.  But that's solvable for a
> > > > special case like this, by having an officer or PMC simply agree to
> > > > invite those outside individuals at Software Guru to be committers
> here.
> > > >   Note also that individuals can be made committers, not companies.
> > >
> > >
> > I believe signing ICLA by those individuals from Software Guru is not a
> > problem at all,
> > and they will be perfectly happy to act in their "individual" capacity. I
> > know them personally
> > very well and I am sure this is not a problem. And on a personal (about
> > individuals) note -
> > they are so much personally involved with other Apache conferences
> > (Airflow, Beam)
> > and now running the Community Over Code EU, that it would make absolutely
> > sense to make them committers.
> >
> > I think it's more of a question - if they are made committers in ComDev,
> > they will have
> > access to the main ASF community site, so possibly having a separate
> > "group"? makes
> > more sense.
> >
> > So I think the main question I have now - is it really possible to have
> it
> > in comdev?
> >
> > Or should we (any leads on how?) create a new "group" to manage it.
> >
> > J.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
>

Re: Setting up Git Project under comdev for Community Over Code EU

Posted by Willem Jiang <wi...@gmail.com>.
FYI, ApacheCon Asia conference website[1] uses Hugo with a customer theme[2].

[1]https://github.com/apache/apachecon-acasia
[2]https://github.com/apache/apachecon-acasia/tree/master/themes/apachecon


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Sat, Jul 8, 2023 at 7:35 PM Jarek Potiuk <ja...@potiuk.com> wrote:
>
> >
> >
> > > it might be simpler to manage if we used this PMC instead - although
> > > that requires some consensus from this PMC first to own something that
> > > really belongs to conferences.
> >
>
> Yeah. That's what I am really looking for :).  I would also be fine to
> create
> a new group ? PMC? for that if ComDev is not the right place. Maybe there
> are ways to set up other "entities" for the ASF structure that could serve
> the purpose ? I do not (yet) know all the options - but I believe PMC is not
> the only option to have a separate "LDAP group".
>
> > One note: do you *specifically* want to copy the ComDev site repo?  Or
> > > do you want to start with the infra-supported (but simpler design)
>
>
> Not really. We can start from scratch, I was referring more to the
> integrations
> that we get from INFRA: .asf.yaml, emails sent to specific discussion lists
> we
> can customize - generally following best practices there.
>
>
> >
> My experience with both Hugo and Pelican is that Hugo is easier to
> > customise.
> >
>
> Yes we also prefer Hugo. Airflow Summit Website - prepared entirely by the
> Software
> Guru team - our producers - is based on Hugo, so that would be our
> preference as well.
>
> https://github.com/softwareguru/airflowsummit-website
>
>
> >
> > > template repo they recommend for new projects?
> > >    https://github.com/apache/template-site
> >
> > I don't think that is production ready.
> >
>
> We have quite a lot of time before our website will be public (at the very
> least
> 3-4 months), so we are ok to take it slowly, follow the right process, and
> then
> even contribute back and make them more ready - if that would be a good
> start,
> We are happy to do so. We could eventually also add an "ASF conference
> template"
> for others and possibly pave the way to follow the same "process" (but I am
> usually
> of the opinion that in order to make something reusable, you have to make
> it usable
> first - so that would likely be a next step and we could "lead by
> example").
>
>
> > >
> > > No.  AFAIK any direct write access to /apache repos can only come from
> > > ASF committers who have signed an ICLA.  But that's solvable for a
> > > special case like this, by having an officer or PMC simply agree to
> > > invite those outside individuals at Software Guru to be committers here.
> > >   Note also that individuals can be made committers, not companies.
> >
> >
> I believe signing ICLA by those individuals from Software Guru is not a
> problem at all,
> and they will be perfectly happy to act in their "individual" capacity. I
> know them personally
> very well and I am sure this is not a problem. And on a personal (about
> individuals) note -
> they are so much personally involved with other Apache conferences
> (Airflow, Beam)
> and now running the Community Over Code EU, that it would make absolutely
> sense to make them committers.
>
> I think it's more of a question - if they are made committers in ComDev,
> they will have
> access to the main ASF community site, so possibly having a separate
> "group"? makes
> more sense.
>
> So I think the main question I have now - is it really possible to have it
> in comdev?
>
> Or should we (any leads on how?) create a new "group" to manage it.
>
> J.

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


Re: Setting up Git Project under comdev for Community Over Code EU

Posted by Daniel Gruno <hu...@apache.org>.
On 2023-07-08 18:22, Jarek Potiuk wrote:
> Sounds like a great plan. Thanks Shane.

I would advise we hold off for a couple of days here. There is an ldap 
auth group for the conferences team that can be used. It looks like that 
group needs to be renamed to better reflect the breadth of conferences, 
and I believe VP Conferences is aware and will request a change.

> 
> On Sat, Jul 8, 2023 at 3:03 PM Shane Curcuru <as...@shanecurcuru.org> wrote:
> 
>> To simplify (and then answer) the question:
>>
>> - You & EU organizers need a repo for the COCEU website, which will
>> include some new contributors, and might be used for other events later.
>>
>> - Is there consensus with the ComDev PMC to be the organizational owner
>> for your new repo?  The INFRA issue is that every repo needs a VP or PMC
>> to own it, so we know who's providing direct oversight.
>>
>> My consensus is yes, go create one.  ComDev already has the events.a.o
>> website repo, so as long as Jarek and the other COCEU organizers will be
>> coming here to actively manage the new repo, that seems fine.
>>
>>     https://github.com/apache/comdev-events-site
>>
>> I would give it a few days to see if anyone objects, then ask Infra to
>> create the repo here, and once done, send a new email to dev@ with the
>> brief plan for what the work is going to be, and alerting people you're
>> going to propose some new committer votes.
>>
>> --
>> - Shane
>>     ComDev PMC
>>     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: Setting up Git Project under comdev for Community Over Code EU

Posted by Jarek Potiuk <ja...@potiuk.com>.
Sounds like a great plan. Thanks Shane.

On Sat, Jul 8, 2023 at 3:03 PM Shane Curcuru <as...@shanecurcuru.org> wrote:

> To simplify (and then answer) the question:
>
> - You & EU organizers need a repo for the COCEU website, which will
> include some new contributors, and might be used for other events later.
>
> - Is there consensus with the ComDev PMC to be the organizational owner
> for your new repo?  The INFRA issue is that every repo needs a VP or PMC
> to own it, so we know who's providing direct oversight.
>
> My consensus is yes, go create one.  ComDev already has the events.a.o
> website repo, so as long as Jarek and the other COCEU organizers will be
> coming here to actively manage the new repo, that seems fine.
>
>    https://github.com/apache/comdev-events-site
>
> I would give it a few days to see if anyone objects, then ask Infra to
> create the repo here, and once done, send a new email to dev@ with the
> brief plan for what the work is going to be, and alerting people you're
> going to propose some new committer votes.
>
> --
> - Shane
>    ComDev PMC
>    The Apache Software Foundation
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
>

Re: Setting up Git Project under comdev for Community Over Code EU

Posted by Shane Curcuru <as...@shanecurcuru.org>.
To simplify (and then answer) the question:

- You & EU organizers need a repo for the COCEU website, which will 
include some new contributors, and might be used for other events later.

- Is there consensus with the ComDev PMC to be the organizational owner 
for your new repo?  The INFRA issue is that every repo needs a VP or PMC 
to own it, so we know who's providing direct oversight.

My consensus is yes, go create one.  ComDev already has the events.a.o 
website repo, so as long as Jarek and the other COCEU organizers will be 
coming here to actively manage the new repo, that seems fine.

   https://github.com/apache/comdev-events-site

I would give it a few days to see if anyone objects, then ask Infra to 
create the repo here, and once done, send a new email to dev@ with the 
brief plan for what the work is going to be, and alerting people you're 
going to propose some new committer votes.

-- 
- Shane
   ComDev PMC
   The Apache Software Foundation


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


Re: Setting up Git Project under comdev for Community Over Code EU

Posted by Jarek Potiuk <ja...@potiuk.com>.
>
>
> > it might be simpler to manage if we used this PMC instead - although
> > that requires some consensus from this PMC first to own something that
> > really belongs to conferences.
>

Yeah. That's what I am really looking for :).  I would also be fine to
create
a new group ? PMC? for that if ComDev is not the right place. Maybe there
are ways to set up other "entities" for the ASF structure that could serve
the purpose ? I do not (yet) know all the options - but I believe PMC is not
the only option to have a separate "LDAP group".

> One note: do you *specifically* want to copy the ComDev site repo?  Or
> > do you want to start with the infra-supported (but simpler design)


Not really. We can start from scratch, I was referring more to the
integrations
that we get from INFRA: .asf.yaml, emails sent to specific discussion lists
we
can customize - generally following best practices there.


>
My experience with both Hugo and Pelican is that Hugo is easier to
> customise.
>

Yes we also prefer Hugo. Airflow Summit Website - prepared entirely by the
Software
Guru team - our producers - is based on Hugo, so that would be our
preference as well.

https://github.com/softwareguru/airflowsummit-website


>
> > template repo they recommend for new projects?
> >    https://github.com/apache/template-site
>
> I don't think that is production ready.
>

We have quite a lot of time before our website will be public (at the very
least
3-4 months), so we are ok to take it slowly, follow the right process, and
then
even contribute back and make them more ready - if that would be a good
start,
We are happy to do so. We could eventually also add an "ASF conference
template"
for others and possibly pave the way to follow the same "process" (but I am
usually
of the opinion that in order to make something reusable, you have to make
it usable
first - so that would likely be a next step and we could "lead by
example").


> >
> > No.  AFAIK any direct write access to /apache repos can only come from
> > ASF committers who have signed an ICLA.  But that's solvable for a
> > special case like this, by having an officer or PMC simply agree to
> > invite those outside individuals at Software Guru to be committers here.
> >   Note also that individuals can be made committers, not companies.
>
>
I believe signing ICLA by those individuals from Software Guru is not a
problem at all,
and they will be perfectly happy to act in their "individual" capacity. I
know them personally
very well and I am sure this is not a problem. And on a personal (about
individuals) note -
they are so much personally involved with other Apache conferences
(Airflow, Beam)
and now running the Community Over Code EU, that it would make absolutely
sense to make them committers.

I think it's more of a question - if they are made committers in ComDev,
they will have
access to the main ASF community site, so possibly having a separate
"group"? makes
more sense.

So I think the main question I have now - is it really possible to have it
in comdev?

Or should we (any leads on how?) create a new "group" to manage it.

J.

Re: Setting up Git Project under comdev for Community Over Code EU

Posted by sebb <se...@gmail.com>.
On Sat, 8 Jul 2023 at 00:03, Shane Curcuru <as...@shanecurcuru.org> wrote:
>
> Jarek Potiuk wrote on 7/6/23 4:52 PM:
> ...snip...
> > The conclusion of the discussion we had last week was that we want to get a
> > statically generated website - based on the same tooling and ASF
> > integration tooling as https://github.com/apache/comdev-site is. We will
> > eventually make it available at eu.communityovercode.org and (secondary)
> > goal of that is to make it a nice starting point for future other
> > communityovercode sites (NA one is currently run via wordpress). Some of
> > the committee members are particularly keen on transparency and
> > archiving/inclusivity, so rather than creating a repo outside of ASF (which
> > is an option) we thought the best will be to get a repo in the "apache"
> > organisation.
> >
> >  From the JIRA ticket https://issues.apache.org/jira/browse/INFRA-24741 - if
> > we were to use INFRA supported GitHub repos (under the apache/
> > organisation) we need a "project" to host it and Rich suggested that
> > instead of creating a new one we could do it via comdev.
>
> Yes, any event website source should definitely be stored in an ASF repo
> (i.e. svn or on github under 'apache').
>
> On the infra ticket it was mentioned that VP Conferences could be the
> owner if they created an LDAP group, which is the "most appropriate"
> place to host the content, since the VP Conferences is in charge.  But
> it might be simpler to manage if we used this PMC instead - although
> that requires some consensus from this PMC first to own something that
> really belongs to conferences.
>
> One note: do you *specifically* want to copy the ComDev site repo?  Or
> do you want to start with the infra-supported (but simpler design)

My experience with both Hugo and Pelican is that Hugo is easier to customise.

> template repo they recommend for new projects?
>    https://github.com/apache/template-site

I don't think that is production ready.

>    https://template.staged.apache.org/
>
>
> > We have some specific requirement re: access to the repository. We are not
> > a typical PMC where we have committers and PMC members. We are cooperating
> > with a producer company (Software Guru) and rather than merging their PRs
> > we would rather (especially at the crucial times before the event) want to
> > give them direct "push" access and capability of merging PRs.
> >
> > So my question is:
> >
> > * has something like that been done before?
> > * is this possible for comdev projects to have such repos
> > (apache/comdev-commovercode-eu) with external people access ?
>
> No.  AFAIK any direct write access to /apache repos can only come from
> ASF committers who have signed an ICLA.  But that's solvable for a
> special case like this, by having an officer or PMC simply agree to
> invite those outside individuals at Software Guru to be committers here.
>   Note also that individuals can be made committers, not companies.
>
> --
> - Shane
>    ComDev PMC
>    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: Setting up Git Project under comdev for Community Over Code EU

Posted by Shane Curcuru <as...@shanecurcuru.org>.
Jarek Potiuk wrote on 7/6/23 4:52 PM:
...snip...
> The conclusion of the discussion we had last week was that we want to get a
> statically generated website - based on the same tooling and ASF
> integration tooling as https://github.com/apache/comdev-site is. We will
> eventually make it available at eu.communityovercode.org and (secondary)
> goal of that is to make it a nice starting point for future other
> communityovercode sites (NA one is currently run via wordpress). Some of
> the committee members are particularly keen on transparency and
> archiving/inclusivity, so rather than creating a repo outside of ASF (which
> is an option) we thought the best will be to get a repo in the "apache"
> organisation.
> 
>  From the JIRA ticket https://issues.apache.org/jira/browse/INFRA-24741 - if
> we were to use INFRA supported GitHub repos (under the apache/
> organisation) we need a "project" to host it and Rich suggested that
> instead of creating a new one we could do it via comdev.

Yes, any event website source should definitely be stored in an ASF repo 
(i.e. svn or on github under 'apache').

On the infra ticket it was mentioned that VP Conferences could be the 
owner if they created an LDAP group, which is the "most appropriate" 
place to host the content, since the VP Conferences is in charge.  But 
it might be simpler to manage if we used this PMC instead - although 
that requires some consensus from this PMC first to own something that 
really belongs to conferences.

One note: do you *specifically* want to copy the ComDev site repo?  Or 
do you want to start with the infra-supported (but simpler design) 
template repo they recommend for new projects?
   https://github.com/apache/template-site
   https://template.staged.apache.org/


> We have some specific requirement re: access to the repository. We are not
> a typical PMC where we have committers and PMC members. We are cooperating
> with a producer company (Software Guru) and rather than merging their PRs
> we would rather (especially at the crucial times before the event) want to
> give them direct "push" access and capability of merging PRs.
> 
> So my question is:
> 
> * has something like that been done before?
> * is this possible for comdev projects to have such repos
> (apache/comdev-commovercode-eu) with external people access ?

No.  AFAIK any direct write access to /apache repos can only come from 
ASF committers who have signed an ICLA.  But that's solvable for a 
special case like this, by having an officer or PMC simply agree to 
invite those outside individuals at Software Guru to be committers here. 
  Note also that individuals can be made committers, not companies.

-- 
- Shane
   ComDev PMC
   The Apache Software Foundation


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