Re: Getting a project back on track

2024-03-29 Thread Michael Sokolov
I guess it depends on what the problem with the project is. It seems
implicit in your ideas that the project has lost momentum; nobody is
contributing to it or maintaining it actively? But I just want to
point out there can be other problems that might need correction with
different solutions (too much chaos, fighting, legal issues, poor
quality releases, etc)

On Fri, Mar 29, 2024 at 9:36 AM Rich Bowen  wrote:
>
> This week, I’ve been approached by someone concerned about one of our 
> projects, and looking for a “how to get back on track” document, with 
> concrete, actionable steps that a project can take when it is struggling to 
> find contributors. This seems like a great doc that we should write. What 
> comes to mind is:
>
> * Clearly tell the dev@ and user@ list that the project is at risk if they 
> don’t step up
> * Publish a list of open issues to the Dev list
> * Contact companies that you know rely on your outputs, and tell them that 
> the project is at risk
> * Clearly document the path/requirements for getting committer. Consider 
> lowering your wall a little
> * What else?
>
> Another question that I have is where to put this doc. I’m thinking it goes 
> in https://github.com/apache/comdev-site/tree/main/source/pmc somewhere, but 
> I’m not sure that to name it.
>
>
>
> —
> Rich Bowen
> rbo...@rcbowen.com
>
>
>
>

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



Re: [ALC] Request to establish ALC in Hangzhou, China

2023-12-04 Thread Michael Sokolov
Thanks for all the info; I hadn't followed these developments closely. It's
great to see all the communities forming.

On Mon, Dec 4, 2023 at 9:01 AM Willem Jiang  wrote:

> The Local ASF chapters allow us to meet the local Apache people in
> person. You can find more information here[1]
> This way, local open-source enthusiasts could get together by hosting
> events, publishing articles, making podcasts, etc. Sharing ASF's
> successful stories within the local community inspired more developers
> and talented college students to join open-source development.
> During the pandemic, we held online events to promote the Apache
> project and advocate the Apache Way and Open Source culture in China.
>
> [1]
> https://cwiki.apache.org/confluence/display/COMDEV/Apache+Local+Community+-+ALC
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Mon, Dec 4, 2023 at 9:10 PM Michael Sokolov  wrote:
> >
> > Hi I'm curious about the whole idea of local ASF chapters. It's not
> > something I'm familiar with. I guess the idea is a local presence of some
> > kind? Do any exist in the US? EU? Elsewhere? What do they do? Meetups, I
> > guess? Do they also maintain separate parallel online communities?
> >
> > On Mon, Dec 4, 2023, 2:43 AM Jun Liu  wrote:
> >
> > > Hi, there
> > > I am writing this mail to launch a discussion of starting an ALC
> chapter
> > > in Hangzhou, China. This idea came to my mind when I was in Beijing
> > > attending the Community Over Code Asia 2023 conference this September.
> I
> > > talked to a couple of ASF Members, PMCs, and Committers from different
> > > projects about this idea and got many positive feedbacks.
> > >
> > > Hangzhou is one of several cities in China with a considerable amount
> of
> > > developers, the headquarters of many world leading tech companies. And
> most
> > > importantly, many ASF projects and their main contributors or members
> are
> > > from Hangzhou. As far as I know, projects like Apache RocketMQ, Apache
> > > Dubbo were originally born in Hangzhou, Apache Flink and Apache Seata
> > > (incubating) have most of their active contributors in Hangzhou. An ALC
> > > chapter here would provide a platform for those ASF projects and active
> > > contributors to build and foster a community. A community can also
> help to
> > > incubating more projects since Hangzhou is never lack of innovations
> and
> > > great ideas.
> > >
> > > I read this new chapter guide[1] laterly and am confident Hangzhou can
> > > meet the basic requirements (also, I would like to help collect those
> > > active ASF members and active contributors in Hangzhou later if
> necessary).
> > > Would be happy to hear your comments on this idea, thanks.
> > >
> > > 1.
> > >
> https://cwiki.apache.org/confluence/display/COMDEV/Process+to+establish+an+ALC+Chapter
> > >
> > > Regards,
> > > Jun Liu, Apache Dubbo PMC Chair live in Hangzhou❤️
> > >
> > >
> > > -
> > > 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: [ALC] Request to establish ALC in Hangzhou, China

