Yep. That would be perfect. On Mon, Jul 10, 2023 at 3:29 PM Rich Bowen <rbo...@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 <willem.ji...@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-unsubscr...@community.apache.org > > > For additional commands, e-mail: dev-h...@community.apache.org > > > > > > > > >
