Re: It’s time to change the name

[Andrew Musselman]

Speaking as someone in the Pacific Northwest US, where we say land
acknowledgement for the Duwamish tribe at the beginning of all school
events, meaning I respect and understand the motivation for this:

I think simply opening this up for a member vote will result in an
unproductive firefight. Reactions will range from enthusiastic sympathy to
bewildered annoyance to outright hostile accusations.

Can I propose an outreach to some Apache tribe governments so we can open a
dialog with them directly, and start to understand what their official
experience of the ASF branding is?

Then we could formulate a plan after some deliberation.

The plan could include logo redesign if the feather symbol is viewed as
insensitive, for example, and other changes balanced with feasibility and
community values.

Best
Andrew

On Fri, Apr 29, 2022 at 6:29 AM me  wrote:

> @Christian
>
> You’re very welcome! I think an internal poll has a great way of defining
> footholds. It’s going to be hard to craft to avoid confirmation bias, but I
> think it’s definitely possible.
>
> @Matt
>
> I agree. There is no doubt that this is something that would require
> stages. Approaching this “Big Bang” style is going to fail pretty quickly.
> I’m thinking the effort is going to be an amalgam of the Washington
> Redskins -> Commanders effort + the migration from JUnit 4 to 5. This
> definitely hits on the “strategic” aspect of Sam’s initial questions.
>
> I think we can probably differentiate a brand change and a name change as
> separate efforts (or at the very least separate life cycles). Large
> organizations that acquire startups and small companies often rebrand the
> acquired assets and their products to better fit their business/tech
> strategy. However, underlying assets (repos, docs, materials) are retrofit
> at a slower burn.
>
>
> I think the first action item is probably a poll. I’m happy to pair/mob
> (virtually or otherwise) on it with someone. Are there any particular
> psychometrics we’d like to leverage (i.e. Likert?)
>
> @Walter, do you want to take a first stab at a poll? Maybe we can put
> together a small tiger team to carry it out?
>
>
>
>
> From: Matt Sicker 
> Reply: dev@community.apache.org 
> Date: April 28, 2022 at 18:45:07
> To: dev@community.apache.org 
> Subject:  Re: It’s time to change the name
>
> Defining a scope here is also fairly important. For example, the
> apache.org domain name is fairly baked into a lot of unchangeable
> places such as Java package names, every single released artifact, the
> software license itself (which is used by tons of people outside of
> ASF), all the existing public URLs to things, email addresses, signing
> keys, the GitHub organization name, tons of infrastructure
> configuration, finance documents, corporate documents, trademarks, and
> surely other areas I'm forgetting.
>
> If we have a name change and only update the places where it's easy to
> do so, the name Apache will still be highly visible in tons of key
> areas for the indefinite future. This isn't even considering
> downstream users of Apache software, either, who may or may not adopt
> a rename. These are some of the fairly intractable concerns I've had
> about a name change, and that's even after working with another OSS
> project that went through a name change and still has tons of
> references to its old names due to compatibility issues.
>
> On Thu, Apr 28, 2022 at 3:49 PM Christian Grobmeier
>  wrote:
> >
> >
> > On Thu, Apr 28, 2022, at 22:19, me wrote:
> > > Christian,
> > >
> > > Were you thinking of an internal poll? That’s actually a spectacular
> idea.
> >
> > Yes, that was I was thinking. Basically a poll on members@, since (I
> guess) members would eventually decide on that proposal.
> >
> > >
> > > How do we go about kicking that off?
> >
> > I am not so sure either, but I guess writing the poll and proposing it
> to community@ would be a first step. Once decided on the content we could
> vote on sending it, and then send it to members@
> >
> > Others may have different ideas, but that is my first idea on it.
> >
> > Thanks for calling my idea spectacular, it gives me a warm feeling,
> since I didn't think of it as such :)
> >
> > Kind regards,
> > Christian
> >
> > >
> > >
> > > Ed Mangini
> > > m...@emangini.com
> > >
> > >
> > > From: Christian Grobmeier 
> > > Reply: dev@community.apache.org 
> > > Date: April 28, 2022 at 15:43:04
> > > To: dev@community.apache.org 
> > > Subject: Re: It’s time to change the name
> > >
> > >>
> > >> Hello,
> > >>
> > >>
> > >> On Thu, Apr 28, 2022, at 20:57, me wrote:
> > >> > The desire to make the change is definitely there. I echo Walter’s
> > >> > passion and statements.
> > >>
> > >> +1
> > >> > I also agree w/ Sam that this isn’t going to be easy to
> accomplish.
> > >>
> > >> +1
> > >>
> > >> > Perhaps a starting point would be to answer these questions in
> concert:
> > >> > - what is the LOE to perform the rebranding/renaming?
> > >> > - are there eno

Re: It’s time to change the name

[Andrew Musselman]

On Fri, Apr 29, 2022 at 8:28 AM me  wrote:

> Andrew,
>
> I agree that putting it to a member vote is possibly polarizing (and
> premature).  That’s not really the intent here. A poll is a dipstick effort
> to check the temperature before we reach strategy and tactics. Polling is
> more about discovery.
>

I think you'll get a similar reaction from a poll.


> I’m all for the outreach. For my own clarification, are you looking at
> this as a means of defining boundaries on the effort, setting urgency on
> the efforts (or some combination of both?)
>

I think this is such an expansive and encompassing topic that covers almost
every aspect of the operations of the foundation that it might be smart for
the board to have a look and build up a plan before doing any ad hoc
outreach.

Is this something you’re willing to do or kick off?
>

I personally don't have bandwidth to participate in activities on this, no.


> Is there any reason why we can’t move forward with both a poll and
> outreach?
>

Again I think this is a board decision but I am not a lawyer.


>
>
>
>
>
>
>
> From: Andrew Musselman 
> Reply: dev@community.apache.org 
> Date: April 29, 2022 at 10:14:05
> To: dev@community.apache.org 
> Cc: Matt Sicker 
> Subject:  Re: It’s time to change the name
>
> Speaking as someone in the Pacific Northwest US, where we say land
> acknowledgement for the Duwamish tribe at the beginning of all school
> events, meaning I respect and understand the motivation for this:
>
> I think simply opening this up for a member vote will result in an
> unproductive firefight. Reactions will range from enthusiastic sympathy
> to
> bewildered annoyance to outright hostile accusations.
>
> Can I propose an outreach to some Apache tribe governments so we can open
> a
> dialog with them directly, and start to understand what their official
> experience of the ASF branding is?
>
> Then we could formulate a plan after some deliberation.
>
> The plan could include logo redesign if the feather symbol is viewed as
> insensitive, for example, and other changes balanced with feasibility and
> community values.
>
> Best
> Andrew
>
> On Fri, Apr 29, 2022 at 6:29 AM me  wrote:
>
> > @Christian
> >
> > You’re very welcome! I think an internal poll has a great way of
> defining
> > footholds. It’s going to be hard to craft to avoid confirmation bias,
> but I
> > think it’s definitely possible.
> >
> > @Matt
> >
> > I agree. There is no doubt that this is something that would require
> > stages. Approaching this “Big Bang” style is going to fail pretty
> quickly.
> > I’m thinking the effort is going to be an amalgam of the Washington
> > Redskins -> Commanders effort + the migration from JUnit 4 to 5. This
> > definitely hits on the “strategic” aspect of Sam’s initial questions.
> >
> > I think we can probably differentiate a brand change and a name change
> as
> > separate efforts (or at the very least separate life cycles). Large
> > organizations that acquire startups and small companies often rebrand
> the
> > acquired assets and their products to better fit their business/tech
> > strategy. However, underlying assets (repos, docs, materials) are
> retrofit
> > at a slower burn.
> >
> >
> > I think the first action item is probably a poll. I’m happy to pair/mob
> > (virtually or otherwise) on it with someone. Are there any particular
> > psychometrics we’d like to leverage (i.e. Likert?)
> >
> > @Walter, do you want to take a first stab at a poll? Maybe we can put
> > together a small tiger team to carry it out?
> >
> >
> >
> >
> > From: Matt Sicker 
> > Reply: dev@community.apache.org 
> > Date: April 28, 2022 at 18:45:07
> > To: dev@community.apache.org 
> > Subject: Re: It’s time to change the name
> >
> > Defining a scope here is also fairly important. For example, the
> > apache.org domain name is fairly baked into a lot of unchangeable
> > places such as Java package names, every single released artifact, the
> > software license itself (which is used by tons of people outside of
> > ASF), all the existing public URLs to things, email addresses, signing
> > keys, the GitHub organization name, tons of infrastructure
> > configuration, finance documents, corporate documents, trademarks, and
> > surely other areas I'm forgetting.
> >
> > If we have a name change and only update the places where it's easy to
> > do so, the name Apache will still be highly visible in tons of key
> > areas for the indefinite future. This isn't even

Re: It’s time to change the name

[Andrew Musselman]

Copying them now.

On Fri, Apr 29, 2022 at 9:46 AM me  wrote:

> @Andrew,
>
> How do we engage the board?
>
>
> Ed Mangini
> m...@emangini.com
>
>
> From: Andrew Musselman 
> Reply: dev@community.apache.org 
> Date: April 29, 2022 at 12:44:28
> To: dev@community.apache.org 
> Subject:  Re: It’s time to change the name
>
> On Fri, Apr 29, 2022 at 8:28 AM me  wrote:
>
> > Andrew,
> >
> > I agree that putting it to a member vote is possibly polarizing (and
> > premature). That’s not really the intent here. A poll is a dipstick
> effort
> > to check the temperature before we reach strategy and tactics. Polling
> is
> > more about discovery.
> >
>
> I think you'll get a similar reaction from a poll.
>
>
> > I’m all for the outreach. For my own clarification, are you looking at
> > this as a means of defining boundaries on the effort, setting urgency
> on
> > the efforts (or some combination of both?)
> >
>
> I think this is such an expansive and encompassing topic that covers
> almost
> every aspect of the operations of the foundation that it might be smart
> for
> the board to have a look and build up a plan before doing any ad hoc
> outreach.
>
> Is this something you’re willing to do or kick off?
> >
>
> I personally don't have bandwidth to participate in activities on this,
> no.
>
>
> > Is there any reason why we can’t move forward with both a poll and
> > outreach?
> >
>
> Again I think this is a board decision but I am not a lawyer.
>
>
> >
> >
> >
> >
> >
> >
> >
> > From: Andrew Musselman 
> > Reply: dev@community.apache.org 
> > Date: April 29, 2022 at 10:14:05
> > To: dev@community.apache.org 
> > Cc: Matt Sicker 
> > Subject: Re: It’s time to change the name
> >
> > Speaking as someone in the Pacific Northwest US, where we say land
> > acknowledgement for the Duwamish tribe at the beginning of all school
> > events, meaning I respect and understand the motivation for this:
> >
> > I think simply opening this up for a member vote will result in an
> > unproductive firefight. Reactions will range from enthusiastic sympathy
> > to
> > bewildered annoyance to outright hostile accusations.
> >
> > Can I propose an outreach to some Apache tribe governments so we can
> open
> > a
> > dialog with them directly, and start to understand what their official
> > experience of the ASF branding is?
> >
> > Then we could formulate a plan after some deliberation.
> >
> > The plan could include logo redesign if the feather symbol is viewed as
> > insensitive, for example, and other changes balanced with feasibility
> and
> > community values.
> >
> > Best
> > Andrew
> >
> > On Fri, Apr 29, 2022 at 6:29 AM me  wrote:
> >
> > > @Christian
> > >
> > > You’re very welcome! I think an internal poll has a great way of
> > defining
> > > footholds. It’s going to be hard to craft to avoid confirmation bias,
> > but I
> > > think it’s definitely possible.
> > >
> > > @Matt
> > >
> > > I agree. There is no doubt that this is something that would require
> > > stages. Approaching this “Big Bang” style is going to fail pretty
> > quickly.
> > > I’m thinking the effort is going to be an amalgam of the Washington
> > > Redskins -> Commanders effort + the migration from JUnit 4 to 5. This
> > > definitely hits on the “strategic” aspect of Sam’s initial questions.
> > >
> > > I think we can probably differentiate a brand change and a name
> change
> > as
> > > separate efforts (or at the very least separate life cycles). Large
> > > organizations that acquire startups and small companies often rebrand
> > the
> > > acquired assets and their products to better fit their business/tech
> > > strategy. However, underlying assets (repos, docs, materials) are
> > retrofit
> > > at a slower burn.
> > >
> > >
> > > I think the first action item is probably a poll. I’m happy to
> pair/mob
> > > (virtually or otherwise) on it with someone. Are there any particular
> > > psychometrics we’d like to leverage (i.e. Likert?)
> > >
> > > @Walter, do you want to take a first stab at a poll? Maybe we can put
> > > together a small tiger team to carry it out?
> > >
> > >
> > >
> > >
> > > From: Matt Sicker 
> > > Reply: dev@community.apache.org 