2023-12-04 Thread Michael Sokolov
Hi I'm curious about the whole idea of local ASF chapters. It's not
something I'm familiar with. I guess the idea is a local presence of some
kind? Do any exist in the US? EU? Elsewhere? What do they do? Meetups, I
guess? Do they also maintain separate parallel online communities?

On Mon, Dec 4, 2023, 2:43 AM Jun Liu  wrote:

> Hi, there
> I am writing this mail to launch a discussion of starting an ALC chapter
> in Hangzhou, China. This idea came to my mind when I was in Beijing
> attending the Community Over Code Asia 2023 conference this September. I
> talked to a couple of ASF Members, PMCs, and Committers from different
> projects about this idea and got many positive feedbacks.
>
> Hangzhou is one of several cities in China with a considerable amount of
> developers, the headquarters of many world leading tech companies. And most
> importantly, many ASF projects and their main contributors or members are
> from Hangzhou. As far as I know, projects like Apache RocketMQ, Apache
> Dubbo were originally born in Hangzhou, Apache Flink and Apache Seata
> (incubating) have most of their active contributors in Hangzhou. An ALC
> chapter here would provide a platform for those ASF projects and active
> contributors to build and foster a community. A community can also help to
> incubating more projects since Hangzhou is never lack of innovations and
> great ideas.
>
> I read this new chapter guide[1] laterly and am confident Hangzhou can
> meet the basic requirements (also, I would like to help collect those
> active ASF members and active contributors in Hangzhou later if necessary).
> Would be happy to hear your comments on this idea, thanks.
>
> 1.
> https://cwiki.apache.org/confluence/display/COMDEV/Process+to+establish+an+ALC+Chapter
>
> Regards,
> Jun Liu, Apache Dubbo PMC Chair live in Hangzhou❤️
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>


Re: RFC: many PMCs have not provided DOAPs

2023-09-06 Thread Michael Sokolov
hm, whatever it is that populates the data we get that helps to seed
board reports. Sorry, maybe that's reporter?

On Wed, Sep 6, 2023 at 9:13 AM sebb  wrote:
>
> On Wed, 6 Sept 2023 at 13:51, Michael Sokolov  wrote:
> >
> > Perhaps if we used the information in these files to drive creation of
> > the board report templates in whimsy, projects would have some
> > stronger incentive to keep them up to date? Or ... maybe we do that
> > already? I'm not sure though because for example we provide
> >
> > 
> >   
> >  > rdf:resource="https://git-wip-us.apache.org/repos/asf/lucene.git"/>
> >   
> > 
> >
> > Yet whimsy's reports on number of commits for the Lucene project
> > doesn't seem to be observing that repo, but rather some other ones.
>
> Whimsy does not report on commit counts.
> Perhaps you mean reporter?
>
> > On Tue, Sep 5, 2023 at 12:21 PM sebb  wrote:
> > >
> > > On Tue, 5 Sept 2023 at 16:28,  wrote:
> > > >
> > > > On Tue, 2023-09-05 at 17:11 +0200, Martijn Dashorst wrote:
> > > > > I think a lot of DOAP files may be out of date as well. At least for
> > > > > Wicket
> > > > > we have moved our site SCM from svn to git a long time ago, but
> > > > > didn't
> > > > > realise that project.a.o needed updating.
> > > > >
> > > > > Suffice to say, Wicket has had several (major and minor) releases
> > > > > since
> > > > > 2015-02-02...
> > > >
> > > > Hmm. Isn't that information available somewhere else, without having to
> > > > manually update a file?
> > > >
> > > > But, yeah, this is a great point. Thanks for mentioning it.
> > >
> > > The DOAP syntax allows for a lot of data that is better stored elsewhere.
> > >
> > > The bits that are unique to the DOAP are less likely to change, for 
> > > example:
> > > - pmc
> > > - short and long description
> > > - language(s)
> > > - category(ies)
> > > - homepage
> > > - standard(s) if any
> > >
> > > I think these are the most important from the point of view of showing
> > > the range of projects at the ASF and enabling people to find a project
> > > that suits their interests and skills.
> > >
> > > I doubt it will ever be possible to ensure that fields like releases
> > > are kept up to date.
> > > It should be possible to get an idea of releases from the distribution
> > > repo (though the file naming can make that a bit of a challenge!)
> > >
> > > Likewise the SVM and download URLs should be readily available from
> > > the homepage.
> > >
> > >
> > > > --Rich
> > > >
> > > > -
> > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > > For additional commands, e-mail: dev-h...@community.apache.org
> > > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > For additional commands, e-mail: dev-h...@community.apache.org
> > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
>
> -
> 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: RFC: many PMCs have not provided DOAPs

