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

[Rich Bowen]

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  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 
> 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  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
> >
> >
>

[jira] [Commented] (COMDEV-326) Committer invite template omits PMC role details

[Shane Curcuru (Jira)]

[ 
https://issues.apache.org/jira/browse/COMDEV-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17741622#comment-17741622
 ] 

Shane Curcuru commented on COMDEV-326:
--

More to the point, this page isn't linked from the "official" PMC guide on how 
to do things like add committers or PMC members, so I'd bet many PMC don't ever 
read it.  A key topic for discussion is how to clearly reconcile - and 
crosslink where relevant - the a.o/dev pages (with explicit guides on how to do 
things) versus any informational content on community.a.o

https://apache.org/dev/pmc.html#newcommitter

> Committer invite template omits PMC role details
> 
>
> Key: COMDEV-326
> URL: https://issues.apache.org/jira/browse/COMDEV-326
> Project: Community Development
>  Issue Type: Bug
>  Components: Website
> Environment: 
> https://community.apache.org/newcommitter.html#committer-invite-template
>Reporter: Sebb
>Priority: Major
>
> The committer invite template [1] is not very clear on the distinction 
> between an invitation as a committer, and invitation as a committer + PMC 
> member.
> In particular, it describes the role of the committer, but largely ignores 
> the PMC role.
> As a result, I have seen at least one acceptance reply that said "I accept to 
> become a committer" [2] - leaving unstated whether or not they agree to 
> become a PMC member.
> I think any template needs to make very clear what is involved in the PMC 
> role, and also that the invitee has 3 choices:
> - decline both invites
> - accept the committer invite and decline the PMC invite
> - accept both committer invite and PMC invite
> [1] https://community.apache.org/newcommitter.html#committer-invite-template
> [2] 
> https://lists.apache.org/thread.html/796c4b3e8c0f191add39c7d1b6cc154a5e316910df8120db1151c739@%3Cprivate.jackrabbit.apache.org%3E



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

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

[Jarek Potiuk]

Yep. That would be perfect.

On Mon, Jul 10, 2023 at 3:29 PM Rich Bowen  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  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 
> > 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  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 uns

[jira] [Closed] (COMDEV-478) https://reporter.apache.org/addrelease.html?sling leads to page crash with Chrome