Re: Request for sharing ASF's "Way of Working"

[Andrew Musselman]

Hi Guido, thanks for your note.

Can you tell us more about why things aren't working so far?



On Fri, Mar 3, 2017 at 1:09 AM, Guido Serra  wrote:

> Hi,
> at my current employer we are trying to define the Way of Working.
>
> The company is distributed across 3 major timezones, 4/5h aparts from each
> others.
> We do have multiple projects and we are trying to define a model of
> ownership
> to have lead developers or teams associated to them, responsible to
> maintain their repos.
>
> I really would like to know more about the Apache Software Foundation
> model,
> it would be great if you could share more about its internal way of
> working.
>
> Specially about use cases of people that already attempted to introduce it
> in
> corporation environments, and the success (or failures) of those attempts.
>
> Regards,
> Guido Serra aka Zeph, FSFE Fellow
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: Apache Climate Contribution

[Andrew Musselman]

Hi Prateek, have you reached out on the Climate dev mailing list? Looks
like there were several months between the last activity on Jira, might
make sense to check in on the list.

Also, does your fix work? Most projects would prefer a test to be checked
in along with any new feature or fix.

Best
Andrew

On Fri, Jun 1, 2018 at 2:22 AM Prateek Chanda 
wrote:

> Hi,
>
>   I have just been introducing myself to Apache Climate for the past few
> weeks and just got started on working on an open issue on Climate issue
> tracker [*id 803]. *The issue deals with handling arrays for datasets which
> are not masked ones, otherwise they will throw an exception and the tests
> will fail.
>
> I have opened one Pull Request for this  CLIMATE - 803 Initial Stucture for
> Handling mask for non-masked arrays #506
> 
>
>
> I would like to know if the approach is fine and would love if some one can
> guide me through.
>
> Regards,
>
> Prateek Chanda
> Apache Climate Contributor
>

Re: Join Apache Community Mailing List

[Andrew Musselman]

Hi Debanjan, the typical way to get involved is to start working with 
specific projects; you could look at open bugs and subscribe to the 
user and dev mailing lists for Kafka, HDFS, etc., and offer your help 
there.


Thanks and good luck!

On Sun, Jul 15, 2018 at 11:23 PM, Debanjan Dhar 
 wrote:

Hello,


I am interested in joining the apache community ( Apache Software 
Foundation ) as a developer.


Myself, Debanjan Dhar, is a 2 year working professional in IT 
industry and have worked on multiple Apache Hadoop Softwares like 
kafka, HDFS, YARN etc.


Please let me know if if any information required for joining the 
community. I will be happy to share any requisite details.




Regards,
Debanjan Dhar

Re: Need help in enabling SAML auth in Apache Knox

[Andrew Musselman]

Hi Praveen, you could get in touch with the Knox team using their 
mailing lists instead of this one:


https://knox.apache.org/mail-lists.html

Good luck!

On Mon, Jul 16, 2018 at 9:58 AM, Ravikumar, Praveen Krishnamoorthy 
 wrote:

Hi,
I'm Praveen. I'm working on POC to setup Apache Knox on the master 
node of an EMR cluster for our client. With the help of 
documentations I was able to install KNOX successfully and was able 
to run few tests. Currently I'm facing an issue on enabling SAML 
authentication, which I'm kind of blocked and I don’t know, how to 
proceed or troubleshoot the issue. I have provided few details 
regarding the issue and I would love to provide more if needed.


Could anyone help me in this, would be very helpful for me to proceed 
further.


TASK:
-
To enable SAML authentication for Apache Knox.

NOTE: Apache Knox is installed and running in port 8446

STEP 1: SSO request initiation.
***
- Our client uses PING Federate Identity provider.
- raised a request to register the application for SSO access.
Entity ID - 
https://:8446/gateway/knoxsso/api/v1/websso?pac4jCallback=true&client_name=SAML2Client
Target URL - https://:8446(I'm not sure the target 
URL is valid, I suspect the page is getting redirected to this link 
after auth)

- I received a IDP metadata.xml and certificate.

STEP 2: Topology config
***

KnoxSSO.xml


   
 
 federation
 pac4j
 true
 
  pac4j.callbackUrl
  
https://:8446/gateway/knoxsso/api/v1/websso

 
 
   clientName
   SAML2Client
 
 
   saml.identityProviderMetadataPath
   /tmp/preprod_metadata_SP.xml
 
 
   saml.serviceProviderMetadataPath
   /tmp/preprod_metadata_SP.xml
 
 
   saml.serviceProviderEntityId
   
https://:8446/gateway/knoxsso/api/v1/websso?pac4jCallback=true&client_name=SAML2Client

 
 
 
 identity-assertion
 Default
 true
 
   
   
   KNOXSSO
   
 knoxsso.cookie.secure.only
 true
  
  
knoxsso.token.ttl
10
  
  
 knoxsso.redirect.whitelist.regex
 
^https?:\/\/(emr-knox-webui-dev\.us-west-2\.elb\.amazonaws\.com|localhost|127\.0\.0\.1|0:0:0:0:0:0:0:1|::1):[0-9].*$

  
   


gate1.xml
-


  

federation
SSOCookieProvider
true

sso.authentication.provider.url

https://:8446/gateway/knoxsso/api/v1/websso




identity-assertion
Default
true

  
  
  YARNUI
  http://:8088
  



PROBLEM:

on accessing the YarnUI (firefox browser) after starting the gateway, 
The browser gets redirected to the Identity provider URL -> asks for 
the login credentials -> on submitting the user is getting 
authenticated but the application gets landed to 
https://:8446 and throws page not found error.
I'm seeing the SAML request sent and SAML response getting received 
but it gets landed to an invalid page after authentication. I'm 
unable to figure out the page to land after authentication.



Hope I have provided the required details. please do let me know if 
you need any additional details.


Thanks,
Praveen.

Re: [ANNOUNCE] Welcome Trevor Grant as a new PMC member

[Andrew Musselman]

Well deserved, congrats!

On Fri, Sep 28, 2018 at 11:21 AM Andrew Palumbo  wrote:

> Congratulations Trevor
>

Roadshow Brazil

[Andrew Musselman]

I was just chatting with Trevor Grant at the Roadshow in Chicago and heard
there might be plans to run one in Brazil; if there's anything I can to do
help please let me know.

We have a small team in Sao Paulo who could be a good resource for planning
and communications.

Best
Andrew

Roadshow Seattle

[Andrew Musselman]

If there's any interest in putting one on in Seattle I'd love to organize
one.

I believe have a lot of Apache folks in town and it would be a great excuse
to get them together.

Best
Andrew

Re: Roadshow Seattle

[Andrew Musselman]

Awesome, thanks for the feedback; I'll look at how to kick off planning.
Any ideas for getting the word out and checking interest levels across
local companies/projects?

On Tue, May 14, 2019 at 11:52 AM Kevin A. McGrail 
wrote:

> On 5/14/2019 2:30 PM, Aizhamal Nurmamat kyzy wrote:
> > I think Seattle would be a great place to host one. I’d be there to help
> if
> > it gets traction, Andrew.
>
> Same and I told him in person I would help.
>
> --
> Kevin A. McGrail
> Member, Apache Software Foundation
> Chair Emeritus Apache SpamAssassin Project
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: Roadshow Brazil

[Andrew Musselman]

Thanks for the link Henk; we are doing one here in Chicago this evening.

On Tue, May 14, 2019 at 12:47 PM Henk P. Penning  wrote:

> On Tue, 14 May 2019, Andrew Musselman wrote:
>
> > Date: Tue, 14 May 2019 18:13:39 +0000
> > From: Andrew Musselman 
> > To: dev@community.apache.org
> > Subject: Roadshow Brazil
> >
> > I was just chatting with Trevor Grant at the Roadshow in Chicago and
> heard
> > there might be plans to run one in Brazil; if there's anything I can to
> do
> > help please let me know.
>
> Hi Andrew,
>
>Please organise a key singing-party :
>
>  https://mirror-vm.apache.org/~henkp/sig/key-signing-party.htmlAt
>
>At least, all Apache people shoud be connected.
>
> > We have a small team in Sao Paulo who could be a good resource for
> planning
> > and communications.
>
> > Andrew
>
>Henk Penning
>
>    _
> Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
> Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
> Leuvenlaan 4, 3584CE Utrecht, NL  F +31 30 253 4553 \_/ \_/
> http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: Roadshow Seattle

[Andrew Musselman]

Aha great; yeah I'm in Seattle, looking forward to getting together.

Best
Andrew

On Tue, May 14, 2019 at 1:20 PM Kevin A. McGrail 
wrote:

> Hah, I was just about to say ask Ross as step 1.
>
> On Tue, May 14, 2019, 15:08 Ross Gardler  wrote:
>
> > Wearing my Microsoft hat, you have Microsoft engaged.
> >
> > Wearing my ASF hat I can help with reaching local companies. But before
> we
> > start reaching out let's decide what kind of event we want. I've been
> > planning to do something for some time and would love to link up with you
> > on it. There is a good chance that you and I are thinking of different
> > events ;-)
> >
> > Are you local do Seattle? If so let's have a coffee (with anyone
> > available) figure out if we are sufficiently aligned and come back with a
> > proposal.
> >
> > Ross
> >
> > Get Outlook for Android<https://aka.ms/ghei36>
> >
> > 
> > From: Andrew Musselman 
> > Sent: Tuesday, May 14, 2019 12:51:49 PM
> > To: dev@community.apache.org
> > Subject: Re: Roadshow Seattle
> >
> > Awesome, thanks for the feedback; I'll look at how to kick off planning.
> > Any ideas for getting the word out and checking interest levels across
> > local companies/projects?
> >
> > On Tue, May 14, 2019 at 11:52 AM Kevin A. McGrail 
> > wrote:
> >
> > > On 5/14/2019 2:30 PM, Aizhamal Nurmamat kyzy wrote:
> > > > I think Seattle would be a great place to host one. I’d be there to
> > help
> > > if
> > > > it gets traction, Andrew.
> > >
> > > Same and I told him in person I would help.
> > >
> > > --
> > > Kevin A. McGrail
> > > Member, Apache Software Foundation
> > > Chair Emeritus Apache SpamAssassin Project
> > >
> >
> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.linkedin.com%2Fin%2Fkmcgrail&data=02%7C01%7C%7C40acb850e14543105c4b08d6d8a5a634%7C84df9e7fe9f640afb435%7C1%7C0%7C636934603295131190&sdata=LvU2y2uf5fiGi3I3kOQF9E%2BgrXM2cw6f%2BOHJ5XgS%2B50%3D&reserved=0
> > - 703.798.0171
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > For additional commands, e-mail: dev-h...@community.apache.org
> > >
> > >
> >
>

Re: Roadshow Seattle

[Andrew Musselman]

Thanks Trev.

Absolutely Aizhamal, anyone else interested in helping in any way please
let us know.

Downtown seemed good since Fremont is a quick trip from Google and there
are so many HQs in SLU. Or maybe that fancy Starbucks in Cap Hill; lots of
big tables there.

Looking forward to it; tentatively look at next week or the following?

On Wed, May 15, 2019 at 07:12 Trevor Grant  wrote:

> I also told him in person I would support w learnings from Chicago.
>
>
>
> On Wed, May 15, 2019 at 2:29 AM Ross Gardler  wrote:
>
> > Will do, Andrew and I decided we'll meet downtown for a chat. No time set
> > yet. Then come back here with a proposal. If anyone else wants to join us
> > for coffee drop us a note offlist (keep organizational noise down).
> >
> > Get Outlook for Android<https://aka.ms/ghei36>
> >
> > 
> > From: Aizhamal Nurmamat kyzy 
> > Sent: Wednesday, May 15, 2019 12:23:40 AM
> > To: dev@community.apache.org
> > Subject: Re: Roadshow Seattle
> >
> > I am based in Seattle, available for a chat over coffee, & would really
> > love to have input here. Also know folks from Google and Lyft that would
> > appreciate this kind of event in Seattle for sure.
> >
> > Please keep me in the loop.
> >
> > Thanks,
> > Aizhamal
> >
> > *From: *Andrew Musselman 
> > *Date: *Tue, May 14, 2019 at 3:23 PM
> > *To: * 
> >
> > Aha great; yeah I'm in Seattle, looking forward to getting together.
> > >
> > > Best
> > > Andrew
> > >
> > > On Tue, May 14, 2019 at 1:20 PM Kevin A. McGrail 
> > > wrote:
> > >
> > > > Hah, I was just about to say ask Ross as step 1.
> > > >
> > > > On Tue, May 14, 2019, 15:08 Ross Gardler 
> wrote:
> > > >
> > > > > Wearing my Microsoft hat, you have Microsoft engaged.
> > > > >
> > > > > Wearing my ASF hat I can help with reaching local companies. But
> > before
> > > > we
> > > > > start reaching out let's decide what kind of event we want. I've
> been
> > > > > planning to do something for some time and would love to link up
> with
> > > you
> > > > > on it. There is a good chance that you and I are thinking of
> > different
> > > > > events ;-)
> > > > >
> > > > > Are you local do Seattle? If so let's have a coffee (with anyone
> > > > > available) figure out if we are sufficiently aligned and come back
> > > with a
> > > > > proposal.
> > > > >
> > > > > Ross
> > > > >
> > > > > Get Outlook for Android<
> >
> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2Fghei36&data=02%7C01%7C%7C434f5f305d024ec9a6ac08d6d9064cf7%7C84df9e7fe9f640afb435%7C1%7C0%7C636935018408634181&sdata=MPz%2BVlADYbtLm5Ghtzsmf%2FGzaWZAh5RuKbX3cTl34uk%3D&reserved=0
> > >
> > > > >
> > > > > 
> > > > > From: Andrew Musselman 
> > > > > Sent: Tuesday, May 14, 2019 12:51:49 PM
> > > > > To: dev@community.apache.org
> > > > > Subject: Re: Roadshow Seattle
> > > > >
> > > > > Awesome, thanks for the feedback; I'll look at how to kick off
> > > planning.
> > > > > Any ideas for getting the word out and checking interest levels
> > across
> > > > > local companies/projects?
> > > > >
> > > > > On Tue, May 14, 2019 at 11:52 AM Kevin A. McGrail <
> > kmcgr...@apache.org
> > > >
> > > > > wrote:
> > > > >
> > > > > > On 5/14/2019 2:30 PM, Aizhamal Nurmamat kyzy wrote:
> > > > > > > I think Seattle would be a great place to host one. I’d be
> there
> > to
> > > > > help
> > > > > > if
> > > > > > > it gets traction, Andrew.
> > > > > >
> > > > > > Same and I told him in person I would help.
> > > > > >
> > > > > > --
> > > > > > Kevin A. McGrail
> > > > > > Member, Apache Software Foundation
> > > > > > Chair Emeritus Apache SpamAssassin Project
> > > > > >
> > > > >
> > > >
> > >
> >
> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.linkedin.com%2Fin%2Fkmcgrail&data=02%7C01%7C%7C434f5f305d024ec9a6ac08d6d9064cf7%7C84df9e7fe9f640afb435%7C1%7C0%7C636935018408634181&sdata=wqB8m%2FP8cypAbO8gIe1psCI2LV2wRhLbG9yQZkQFsTo%3D&reserved=0
> > > > > - 703.798.0171
> > > > > >
> > > > > >
> > > > > >
> > -
> > > > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > > > > For additional commands, e-mail: dev-h...@community.apache.org
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: Roadshow Seattle

[Andrew Musselman]

Roger that, looking forward to meeting up!

On Wed, May 15, 2019 at 10:04 AM Kenneth Knowles  wrote:

> Sign me up to help as well. I'd also just love to meet face to face.
>
> Kenn
>
>
> On Wed, May 15, 2019, 09:40 Andrew Musselman 
> wrote:
>
> > Thanks Trev.
> >
> > Absolutely Aizhamal, anyone else interested in helping in any way please
> > let us know.
> >
> > Downtown seemed good since Fremont is a quick trip from Google and there
> > are so many HQs in SLU. Or maybe that fancy Starbucks in Cap Hill; lots
> of
> > big tables there.
> >
> > Looking forward to it; tentatively look at next week or the following?
> >
> > On Wed, May 15, 2019 at 07:12 Trevor Grant 
> > wrote:
> >
> > > I also told him in person I would support w learnings from Chicago.
> > >
> > >
> > >
> > > On Wed, May 15, 2019 at 2:29 AM Ross Gardler 
> > wrote:
> > >
> > > > Will do, Andrew and I decided we'll meet downtown for a chat. No time
> > set
> > > > yet. Then come back here with a proposal. If anyone else wants to
> join
> > us
> > > > for coffee drop us a note offlist (keep organizational noise down).
> > > >
> > > > Get Outlook for Android<https://aka.ms/ghei36>
> > > >
> > > > 
> > > > From: Aizhamal Nurmamat kyzy 
> > > > Sent: Wednesday, May 15, 2019 12:23:40 AM
> > > > To: dev@community.apache.org
> > > > Subject: Re: Roadshow Seattle
> > > >
> > > > I am based in Seattle, available for a chat over coffee, & would
> really
> > > > love to have input here. Also know folks from Google and Lyft that
> > would
> > > > appreciate this kind of event in Seattle for sure.
> > > >
> > > > Please keep me in the loop.
> > > >
> > > > Thanks,
> > > > Aizhamal
> > > >
> > > > *From: *Andrew Musselman 
> > > > *Date: *Tue, May 14, 2019 at 3:23 PM
> > > > *To: * 
> > > >
> > > > Aha great; yeah I'm in Seattle, looking forward to getting together.
> > > > >
> > > > > Best
> > > > > Andrew
> > > > >
> > > > > On Tue, May 14, 2019 at 1:20 PM Kevin A. McGrail <
> > kmcgr...@apache.org>
> > > > > wrote:
> > > > >
> > > > > > Hah, I was just about to say ask Ross as step 1.
> > > > > >
> > > > > > On Tue, May 14, 2019, 15:08 Ross Gardler 
> > > wrote:
> > > > > >
> > > > > > > Wearing my Microsoft hat, you have Microsoft engaged.
> > > > > > >
> > > > > > > Wearing my ASF hat I can help with reaching local companies.
> But
> > > > before
> > > > > > we
> > > > > > > start reaching out let's decide what kind of event we want.
> I've
> > > been
> > > > > > > planning to do something for some time and would love to link
> up
> > > with
> > > > > you
> > > > > > > on it. There is a good chance that you and I are thinking of
> > > > different
> > > > > > > events ;-)
> > > > > > >
> > > > > > > Are you local do Seattle? If so let's have a coffee (with
> anyone
> > > > > > > available) figure out if we are sufficiently aligned and come
> > back
> > > > > with a
> > > > > > > proposal.
> > > > > > >
> > > > > > > Ross
> > > > > > >
> > > > > > > Get Outlook for Android<
> > > >
> > >
> >
> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2Fghei36&data=02%7C01%7C%7C434f5f305d024ec9a6ac08d6d9064cf7%7C84df9e7fe9f640afb435%7C1%7C0%7C636935018408634181&sdata=MPz%2BVlADYbtLm5Ghtzsmf%2FGzaWZAh5RuKbX3cTl34uk%3D&reserved=0
> > > > >
> > > > > > >
> > > > > > > 
> > > > > > > From: Andrew Musselman 
> > > > > > > Sent: Tuesday, May 14, 2019 12:51:49 PM
> > > > > > > To: dev@community.apache.org
> > > > > > > Subject: Re: Roadshow Seattle
> > > > > > >
> > > > > > > Awesome, thanks for

Re: ComDev website, pelican

[Andrew Musselman]

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

> 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
> http://rcbowen.com/
> @rbowen
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: ComDev website, pelican

[Andrew Musselman]

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 perfect
reproduction; we can log differences in this JIRA ticket and decide how to
handle as we go.

On Mon, May 20, 2019 at 12:20 PM Rich Bowen  wrote:

>
>
> 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.
> >
>
> Works for me. Sooner than I'd get to it.
>
> --Rich
>
>
> > On Mon, May 20, 2019 at 11:43 AM Rich Bowen  wrote:
> >
> >> 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
> >> http://rcbowen.com/
> >> @rbowen
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> >> For additional commands, e-mail: dev-h...@community.apache.org
> >>
> >>
> >
>
> --
> Rich Bowen - rbo...@rcbowen.com
> http://rcbowen.com/
> @rbowen
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: Please move DI notifications to the diversity list

[Andrew Musselman]

Filed a ticket, thanks for the reminder.

On Fri, May 31, 2019 at 18:35 Dave Fisher  wrote:

> Hi -
>
> Since diversity and inclusion is no longer comdev please move JIRA
> notifications to diversity@.
>
> Regards,
> Dave
>
> Sent from my iPhone
>
> > On May 31, 2019, at 6:29 PM, Andrew Musselman (JIRA) 
> wrote:
> >
> >
> >[
> https://issues.apache.org/jira/browse/DI-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16853532#comment-16853532
> ]
> >
> > Andrew Musselman commented on DI-7:
> > ---
> >
> > Ijeoma Oluo
> >
> > Seattle
> >
> > English
> >
> > D&I, how to talk about racism and equity
> >
> > [http://www.ijeomaoluo.com|http://www.ijeomaoluo.com/]
> >
> > Contact form on her home page
> >
> >
> >
> >> Curating a list of speakers for ApacheCon
> >> -
> >>
> >>Key: DI-7
> >>URL: https://issues.apache.org/jira/browse/DI-7
> >>Project: Diversity and Inclusion
> >> Issue Type: Wish
> >> Components: knowledge, resources
> >>   Reporter: Griselda Cuevas Zambrano
> >>   Assignee: Griselda Cuevas Zambrano
> >>   Priority: Normal
> >> Labels: events, how-to, speakers
> >>  Original Estimate: 168h
> >> Remaining Estimate: 168h
> >>
> >> Hi folks - let's curate a list of speakers we'd like to invite to
> discuss D&I with the ASF community. We can use this list to invite folks to
> events like ApacheCon, or project summits, and also maybe create a Speakers
> series?
> >>
> >> Ok, all you need to do is list this info:
> >> * Speaker:
> >> * Location:
> >> * Language:
> >> * Topic:
> >> * URL: (can be a talk/website/twitter/etc)
> >> * How to contact: (if you don't know put don't know)
> >> Cheers
> >
> >
> >
> > --
> > This message was sent by Atlassian JIRA
> > (v7.6.3#76005)
> >
> > -
> > 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: ComDev website, pelican

[Andrew Musselman]

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 being used, would be a nice way
to surface the code for people to pitch in.

Let me know, if there are no objections I'll request a repo and start
getting things set up.

On Mon, May 20, 2019 at 12:34 PM Andrew Musselman <
andrew.mussel...@gmail.com> wrote:

> 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 perfect
> reproduction; we can log differences in this JIRA ticket and decide how to
> handle as we go.
>
> On Mon, May 20, 2019 at 12:20 PM Rich Bowen  wrote:
>
>>
>>
>> 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.
>> >
>>
>> Works for me. Sooner than I'd get to it.
>>
>> --Rich
>>
>>
>> > On Mon, May 20, 2019 at 11:43 AM Rich Bowen  wrote:
>> >
>> >> 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
>> >> http://rcbowen.com/
>> >> @rbowen
>> >>
>> >> -
>> >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>> >> For additional commands, e-mail: dev-h...@community.apache.org
>> >>
>> >>
>> >
>>
>> --
>> Rich Bowen - rbo...@rcbowen.com
>> http://rcbowen.com/
>> @rbowen
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>> For additional commands, e-mail: dev-h...@community.apache.org
>>
>>

Re: ComDev website, pelican

[Andrew Musselman]

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

Re: ComDev website, pelican

[Andrew Musselman]

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

Re: ComDev website, pelican

[Andrew Musselman]

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 selects the PMC "community",
and puts "site" in the Repository Name field, "community-site.git" should
be generated. Sebb, would you mind trying that, to see if we need INFRA
help?

On Wed, Jun 5, 2019 at 5:40 AM sebb  wrote:

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

Re: ComDev website, pelican

[Andrew Musselman]

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 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 selects the PMC "community",
> and puts "site" in the Repository Name field, "community-site.git" should
> be generated. Sebb, would you mind trying that, to see if we need INFRA
> help?
>
> On Wed, Jun 5, 2019 at 5:40 AM sebb  wrote:
>
>> 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 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 
>> 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 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
>>
>>

Re: Patch for reporter.a.o

[Andrew Musselman]

Looks good to me. Maybe similar language on this page too?
https://reporter.apache.org/wizard/statistics?lucene

This ticket could be a good link to point the "Patches welcome" to:
COMDEV-487 

On Tue, Feb 14, 2023 at 1:22 PM  wrote:

> I'd like to propose the attached patch to reporter.a.o so that people
> don't keep submitting the same mailing list stats, quarter after
> quarter, a year after that part of the reporter is broken.
>
> Thoughts?
>
> -
> 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: Patch for reporter.a.o

[Andrew Musselman]

On Wed, Feb 15, 2023 at 5:19 AM  wrote:

> On Tue, 2023-02-14 at 14:33 -0800, Andrew Musselman wrote:
> > Looks good to me. Maybe similar language on this page
> > too? https://reporter.apache.org/wizard/statistics?lucene
>
> That page is generated by the code affected by that patch.


Got it

>

Re: [jira] [Commented] (COMDEV-227) Only list last X releases and the add/remove release page

[Andrew Musselman]

Patch attached here; allows for new query param `limit` so projects that
are getting bogged down can just specify how many releases they want to see
on the page.

E.g.,
reporter.apache.org/addrelease.html?sling shows all releases
reporter.apache.org/addrelease.html?sling&limit=50 shows only the latest 50
releases
reporter.apache.org/addrelease.html?sling;2000 sets baseline year to 2000
reporter.apache.org/addrelease.html?sling;2000&limit=50 sets baseline year
to 2000 and limits to latest 50 releases
Probably would make sense to add a note above "Already registered releases"
to explain this.

Tested query param handling but not cutting off releases at limit since I
don't have a testing env. See if it looks reasonable.

[Y/n]?

On Wed, Feb 15, 2023 at 1:06 PM Andrew Musselman (Jira) 
wrote:

>
> [
> https://issues.apache.org/jira/browse/COMDEV-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17689339#comment-17689339
> ]
>
> Andrew Musselman commented on COMDEV-227:
> -
>
> Attaching proposed patch
>
> > Only list last X releases and the add/remove release page
> > -
> >
> > Key: COMDEV-227
> > URL: https://issues.apache.org/jira/browse/COMDEV-227
> > Project: Community Development
> >  Issue Type: Improvement
> >  Components: Reporter Tool
> >Reporter: Robert Munteanu
> >Priority: Major
> > Attachments: COMDEV-227.patch.txt
> >
> >
> > In the Apache Sling project we have a large number of releases as we
> have many independent modules. When loading the
> https://reporter.apache.org/addrelease.html?sling page, it takes upwards
> of 10 seconds to load. It would be great if only the last X (50?) releases
> were shown, and then a "load all" link would be available at the bottom.
> > This would greatly speed up our usage of this tool.
>
>
>
> --
> 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
>
>
Index: site/js/addrelease.js
===
--- site/js/addrelease.js   (revision 1907684)
+++ site/js/addrelease.js   (working copy)
@@ -1,6 +1,8 @@
 // location may have appended ; for debugging purposes
+// limit param can be passed as query param in URL to limit # of releases 
written to the page
+// This URL-handling section could use clean-up
  var srch = document.location.search.substr(1).split(';'); // drop ? from the 
search and split at semicolon
- var committee = srch[0]; // before the semi (if any)
+ var committee = srch[0].split('&')[0]; // before the semi (if any) and amp 
(if any)
  var baseyear = 1999;
  if (srch.length > 1) {
  baseyear = parseInt(srch[1]); // grab trailing start year
@@ -8,6 +10,9 @@
  baseyear=1999; // ensure sensible default value
  }
  }
+ const queryString = document.location.search;
+ const params = new URLSearchParams(queryString);
+ const limit = parseInt(params.get("limit"));
  document.getElementById('committee').value = committee;
  var xdate = document.getElementById('xdate');
  var done = false;
@@ -47,6 +52,9 @@
   var basedate = bd.getTime()/1000 // value as stored in the database
   var recent = new Array();
   for (version in json) {
+if (limit && x == limit) {
+  break;
+}
 if (json[version] > basedate) {
   recent.push(new Release(version, json[version]));
   x++;
@@ -69,4 +77,3 @@
   }
   document.getElementById('committee').value = committee;
  }
- 

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

Re: Back to basics: What we do @comdev

[Andrew Musselman]

>
> > projects.a.o
> > reporter.a.o
> > helpwanted (I think this is EOL, realistically)
>

I am interested in helping with reporter.a.o and possibly more.

On Thu, Mar 16, 2023 at 9:29 AM Daniel Gruno  wrote:

> On 3/16/23 11:26, Maxim Solodovnik wrote:
> >
> > almost all communications are already at mentors@community :)
> >
>
> And yet we have 185 messages on this list in just the past month. I do
> believe splitting GSOC out from the COMDEV Jira space will make most of
> that go away.
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: Reporter tool for board reports needs some love