2023-09-06 Thread Michael Sokolov
Perhaps if we used the information in these files to drive creation of
the board report templates in whimsy, projects would have some
stronger incentive to keep them up to date? Or ... maybe we do that
already? I'm not sure though because for example we provide


  
https://git-wip-us.apache.org/repos/asf/lucene.git"/>
  


Yet whimsy's reports on number of commits for the Lucene project
doesn't seem to be observing that repo, but rather some other ones.

On Tue, Sep 5, 2023 at 12:21 PM sebb  wrote:
>
> On Tue, 5 Sept 2023 at 16:28,  wrote:
> >
> > On Tue, 2023-09-05 at 17:11 +0200, Martijn Dashorst wrote:
> > > I think a lot of DOAP files may be out of date as well. At least for
> > > Wicket
> > > we have moved our site SCM from svn to git a long time ago, but
> > > didn't
> > > realise that project.a.o needed updating.
> > >
> > > Suffice to say, Wicket has had several (major and minor) releases
> > > since
> > > 2015-02-02...
> >
> > Hmm. Isn't that information available somewhere else, without having to
> > manually update a file?
> >
> > But, yeah, this is a great point. Thanks for mentioning it.
>
> The DOAP syntax allows for a lot of data that is better stored elsewhere.
>
> The bits that are unique to the DOAP are less likely to change, for example:
> - pmc
> - short and long description
> - language(s)
> - category(ies)
> - homepage
> - standard(s) if any
>
> I think these are the most important from the point of view of showing
> the range of projects at the ASF and enabling people to find a project
> that suits their interests and skills.
>
> I doubt it will ever be possible to ensure that fields like releases
> are kept up to date.
> It should be possible to get an idea of releases from the distribution
> repo (though the file naming can make that a bit of a challenge!)
>
> Likewise the SVM and download URLs should be readily available from
> the homepage.
>
>
> > --Rich
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>

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



Re: Project Stickers for the ASF Booh at ApacheCon New Orleans

2022-09-12 Thread Michael Sokolov
Now I want to start a new project (just in time for halloween): "Apache Booh"

um -- would like some Lucene stickers please. There will be a bunch of us there

