I wanted us to consider naming our group Apache Solr, especially since the other "Apache Solr" group was recently deleted. However, given the number of existing private groups with that exact name, "Solr" seems most appropriate.
However, my question is: Will using "Solr" provide sufficient familiarity and reference to ensure we are clearly identified as Apache Solr, rather than being mistaken for a stylized version of "Solar" by the general public? Sincerely, *Arup Chauhan* LinkedIn <https://www.linkedin.com/in/arupchauhan> | Website <https://arup-chauhan.github.io/> | GitHub <https://github.com/Arup-Chauhan> On Mon, Aug 24, 2026 at 9:00 AM David Smiley <[email protected]> wrote: > Following up: The "Solr" LinkedIn Group should be the only group. I > convinced the "Apache Solr" group owner to delete that group. > > On Sat, Feb 1, 2025 at 8:10 AM Nazerke S <[email protected]> wrote: > > > So, the "Solr" (https://www.linkedin.com/groups/1557747/) is a public > > group > > now. I did some purging by removing job postings and unrelated topics. > > > > On Fri, Jan 24, 2025 at 10:22 PM David Smiley <[email protected]> > wrote: > > > > > Nobody on the PMC expressed an appetite for having a formal > relationship > > > with a LinkedIn group. That's good because it basically reduces > > > barriers/concerns. > > > > > > I suggest that we embrace the group with the highest number of members: > > > https://www.linkedin.com/groups/1557747/ named "Solr" currently at > 5815 > > > members. BTW we can reasonably expect that number to drop a lot as > > members > > > who joined forever ago that aren't using Solr today are likely to > > leave. I > > > posted the Solr 9.8 release announcement there yesterday. Jan inquired > > > there about making the group public (which I definitely think we should > > > do). Nazerke, I'll try and add you as an admin; thank you for your > > > initiative here! > > > > > > ~ David > > > > > > On Fri, Jan 17, 2025 at 2:10 PM David Smiley <[email protected]> > wrote: > > > > > > > Shane Curcuru shared the following advice, > > > > > > > > This is partly a branding question (in terms of what name to use, > > > >> especially if there is any perceived direct relationship between the > > > >> social media group and the PMC. Some guidelines to review to help > you > > > >> decide are: > > > >> > > > >> https://apache.org/foundation/marks/socialmedia > > > >> > > > >> > > > >> > > > > > > https://cwiki.apache.org/confluence/display/PRESS/Publicity+Guidelines+for+Top-Level+Projects#PublicityGuidelinesforTopLevelProjects-socialguidelines > > > >> > > > >> Also, has the PMC discussed this and have a rough consensus (or at > > least > > > >> enough discussion to show there's no objections)? There certainly > are > > > >> plenty of affinity groups named after our projects on LinkedIn and > > > >> similar places. The great majority are fine, because readers > > understand > > > >> they're affinity groups, not official project areas. > > > >> > > > >> The real issues to watch out for are: > > > >> - Making sure that groups like this note in their descriptions they > > are > > > >> not official parts of the project or PMC. > > > >> - Keeping the discussion focused on the project and technology, and > > not > > > >> letting it become merely a place for vendor ads or other brand > > > >> infringement. > > > >> > > > > > > > > I'll reach out internally in our PMC to see if we need an official > > > project > > > > relationship or whether an "affinity group" would be fine. > > > > So far it appears both LinkedIn Group owners are willing to share > > > > ownership :-D > > > > > > > > On Fri, Jan 17, 2025 at 9:12 AM David Smiley <[email protected]> > > wrote: > > > > > > > >> I sent a question to Apache ComDev last night. I'll forward their > > > >> response. > > > >> > > > >> On Fri, Jan 17, 2025 at 6:46 AM Nazerke S <[email protected]> > > > wrote: > > > >> > > > >>> Surprised about this existing "Solr" group and didn't know its > > > existence. > > > >>> https://www.linkedin.com/groups/1557747/. > > > >>> > > > >>> Also found this group https://www.linkedin.com/groups/10319666/ > > named > > > >>> "Apache Solr". The owner of this group agreed to give/have control > > over > > > >>> the > > > >>> group. > > > >>> > > > >>> Agree, the first "Solr" group seems appealing to get started with, > > > simply > > > >>> with more followers. > > > >>> > > > >>> On Fri, Jan 17, 2025 at 4:11 PM Alessandro Benedetti < > > > >>> [email protected]> > > > >>> wrote: > > > >>> > > > >>> > +1 to contact the administrator and use the 6k user base to > > resurrect > > > >>> the > > > >>> > group and get more traction. > > > >>> > > > > >>> > Cheers > > > >>> > -------------------------- > > > >>> > *Alessandro Benedetti* > > > >>> > Director @ Sease Ltd. > > > >>> > *Apache Lucene/Solr Committer* > > > >>> > *Apache Solr PMC Member* > > > >>> > > > > >>> > e-mail: [email protected] > > > >>> > > > > >>> > > > > >>> > *Sease* - Information Retrieval Applied > > > >>> > Consulting | Training | Open Source > > > >>> > > > > >>> > Website: Sease.io <http://sease.io/> > > > >>> > LinkedIn <https://linkedin.com/company/sease-ltd> | Twitter > > > >>> > <https://twitter.com/seaseltd> | Youtube > > > >>> > <https://www.youtube.com/channel/UCDx86ZKLYNpI3gzMercM7BQ> | > > Github > > > >>> > <https://github.com/seaseltd> > > > >>> > > > > >>> > > > > >>> > On Thu, 16 Jan 2025 at 22:50, Jan Høydahl <[email protected] > > > > > >>> wrote: > > > >>> > > > > >>> > > Guess some PMC members could reach out and ask to be added as > > > admins > > > >>> of > > > >>> > > the group. Then advocate for crafting some group rules and make > > it > > > >>> more > > > >>> > > about Solr again. Perhaps convert til to a public group for > more > > > >>> > visibility? > > > >>> > > > > > >>> > > Jan Høydahl > > > >>> > > > > > >>> > > > 16. jan. 2025 kl. 19:34 skrev Alessandro Benedetti < > > > >>> > [email protected] > > > >>> > > >: > > > >>> > > > > > > >>> > > > There is a Solr group on Linkedin actually: > > > >>> > > > https://www.linkedin.com/groups/1557747/ > > > >>> > > > > > > >>> > > > it's administered by someone I don't know and who's not > > involved > > > >>> as a > > > >>> > > > committer or PMC in any way (as far as I know): Patrick > > Plaatje ( > > > >>> > > > https://www.linkedin.com/in/patrickplaatje/). > > > >>> > > > > > > >>> > > > Its main contributor is a gentleman who has polluted the > group > > > with > > > >>> > posts > > > >>> > > > that have hardly any relationship with Solr at all. > > > >>> > > > You can find probably a handful of posts vaguely related to > > Solr > > > >>> in the > > > >>> > > > last year or so. > > > >>> > > > > > > >>> > > > I thought I posted there occasionally, but couldn't find any > of > > > my > > > >>> > posts > > > >>> > > in > > > >>> > > > the last couple of years so I may be wrong. > > > >>> > > > > > > >>> > > > The group seems decently dead to me, not sure if recoverable, > > > maybe > > > >>> > it's > > > >>> > > > worth starting afresh? > > > >>> > > > It has a good follower base though (roughly 6k). > > > >>> > > > > > > >>> > > > Cheers > > > >>> > > > > > > >>> > > > > > > >>> > > > -------------------------- > > > >>> > > > *Alessandro Benedetti* > > > >>> > > > Director @ Sease Ltd. > > > >>> > > > *Apache Lucene/Solr Committer* > > > >>> > > > *Apache Solr PMC Member* > > > >>> > > > > > > >>> > > > e-mail: [email protected] > > > >>> > > > > > > >>> > > > > > > >>> > > > *Sease* - Information Retrieval Applied > > > >>> > > > Consulting | Training | Open Source > > > >>> > > > > > > >>> > > > Website: Sease.io <http://sease.io/> > > > >>> > > > LinkedIn <https://linkedin.com/company/sease-ltd> | Twitter > > > >>> > > > <https://twitter.com/seaseltd> | Youtube > > > >>> > > > <https://www.youtube.com/channel/UCDx86ZKLYNpI3gzMercM7BQ> | > > > >>> Github > > > >>> > > > <https://github.com/seaseltd> > > > >>> > > > > > >>> > > > > > --------------------------------------------------------------------- > > > >>> > > To unsubscribe, e-mail: [email protected] > > > >>> > > For additional commands, e-mail: [email protected] > > > >>> > > > > > >>> > > > > > >>> > > > > >>> > > > >> > > > > > >