[Andrew Musselman]

https://reporter.apache.org/about.html

On Tue, Mar 19, 2024 at 8:56 AM tison  wrote:

> May I ask where we host the reporter tool source code?
>
> Best,
> tison.
>
>
> Rich Bowen  于2024年3月19日周二 23:52写道：
>
> >
> >
> >
> > > On Mar 18, 2024, at 5:18 PM, Craig Russell 
> wrote:
> > >
> > > Hi,
> > >
> > > Is there anyone who can take a look at the Reporter tool that many
> > projects rely on to help create board reports?
> > >
> > > A number of projects have commented that the statistics seem to be in
> > conflict with reality.
> >
> > Every month several projects make this complaint. I almost always
> > encourage them to bring their complaint here. They almost never do,
> leaving
> > us with only the vaguest idea of what they think is broken. Do you feel
> you
> > understand what they think is being reported inaccurately? I think some
> > folks have complained about Github stats being off, but that’s pretty
> easy
> > to go retrieve on their own.
> >
> >
>

Re: Reporter tool for board reports needs some love

[Andrew Musselman]

I'll make that edit, thanks sebb.

On Tue, Mar 19, 2024 at 10:11 AM sebb  wrote:

> The linked README file is a bit out of date.
>
> Neither it nor the About page mention that many of the stats come from
> https://demo.kibble.apache.org/
>
> On Tue, 19 Mar 2024 at 16:25, Andrew Musselman  wrote:
> >
> > https://reporter.apache.org/about.html
> >
> > On Tue, Mar 19, 2024 at 8:56 AM tison  wrote:
> >
> > > May I ask where we host the reporter tool source code?
> > >
> > > Best,
> > > tison.
> > >
> > >
> > > Rich Bowen  于2024年3月19日周二 23:52写道：
> > >
> > > >
> > > >
> > > >
> > > > > On Mar 18, 2024, at 5:18 PM, Craig Russell 
> > > wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > Is there anyone who can take a look at the Reporter tool that many
> > > > projects rely on to help create board reports?
> > > > >
> > > > > A number of projects have commented that the statistics seem to be
> in
> > > > conflict with reality.
> > > >
> > > > Every month several projects make this complaint. I almost always
> > > > encourage them to bring their complaint here. They almost never do,
> > > leaving
> > > > us with only the vaguest idea of what they think is broken. Do you
> feel
> > > you
> > > > understand what they think is being reported inaccurately? I think
> some
> > > > folks have complained about Github stats being off, but that’s pretty
> > > easy
> > > > to go retrieve on their own.
> > > >
> > > >
> > >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: Reporter tool for board reports needs some love

[Andrew Musselman]

I checked this revision in, inadvertently adding something I did a while
back to make page loading faster as I recall. I can back that change out
now.

$ svn ci -m"Adding updated information about what code is running behind
the scenes for the reporter page (kibble)"
SendingREADME.txt
Sendingsite/js/addrelease.js
Transmitting file data ..done
Committing transaction...
Committed revision 1916425.

On Tue, Mar 19, 2024 at 10:24 AM Andrew Musselman  wrote:

> I'll make that edit, thanks sebb.
>
> On Tue, Mar 19, 2024 at 10:11 AM sebb  wrote:
>
>> The linked README file is a bit out of date.
>>
>> Neither it nor the About page mention that many of the stats come from
>> https://demo.kibble.apache.org/
>>
>> On Tue, 19 Mar 2024 at 16:25, Andrew Musselman  wrote:
>> >
>> > https://reporter.apache.org/about.html
>> >
>> > On Tue, Mar 19, 2024 at 8:56 AM tison  wrote:
>> >
>> > > May I ask where we host the reporter tool source code?
>> > >
>> > > Best,
>> > > tison.
>> > >
>> > >
>> > > Rich Bowen  于2024年3月19日周二 23:52写道：
>> > >
>> > > >
>> > > >
>> > > >
>> > > > > On Mar 18, 2024, at 5:18 PM, Craig Russell 
>> > > wrote:
>> > > > >
>> > > > > Hi,
>> > > > >
>> > > > > Is there anyone who can take a look at the Reporter tool that many
>> > > > projects rely on to help create board reports?
>> > > > >
>> > > > > A number of projects have commented that the statistics seem to
>> be in
>> > > > conflict with reality.
>> > > >
>> > > > Every month several projects make this complaint. I almost always
>> > > > encourage them to bring their complaint here. They almost never do,
>> > > leaving
>> > > > us with only the vaguest idea of what they think is broken. Do you
>> feel
>> > > you
>> > > > understand what they think is being reported inaccurately? I think
>> some
>> > > > folks have complained about Github stats being off, but that’s
>> pretty
>> > > easy
>> > > > to go retrieve on their own.
>> > > >
>> > > >
>> > >
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>> For additional commands, e-mail: dev-h...@community.apache.org
>>
>>

Re: Reporter tool for board reports needs some love

[Andrew Musselman]

Backed out; thanks

$ svn ci -m"Backing out unintended changes"
Sendingsite/js/addrelease.js
Transmitting file data .done
Committing transaction...
Committed revision 1916426.

On Tue, Mar 19, 2024 at 10:41 AM sebb  wrote:

> On Tue, 19 Mar 2024 at 17:37, Andrew Musselman  wrote:
> >
> > I checked this revision in, inadvertently adding something I did a while
> > back to make page loading faster as I recall. I can back that change out
> > now.
>
> Thanks.
>
> I was about to reply to that commit to ask if that part of the change
> was intended, as it was not mentioned in the log.
>
> > $ svn ci -m"Adding updated information about what code is running behind
> > the scenes for the reporter page (kibble)"
> > SendingREADME.txt
> > Sendingsite/js/addrelease.js
> > Transmitting file data ..done
> > Committing transaction...
> > Committed revision 1916425.
> >
> > On Tue, Mar 19, 2024 at 10:24 AM Andrew Musselman 
> wrote:
> >
> > > I'll make that edit, thanks sebb.
> > >
> > > On Tue, Mar 19, 2024 at 10:11 AM sebb  wrote:
> > >
> > >> The linked README file is a bit out of date.
> > >>
> > >> Neither it nor the About page mention that many of the stats come from
> > >> https://demo.kibble.apache.org/
> > >>
> > >> On Tue, 19 Mar 2024 at 16:25, Andrew Musselman 
> wrote:
> > >> >
> > >> > https://reporter.apache.org/about.html
> > >> >
> > >> > On Tue, Mar 19, 2024 at 8:56 AM tison  wrote:
> > >> >
> > >> > > May I ask where we host the reporter tool source code?
> > >> > >
> > >> > > Best,
> > >> > > tison.
> > >> > >
> > >> > >
> > >> > > Rich Bowen  于2024年3月19日周二 23:52写道：
> > >> > >
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > > > On Mar 18, 2024, at 5:18 PM, Craig Russell <
> apache@gmail.com>
> > >> > > wrote:
> > >> > > > >
> > >> > > > > Hi,
> > >> > > > >
> > >> > > > > Is there anyone who can take a look at the Reporter tool that
> many
> > >> > > > projects rely on to help create board reports?
> > >> > > > >
> > >> > > > > A number of projects have commented that the statistics seem
> to
> > >> be in
> > >> > > > conflict with reality.
> > >> > > >
> > >> > > > Every month several projects make this complaint. I almost
> always
> > >> > > > encourage them to bring their complaint here. They almost never
> do,
> > >> > > leaving
> > >> > > > us with only the vaguest idea of what they think is broken. Do
> you
> > >> feel
> > >> > > you
> > >> > > > understand what they think is being reported inaccurately? I
> think
> > >> some
> > >> > > > folks have complained about Github stats being off, but that’s
> > >> pretty
> > >> > > easy
> > >> > > > to go retrieve on their own.
> > >> > > >
> > >> > > >
> > >> > >
> > >>
> > >> -
> > >> 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: Berlin Buzzwords BarCamp

[Andrew Musselman]

Thanks Nick!

On Tue, Mar 25, 2025 at 2:25 PM Nick Burch  wrote:

> On Tue, 25 Mar 2025, Andrew Musselman wrote:
> > If my talk is approved I'm going to try to swing it; is barcamp that
> > Sunday?
>
> Yes, it is! As per
>
> https://2024.berlinbuzzwords.de/2024/06/26/berlin-buzzwords-2025-save-the-date/index.html
> it'll be happening in the usual slot on the Sunday afternoon, running from
> late lunch until the speakers dinner. (Typically most non-speakers head
> out for dinner together after the BarCamp)
>
> Weather-permitting there'll be two tracks with plenty of participant
> space, one inside and one outside. If the weather is against us, there'll
> be a big inside and small inside space available.
>
> Scheduling is a collaboritive affair, as is always the case with a
> BarCamp, but Berlin Buzzwords is also an event that always seems to
> welcome Apache related sessions :)
>
> Nick
> (Once again roped into helping organise the #bbuzz barcamp)
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: Berlin Buzzwords BarCamp

[Andrew Musselman]

If my talk is approved I'm going to try to swing it; is barcamp that Sunday?

On Tue, Mar 25, 2025 at 12:57 PM Jarek Potiuk  wrote:

> I am definitely in - full-in :)
>
> On Tue, Mar 25, 2025 at 8:28 PM Anshum Gupta 
> wrote:
>
> > I'll be at the conference and will certainly try to be at the Bar Camp
> too.
> >
> > Like me, I know there would be other folks from the Apache Lucene and
> > Solr projects at the conference, but I'm not sure how many would be at
> > the Bar Camp.
> >
> > On Wed, Mar 26, 2025 at 12:52 AM Roman Shaposhnik 
> wrote:
> > >
> > > Hi All!
> > >
> > > anyone planning on going to BarCamp specifically and
> > > more generally to the BB in June? I'm considering of
> > > doing a community thing there and was wondering how
> > > many of the fellow ASF folks (and from which projects!)
> > > plan to be there.
> > >
> > > Thanks,
> > > Roman.
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > For additional commands, e-mail: dev-h...@community.apache.org
> > >
> >
> >
> > --
> > Anshum Gupta
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
> >
>