On Mon, Sep 12, 2022 at 7:57 AM Steve Lawrence  wrote:
>
> Please add Daffodil to the list. We'll be giving a talk at ApacheCon NA
> and will have multiple community members attending.
>
> Thanks!
> - Steve
>
> On 9/10/22 6:00 AM, sharanf wrote:
> > Hi All
> >
> > I am preparing the order for project stickers for ApacheCon New Orleans.
> > Traditionally the ASF booth is the place to come and get your projects
> > stickers, chat and have fun!.
> >
> > If you are going to be at ApacheCon and would like to have some of your
> > project stickers available at the ASF booth then please let me know by
> > responding to this thread.
> >
> > I have been through the ApacheCon schedule and created a list of all the
> > projects that have talks at the event on the ComDev Wiki
> > https://s.apache.org/z0es8. so will be ordering stickers for all those
> > on the list. If your project is not on the list and you would like to
> > have some stickers - then please respond to this thread with the project
> > name and I will add it.
> >
> > Please note this also includes getting stickers for  incubating projects
> > :-)
> >
> > I'll be putting the order on 14th September to make sure it can be
> > delivered in time.
> >
> > Looking forward to seeing you in New Orleans with a booth packed with
> > project stickers!
> >
> > Thanks
> > Sharan
> >
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>

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



Re: Java 17 Compatibility

2022-07-28 Thread Michael Sokolov
Have you tried contacting the individual projects via their mailing lists?
Apache projects run themselves with only minimal oversight from Apache
foundation, and we don't maintain any kind of centralized compatibility
matrix. However the projects you mention can probably help you find out
what you need to know.

On Wed, Jul 27, 2022, 10:43 AM Shivaraj Sivasankaran
 wrote:

> Gentle reminder on the below query.
>
> From: Shivaraj Sivasankaran
> Sent: Tuesday, March 29, 2022 11:54 AM
> To: dev@community.apache.org
> Cc: M Vasanthakumar 
> Subject: Java 17 Compatibility
>
> Hi,
>
> Am Shivaraj from Ericsson India Global Private Limited, we have our own
> software to meet the business need and we use below open source library to
> achieve certain functionalities. Since we have a plan to upgrade existing
> java runtime environment to Java 17 we need to know the compatibility of
> the below component that can run on top of Java 17. Please let us know the
> plan/roadmap of upgrading to java 17, it would be helpful if you are giving
> matrix with table for components and their supported java version
> (including java 17).
>
>
> Vendor
> Software Name
> Version
> Apache
> Parquet Avro
> 1.12.2
> Apache
> Avro
> 1.11.0
> Apache
> Parquet Hadoop Bundle
> 1.12.2
>
>
>
> Regards,
> Shivaraj Sivasankaran.
>


Re: [GSoC Mentors] Re: Org admin from Russia

2022-04-08 Thread Michael Sokolov
It's terrible when events such as this divide us. I'm sure there are
reasons for needing to take this step, but it saddens me. OK not as
much as the terrible things happening in the real world, but still
sad.