[Shane Curcuru (Jira)]

 [ 
https://issues.apache.org/jira/browse/COMDEV-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shane Curcuru closed COMDEV-478.

Resolution: Cannot Reproduce

I can't reproduce either on Mac / Chrome {color:#5f6368}Version 114.0.5735.133 
(Official Build) (arm64), and I know some work has been done on reporter since 
this was reported, so... and yes, the page renders with a LOT of past 
releases!{color}

{color:#5f6368}Apologies for the delay and feel free to reopen if needed.{color}

> https://reporter.apache.org/addrelease.html?sling leads to page crash with 
> Chrome
> -
>
> Key: COMDEV-478
> URL: https://issues.apache.org/jira/browse/COMDEV-478
> Project: Community Development
>  Issue Type: Bug
>  Components: Reporter Tool
> Environment: Chrome Version 104.0.5112.101 (Official Build) (arm64)
> Mac OS 12.5.1
>Reporter: Konrad Windszus
>Priority: Major
>
> When opening the page [https://reporter.apache.org/addrelease.html?sling] it 
> crashes in Google Chrome after a few seconds with Error Code 5 
> ([https://support.google.com/chrome/answer/95669?visit_id=637966697117475835-2175500643&p=e_awsnap&rd=1#zippy=%2Cpage-loading-error-codes-and-issues]).
> With Firefox it does load (but takes a while).
> I assume this is due to the huge amount of past releases done by Sling.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Closed] (COMDEV-423) svn pubsub fallen over on apachecon.com

[Shane Curcuru (Jira)]

 [ 
https://issues.apache.org/jira/browse/COMDEV-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shane Curcuru closed COMDEV-423.

Resolution: Cannot Reproduce

It's Community Over Code, now! :)

> svn pubsub fallen over on apachecon.com
> ---
>
> Key: COMDEV-423
> URL: https://issues.apache.org/jira/browse/COMDEV-423
> Project: Community Development
>  Issue Type: Task
>  Components: Website
>Reporter: Rich Bowen
>Priority: Major
>
> Updates to svn are no longer being reflected on 
> [www.apachecon.com|http://www.apachecon.com/] 
> Can someone please kick svnpubsub? Thanks.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Re: Community-run MVP programs at the ASF

[Melissa Logan]

I've been on bereavement leave for the past two weeks, hence the radio
silence. I will be reading and replying to feedback this week.

On Fri, Jun 23, 2023 at 2:20 AM Roman Shaposhnik 
wrote:

> On Thu, Jun 22, 2023 at 1:39 AM Phil Steitz  wrote:
> >
> > On Wed, Jun 21, 2023 at 12:57 PM Mark Thomas  wrote:
> >
> > > On 21/06/2023 19:57, Jeff Jirsa wrote:
> > > > Member of the cassandra PMC, but responding here individually. I'm
> not
> > > actually sure I actually support the idea of an MVP program, but do
> want to
> > > point out that "PMC" has other special meaning:
> > > >
> > > > - A member of the PMC is (or at least was, and if it's changed, I
> missed
> > > it) strictly required to be a committer. We've had threads in the past
> > > about whether or not there was room for flexibility, and structurally
> the
> > > answer was no. That's a problem because:
> > > >
> > > > - Committer requires signing an ICLA. That's a problem because:
> > > >
> > > > - Not all community members CAN sign an ICLA. Some are prevented from
> > > doing so by employment restrictions or other legal requirements. So
> even if
> > > it were the case that SOMEONE might be the type of contributor who a
> > > project WOULD make a member of the PMC, some individuals CAN NOT accept
> > > that.
> > >
> > > Yes, that is an issue. It would be interesting to get some numbers on
> > > how often that happens and whether there is anything the ASF can do to
> > > help reduce the frequency - e.g. engagement with employers. Probably a
> > > topic for a separate thread.
> > >
> > > Regardless, it is pretty much inevitable given the size of the ASF that
> > > there will be some people that can't sign the ICLA and that is an issue
> > > worth trying to address.
> > >
> > > Note: Projects can invite whoever they like to join their private list.
> > > It would be unusual but I can't think of any reason a project couldn't
> > > have honorary PMC members (or similar name), subscribed to the private
> > > list and their voices listened to as if there were PMC members - the
> > > only difference being they would not be listed in committee-info.txt
> and
> > > their votes would not be binding.
> > >
> > > > Beyond that:
> > > >
> > > > The PMC is permanent, irrevocable, and binding.
> > >
> > > Not quite. There are ways to remove bad actors from a PMC if necessary.
> > >
> > > > There are existence proofs of single bad actors  on the PMC
> effectively
> > > blowing up projects (I will show them to you if needed, but PMC
> members who
> > > veto every single action and lead other contributors to fork).
> > >
> > > Been there. Got the t-shirt. Several times. And I hope I never have to
> > > go there again. It is never pretty, always stressful and damages the
> > > community. That it is rare is both good and bad. It is good it doesn't
> > > happen often but the downside is there is relatively little experience
> > > of dealing with it to draw on if you find yourself in that situation.
> > >
> > > > "This person is doing cool things to help the community THIS YEAR" is
> > > not the same as "please be a driving force of the project forever".
> > >
> > > While there are bad actors, there represent a very small faction of the
> > > community. I'd argue there is a greater risk of harm to the community
> by
> > > having high bars for committership and PMC membership and excluding
> > > folks than there is by having low bars and accepting the risk of a bad
> > > actor.
> > >
> > > > On a personal level, I started working with Cassandra to solve a
> problem
> > > at work, but I kept working on it because some company I had never
> heard of
> > > sent me an email and a t-shirt that said MVP on it. I was nowhere NEAR
> the
> > > level of contributions you'd need to be a committer, much less a
> member of
> > > the PMC (a conference talk and a couple emails, no code contributed at
> > > all). It was a nice marketing gesture for the project, and probably
> for the
> > > company (maybe they assumed my employer would turn into a paying
> customer,
> > > which definitely wasnt going to happen).
> > >
> > > I think there is plenty of room for that sort of contributor
> > > appreciation. Putting on my VP Brand hat for a minute, I have approved
> > > companies producing project branded swag for exactly this purpose. The
> > > main concern is making sure it is community swag rather than corporate
> > > swag.
> > >
> > > > All of that said: it feels weird. I can argue about why it's good and
> > > important. It still feels weird. Emotionally, I don't love the idea,
> but we
> > > also don't want affiliated companies running programs that may be
> > > misconstrued as acting for the (trademarked) brand, and that's the
> typical
> > > place you'd see a program like this. Microsoft has MVPs. AWS has
> community
> > > heroes. Apache projects  have merit within the project and within
> the
> > > foundation, but again, permanent, binding, and requires contracts.
> > >
> > > It 

Re: Reviewers Needed for Community Over Code NA Community Track

[Sharan Foga]

Hi Kelly

Thanks for the offering to help with the Community track reviews. Unfortunately 
we have enough reviewers so are not accepting any more. Perhaps you can help 
out next time.

Thanks
Sharan

On 2023/07/09 19:28:06 Kelly Oglesbee wrote:
> Can I volunteer
> 
> 
> On Sun, Jul 9, 2023, 12:34 PM Sharan Foga  wrote:
> 
> > Hi Priya
> >
> > Thanks for volunteering - I will add you to the list.
> >
> > Thanks
> > Sharan
> >
> > On 2023/07/03 12:58:49 Priya Sharma wrote:
> > > Hey Sharan,
> > > Please count me in if you still need more volunteers.
> > >
> > > On Thu, 29 Jun 2023 at 01:05, Sharan Foga  wrote:
> > >
> > > > Thanks Daniel - Accepted! (And which district do you represent :-)
> > > >
> > > > On 2023/06/28 19:28:03 Daniel Gruno wrote:
> > > > > On 2023-06-28 20:28, sharanf wrote:
> > > > > > Hi Everyone
> > > > > >
> > > > > > It's coming up to that time again... The CFP for Community Over
> > Code
> > > > > > North America will be closing soon (on 13th July to be precise!)
> > and
> > > > we
> > > > > > are now looking for some volunteers to help us review the
> > proposals.
> > > > One
> > > > > > thing we are currently asking of the track reviewers is that they
> > are
> > > > > > not planning to make a submission to the track they are reviewing.
> > > > > >
> > > > > > If you are interested in helping out and haven't made a submission
> > to
> > > > > > the Community track then please respond.
> > > > >
> > > > > I volunteer as tribute!
> > > > >
> > > > > >
> > > > > > Thanks
> > > > > > Sharan
> > > > > >
> > > > > >
> > -
> > > > > > 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
> > > > >
> > > > >
> > > >
> > > > -
> > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > > For additional commands, e-mail: dev-h...@community.apache.org
> > > >
> > > >
> > >
> > > --
> > > Best Regards,
> > > Priya
> > >
> >
> > -
> > 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

Re: Reviewers Needed for Community Over Code NA Community Track

[Sharan Foga]

Hi Brahma

Thanks for offering but we've got enough volunteer reviewers for the Community 
track. Maybe you can help us out next time.

Thanks
Sharan

On 2023/07/10 02:39:10 Brahma Reddy Battula wrote:
> Hey sharan,
> 
> Consider me if you still need.
> 
> 
> 
> 
> On Mon, 10 Jul 2023 at 12:58 AM, Kelly Oglesbee 
> wrote:
> 
> > Can I volunteer
> >
> >
> > On Sun, Jul 9, 2023, 12:34 PM Sharan Foga  wrote:
> >
> > > Hi Priya
> > >
> > > Thanks for volunteering - I will add you to the list.
> > >
> > > Thanks
> > > Sharan
> > >
> > > On 2023/07/03 12:58:49 Priya Sharma wrote:
> > > > Hey Sharan,
> > > > Please count me in if you still need more volunteers.
> > > >
> > > > On Thu, 29 Jun 2023 at 01:05, Sharan Foga  wrote:
> > > >
> > > > > Thanks Daniel - Accepted! (And which district do you represent :-)
> > > > >
> > > > > On 2023/06/28 19:28:03 Daniel Gruno wrote:
> > > > > > On 2023-06-28 20:28, sharanf wrote:
> > > > > > > Hi Everyone
> > > > > > >
> > > > > > > It's coming up to that time again... The CFP for Community Over
> > > Code
> > > > > > > North America will be closing soon (on 13th July to be precise!)
> > > and
> > > > > we
> > > > > > > are now looking for some volunteers to help us review the
> > > proposals.
> > > > > One
> > > > > > > thing we are currently asking of the track reviewers is that they
> > > are
> > > > > > > not planning to make a submission to the track they are
> > reviewing.
> > > > > > >
> > > > > > > If you are interested in helping out and haven't made a
> > submission
> > > to
> > > > > > > the Community track then please respond.
> > > > > >
> > > > > > I volunteer as tribute!
> > > > > >
> > > > > > >
> > > > > > > Thanks
> > > > > > > Sharan
> > > > > > >
> > > > > > >
> > > -
> > > > > > > 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
> > > > > >
> > > > > >
> > > > >
> > > > > -
> > > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > > > For additional commands, e-mail: dev-h...@community.apache.org
> > > > >
> > > > >
> > > >
> > > > --
> > > > Best Regards,
> > > > Priya
> > > >
> > >
> > > -
> > > 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

Re: Reviewers Needed for Community Over Code NA Community Track

[Kelly Oglesbee]

How will I know when to start?

On Mon, Jul 10, 2023, 3:38 PM Sharan Foga  wrote:

> Hi Brahma
>
> Thanks for offering but we've got enough volunteer reviewers for the
> Community track. Maybe you can help us out next time.
>
> Thanks
> Sharan
>
> On 2023/07/10 02:39:10 Brahma Reddy Battula wrote:
> > Hey sharan,
> >
> > Consider me if you still need.
> >
> >
> >
> >
> > On Mon, 10 Jul 2023 at 12:58 AM, Kelly Oglesbee <
> humbleoppurtun...@gmail.com>
> > wrote:
> >
> > > Can I volunteer
> > >
> > >
> > > On Sun, Jul 9, 2023, 12:34 PM Sharan Foga  wrote:
> > >
> > > > Hi Priya
> > > >
> > > > Thanks for volunteering - I will add you to the list.
> > > >
> > > > Thanks
> > > > Sharan
> > > >
> > > > On 2023/07/03 12:58:49 Priya Sharma wrote:
> > > > > Hey Sharan,
> > > > > Please count me in if you still need more volunteers.
> > > > >
> > > > > On Thu, 29 Jun 2023 at 01:05, Sharan Foga 
> wrote:
> > > > >
> > > > > > Thanks Daniel - Accepted! (And which district do you represent
> :-)
> > > > > >
> > > > > > On 2023/06/28 19:28:03 Daniel Gruno wrote:
> > > > > > > On 2023-06-28 20:28, sharanf wrote:
> > > > > > > > Hi Everyone
> > > > > > > >
> > > > > > > > It's coming up to that time again... The CFP for Community
> Over
> > > > Code
> > > > > > > > North America will be closing soon (on 13th July to be
> precise!)
> > > > and
> > > > > > we
> > > > > > > > are now looking for some volunteers to help us review the
> > > > proposals.
> > > > > > One
> > > > > > > > thing we are currently asking of the track reviewers is that
> they
> > > > are
> > > > > > > > not planning to make a submission to the track they are
> > > reviewing.
> > > > > > > >
> > > > > > > > If you are interested in helping out and haven't made a
> > > submission
> > > > to
> > > > > > > > the Community track then please respond.
> > > > > > >
> > > > > > > I volunteer as tribute!
> > > > > > >
> > > > > > > >
> > > > > > > > Thanks
> > > > > > > > Sharan
> > > > > > > >
> > > > > > > >
> > > > -
> > > > > > > > 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
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> -
> > > > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > > > > For additional commands, e-mail: dev-h...@community.apache.org
> > > > > >
> > > > > >
> > > > >
> > > > > --
> > > > > Best Regards,
> > > > > Priya
> > > > >
> > > >
> > > > -
> > > > 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
>
>

Simple question: Project blogs

[Brian Proffitt]

Simply put, if I want to direct people to Apache project's blogs, I would
send them to... where?

The answer should be a URL(s).

Thanks!
BKP

Re: Simple question: Project blogs

[B C]

I wouldn't send them to the Apache projects.
Infact I would tell them to run the other direction.

Get Outlook for Android

From: Brian Proffitt 
Sent: Monday, July 10, 2023 5:13:17 PM
To: dev@community.apache.org 
Subject: Simple question: Project blogs

Simply put, if I want to direct people to Apache project's blogs, I would
send them to... where?

The answer should be a URL(s).

Thanks!
BKP