Re: GSoC volunteer

[Andrew Musselman]

Okay thanks Sanyam; Krishna, FYI if you can get a blurb together for a
proposal we can get this underway.

On Mon, Feb 17, 2025 at 10:08 AM Sanyam Goel  wrote:

> Hi Andrew,
> If Any project wants to participate on Google Summer of Code this year with
> ASF
> I recommend you to kindly go through the documentation:
> https://community.apache.org/gsoc/guide-to-being-a-mentor.html
>
> and Mentors are requested to communicate using
> ment...@community.apache.org
> mailing list
> All the GSoC communications happens on the above mailing list.
>
> FYI: We have already submitted the application to participate in summer of
> code with Google [and it is in-progress]
> But I highly recommend to add the project along with the guidelines
> mentioned tags[kindly go through the above link] as soon as possible
> All the GSoC Ideas are listed on this page
> https://s.apache.org/gsoc2025ideas
>
> Thank you,
> Sanyam Goel
>
> On Mon, Feb 17, 2025 at 10:20 PM Andrew Musselman  wrote:
>
> > Hi all, is this still the right list to ask about getting someone
> involved
> > in summer of code? We have a new volunteer interested in doing some work.
> >
> > Best
> > Andrew
> >
>

GSoC volunteer

[Andrew Musselman]

Hi all, is this still the right list to ask about getting someone involved
in summer of code? We have a new volunteer interested in doing some work.

Best
Andrew

[jira] [Commented] (DI-7) Curating a list of speakers for ApacheCon

[Andrew Musselman (JIRA)]

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

Andrew Musselman commented on DI-7:
---

Ijeoma Oluo

Seattle

English

D&I, how to talk about racism and equity

[http://www.ijeomaoluo.com|http://www.ijeomaoluo.com/]

Contact form on her home page

 

> Curating a list of speakers for ApacheCon
> -
>
> Key: DI-7
> URL: https://issues.apache.org/jira/browse/DI-7
> Project: Diversity and Inclusion
>  Issue Type: Wish
>  Components: knowledge, resources
>Reporter: Griselda Cuevas Zambrano
>Assignee: Griselda Cuevas Zambrano
>Priority: Normal
>  Labels: events, how-to, speakers
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> Hi folks - let's curate a list of speakers we'd like to invite to discuss D&I 
> with the ASF community. We can use this list to invite folks to events like 
> ApacheCon, or project summits, and also maybe create a Speakers series? 
>  
> Ok, all you need to do is list this info: 
>  * Speaker:
>  * Location:
>  * Language: 
>  * Topic:
>  * URL: (can be a talk/website/twitter/etc)
>  * How to contact: (if you don't know put don't know)
> Cheers



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Comment Edited] (DI-7) Curating a list of speakers for ApacheCon

[Andrew Musselman (JIRA)]

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

Andrew Musselman edited comment on DI-7 at 6/1/19 1:30 AM:
---