On Wed, Apr 6, 2022 at 9:43 PM Maxim Solodovnik  wrote:
>
> Hello All,
>
> Due to recent changes in GSoC rules (see the emails below) I step down as
> Org Admin for ASF
> I will continue to help on ASF side but will be unable to send invitations
> and act as ASF org admin
>
> please contact this list in case of any questions and @Sanyam Goel
>  and @Swapnil M Mane 
>
> I guess I will not receive any email notifications so please ping me in
> case of any URGENT steps need to be done :)
>
> On Thu, 7 Apr 2022 at 00:40, 'sttaylor' via Google Summer of Code Mentors
> List  wrote:
>
> > Hi Maxim,
> >
> > Good question.
> >
> > As mentioned in the FAQ (and on this list last week):
> > *Due to current circumstances, GSoC 2022 is not accepting participants
> > (Contributors, Mentors or Organization Administrators) from Russia,
> > Belarus, or the so-called Donetsk People's Republic ("DNR") and Luhansk
> > People's Republic ("LNR"). There are no restrictions on participants
> > located within Ukraine but outside of the DNR and LNR.*
> >
> > Any Org Admins or Mentors that are in Russia, Belarus, DNR or LNR will
> > need to withdraw themselves from the GSoC 2022 program. There is a
> > 'Withdraw from Program' red link in your User Profile (toward the bottom of
> > the page). That will just withdraw you from this GSoC 2022 program and in
> > the future you will be able to use the same profile to register for a given
> > program when the situation allows.
> >
> > Best,
> > Stephanie
> >
> >
> > On Wednesday, April 6, 2022 at 10:22:33 AM UTC-7 solom...@gmail.com wrote:
> >
> >> Hello Stephanie,
> >>
> >> Recently I read from news, and read in FAQ [1]
> >>
> >> "GSoC 2022 is not accepting participants (Contributors, Mentors or
> >> Organization Administrators) from Russia"
> >>
> >> Shall I step down from org admin position?
> >>
> >> ps sorry it seems I've miss the announcement :(
> >>
> >> [1]
> >> https://developers.google.com/open-source/gsoc/faq#are_participants_from_ukraine_russia_or_belarus_allowed_to_participate_in_gsoc_2022
> >>
> >> from mobile (sorry for typos ;)
> >>
> >>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Google Summer of Code Mentors List" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to google-summer-of-code-mentors-list+unsubscr...@googlegroups.com.
> > To view this discussion on the web visit
> > https://groups.google.com/d/msgid/google-summer-of-code-mentors-list/2bd96946-6b18-4da7-a1b4-d14d50c49f0an%40googlegroups.com
> > 
> > .
> >
>
>
> --
> Best regards,
> Maxim

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



Re: SPDX identifiers in Apache projects kinetics what up))/))09

2022-03-19 Thread Michael Sokolov
Lillopplllopoplllpolplkllklppo lol lllopoo

On Sat, Mar 19, 2022, 5:04 AM tison  wrote:

> Hi,
>
> Recently I notice the SPDX identifiers format defined by the Linux
> Foundation for machine
> processing of license information based on the SPDX License Identifiers
> that are here available:
> http://spdx.org/licenses/.
>
> I can see that all of Apache project use it's own License header
> template[1] and curious what's
> the suggestions on using SPDX identifiers in Apache projects. Can an Apache
> project adopts both
> conventions? Is it encouraged or acceptable a general project using Apache
> License using the
> SPDX identifiers as license header?
>
> Best,
> tison.
>
> [1]
>
> https://github.com/apache/skywalking-eyes/blob/eb0e0b091ea41213f712f622797e37526ca1e5d6/assets/header-templates/Apache-2.0-ASF.txt
>


Re: Thoughts on alternative communication channels for our communities

2022-02-25 Thread Michael Sokolov
Just my personal perspective as an aging white man, but if substantial
portion of project discussions moved to an ephemeral communications
channel, it would be on the one hand freeing since I wouldn't feel the
obligation to wade through the tons of email when I catch up every few
days, but on the other hand sad, because I would probably just not read the
messages, and become ever more disconnected. Perhaps that's natural. Times
change. C'est la vie

Or maybe I just don't understand how it would work on the Apache Twitter
channels of the future, but that's my concern.

On Tue, Feb 22, 2022, 10:32 AM Roman Shaposhnik 
wrote:

> On Mon, Feb 21, 2022 at 10:19 AM Zhiyuan Ju  wrote:
>
> > Hi,
> >
> > I involved in the Apache APISIX Community since 2019, and I would prefer
> to
> > keep using the mailing list than other ways.  There have been
> > some challenges like not a friendly way to discuss codes, not every
> > volunteer or contributor watching the mailing list, and so on, but there
> > also have advantages:
> >
> > 1. It's public, archived, and searchable. When the APISIX project is was
> > not donated to the ASF, maintainers search historical mails from other
> ASF
> > projects and follow the guidelines, without much help to ask "How to do
> > this?" again and again.
> > 2. We could use Slack to discuss things of course, but if the community
> is
> > very active and there will have lots of unread messages, it's indeed a
> > challenge for me personally.
> > 3. I agree that many projects tend to use other tools to discuss than a
> > mailing list, like Slack and Discord, they're ok because our goal is to
> > keep things transparent and clear (personally think), also the project
> > community is active and healthy.
> > 4. As for "If it did not happen on the ML, then it did not happen.", it's
> > our foundation's community culture, it doesn't conflict with other tools.
> > No matter which tool we use, don't forget what's our goal :)
> >
>
> Thanks for all the feedback so far. If I were to summarize what's been
> expressed
> on this thread so far, it seems that we're all agreeing that:
>1. Even if mailing lists appear to be clunky in 2022 they are still
> appreciated
> as THE channel for any kind of "official" ASF business to be conducted
> (e.g. major decision points, voting, etc.). In that sense -- whatever
> other
> channels may have been used to build consensus -- the final (or
> official
> if you will) closure is expected to happen on a mailing list.
>
> 2. There are TONS of alternative communication channels for developers
> and users to explore and it is unlikely that we will have any semblance
> of convergence there -- these are too fragmented by geographical,
> cultural,
> language and other preferences.
>
> Now, if I were to make an observation, I'd split our constituency in 3 of
> the
> usual concentric circles: PMC, Developers/Committers, Users.
>
> It sounds like making sure that all official PMC business to be conducted
> on the
> mailing list is not only desirable from the ASF's perspective but also
> [mostly]
> appreciated by the PMCs themselves. That leaves Developers/Committers and
> Users.
>
> My biggest problem is actually with users -- it seems that having all these
> extra
> communication channels makes it more difficult for newcomers to find good
> entry points re: engaging with the projects -- or maybe not. That's still
> not clear
> to me and I would love to hear more feedback.
>
> What do ppl think?
>
> Thanks,
> Roman.
>


[jira] [Comment Edited] (COMDEV-425) Reporter tool's "Busiest GitHub topics" is missing "lucene" for Lucene project

2021-10-18 Thread Michael Sokolov (Jira)


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

Michael Sokolov edited comment on COMDEV-425 at 10/19/21, 1:44 AM:
---