* Speaker: Ijeoma Oluo
 * Location: Seattle, WA
 * Language: English
 * Topics: D&I, how to talk about racism and equity
 * Contact form on her home page 
 * URL: [http://www.ijeomaoluo.com|http://www.ijeomaoluo.com/]
 * How to contact: email form from her home page


was (Author: andrew.musselman):
Ijeoma Oluo

Seattle

English

D&I, how to talk about racism and equity

[http://www.ijeomaoluo.com|http://www.ijeomaoluo.com/]

Contact form on her home page

 

> Curating a list of speakers for ApacheCon
> -
>
> Key: DI-7
> URL: https://issues.apache.org/jira/browse/DI-7
> Project: Diversity and Inclusion
>  Issue Type: Wish
>  Components: knowledge, resources
>Reporter: Griselda Cuevas Zambrano
>Assignee: Griselda Cuevas Zambrano
>Priority: Normal
>  Labels: events, how-to, speakers
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> Hi folks - let's curate a list of speakers we'd like to invite to discuss D&I 
> with the ASF community. We can use this list to invite folks to events like 
> ApacheCon, or project summits, and also maybe create a Speakers series? 
>  
> Ok, all you need to do is list this info: 
>  * Speaker:
>  * Location:
>  * Language: 
>  * Topic:
>  * URL: (can be a talk/website/twitter/etc)
>  * How to contact: (if you don't know put don't know)
> Cheers



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Created] (DI-8) Point JIRA updates to dev@d.a.o

[Andrew Musselman (JIRA)]

Andrew Musselman created DI-8:
-

 Summary: Point JIRA updates to dev@d.a.o
 Key: DI-8
 URL: https://issues.apache.org/jira/browse/DI-8
 Project: Diversity and Inclusion
  Issue Type: Task
Reporter: Andrew Musselman


Currently updates to D&I Jira tickets are mailed to comdev; now that there's a 
dedicated project they should go to d...@diversity.apache.org.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (COMDEV-454) Report Wizard gives "[object Response]" error with underlying 503

[Andrew Musselman (Jira)]

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

Andrew Musselman commented on COMDEV-454:
-

Working for me too, [~curcuru] is this resolved?

> Report Wizard gives "[object Response]" error with underlying 503
> -
>
> Key: COMDEV-454
> URL: https://issues.apache.org/jira/browse/COMDEV-454
> Project: Community Development
>  Issue Type: Bug
>  Components: Reporter Tool
> Environment: Mac/FF
>Reporter: Shane Curcuru
>Priority: Major
>
> As reported elsewhere, navigating to [https://reporter.apache.org/wizard/] 
> pops up a notification error, and does nothing else.
> Console shows an underlying 503:
> /*** ASF Board Report Wizard initializing / 
> [wizard.js:1792:9|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4]
> Fetching JSON resource at /reportingcycles.json 
> [wizard.js:79:13|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4]
> putting /reportingcycles.json in escrow... 
> [wizard.js:96:21|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4]
> Successfully fetched /reportingcycles.json 
> [wizard.js:119:21|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4]
> Fetching JSON resource at /api/overview 
> [wizard.js:79:13|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4]
> putting /api/overview in escrow... 
> [wizard.js:96:21|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4]
> URL /api/overview returned HTTP code 503, snapping! 
> [wizard.js:132:21|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4]



--
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] [Commented] (COMDEV-478) https://reporter.apache.org/addrelease.html?sling leads to page crash with Chrome

[Andrew Musselman (Jira)]

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

Andrew Musselman commented on COMDEV-478:
-

[~kwin] is this still an open issue, not reproing here now

> 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] [Commented] (COMDEV-429) The Committer-to-PMC ratio in Board Report Wizard may not give the best ratio

[Andrew Musselman (Jira)]

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

Andrew Musselman commented on COMDEV-429:
-

[~szetszwo] are you sure this patch works? I tried it in a JS console online 
and got an error that looks like it's complaining that a string doesn't have a 
`.format` function:

{{> searchBestRatioString(10,3)}}
{{ TypeError { "roughly %u:%u".format is not a function } }}

> The Committer-to-PMC ratio in Board Report Wizard may not give the best ratio
> -
>
> Key: COMDEV-429
> URL: https://issues.apache.org/jira/browse/COMDEV-429
> Project: Community Development
>  Issue Type: New Feature
>  Components: Reporter Tool
>Reporter: Tsz-wo Sze
>Priority: Minor
> Attachments: 20220705_COMDEV-429.patch
>
>
> Thanks a lot for providing the Board Report Wizard 
> ([https://reporter.apache.org/wizard/])! It is a great tool which helps save 
> a lot of time.
> I notice that the Committer-to-PMC ratio computed by the tool may not give 
> the best ratio. For example, in 
> [https://reporter.apache.org/wizard/statistics?ratis] ,
>  - There are currently 27 committers and 17 PMC members in this project.
>  - The Committer-to-PMC ratio is roughly 7:5.
> We have 27/17 = 1.588 and 7/5 = 1.4. A better ratio is 8/5 = 1.6.



--
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] [Comment Edited] (COMDEV-429) The Committer-to-PMC ratio in Board Report Wizard may not give the best ratio

[Andrew Musselman (Jira)]

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

Andrew Musselman edited comment on COMDEV-429 at 2/13/23 10:02 PM:
---

[~szetszwo] are you sure this patch works? I tried it in a JS console online 
and got an error that looks like it's complaining that a string doesn't have a 
`.format` function:

{{> searchBestRatioString(10,3)}}
{{TypeError { "roughly %u:%u".format is not a function }}}


was (Author: akm):
[~szetszwo] are you sure this patch works? I tried it in a JS console online 
and got an error that looks like it's complaining that a string doesn't have a 
`.format` function:

{{> searchBestRatioString(10,3)}}
{{ TypeError { "roughly %u:%u".format is not a function } }}

> The Committer-to-PMC ratio in Board Report Wizard may not give the best ratio
> -
>
> Key: COMDEV-429
> URL: https://issues.apache.org/jira/browse/COMDEV-429
> Project: Community Development
>  Issue Type: New Feature
>  Components: Reporter Tool
>Reporter: Tsz-wo Sze
>Priority: Minor
> Attachments: 20220705_COMDEV-429.patch
>
>
> Thanks a lot for providing the Board Report Wizard 
> ([https://reporter.apache.org/wizard/])! It is a great tool which helps save 
> a lot of time.
> I notice that the Committer-to-PMC ratio computed by the tool may not give 
> the best ratio. For example, in 
> [https://reporter.apache.org/wizard/statistics?ratis] ,
>  - There are currently 27 committers and 17 PMC members in this project.
>  - The Committer-to-PMC ratio is roughly 7:5.
> We have 27/17 = 1.588 and 7/5 = 1.4. A better ratio is 8/5 = 1.6.



--
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] [Comment Edited] (COMDEV-429) The Committer-to-PMC ratio in Board Report Wizard may not give the best ratio

[Andrew Musselman (Jira)]

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

Andrew Musselman edited comment on COMDEV-429 at 2/13/23 10:03 PM:
---

[~szetszwo] are you sure this patch works? I tried it in a JS console online 
and got an error that looks like it's complaining that a string doesn't have a 
`.format` function:

> searchBestRatioString(10,3)
{{TypeError \{ "roughly %u:%u".format is not a function }}}


was (Author: akm):
[~szetszwo] are you sure this patch works? I tried it in a JS console online 
and got an error that looks like it's complaining that a string doesn't have a 
`.format` function:

{{> searchBestRatioString(10,3)}}
{{TypeError { "roughly %u:%u".format is not a function }}}

> The Committer-to-PMC ratio in Board Report Wizard may not give the best ratio
> -
>
> Key: COMDEV-429
> URL: https://issues.apache.org/jira/browse/COMDEV-429
> Project: Community Development
>  Issue Type: New Feature
>  Components: Reporter Tool
>Reporter: Tsz-wo Sze
>Priority: Minor
> Attachments: 20220705_COMDEV-429.patch
>
>
> Thanks a lot for providing the Board Report Wizard 
> ([https://reporter.apache.org/wizard/])! It is a great tool which helps save 
> a lot of time.
> I notice that the Committer-to-PMC ratio computed by the tool may not give 
> the best ratio. For example, in 
> [https://reporter.apache.org/wizard/statistics?ratis] ,
>  - There are currently 27 committers and 17 PMC members in this project.
>  - The Committer-to-PMC ratio is roughly 7:5.
> We have 27/17 = 1.588 and 7/5 = 1.4. A better ratio is 8/5 = 1.6.



--
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] [Commented] (COMDEV-429) The Committer-to-PMC ratio in Board Report Wizard may not give the best ratio

[Andrew Musselman (Jira)]

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

Andrew Musselman commented on COMDEV-429:
-

Thanks [~humbedooh] 

Seems to work fine on several inputs. Looks like a simple merge. +1
 {{searchBestRatioString(10,3)}}
roughly 7:2
 searchBestRatioString(3,10)
 
roughly 2:7
 searchBestRatioString(100,3)
 
roughly 1:0
 searchBestRatioString(3,100)
 
roughly 0:1
 searchBestRatioString(9,3)
 
3:1
 searchBestRatioString(3,9)
{{{}{}}}{{{}1:3{}}}

> The Committer-to-PMC ratio in Board Report Wizard may not give the best ratio
> -
>
> Key: COMDEV-429
> URL: https://issues.apache.org/jira/browse/COMDEV-429
> Project: Community Development
>  Issue Type: New Feature
>  Components: Reporter Tool
>Reporter: Tsz-wo Sze
>Priority: Minor
> Attachments: 20220705_COMDEV-429.patch
>
>
> Thanks a lot for providing the Board Report Wizard 
> ([https://reporter.apache.org/wizard/])! It is a great tool which helps save 
> a lot of time.
> I notice that the Committer-to-PMC ratio computed by the tool may not give 
> the best ratio. For example, in 
> [https://reporter.apache.org/wizard/statistics?ratis] ,
>  - There are currently 27 committers and 17 PMC members in this project.
>  - The Committer-to-PMC ratio is roughly 7:5.
> We have 27/17 = 1.588 and 7/5 = 1.4. A better ratio is 8/5 = 1.6.



--
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] [Comment Edited] (COMDEV-429) The Committer-to-PMC ratio in Board Report Wizard may not give the best ratio

[Andrew Musselman (Jira)]

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

Andrew Musselman edited comment on COMDEV-429 at 2/13/23 10:34 PM:
---

Thanks [~humbedooh] 

Seems to work fine on several inputs. Looks like a simple merge. +1
 

searchBestRatioString(10,3)
{{roughly 7:2}}
{{searchBestRatioString(3,10) }}
{{roughly 2:7}}
{{searchBestRatioString(100,3)}}
{{roughly 1:0}}
{{searchBestRatioString(3,100) }}
{{roughly 0:1}}
{{searchBestRatioString(9,3) }}
{{3:1}}
{{searchBestRatioString(3,9)}}
1:3


was (Author: akm):
Thanks [~humbedooh] 

Seems to work fine on several inputs. Looks like a simple merge. +1
 {{searchBestRatioString(10,3)}}
roughly 7:2
 searchBestRatioString(3,10)
 
roughly 2:7
 searchBestRatioString(100,3)
 
roughly 1:0
 searchBestRatioString(3,100)
 
roughly 0:1
 searchBestRatioString(9,3)
 
3:1
 searchBestRatioString(3,9)
{{{}{}}}{{{}1:3{}}}

> The Committer-to-PMC ratio in Board Report Wizard may not give the best ratio
> -
>
> Key: COMDEV-429
> URL: https://issues.apache.org/jira/browse/COMDEV-429
> Project: Community Development
>  Issue Type: New Feature
>  Components: Reporter Tool
>Reporter: Tsz-wo Sze
>Priority: Minor
> Attachments: 20220705_COMDEV-429.patch
>
>
> Thanks a lot for providing the Board Report Wizard 
> ([https://reporter.apache.org/wizard/])! It is a great tool which helps save 
> a lot of time.
> I notice that the Committer-to-PMC ratio computed by the tool may not give 
> the best ratio. For example, in 
> [https://reporter.apache.org/wizard/statistics?ratis] ,
>  - There are currently 27 committers and 17 PMC members in this project.
>  - The Committer-to-PMC ratio is roughly 7:5.
> We have 27/17 = 1.588 and 7/5 = 1.4. A better ratio is 8/5 = 1.6.



--
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] [Comment Edited] (COMDEV-429) The Committer-to-PMC ratio in Board Report Wizard may not give the best ratio

[Andrew Musselman (Jira)]

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

Andrew Musselman edited comment on COMDEV-429 at 2/13/23 10:35 PM:
---

Thanks [~humbedooh] 

Seems to work fine on several inputs. Looks like a simple merge. +1
 

{{searchBestRatioString(10,3)}}
{{roughly 7:2}}
{{searchBestRatioString(3,10)}}
{{roughly 2:7}}
{{searchBestRatioString(100,3)}}
{{roughly 1:0}}
{{searchBestRatioString(3,100)}}
{{roughly 0:1}}
{{searchBestRatioString(9,3)}}
{{3:1}}
{{searchBestRatioString(3,9)}}
{{1:3}}


was (Author: akm):
Thanks [~humbedooh] 

Seems to work fine on several inputs. Looks like a simple merge. +1
 

searchBestRatioString(10,3)
{{roughly 7:2}}
{{searchBestRatioString(3,10) }}
{{roughly 2:7}}
{{searchBestRatioString(100,3)}}
{{roughly 1:0}}
{{searchBestRatioString(3,100) }}
{{roughly 0:1}}
{{searchBestRatioString(9,3) }}
{{3:1}}
{{searchBestRatioString(3,9)}}
1:3

> The Committer-to-PMC ratio in Board Report Wizard may not give the best ratio
> -
>
> Key: COMDEV-429
> URL: https://issues.apache.org/jira/browse/COMDEV-429
> Project: Community Development
>  Issue Type: New Feature
>  Components: Reporter Tool
>Reporter: Tsz-wo Sze
>Priority: Minor
> Attachments: 20220705_COMDEV-429.patch
>
>
> Thanks a lot for providing the Board Report Wizard 
> ([https://reporter.apache.org/wizard/])! It is a great tool which helps save 
> a lot of time.
> I notice that the Committer-to-PMC ratio computed by the tool may not give 
> the best ratio. For example, in 
> [https://reporter.apache.org/wizard/statistics?ratis] ,
>  - There are currently 27 committers and 17 PMC members in this project.
>  - The Committer-to-PMC ratio is roughly 7:5.
> We have 27/17 = 1.588 and 7/5 = 1.4. A better ratio is 8/5 = 1.6.



--
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] [Commented] (COMDEV-425) Reporter tool's "Busiest GitHub topics" is missing "lucene" for Lucene project

[Andrew Musselman (Jira)]

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

Andrew Musselman commented on COMDEV-425:
-

[~sharan] and [~mikemccand] looks like this is still happening for lucene; is 
there a ticket open on kibble that could be linked here?

> Reporter tool's "Busiest GitHub topics" is missing "lucene" for Lucene project
> --
>
> Key: COMDEV-425
> URL: https://issues.apache.org/jira/browse/COMDEV-425
> Project: Community Development
>  Issue Type: Bug
>  Components: Reporter Tool
>Reporter: Michael McCandless
>Priority: Minor
> Attachments: Screen Shot 2021-09-09 at 5.34.16 PM.png, Screen Shot 
> 2021-10-21 at 8.55.58 AM.png, image-2021-10-21-08-56-15-016.png, 
> lucene-kibble.png
>
>
> I am working on the quarterly board report for Apache Lucene, and noticed 
> under the "Community Health" section that the "Busiest GitHub topics" seems 
> to be missing the "lucene" GitHub repository.
> It seems to contain only {{lucene-solr}}, {{lucenenet}}, {{lucene-site}}.
> Likely something needs to be updated because Solr split out of Lucene, and 
> Lucene's main (to be 9.0 release soon) branch is on a new(-ish) {{lucene}} 
> repository: [https://github.com/apache/lucene]
> !Screen Shot 2021-09-09 at 5.34.16 PM.png!



--
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] [Commented] (COMDEV-416) make reporter wizard send notifications to private@

[Andrew Musselman (Jira)]

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

Andrew Musselman commented on COMDEV-416:
-

In the `https://reporter.apache.org/wizard` page the reporter data can be 
included directly into the board report editor. Does that satisfy this request 
as another solution?

> make reporter wizard send notifications to private@
> ---
>
> Key: COMDEV-416
> URL: https://issues.apache.org/jira/browse/COMDEV-416
> Project: Community Development
>  Issue Type: Improvement
>  Components: Reporter Tool
>Reporter: Herve Boutemy
>Priority: Major
>
> Reporter wizard is awesome to help the PMC chair prepare and submit board 
> reports.
> The only key missing step is sending drafts and/or final submitted report to 
> the PMC, for review or just info



--
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] [Commented] (COMDEV-317) tabs hidden if maildata.json is empty

[Andrew Musselman (Jira)]

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

Andrew Musselman commented on COMDEV-317:
-

[~sebb] is this a quick fix in `render.js`? I see `json.mail[pmc]` as a check 
among other things but it's not obvious where `data/maildata.json` would show 
up empty.

> tabs hidden if maildata.json is empty
> -
>
> Key: COMDEV-317
> URL: https://issues.apache.org/jira/browse/COMDEV-317
> Project: Community Development
>  Issue Type: Bug
>  Components: Reporter Tool
>Reporter: Sebb
>Priority: Minor
>
> See COMDEV-316
> The display tabs were hidden and there were other problems when the file 
> data/maildata.json was an empty JSON structure.
> The Javascript render.js should be able to handle this better.



--
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] [Commented] (COMDEV-295) Consider whether to extract mod_mbox statistics locally

[Andrew Musselman (Jira)]

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

Andrew Musselman commented on COMDEV-295:
-

[~sebb] Where would the "updating the mod_mbox indexes" happen, somewhere 
outside the `mailglomper2.py` script?

Is this still open, there is a filter `c = re.match(b"^From \S+ (.+)", line) # 
match as binary` in that script now.

> Consider whether to extract mod_mbox statistics locally
> ---
>
> Key: COMDEV-295
> URL: https://issues.apache.org/jira/browse/COMDEV-295
> Project: Community Development
>  Issue Type: Improvement
>  Components: Reporter Tool
>Reporter: Sebb
>Priority: Major
>
> At present the reporter tool uses the mailglomper script to extract 
> information about the number and timing of mails sent to each list.
> To do this, it has to download the entire mailbox, even though it only needs 
> the ^From_ lines.
> Whilst the code attempts to avoid unnecessary downloads (by checking dates 
> and sizes), for busy mbox files there can be a lot of network traffic.
> It might make sense for some initial data extraction to be done locally and 
> cached in a file.
> This could be done as part of updating the mod_mbox indexes.
> For example, the script could extract just the ^From_ lines into a separate 
> file and store that alongside the .mbox file. Mailglomper would read the much 
> abbreviated file instead.



--
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] [Commented] (COMDEV-317) tabs hidden if maildata.json is empty

[Andrew Musselman (Jira)]

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

Andrew Musselman commented on COMDEV-317:
-

If this only happened after a mail server problem in 2019 and has not been an 
ongoing issue can we close this?

> tabs hidden if maildata.json is empty
> -
>
> Key: COMDEV-317
> URL: https://issues.apache.org/jira/browse/COMDEV-317
> Project: Community Development
>  Issue Type: Bug
>  Components: Reporter Tool
>Reporter: Sebb
>Priority: Minor
>
> See COMDEV-316
> The display tabs were hidden and there were other problems when the file 
> data/maildata.json was an empty JSON structure.
> The Javascript render.js should be able to handle this better.



--
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] [Commented] (COMDEV-294) scandist.py: detect and report deprecated hash types

[Andrew Musselman (Jira)]

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

Andrew Musselman commented on COMDEV-294:
-

Is this still relevant? I remember infra doing a cleanup with projects a while 
back, maybe in 2020?

> scandist.py: detect and report deprecated hash types
> 
>
> Key: COMDEV-294
> URL: https://issues.apache.org/jira/browse/COMDEV-294
> Project: Community Development
>  Issue Type: New Feature
>  Components: Reporter Tool
>Reporter: Sebb
>Priority: Major
>
> scandist.py could be enhanced to detect deprecated hash types (.md5/.sha1) 
> and send an email to the committer linking to the policy.
> For the earliest warning, it should be done for dist/dev.
> However some projects may commit directly to dist/release, so it might be 
> necessary to  check dist/release as well.
> Generally, all the files for a release artifact are added as part of the same 
> commit, so it should be possible to detect where a project is providing 
> deprecated hashes in addition (e.g. for historic purposes). To avoid too many 
> messages, such commits could be ignored for the present.



--
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] [Commented] (COMDEV-293) scandist does not detect releases renamed from dist/dev

[Andrew Musselman (Jira)]

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

Andrew Musselman commented on COMDEV-293:
-

Is this still relevant, are there people needing it, etc.?

I see it's looking for this pattern `RELEASE_MATCH = r"^release/([^/]+)/" # 
match any name followed by /`. Not immediately clear why it's not catching the 
path in `A /release/spark/spark-2.2.2 (from /dev/spark/v2.2.2-rc2-bin:27901)`

> scandist does not detect releases renamed from dist/dev
> ---
>
> Key: COMDEV-293
> URL: https://issues.apache.org/jira/browse/COMDEV-293
> Project: Community Development
>  Issue Type: Bug
>  Components: Reporter Tool
>Reporter: Sebb
>Priority: Major
>
> The scandist script ignores commits which only affect a directory.
> This is OK for simple directory creation, but means that releases which are 
> created by renaming/copying from dist/dev are ignored.
> For example the following did not cause an email to be sent:
> $ svn log -r27902 -v https://dist.apache.org/repos/dist/
> 
> r27902 | tgraves | 2018-07-03 19:08:54 +0100 (Tue, 03 Jul 2018) | 2 lines
> Changed paths:
>D /dev/spark/v2.2.2-rc2-bin
>A /release/spark/spark-2.2.2 (from /dev/spark/v2.2.2-rc2-bin:27901)
> Publish spark 2.2.2
> 



--
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] [Commented] (COMDEV-429) The Committer-to-PMC ratio in Board Report Wizard may not give the best ratio

[Andrew Musselman (Jira)]

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

Andrew Musselman commented on COMDEV-429:
-

If it were me I would just show the raw numbers.

If there's additional commentary like [~sebb] mentions it could be noted as 
info on the page.

> The Committer-to-PMC ratio in Board Report Wizard may not give the best ratio
> -
>
> Key: COMDEV-429
> URL: https://issues.apache.org/jira/browse/COMDEV-429
> Project: Community Development
>  Issue Type: New Feature
>  Components: Reporter Tool
>Reporter: Tsz-wo Sze
>Priority: Minor
> Attachments: 20220705_COMDEV-429.patch
>
>
> Thanks a lot for providing the Board Report Wizard 
> ([https://reporter.apache.org/wizard/])! It is a great tool which helps save 
> a lot of time.
> I notice that the Committer-to-PMC ratio computed by the tool may not give 
> the best ratio. For example, in 
> [https://reporter.apache.org/wizard/statistics?ratis] ,
>  - There are currently 27 committers and 17 PMC members in this project.
>  - The Committer-to-PMC ratio is roughly 7:5.
> We have 27/17 = 1.588 and 7/5 = 1.4. A better ratio is 8/5 = 1.6.



--
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] [Commented] (COMDEV-291) Prefetch all data/JIRA/*.json files

[Andrew Musselman (Jira)]

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

Andrew Musselman commented on COMDEV-291:
-

Is `readjira.py` still used?

> Prefetch all data/JIRA/*.json files
> ---
>
> Key: COMDEV-291
> URL: https://issues.apache.org/jira/browse/COMDEV-291
> Project: Community Development
>  Issue Type: Improvement
>  Components: Reporter Tool
>Reporter: Sebb
>Priority: Major
>
> script/readjira.py keeps the data/JIRA/*.json files up to date as a cron job.
> However it does not create them initially.
> That is done by site/getjson.py which is called from the GUI.
> This can result in a long wait (possibly causing a timeout failure) if there 
> are many missing files for the currently logged in user.
> Also the code to create and parse the files is duplicated in the scripts.
> It might be better for all the files to be fetched in the readjira.py cron 
> job.



--
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] [Commented] (COMDEV-295) Consider whether to extract mod_mbox statistics locally

[Andrew Musselman (Jira)]

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

Andrew Musselman commented on COMDEV-295:
-

It's still referred to in the readme fwiw, maybe that needs more TLC

{{crontab -l -u www-data: (Not currently stored in puppet)
# m h   dom mon dow   command
00 4,12,20 * * * cd /var/www/reporter.apache.org/scripts && ./python3logger.sh 
parsepmcs.py
00 01 * * *  cd /var/www/reporter.apache.org/scripts && ./python3logger.sh 
mailglomper2.py
00 09 * * *  cd /var/www/reporter.apache.org/scripts && ./python3logger.sh 
readjira.py
10 00 * * *  cd /var/www/reporter.apache.org/scripts && ./python3logger.sh 
reportingcycles.py
20 00 * * *  cd /var/www/reporter.apache.org/scripts && ./python3logger.sh 
pmcdates.py
30 00 * * *  cd /var/www/reporter.apache.org/scripts && ./python3logger.sh 
bugzillastats.py
50 00 * * *  cd /var/www/reporter.apache.org/scripts && ./python3logger.sh 
health.py
32  * * * *  cd /var/www/reporter.apache.org/scripts && ./python3logger.sh 
readchecker.py
*/15 * * * * pgrep -f "gunicorn3.*wsgi:app" || (cd 
/var/www/reporter.apache.org/scripts && gunicorn3 -b 127.0.0.1 -w 6 -D wsgi:app 
&& echo "restarting gunicorn")}}

> Consider whether to extract mod_mbox statistics locally
> ---
>
> Key: COMDEV-295
> URL: https://issues.apache.org/jira/browse/COMDEV-295
> Project: Community Development
>  Issue Type: Improvement
>  Components: Reporter Tool
>Reporter: Sebb
>Priority: Major
>
> At present the reporter tool uses the mailglomper script to extract 
> information about the number and timing of mails sent to each list.
> To do this, it has to download the entire mailbox, even though it only needs 
> the ^From_ lines.
> Whilst the code attempts to avoid unnecessary downloads (by checking dates 
> and sizes), for busy mbox files there can be a lot of network traffic.
> It might make sense for some initial data extraction to be done locally and 
> cached in a file.
> This could be done as part of updating the mod_mbox indexes.
> For example, the script could extract just the ^From_ lines into a separate 
> file and store that alongside the .mbox file. Mailglomper would read the much 
> abbreviated file instead.



--
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] [Commented] (COMDEV-288) Request "Projects Directory" migration to GIT

[Andrew Musselman (Jira)]

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

Andrew Musselman commented on COMDEV-288:
-

I see a lot of activity in that thread in the archives; [~sebb] and [~hboutemy] 
is this still underway?

> Request "Projects Directory" migration to GIT
> -
>
> Key: COMDEV-288
> URL: https://issues.apache.org/jira/browse/COMDEV-288
> Project: Community Development
>  Issue Type: SVN->GIT Migration
>  Components: Projects Tool, Reporter Tool
>Reporter: Vincent Tuybens
>Priority: Trivial
>
> Dear all,
> is it possible for you to plan SVN to GIT migration for "Projects Directory" 
> project ?
> [{color:#0066cc}https://svn.apache.org/repos/asf/comdev/projects.apache.org/{color}]
> Thank you,
> Regards.



--
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] [Commented] (COMDEV-227) Only list last X releases and the add/remove release page

[Andrew Musselman (Jira)]

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

Andrew Musselman commented on COMDEV-227:
-

It is slow to load but I do see the page filling up; [~rombert] is this 
something you're actively looking for still?

> Only list last X releases and the add/remove release page
> -
>
> Key: COMDEV-227
> URL: https://issues.apache.org/jira/browse/COMDEV-227
> Project: Community Development
>  Issue Type: Improvement
>  Components: Reporter Tool
>Reporter: Robert Munteanu
>Priority: Major
>
> In the Apache Sling project we have a large number of releases as we have 
> many independent modules. When loading the 
> https://reporter.apache.org/addrelease.html?sling page, it takes upwards of 
> 10 seconds to load. It would be great if only the last X (50?) releases were 
> shown, and then a "load all" link would be available at the bottom.
> This would greatly speed up our usage of this tool.



--
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] [Commented] (COMDEV-295) Consider whether to extract mod_mbox statistics locally

[Andrew Musselman (Jira)]

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

Andrew Musselman commented on COMDEV-295:
-

Is that crontab running here still?

{{The site runs on the host projects-vm3.a.o at present (May 2021)}}

> Consider whether to extract mod_mbox statistics locally
> ---
>
> Key: COMDEV-295
> URL: https://issues.apache.org/jira/browse/COMDEV-295
> Project: Community Development
>  Issue Type: Improvement
>  Components: Reporter Tool
>Reporter: Sebb
>Priority: Major
>
> At present the reporter tool uses the mailglomper script to extract 
> information about the number and timing of mails sent to each list.
> To do this, it has to download the entire mailbox, even though it only needs 
> the ^From_ lines.
> Whilst the code attempts to avoid unnecessary downloads (by checking dates 
> and sizes), for busy mbox files there can be a lot of network traffic.
> It might make sense for some initial data extraction to be done locally and 
> cached in a file.
> This could be done as part of updating the mod_mbox indexes.
> For example, the script could extract just the ^From_ lines into a separate 
> file and store that alongside the .mbox file. Mailglomper would read the much 
> abbreviated file instead.



--
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] [Commented] (COMDEV-293) scandist does not detect releases renamed from dist/dev

[Andrew Musselman (Jira)]

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

Andrew Musselman commented on COMDEV-293:
-

[~sebb] I agree.

In `scandist.py` there is an example commit from pubsub that looks like this:
# e.g. {"committer": "sebb", "log": "Ensure we exit on control+C", 
"repository": "13f79535-47bb-0310-9956-ffa450edef68", "format": 1,
# "changed": {"comdev/reporter.apache.org/trunk/scandist.py": {"flags": "U  
"}},
# "date": "2015-07-13 13:38:33 + (Mon, 13 Jul 2015)", "type": "svn", 
"id": 1690668}

For the test case in the original description, what form would it take in the 
pubsub-generated commit?

The regex in `scandist.py` catches the release string as shown below:

{{#!/usr/bin/env python3
import re
path = "release/spark/spark-2.2.2"
RELEASE_MATCH = r"^release/([^/]+)/"
match = re.match(RELEASE_MATCH, path)
print(match[0])

$ ./test-release.py
release/spark/}}

> scandist does not detect releases renamed from dist/dev
> ---
>
> Key: COMDEV-293
> URL: https://issues.apache.org/jira/browse/COMDEV-293
> Project: Community Development
>  Issue Type: Bug
>  Components: Reporter Tool
>Reporter: Sebb
>Priority: Major
>
> The scandist script ignores commits which only affect a directory.
> This is OK for simple directory creation, but means that releases which are 
> created by renaming/copying from dist/dev are ignored.
> For example the following did not cause an email to be sent:
> $ svn log -r27902 -v https://dist.apache.org/repos/dist/
> 
> r27902 | tgraves | 2018-07-03 19:08:54 +0100 (Tue, 03 Jul 2018) | 2 lines
> Changed paths:
>D /dev/spark/v2.2.2-rc2-bin
>A /release/spark/spark-2.2.2 (from /dev/spark/v2.2.2-rc2-bin:27901)
> Publish spark 2.2.2
> 



--
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] [Commented] (COMDEV-216) Fixup styles so header/footer appear properly

[Andrew Musselman (Jira)]

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

Andrew Musselman commented on COMDEV-216:
-

[~curcuru] is this still relevant?

> Fixup styles so header/footer appear properly
> -
>
> Key: COMDEV-216
> URL: https://issues.apache.org/jira/browse/COMDEV-216
> Project: Community Development
>  Issue Type: Wish
>  Components: Reporter Tool
>Reporter: Shane Curcuru
>Priority: Minor
>
> I spent a while trying to get the footer text - which now points to the new 
> /about.html page, that explains where the source is - to appear, to no avail.
> - Why is the content div row-12?
> - Why don't we have three foundation.css rows in the page?  Header - which 
> would be just the static title, and a link to the About page; Contents - same 
> as now, but without the H2 element - and Footer - which includes license etc 
> and can get pushed off the page if contents needs to grow.



--
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] [Commented] (COMDEV-206) Add "Any prospects for new committers/pmc members?" line if no changes in last year

[Andrew Musselman (Jira)]

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

Andrew Musselman commented on COMDEV-206:
-

Not sure this is still relevant but there is already a warning if the last 
committer was added over two years ago, see these lines in the newer 
`site/js/render.js`:

{{ 471 if (ncn) {
 472 if (nc < after.getTime() / 1000) {
 473 addLine(pmc, " - Last committer addition was " + ncn + 
" at " + new Date(nc * 1000).toDateString())
 474 }
 475 changes.innerHTML += "→ " + "Last committer 
addition: " + new Date(nc * 1000).toDateString() + " (" + ncn + ")"
 476 } else {
 477 addLine(pmc, " - Last committer addition was more than 2 
years ago")
 478 changes.innerHTML += "→ " + "Last committer 
addition: more than two years ago (not in the 
archive!)"
 479 }
 480 changes.innerHTML += "→ " + "Currently " + 
json.count[pmc][1] + " committers and " + json.count[pmc][0] + " PMC members."
 481 addLine(pmc)}}

> Add "Any prospects for new committers/pmc members?" line if no changes in 
> last year
> ---
>
> Key: COMDEV-206
> URL: https://issues.apache.org/jira/browse/COMDEV-206
> Project: Community Development
>  Issue Type: Improvement
>  Components: Reporter Tool
>Reporter: Mike Kienenberger
>Priority: Minor
>
> I've likely seen more than a hundred "No new contributers in last year -- any 
> prospects?" board report comments posted in the last year.   Could we add a 
> prompt for this to the reporter template if no new contributors were detected 
> in the last year?
> I took a look at the reporter source and got to 
> /comdev/reporter.apache.org/trunk/site/render_proposed.js but I'm not much of 
> a python / javascript hacker.
> I'd recommend adding it to these sections:
> ## PMC changes: 
>
> ## Committer base changes: 
> and phrase it like:
> It has been a year since the last [ new committer | PMC member ] was added. 
> Any candidates on the horizon?



--
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] [Comment Edited] (COMDEV-206) Add "Any prospects for new committers/pmc members?" line if no changes in last year

[Andrew Musselman (Jira)]

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

Andrew Musselman edited comment on COMDEV-206 at 2/14/23 1:03 AM:
--