Hi Sharan - we use [https://issues.apache.org/jira/,] same as this issue, with 
project = Lucene


was (Author: sokolov):
Hi Shaan - we use [https://issues.apache.org/jira/,] same as this issue, with 
project = Lucene

> 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, 
> 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.3.4#803005)

-
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

2021-10-18 Thread Michael Sokolov (Jira)


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

Michael Sokolov commented on COMDEV-425:


Hi Shaan - we use [https://issues.apache.org/jira/,] same as this issue, with 
project = Lucene

> 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, 
> 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.3.4#803005)

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



Re: Conscious Language Checker Tool Being Developed

2021-09-17 Thread Michael Sokolov
got it, thanks

On Fri, Sep 17, 2021 at 8:33 AM Sharan Foga  wrote:
>
> Hi Mike
>
> Thanks for taking a look.
>
> The tool is an initiative that has come out of the D effort so if you ask 
> over at d...@diversity.apache.org they should be able to help you.
>
> Thanks
> Sharan
>
> > Hi Sharan, just getting back from some time away from it all and
> > catching up on my emails. I clicked around and tried to add
> > https://github.com/apache/lucene.git as a scan target for this tool,
> > but don't have permissions. Are you accepting new repos for scanning
> > now? Would you do that? Or are you adding people to the permissions
> > group that can do it?
> >
> > Thanks for working on this, it looks helpful
> >
> > Mike
> >
> > On Thu, Sep 9, 2021 at 2:38 PM Sharan Foga  wrote:
> > >
> > > Hi All
> > >
> > > I'm posting this here as it is sort of related to my thread around tools 
> > > that could help with language.
> > >
> > > A new tool is currently being developed under our  D project that is 
> > > called the Conscious Language Checker that can scan Apache projects 
> > > repos, code and highlight potential words that could be potentially 
> > > inappropriate or may cause offence. Like any ASF project the tool is 
> > > under development and the first version of it is getting a range of 
> > > feedback.
> > >
> > > If you want to learn a bit more about the tool, help to develop it or 
> > > simply want to join the conversation - the discussion is happening over 
> > > the d...@diversity.apache.org and here is a link to the discussion thread 
> > > https://s.apache.org/r57ba
> > >
> > > If you are interested in taking a look at the tool dashboard - here is 
> > > the link: https://clc.diversity.apache.org/
> > >
> > > My understanding is that projects can opt in if they want their results 
> > > to be included so please feel free to join the conversation.
> > >
> > > Thanks
> > > Sharan
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > For additional commands, e-mail: dev-h...@community.apache.org
> > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>

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



Re: Conscious Language Checker Tool Being Developed

2021-09-17 Thread Michael Sokolov
Hi Sharan, just getting back from some time away from it all and
catching up on my emails. I clicked around and tried to add
https://github.com/apache/lucene.git as a scan target for this tool,
but don't have permissions. Are you accepting new repos for scanning
now? Would you do that? Or are you adding people to the permissions
group that can do it?

Thanks for working on this, it looks helpful

Mike

On Thu, Sep 9, 2021 at 2:38 PM Sharan Foga  wrote:
>
> Hi All
>
> I'm posting this here as it is sort of related to my thread around tools that 
> could help with language.
>
> A new tool is currently being developed under our  D project that is called 
> the Conscious Language Checker that can scan Apache projects repos, code and 
> highlight potential words that could be potentially inappropriate or may 
> cause offence. Like any ASF project the tool is under development and the 
> first version of it is getting a range of feedback.
>
> If you want to learn a bit more about the tool, help to develop it or simply 
> want to join the conversation - the discussion is happening over the 
> d...@diversity.apache.org and here is a link to the discussion thread 
> https://s.apache.org/r57ba
>
> If you are interested in taking a look at the tool dashboard - here is the 
> link: https://clc.diversity.apache.org/
>
> My understanding is that projects can opt in if they want their results to be 
> included so please feel free to join the conversation.
>
> Thanks
> Sharan
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>

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



Re: [Register] Allyship workshop for open source communities

2021-08-22 Thread Michael Sokolov
Thanks for the invitation. I'm interested, but will be unavailable on
that day. Please do let us know if another opportunity comes around

-Mike

On Fri, Aug 20, 2021 at 1:03 PM Aizhamal Nurmamat kyzy
 wrote:
>
> Hi everyone,
>
> I am helping to organize an allyship training for open source contributors
> sponsored by Google's OSPO. Few folks have expressed interest in this
> workshop, so I am extending the invite to all of you.
>
> Workshop date: Thursday, September 16th, 2021 at 8:30am PST or 5:30 PM
> CEST.
> Please register by filling out the form linked below[1]
>
> Here are more details:
>
> The training led by Dr. Kim Tran (https://www.kimtranphd.com/) aims to
> position people of color and those in solidarity with us to develop the
> necessary skills to build bridges across race, ability, gender, sexuality
> and class.
>
> Participants will leave:
> - With the capacity to identify marginalization in real time in the open
> source community
> - Knowing how to address and respond to marginalization at individual and
> systemic levels
> - With a strong, critical understanding of the allyship framework
> - Intersectional lenses, examining dynamics around gender, class, ability
> and race
> - A toolkit for recognizing and combating marginalization in real time
>
> Format:
> - Large groups will engage in a *90 minute*, remote learning session.
> - Participants will be capped at 45 to enable engaging interactive
> participation and responsiveness to participant questions and concerns.
> - Session will include webinar style portion as well as breakouts for
> hypothetical scenarios.
>
>
> [1]
> https://docs.google.com/forms/d/1DM7KNyd7QQKiCRrepQTIDAChvtC6QERCt1JUNO5R3Fc/edit

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