Not sure this is still relevant but there is already a warning if the last 
committer was added over two years ago, see these lines in the newer 
`site/js/render.js`:

 471 if (ncn) {
 472 if (nc < after.getTime() / 1000) {
 473 addLine(pmc, " - Last committer addition was " + ncn + 
" at " + new Date(nc * 1000).toDateString())
 474 }
 475 changes.innerHTML += "→ " + "Last committer 
addition: " + new Date(nc * 1000).toDateString() + " (" + ncn + ")"
 476 } else {
 477 addLine(pmc, " - Last committer addition was more than 2 
years ago")
 478 changes.innerHTML += "→ " + "Last committer 
addition: more than two years ago (not in the 
archive!)"
 479 }
 480 changes.innerHTML += "→ " + "Currently " + 
json.count[pmc][1] + " committers and " + json.count[pmc][0] + " PMC members."
 481 addLine(pmc)


was (Author: akm):
Not sure this is still relevant but there is already a warning if the last 
committer was added over two years ago, see these lines in the newer 
`site/js/render.js`:

{{ 471 if (ncn) {
 472 if (nc < after.getTime() / 1000) {
 473 addLine(pmc, " - Last committer addition was " + ncn + 
" at " + new Date(nc * 1000).toDateString())
 474 }
 475 changes.innerHTML += "→ " + "Last committer 
addition: " + new Date(nc * 1000).toDateString() + " (" + ncn + ")"
 476 } else {
 477 addLine(pmc, " - Last committer addition was more than 2 
years ago")
 478 changes.innerHTML += "→ " + "Last committer 
addition: more than two years ago (not in the 
archive!)"
 479 }
 480 changes.innerHTML += "→ " + "Currently " + 
json.count[pmc][1] + " committers and " + json.count[pmc][0] + " PMC members."
 481 addLine(pmc)}}

> Add "Any prospects for new committers/pmc members?" line if no changes in 
> last year
> ---
>
> Key: COMDEV-206
> URL: https://issues.apache.org/jira/browse/COMDEV-206
> Project: Community Development
>  Issue Type: Improvement
>  Components: Reporter Tool
>Reporter: Mike Kienenberger
>Priority: Minor
>
> I've likely seen more than a hundred "No new contributers in last year -- any 
> prospects?" board report comments posted in the last year.   Could we add a 
> prompt for this to the reporter template if no new contributors were detected 
> in the last year?
> I took a look at the reporter source and got to 
> /comdev/reporter.apache.org/trunk/site/render_proposed.js but I'm not much of 
> a python / javascript hacker.
> I'd recommend adding it to these sections:
> ## PMC changes: 
>
> ## Committer base changes: 
> and phrase it like:
> It has been a year since the last [ new committer | PMC member ] was added. 
> Any candidates on the horizon?



--
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] [Commented] (COMDEV-145) Duplicated data in generated json files

[Andrew Musselman (Jira)]

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

Andrew Musselman commented on COMDEV-145:
-

+1 close it

> Duplicated data in generated json files
> ---
>
> Key: COMDEV-145
> URL: https://issues.apache.org/jira/browse/COMDEV-145
> Project: Community Development
>  Issue Type: Improvement
>  Components: Reporter Tool
>Reporter: Sebb
>Priority: Major
>
> There is some duplication/overlap in the json data files.
> For example, chairs.json has full names of both chairs and committee.
> committees.json has full name of committee and availid of chair
> pmcs.json has similar info to committees.json.
> I would have thought one file would be sufficient here.
> people_name.json has availid and full name
> people.json has availid and full name plus other data
> They could surely be combined.
> releases.json and releases-files have some overlapping data



--
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] [Created] (COMDEV-486) Copyright in footer not updated

[Andrew Musselman (Jira)]

Andrew Musselman created COMDEV-486:
---

 Summary: Copyright in footer not updated
 Key: COMDEV-486
 URL: https://issues.apache.org/jira/browse/COMDEV-486
 Project: Community Development
  Issue Type: Improvement
Reporter: Andrew Musselman


In reporter.apache.org and other pages the copyright is 2020.

Either update to current year or pick up $current_year automatically.



--
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] [Updated] (COMDEV-486) Copyright in footer not updated

[Andrew Musselman (Jira)]

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

Andrew Musselman updated COMDEV-486:

Component/s: Website

> Copyright in footer not updated
> ---
>
> Key: COMDEV-486
> URL: https://issues.apache.org/jira/browse/COMDEV-486
> Project: Community Development
>  Issue Type: Improvement
>  Components: Website
>    Reporter: Andrew Musselman
>Priority: Minor
>
> In reporter.apache.org and other pages the copyright is 2020.
> Either update to current year or pick up $current_year automatically.



--
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] [Updated] (COMDEV-486) Copyright in footer not updated

[Andrew Musselman (Jira)]

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

Andrew Musselman updated COMDEV-486:

Component/s: Reporter Tool
 (was: Website)

> Copyright in footer not updated
> ---
>
> Key: COMDEV-486
> URL: https://issues.apache.org/jira/browse/COMDEV-486
> Project: Community Development
>  Issue Type: Improvement
>  Components: Reporter Tool
>    Reporter: Andrew Musselman
>Priority: Minor
>
> In reporter.apache.org and other pages the copyright is 2020.
> Either update to current year or pick up $current_year automatically.



--
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] [Created] (COMDEV-487) Stats outdated on Project Statistics page

[Andrew Musselman (Jira)]

Andrew Musselman created COMDEV-487:
---

 Summary: Stats outdated on Project Statistics page
 Key: COMDEV-487
 URL: https://issues.apache.org/jira/browse/COMDEV-487
 Project: Community Development
  Issue Type: Improvement
  Components: Reporter Tool
Reporter: Andrew Musselman


https://reporter.apache.org/wizard/statistics?mahout

Just seeing mismatches from what we see in mailing list archives and other 
tools. I am not sure if this is just a latency thing and if these will line up 
in a week or a month.

CHI is still "Action required" though on the chi.py page it's upgraded to 
"unhealthy," mail activity is lagging behind actual, etc.

Charts seem to have different figures than the text summaries as well.

I heard this was a known set of issues but did not see an open ticket about it.



--
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] [Updated] (COMDEV-486) Copyright in footer not updated

[Andrew Musselman (Jira)]

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

Andrew Musselman updated COMDEV-486:

Attachment: COMDEV-486.patch

> Copyright in footer not updated
> ---
>
> Key: COMDEV-486
> URL: https://issues.apache.org/jira/browse/COMDEV-486
> Project: Community Development
>  Issue Type: Improvement
>  Components: Reporter Tool
>    Reporter: Andrew Musselman
>Priority: Minor
> Attachments: COMDEV-486.patch
>
>
> In reporter.apache.org and other pages the copyright is 2020.
> Either update to current year or pick up $current_year automatically.



--
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] [Commented] (COMDEV-486) Copyright in footer not updated

[Andrew Musselman (Jira)]

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

Andrew Musselman commented on COMDEV-486:
-

Fixed in 1907662

Sendingsite/about.html
Sendingsite/addrelease.html
Sendingsite/wizard/index.html
Sendingsite/wizard/statistics.html

> Copyright in footer not updated
> ---
>
> Key: COMDEV-486
> URL: https://issues.apache.org/jira/browse/COMDEV-486
> Project: Community Development
>  Issue Type: Improvement
>  Components: Reporter Tool
>    Reporter: Andrew Musselman
>Priority: Minor
> Attachments: COMDEV-486.patch
>
>
> In reporter.apache.org and other pages the copyright is 2020.
> Either update to current year or pick up $current_year automatically.



--
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] [Resolved] (COMDEV-486) Copyright in footer not updated

[Andrew Musselman (Jira)]

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

Andrew Musselman resolved COMDEV-486.
-
Resolution: Fixed

> Copyright in footer not updated
> ---
>
> Key: COMDEV-486
> URL: https://issues.apache.org/jira/browse/COMDEV-486
> Project: Community Development
>  Issue Type: Improvement
>  Components: Reporter Tool
>    Reporter: Andrew Musselman
>Priority: Minor
> Attachments: COMDEV-486.patch
>
>
> In reporter.apache.org and other pages the copyright is 2020.
> Either update to current year or pick up $current_year automatically.



--
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] [Commented] (COMDEV-227) Only list last X releases and the add/remove release page

[Andrew Musselman (Jira)]

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

Andrew Musselman commented on COMDEV-227:
-

[~rombert] It would be easy to allow a new query param, e.g., 
https://reporter.apache.org/addrelease.html?sling&limit=50

How does that sound?

> Only list last X releases and the add/remove release page
> -
>
> Key: COMDEV-227
> URL: https://issues.apache.org/jira/browse/COMDEV-227
> Project: Community Development
>  Issue Type: Improvement
>  Components: Reporter Tool
>Reporter: Robert Munteanu
>Priority: Major
>
> In the Apache Sling project we have a large number of releases as we have 
> many independent modules. When loading the 
> https://reporter.apache.org/addrelease.html?sling page, it takes upwards of 
> 10 seconds to load. It would be great if only the last X (50?) releases were 
> shown, and then a "load all" link would be available at the bottom.
> This would greatly speed up our usage of this tool.



--
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] [Commented] (COMDEV-227) Only list last X releases and the add/remove release page

[Andrew Musselman (Jira)]

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

Andrew Musselman commented on COMDEV-227:
-

Attaching proposed patch

> Only list last X releases and the add/remove release page
> -
>
> Key: COMDEV-227
> URL: https://issues.apache.org/jira/browse/COMDEV-227
> Project: Community Development
>  Issue Type: Improvement
>  Components: Reporter Tool
>Reporter: Robert Munteanu
>Priority: Major
> Attachments: COMDEV-227.patch.txt
>
>
> In the Apache Sling project we have a large number of releases as we have 
> many independent modules. When loading the 
> https://reporter.apache.org/addrelease.html?sling page, it takes upwards of 
> 10 seconds to load. It would be great if only the last X (50?) releases were 
> shown, and then a "load all" link would be available at the bottom.
> This would greatly speed up our usage of this tool.



--
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] [Updated] (COMDEV-227) Only list last X releases and the add/remove release page

[Andrew Musselman (Jira)]

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

Andrew Musselman updated COMDEV-227:

Attachment: COMDEV-227.patch.txt

> Only list last X releases and the add/remove release page
> -
>
> Key: COMDEV-227
> URL: https://issues.apache.org/jira/browse/COMDEV-227
> Project: Community Development
>  Issue Type: Improvement
>  Components: Reporter Tool
>Reporter: Robert Munteanu
>Priority: Major
> Attachments: COMDEV-227.patch.txt
>
>
> In the Apache Sling project we have a large number of releases as we have 
> many independent modules. When loading the 
> https://reporter.apache.org/addrelease.html?sling page, it takes upwards of 
> 10 seconds to load. It would be great if only the last X (50?) releases were 
> shown, and then a "load all" link would be available at the bottom.
> This would greatly speed up our usage of this tool.



--
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] [Commented] (COMDEV-227) Only list last X releases and the add/remove release page

[Andrew Musselman (Jira)]

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

Andrew Musselman commented on COMDEV-227:
-

I suppose so; you have another thought?

The person viewing the page can set limit to whatever they want; my intent here 
was to provide a quick solution and not to solve for everything.

> Only list last X releases and the add/remove release page
> -
>
> Key: COMDEV-227
> URL: https://issues.apache.org/jira/browse/COMDEV-227
> Project: Community Development
>  Issue Type: Improvement
>  Components: Reporter Tool
>Reporter: Robert Munteanu
>Priority: Major
> Attachments: COMDEV-227.patch.txt
>
>
> In the Apache Sling project we have a large number of releases as we have 
> many independent modules. When loading the 
> https://reporter.apache.org/addrelease.html?sling page, it takes upwards of 
> 10 seconds to load. It would be great if only the last X (50?) releases were 
> shown, and then a "load all" link would be available at the bottom.
> This would greatly speed up our usage of this tool.



--
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] [Commented] (COMDEV-227) Only list last X releases and the add/remove release page

[Andrew Musselman (Jira)]

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

Andrew Musselman commented on COMDEV-227:
-

[~rombert] if you want these fixes instead could you submit a patch we can 
review? That's beyond what I have capacity for.

> Only list last X releases and the add/remove release page
> -
>
> Key: COMDEV-227
> URL: https://issues.apache.org/jira/browse/COMDEV-227
> Project: Community Development
>  Issue Type: Improvement
>  Components: Reporter Tool
>Reporter: Robert Munteanu
>Priority: Major
> Attachments: COMDEV-227.patch.txt
>
>
> In the Apache Sling project we have a large number of releases as we have 
> many independent modules. When loading the 
> https://reporter.apache.org/addrelease.html?sling page, it takes upwards of 
> 10 seconds to load. It would be great if only the last X (50?) releases were 
> shown, and then a "load all" link would be available at the bottom.
> This would greatly speed up our usage of this tool.



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